Closed marcello-dev closed 1 month ago
New feature idea: it would be good to add a timestamp next to the log message for better troubleshooting.
Good idea.
Keeping this here for later:
Nexcloud is up again finally. I could not kill the Borg container, so I force restarted the server. On startup Ubuntu failed to load because the external drive (where the Nextcloud datadir is located) could not mount properly. Unplug and plug back in the external drive fixed the drive issue, then Ubuntu could start. The Borg container also started on startup but this time finished the backup correctly and Nextcloud came back online. I'd say, the backup getting stuck is due to my external drive playing games with me.
I'd say, the backup getting stuck is due to my external drive playing games with me.
yes, I think so as well
New feature idea: it would be good to add a timestamp next to the log message for better troubleshooting.
Good idea.
This is now released with v9.1.0 Beta. Testing and feedback is welcome! See https://github.com/nextcloud/all-in-one#how-to-switch-the-channel
This is a continuation of https://github.com/nextcloud/all-in-one/issues/4736 because the issue appeared again but this time a bit different. Details below.
Steps to reproduce
Expected behavior
The backup should start at 4am UTC and finish after a few minutes
Actual behavior
The backup is still ongoing at 2pm UTC (~10hours later)
Host OS
Ubuntu 22.04
Nextcloud AIO version
v8.3.0
Current channel
latest
Other valuable info
The Borg container is still running after 10 hours, when it usually takes only a few minutes. Logs from Borg container:
AIO logs shows that it is waiting for the Borg container to stop (see logs below)
I tried to stop manually Borg container and got:
I still don't have the feature to manually unblock the backup from the dashboard, because it was implemented for AIO v9. Also how to know if Borg is still doing something? I did upload some big files yesterday but it should not take that long.
New feature idea: it would be good to add a timestamp next to the log message for better troubleshooting.