
Hey Folks, there is a fresh bug on launchpad [1] which brings up the opportunity for me to learn something. In short about the bug: I assume the LOCK file is somewhere. But I don't know where BIT stores it. Maybe one of you can jump in and help. And I didn't found the LOCK-file topic in our FAQ. Would be great to add this there, too. Back to the main topic of that mail. It is an often experience situation for me when dealing with log files and debug output. In relation to that specific issue let me ask some questions please. - The reporter use "systemctl status cron" to show us cron output. But BIT isn't a systemd unit. How can I ask the system for BIT releated syslog output? Next time I can answer the user with "Please execute 'xyz' in the shell and post me the output.". - Where does BIT store its LOCK files? It seems to me this information is not present in debug output. But I'm not sure. Kind Christian [1] -- <https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2003326>

Dear Christian, BiT stores detailed backup logs under "/$BIT_FOLDER/$HOSTNAME/$USER/$PROFILE_ID/last_snapshot/takesnapshot.log.bz2" (e.g.: /storage/backup/backintime/temple/zero/1/last_snapshot/takesnapshot.log.bz2) file. This file is the file shown by the BiT user interface, and is the main logfile for the job as far as I know. You can see the file contents with "bzless" command without extracting it. Also, a copy and less detailed version is present under my system's /var/log/user.log file. Maybe that place will provide more information, too. /var/log/cron.log will only show the commands ran as part of the job. So it won't provide us any details. For the lock file, BiT creates an empty file "save_to_continue" under "new_snapshot" folder it creates during backup, and deletes afterwards. This might be the lock file itself, but I'm not sure about that. Hope this helps, Cheers, Hakan On 19.01.2023 18:20, c.buhtz@posteo.jp wrote:

Just to be sure: Do you want to find out the location of LOCK or *.log files (or both)? With *.log files I mean the logging output of BIT (optionally quite verbose with "--debug") which is produced via a non-standard self-developed logging module in the file https://github.com/bit-team/backintime/blob/main/common/logger.py It writes not only to the console but also into the syslog that can be queried in a terminal e. g. with: journalctl | grep -i backintime With LOCK file I mean the file(s) that BIT uses to avoid parallel executions (GUI or taking a snapshot)... I can neither find systematic logging output of the LOCK files in BIT nor related output with "--diagnostics" but the lock file locations are defined in these code files: /tmp/backintime.lock https://github.com/bit-team/backintime/blob/979b757d2cbbe65b332c5fd15244d400... ~/.local/share/backintime/* (e.g. "app.lock" and "worker*.lock") https://github.com/bit-team/backintime/blob/979b757d2cbbe65b332c5fd15244d400... https://github.com/bit-team/backintime/blob/main/common/config.py#L1304 I have opened a new issue to add logging output of the lock files when "--debug" is used: https://github.com/bit-team/backintime/issues/1400 I have put this issue on my TODO list... On Thu, 2023-01-19 at 15:20 +0000, c.buhtz@posteo.jp wrote:

Dear Christian, BiT stores detailed backup logs under "/$BIT_FOLDER/$HOSTNAME/$USER/$PROFILE_ID/last_snapshot/takesnapshot.log.bz2" (e.g.: /storage/backup/backintime/temple/zero/1/last_snapshot/takesnapshot.log.bz2) file. This file is the file shown by the BiT user interface, and is the main logfile for the job as far as I know. You can see the file contents with "bzless" command without extracting it. Also, a copy and less detailed version is present under my system's /var/log/user.log file. Maybe that place will provide more information, too. /var/log/cron.log will only show the commands ran as part of the job. So it won't provide us any details. For the lock file, BiT creates an empty file "save_to_continue" under "new_snapshot" folder it creates during backup, and deletes afterwards. This might be the lock file itself, but I'm not sure about that. Hope this helps, Cheers, Hakan On 19.01.2023 18:20, c.buhtz@posteo.jp wrote:

Just to be sure: Do you want to find out the location of LOCK or *.log files (or both)? With *.log files I mean the logging output of BIT (optionally quite verbose with "--debug") which is produced via a non-standard self-developed logging module in the file https://github.com/bit-team/backintime/blob/main/common/logger.py It writes not only to the console but also into the syslog that can be queried in a terminal e. g. with: journalctl | grep -i backintime With LOCK file I mean the file(s) that BIT uses to avoid parallel executions (GUI or taking a snapshot)... I can neither find systematic logging output of the LOCK files in BIT nor related output with "--diagnostics" but the lock file locations are defined in these code files: /tmp/backintime.lock https://github.com/bit-team/backintime/blob/979b757d2cbbe65b332c5fd15244d400... ~/.local/share/backintime/* (e.g. "app.lock" and "worker*.lock") https://github.com/bit-team/backintime/blob/979b757d2cbbe65b332c5fd15244d400... https://github.com/bit-team/backintime/blob/main/common/config.py#L1304 I have opened a new issue to add logging output of the lock files when "--debug" is used: https://github.com/bit-team/backintime/issues/1400 I have put this issue on my TODO list... On Thu, 2023-01-19 at 15:20 +0000, c.buhtz@posteo.jp wrote:
participants (3)
-
BiT dev
-
c.buhtz@posteo.jp
-
Hakan Bayındır