I had a very strange thing just now, two of my dockers were not started and I could not start them manually - Nextcloud and MariaDB. As far as I knew they were running with out a problem for a months, and regularly updated. Today, an update was shown for both. Updates went smotthly ( I think). However, afterwards neither docker was starting and Nextcloud was unreachable. I am attaching the system diagnostics. 

 

I rebooted the server and I think all is well with both again. Can someone let me know if there is anything in the logs to explain why they both decided to act up?

 

Thanks,

 

Lev

tower-diagnostics-20241113-2224.zip

nextclound issues are better asked on the nextcloud forum...

could be any number of unraid docker issues or misconfigured nextcloud ...

 

The docker.txt log file contains mostly informational messages related to Docker's runtime but doesn't immediately reveal errors specific to why the Nextcloud and MariaDB containers failed to start. I'll need to dig deeper into the syslog to identify potential system-wide issues or events that might explain the Docker container failures.

Let me check the system log (syslog.txt) for errors or warnings related to these Docker containers.

 

 

The logs don't show critical errors related directly to the startup of MariaDB and Nextcloud containers, but there are some notable points:

Successful Starts After Reboot:

The logs confirm that both nextcloud and mariadb started successfully after the reboot

Quote

rc.docker: mariadb: started successfully!
rc.docker: nextcloud: started successfully!
 

Potential Issue with Docker Networking:

Numerous messages indicate ports on the docker0 bridge (vethX) transitioning into and out of a disabled state. This could hint at:

Network instability in the Docker bridge.

Conflicting network configurations or errors related to IPvLAN or macvlan setups.

Stale container states due to failed updates or other network dependencies.

Docker Image Space:

The Docker image (/var/lib/docker) is trimmed regularly and has been fluctuating between ~4 GB and 31 GB of usage. While not directly problematic, large fluctuations might point to heavy resource consumption by containers like Nextcloud or MariaDB.

Probable Causes for the Issues

Failed Updates or Stale Configurations:

The updates for both containers could have left them in a corrupted or misconfigured state.

This could have been fixed by the reboot, which forced a clean restart of both.

Resource or Timeout Issues:

MariaDB and Nextcloud are tightly integrated. If MariaDB failed to start properly, Nextcloud would also fail.

Resource constraints (e.g., memory or disk I/O) during startup could cause one or both containers to hang.

Docker Networking:

The docker0 bridge's state changes indicate potential network instability, which might have disrupted container communication.

 

Recommendations

Inspect Container Logs:

Check the logs for mariadb and nextcloud to see if there are specific error messages:
*Diag doen't capture individual docker logs..
docker logs nextcloud
docker logs mariadb
 

docker logs nextcloud
docker logs mariadb

Verify Updates:

Confirm that both containers are running the expected versions after the update

docker inspect nextcloud | grep "Image"
docker inspect mariadb | grep "Image"

Check Resource Utilization:

Monitor the system's CPU, memory, and disk I/O usage to ensure sufficient resources for both containers

docker stats

 

Inspect Network Configuration:

Check if there are conflicts or issues with Docker's docker0 bridge or any custom network configuration.

Long-Term Fixes:

Consider increasing Docker image size or moving heavy I/O operations (like MariaDB database storage) to a dedicated disk or share.

Use a plugin like CA Backup/Restore Appdata to create regular backups for both app data and Docker configurations

remove Nextcloud use something easier.. rejetto HFS ... what is nextcloud doing that another service application can't?

32 minutes ago, bmartino1 said:

nextclound issues are better asked on the nextcloud forum...

could be any number of unraid docker issues or misconfigured nextcloud ...

 

The docker.txt log file contains mostly informational messages related to Docker's runtime but doesn't immediately reveal errors specific to why the Nextcloud and MariaDB containers failed to start. I'll need to dig deeper into the syslog to identify potential system-wide issues or events that might explain the Docker container failures.

Let me check the system log (syslog.txt) for errors or warnings related to these Docker containers.

 

 

The logs don't show critical errors related directly to the startup of MariaDB and Nextcloud containers, but there are some notable points:

Successful Starts After Reboot:

The logs confirm that both nextcloud and mariadb started successfully after the reboot

Potential Issue with Docker Networking:

Numerous messages indicate ports on the docker0 bridge (vethX) transitioning into and out of a disabled state. This could hint at:

Network instability in the Docker bridge.

Conflicting network configurations or errors related to IPvLAN or macvlan setups.

Stale container states due to failed updates or other network dependencies.

Docker Image Space:

The Docker image (/var/lib/docker) is trimmed regularly and has been fluctuating between ~4 GB and 31 GB of usage. While not directly problematic, large fluctuations might point to heavy resource consumption by containers like Nextcloud or MariaDB.

Probable Causes for the Issues

Failed Updates or Stale Configurations:

The updates for both containers could have left them in a corrupted or misconfigured state.

This could have been fixed by the reboot, which forced a clean restart of both.

Resource or Timeout Issues:

MariaDB and Nextcloud are tightly integrated. If MariaDB failed to start properly, Nextcloud would also fail.

Resource constraints (e.g., memory or disk I/O) during startup could cause one or both containers to hang.

Docker Networking:

The docker0 bridge's state changes indicate potential network instability, which might have disrupted container communication.

 

Recommendations

Inspect Container Logs:

Check the logs for mariadb and nextcloud to see if there are specific error messages:
*Diag doen't capture individual docker logs..
docker logs nextcloud
docker logs mariadb
 

docker logs nextcloud
docker logs mariadb

Verify Updates:

Confirm that both containers are running the expected versions after the update

docker inspect nextcloud | grep "Image"
docker inspect mariadb | grep "Image"

Check Resource Utilization:

Monitor the system's CPU, memory, and disk I/O usage to ensure sufficient resources for both containers

docker stats

 

Inspect Network Configuration:

Check if there are conflicts or issues with Docker's docker0 bridge or any custom network configuration.

Long-Term Fixes:

Consider increasing Docker image size or moving heavy I/O operations (like MariaDB database storage) to a dedicated disk or share.

Use a plugin like CA Backup/Restore Appdata to create regular backups for both app data and Docker configurations

remove Nextcloud use something easier.. rejetto HFS ... what is nextcloud doing that another service application can't?

Thank you very much for the amazingly detailed response. Since rebooting, Nextcloud and other dockers have been running stable, updating and not causing any issues.

 

Since my knowledge of the "under the hood" docker and it's use is very limited, I will assume that the problem was relatedto the update corruption, resolved by restarting the PC. I do regular backups and hope to never have resorting to using them.

 

I am curios about other options to Nextcloud and will definitely look into rejetto. Never heard of it and very curious about options to Nextcloud.

 

Also, I will look into getting a dedicated disk for MariaDB. Are there instructions as to how to move the database?

 

Thanks,

 

Lev

Databases have a lot of reads and writes, its more on making sure a decent drive is there to handle the databases needs. There is a lot towards database migrations....

review there docs....
https://docs.nextcloud.com/server/latest/admin_manual/configuration_database/linux_database_configuration.html

https://docs.nextcloud.com/server/latest/developer_manual/basics/storage/index.html

No i'm not aware of any database migration again Nextcloud question are better asked on there fourm.
https://help.nextcloud.com/

I left Nextcloud for many reasons, I can no longer condone nor recommend them...

As for rejetto hfs, I can highly recommend them:
https://www.rejetto.com/hfs/

HFS is not a 1 for 1 nextcloud replacement some features don't exist an example is the Google sheets document editor...

You have to look at what nextcloud is providing you.