-
Steps to reproduce
Expected behaviorLogs should be visible in their entirety Actual behaviorOnly a few lines of log shown, then an error. The number of log lines shown varies. Sometimes 1, sometimes as much as 6.
Other informationHost OSUbuntu 22.0.4 LTS Output of
|
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
Since displaying the log is not working via the admin web interface, how do I fetch the backup log to find out why the backup is failing? |
Beta Was this translation helpful? Give feedback.
-
Hi,
|
Beta Was this translation helpful? Give feedback.
-
The logs from this command gives the same output as the "logs" viewed from the AIO admin web interface. "error from daemon in stream:", then the "Error grabbing logs: invalid character ..." |
Beta Was this translation helpful? Give feedback.
-
Okay. Then this is a docker issue and nothing we can fix in AIO. You might want to try to do the backup again. |
Beta Was this translation helpful? Give feedback.
-
I tried to add my comments but since you were quick to change this from an issue to a discussion, I couldn't. Adding here for more details.
FYI, I found I can fetch the log location via: docker inspect --format='{{.LogPath}}' nextcloud-aio-borgbackup Looks like one log line in this file is malformed, with a new {"log": ...} entry being started before the previous one is finished. That's why the error notes the invalid character is a lower-case L. Unclear to me why this could happen; perhaps related to why the backup itself ends up failing, running out of storage space? Odd that it's able to continue logging after this, though. The cause for the backup failing is clear from the log now that I can see it; "no space left on device." I presume the backup is trying to store all user files, including trash. And, this is then related to another issue I have with Nextcloud in general (not specifically AIO), where Nextcloud is moving deleted files from external storage, to the trash folder in the root of the user's files. The external storage is not flagged for backup, while the "local" files including the trash are. I need to remember to clean the trash folder after deleting huge files. For now, I'll make sure to store backups on my NAS instead of the VM's local drive, to avoid running out of space for backups. |
Beta Was this translation helpful? Give feedback.
I tried to add my comments but since you were quick to change this from an issue to a discussion, I couldn't. Adding here for more details.
FYI, I found I can fetch the log location via: docker inspect --format='{{.LogPath}}' nextcloud-aio-borgbackup
Looks like one log line in this file is malformed, with a new {"log": ...} entry being started before the previous one is finished. That's why the error notes the invalid character is a lower-case L. Unclear to me why this could happen; perhaps related to why the backup itself ends up failing, running out of storage space? Odd that…