Nextcloud AIO v8.0.0
Ubuntu 22.04
This is weird.
I let a laptop sync over night. This morning it was done - all looking good. I reboot my nextcloud server this morning and it would not start.
Nextcloud container stuck in Starting mode.
I checked the logs
ncadmin@nextcloud:/mnt$ sudo docker logs nextcloud-aio-nextcloud
[sudo] password for ncadmin:
Connection to nextcloud-aio-database (172.18.0.4) 5432 port [tcp/postgresql] succeeded!
now
2024-03-23 13:24:33.268298-07
(1 row)
- ‘[’ -f /dev-dri-group-was-added ‘]’
++ find /dev -maxdepth 1 -mindepth 1 -name dri - ‘[’ -n ‘’ ‘]’
- set +x
Enabling Imagick…
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.19/main: No such file or directory
WARNING: opening from cache https://dl-cdn.alpinelinux.org/alpine/v3.19/community: No such file or directory
Configuring Redis as session handler…
The www-data user doesn’t seem to have access rights in the datadir.
Most likely are the files located on a drive that does not follow linux permissions.
Please adjust the permissions like mentioned below.
The found permissions are:
33:0 750
(userID:groupID permissions)
but they should be:
33:0 750
(userID:groupID permissions)
Also make sure that the parent directories on the host of the directory that you’ve chosen as datadir are publicly readable with e.g. ‘sudo chmod +r /mnt’ (adjust the command accordingly to your case) and the same for all subdirectories.
Additionally, if you want to use a Fuse-mount as datadir, set ‘allow_other’ as additional mount option.
For SMB/CIFS mounts as datadir, see GitHub - nextcloud/all-in-one: The official Nextcloud installation method. Provides easy deployment and maintenance with most features included in this one Nextcloud instance.
Connection to nextcloud-aio-database (172.18.0.4) 5432 port [tcp/postgresql] succeeded!
now
2024-03-23 14:11:49.387417-07
(1 row)
- ‘[’ -f /dev-dri-group-was-added ‘]’
++ find /dev -maxdepth 1 -mindepth 1 -name dri - ‘[’ -n ‘’ ‘]’
- set +x
ncadmin@nextcloud:/mnt$
I pasted this log into chatgpt to see what it said and it says the container should be running.
What am I missing? Where else I can look for further troubleshooting?
Thanks
Mike