Nextcloud no longer reachable Topic is solved

[cdlenfert]

I cleared force recovery line and restarted the mariadb service again. Still no output to the mysql log. I then found a Stack Exchange thread about trying to clear the innodb log files so I made a backup and did that.

Code: Select all

root@DietPi:~# rm /var/lib/mysql/ib_logfile0
root@DietPi:~# rm /var/lib/mysql/ib_logfile1

Then I tried restarting the mariadb service again and this time it started. That was exciting, but I still couldn't reach Nextcloud. I tried restarting the Pi and that didn't bring Nextcloud back, but Mariadb was running fine after the reboot.

Here is the status of the Mariadb service:

Code: Select all

root@DietPi:~# systemctl status mariadb
● mariadb.service - MariaDB 10.1.38 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; disabled; vendor preset:
 enabled)
   Active: active (running) since Tue 2020-01-21 13:18:52 MST; 3s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 2079 ExecStartPost=/bin/sh -c systemctl unset-environment _WSREP_STAR
T_POSITION (code=exited, status=0/SUCCESS)
  Process: 2077 ExecStartPost=/etc/mysql/debian-start (code=exited, status=0/SUC
CESS)
  Process: 2023 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR
= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environme
nt _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 2018 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START
_POSITION (code=exited, status=0/SUCCESS)
  Process: 2015 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/ru
n/mysqld (code=exited, status=0/SUCCESS)
 Main PID: 2048 (mysqld)
   Status: "Taking your SQL requests now..."
    Tasks: 26 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─2048 /usr/sbin/mysqld

Jan 21 13:18:51 DietPi mysqld[2048]: InnoDB: for more information.
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] InnoD
B: 128 rollback segment(s) are active.
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] InnoD
B: Waiting for purge to start
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] InnoD
B:  Percona XtraDB (http://www.percona.com) 5.6.42-84.2 started; log sequence nu
mber 1070602161
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1283453760 [Note] InnoD
B: Dumping buffer pool(s) not yet started
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] Plugi
n 'FEEDBACK' is disabled.
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] Serve
r socket created on IP: '::'.
Jan 21 13:18:51 DietPi mysqld[2048]: 2020-01-21 13:18:51 1995968304 [Note] /usr/
sbin/mysqld: ready for connections.
Jan 21 13:18:51 DietPi mysqld[2048]: Version: '10.1.38-MariaDB-0+deb9u1'  socket
: '/var/run/mysqld/mysqld.sock'  port: 3306  Raspbian 9.0
Jan 21 13:18:52 DietPi systemd[1]: Started MariaDB 10.1.38 database server.

Still nothing in the logs (/var/log/mysql/error.log)

[Joulinar]

what happen if you run

Code: Select all

ncc maintenance:mode --off

[cdlenfert]

Thanks for your assistance. It's greatly appreciated!

The command told me Maintenance mode was already off.

Code: Select all

root@DietPi:~# ncc maintenance:mode --off
Maintenance mode already disabled

I belive restoring the mariadb service did solve the issue however and I was unfortunately looking at the wrong URL to get to the server. Forgot the /nextcloud directory

Nextcloud appears to be working once again!! Thank you!

[Joulinar]

Ok no problem. I marked the issue as solved now.