Back In Time

Empty logfile: only info log entries as root

Bug #1463367 reported by Benjamin Schmid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Back In Time
Fix Released
Medium
Germar
Back In Time 1.1.6

Bug Description

In my set up I'm running a BIT instance under my user account as well as one instance as root to backup the rest of the system. I'm on Linux Mint, Cinnamon and using the desktop links to start BIT.

For my regular user the logging works as expected: I've set the loglevel to all and I can inspect the changes via the BIT GUI option.

The root instance seems to ignore the log level settings. The log file is typically just empty. The very first run did produce some output, all messages at INFO level.

    ========== Take snapshot (profile 1): Tue Jun 9 11:16:12 2015 ==========

    [I] …
    [I] Snapshot erstellen
    [I] rsync -rtDHh --links --no-p -....
    [I] Snapshot erstellen (rsync: building file list ... done)
    [I] Snapshot erstellen (rsync: ./)
    [I] Snapshot erstellen (rsync: Hq1B2StMXn-fYj -> l,vHg3gugnIc1...

Now all other snapshots only contain:

   ========== Take snapshot (profile 1): Tue Jun 9 11:58:54 2015 ==========

This is a pity, because I want to optimize my exclusion patterns based on the backed up files. Anything I can do to tackle my issue?

See original description
Benjamin Schmid (benbuntu)
description: updated
Revision history for this message
Germar (germar) wrote :

Please take a look inside the log files if there is more content. You will find the last log in /root/.local/share/backintime/takesnapshot_.log and inside every snapshot there is a takesnapshot.log.bz2 (backintime/HOST/USER/PROFILE_ID/SNAPSHOT_ID/takesnapshot.log.bz2). Use bzless to view this or extract it first.

Which version of BackInTime do you use?

Revision history for this message
Benjamin Schmid (benbuntu) wrote :

Thank you Germar for your support!

I'm using BIT 1.1.4.

The last log in /root/.local/share/backintime/takesnapshot_.log is the same as shown in the GUI with the "everything" filter and contains only INFO level entries.

Opposite to my initial description, it now seems also to contain INFO-level entries for updated files. Originally the log file was alway almost completely empty.

So the remaining issue seems to me, that file updates should be probably recorded as [C] not [I] entry, no?

Revision history for this message
Germar (germar) wrote :

Did you disable 'Check for changes' (which makes perfectly sense for root as there are always changes in /var/log)?

The 'Changes [C]' log is the output of 'rsync --dry-run' which is run before taking the snapshot (if you don't use 'Full rsync mode'). With 'Check for changes' disabled there is no 'rsync --dry-run'. BIT will directly create a new snapshot.

If you use 'Full rsync mode' there is no dry-run either but BIT will create the 'Changes [C]' log from the normal rsync run for historical reason.

Revision history for this message
Benjamin Schmid (benbuntu) wrote :

Thank you germar. That indeed does the trick. I switched to "Full rsync mode" which is significantly faster for me, too.

Changed in backintime:
status: New → Invalid
Revision history for this message
Germar (germar) wrote :

I'll still consider this as a bug as it is confusing. I'll make BIT log Changes with disabled 'Full rsync mode' and disabled 'Check for changes'.

Changed in backintime:
status: Invalid → In Progress
importance: Undecided → Medium
assignee: nobody → Germar (germar)
milestone: none → 1.1.6
Germar (germar)
Changed in backintime:
status: In Progress → Fix Committed
Germar (germar)
Changed in backintime:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.