Nextcloud AIO v5.1.0 Apache & Nextcloud won't start. Been over 2 hours now

I had my NC Server running for 3 months through VB on an Ubuntu 22.04 host with no real issues. I downloaded it from Index of /aio-vm
To keep disk usage low I did not unminimize it. If I needed a command that wasn’t there I have been installing it. If you want me to run a command for testing, please include the commands necessary to install the command incase I don’t have it.

I have an SSL cert from LetsEncrypt. I used the certbot. No SSL issues.

I was syncing folders into a nextcloud share and everything was ine, then I started getting red Xs on everything. I shut it down and rebooted and it never came back up. I didn’t check status of containers before rebooting. I went into the AIO and saw everything running excep for Apache and Nextcloud which were stuck on Starting.
I tried to create new doc in the folder and on the web interface and nothing was syncing; I was also getting the same pop up error on everything saying the file could not sync due to an error.

My research hasn’t come up with anything helpful but I will post what I can

chrome will not open these links becasue they are not SSL, but you can view them through MS Edge. I don’t know about firefox.
Link to results of sudo docker inspect nextcloud-aio-apache: http://nextme.ddns.net:8020/logs/docker.txt

Link to AIO logs: http://nextme.ddns.net:8020/logs/aio.txt

Thanks

Mike

1 Like

Hi, can you post the logs of the nextcloud-aio-nextcloud and nextcloud-aio-apache container here? Also what is the output of sudo df -h ?

1 Like

How do I get the logs of the nextcloud-aio-nextcloud and nextcloud-aio-apache container?

ncadmin@nextcloud:~$ sudo df -h
[sudo] password for ncadmin:
Filesystem                         Size  Used Avail Use% Mounted on
tmpfs                              995M  1.9M  993M   1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv   98G   20G   74G  21% /
tmpfs                              4.9G     0  4.9G   0% /dev/shm
tmpfs                              5.0M     0  5.0M   0% /run/lock
/dev/sda2                          2.0G  254M  1.6G  14% /boot
/dev/sda1                          1.1G  5.3M  1.1G   1% /boot/efi
//192.168.1.1/storage              932G  723G  209G  78% /mnt/ncdata
//192.168.1.1/nextcloudbackup      932G  723G  209G  78% /mnt/backup
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/99fe67807f4ad70d8938ac181174ab91fce42ae608b6b34341bee975892fd10f/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/d83492947a0fcf02c5799b98ba8d432cf14a28d03bca6c8aa871fabedc60809f/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/d07266ad879c9ee5d037f77c451e32eb86d4ca53b716c4c0b3cd304035d359e7/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/0b6a2a70cc79f6ea99ad23c382e60a52863c867b0bb12100117d875075ff7e4d/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/e23910c73573da52127a00197019d5f0c2f3fd59f46481ad6bc71f5a8b4aab95/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/ecb6173d030ac7a4aa9ac01c0e8908f4036abf60eaa3abe8c4642e39599dc534/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/8d2a60efc8114f43b06d6cca42fc9c0167b2c84a91e94135dc4745c5a3157c07/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/3873768ae3a8c7dda2dfae7fbb4cb5e2742e2aa7bfab6d7e64991dba8c0ad037/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/7c053f0e452d9880194ce9cff0d5caa5d40ace94f075cc0e8a86cab367aaed40/merged
overlay                             98G   20G   74G  21% /var/lib/docker/overlay2/af6d68cdb0c04cade89dc33f6040f326b7025fc14605d4c5712c25c57e887ac1/merged
tmpfs                              995M   12K  995M   1% /run/user/1000
ncadmin@nextcloud:~$

E.g. with sudo docker logs nextcloud-aio-apache and sudo docker logs nextcloud-aio-nextcloud

I couldnt run these commands as ncadmin so i did sudo su, which I’ve done many times but this time I got this message:
qt.qpa.xcb: could not connect to display
qt.qpa.plugin: Could not load the Qt platform plugin “xcb” in “” even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb.

root@nextcloud:/mnt/ncdata# docker logs nextcloud-aio-apache
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…
Waiting for Nextcloud to start…

It displays so many of these lines that I can't see the beginning. I tried to redirect to a file

root@nextcloud:/mnt/ncdata# docker logs nextcloud-aio-apache > docker_apache
bash: docker_apache: Invalid argument
root@nextcloud:/mnt/ncdata#

Cant figure out why this isnt working, I redirect all the time.

root@nextcloud:/mnt/ncdata# docker logs nextcloud-aio-nextcloud
Logs too large to post, here is a link to them: http://nextme.ddns.net:8020/logs/docker_nextcloud.txt

1 Like

Thanks for the logs! Can you also post the output of docker inspect nextcloud-aio-nextcloud --format {{.Mounts}} ?

Forgive my ignorance. Can you give me an example of what to do with {{.Mounts}} ?

Is it something like:
docker inspect nextcloud-aio-nextcloud --format /mnt/ncdata ?

Please just post the output of

sudo docker inspect nextcloud-aio-nextcloud --format {{.Mounts}}
1 Like

root@nextcloud:/mnt/ncdata# docker inspect nextcloud-aio-nextcloud --format {{.Mounts}}
[{bind /mnt /mnt rw true rprivate} {bind /mnt/ncdata /mnt/ncdata rw true rprivate} {volume nextcloud_aio_nextcloud /var/lib/docker/volumes/nextcloud_aio_nextcloud/_data /var/www/html local rw true }]
root@nextcloud:/mnt/ncdata#

What kind of mount is this? SMB/CIFS or NFS?

smb to a drive on my router.
mounted to /mnt/ncdata

worked with no issues for 3-months

Can you show the /etc/fstab entry for that?

fstab:

root@nextcloud:/mnt/ncdata# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/ubuntu-vg/ubuntu-lv during curtin installation
/dev/disk/by-id/dm-uuid-LVM-Go2c6FQtJct0RcUMGt59JOVirRS9ftcQc75HYXafYAAPPZn85dfmUwPwzi00n3Eu / ext4 defaults 0 1
# /boot was on /dev/sda2 during curtin installation
/dev/disk/by-uuid/0ceee2f6-3004-4acd-9529-8314584a9980 /boot ext4 defaults 0 1
# /boot/efi was on /dev/sda1 during curtin installation
/dev/disk/by-uuid/B75A-BE99 /boot/efi vfat defaults 0 1
/swap.img       none    swap    sw      0       0
//192.168.1.1/storage  /mnt/ncdata  cifs   vers=1.0,uid=www-data,gid=www-data,credentials=/mnt/.credentials,iocharset=utf8   0       0
//192.168.1.1/nextcloudbackup  /mnt/backup  cifs   vers=1.0,uid=www-data,gid=www-data,credentials=/mnt/.credentials,iocharset=utf8   0       0

root@nextcloud:/mnt/ncdata#
1 Like

Is the network drive still mounted? Can you reboot the VM and afterwards run sudo -ls /mnt/ncdata and check if the container has access to the mountpoint afterwards again?

1 Like

Thats one of the first things I checked yesterday and it did have access to the mount.
Rebooted the VM

ncadmin@nextcloud:~$ sudo ls /mnt/ncdata
[sudo] password for ncadmin:
admin files_encryption mike
appdata_ocz93kvhm654 files_external nextcloud.log
audit.log fts-index.done snoopy
backup ‘googlef37f6a59e435b34b (1).html’ tmp
bind index.html
ncadmin@nextcloud:~$

Can you also stop the containers from the AIO interface and start them again from there for a test?

1 Like

No, since I have to containers that haven’t started yet, I do not have the option to stop the containers from the AIO interface

1 Like

I see. Please run sudo docker stop nextcloud-aio-apache then and reload the AIO interface. Then you should have the option to stop them and afterwards you should be able to start them again.

1 Like

I ran the command and stopped the containers. I see there is a mastercontainer update available. and that is my only option. Should I update?

1 Like

I would recommend to create a backup first.

1 Like