Unable to successfully restart NextcloudPi image after shutdown and powering back up after two weeks offline. Image restarts but with a MariaDB error (see log below). Also the NextcloudPi System Info page indicates that the MariaDB, Redis, Postfix services are down.
I’m able to access the NextcloudPi UI but not able to access Nextcloud.
The output of the NextcloudPi container log:
Starting PHP-fpm, Starting Apache, Starting mariaDB, 2020-03-06 20:11:50 0 [Note] mysqld (mysqld 10.3.15-MariaDB-1) starting as process 92 ..., /etc/services-enabled.d/010lamp: line 38: 92 Aborted mysqld,
Nextcloudpi image: ownyourbits/nextcloudpi:latest
Operating system and version: FreeNAS-11.2-U7 VM Docker Host (Docker version: 18.03.1-ce)
Nextcloudpi Sytem Info:
NextCloudPi version v1.15.2 NextCloudPi image NextCloudPi_docker_07-20-19 distribution Debian GNU/Linux 10 \n \l automount no USB devices none datadir (doesn't exist) rootfs usage 13G/19G swapfile none dbdir /data/database Nextcloud check ok Nextcloud version 184.108.40.206 HTTPD service up PHP service up MariaDB service down Redis service down Postfix service down internet check ok port check 80 closed port check 443 closed IP 172.17.0.5 gateway 172.17.0.1 interface eth0 certificates none NAT loopback no uptime 3days
Another post with a Redis service down issue suggestes this may be a log file permission issue, so I tried the nc-fix-permissions tab, but received the response below. I have basic unix skills and not sure how to configure this tool.
[ nc-fix-permissions ] There are no commands defined in the "config:system" namespace. data directory not found
If this is worth pursuing, can you layout how to fix the permission please.
I also checked that the dbdir exists, which it does.
Any suggestions on how to continue troubleshooting the cause of this issue?
Thanks in advance.