Back In Time schedule hangs, but "manual" backup works

Bug #489385 reported by Jan Schnackenberg
This bug report is a duplicate of:  Bug #441628: BAckintime crash when screen locked. Edit Remove
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Back In Time
New
Undecided
Unassigned

Bug Description

Using Kubuntu 9.10 and the le-web repository. Installed versions (backintime-common and backintime-kde) are 0.9.26-3.

If I start backintime from the commandline, the KDE4-frontend comes up. Clicking the "Backup"-Icon starts the backup-process which will work correctly.

I have configured a daily backup-schedule. "crontab -l" gives:

@daily nice -n 19 /usr/bin/backintime --backup-job >/dev/null 2>&1

Unfortunately this does _not_ seem to work. The backup-process starts, correctly, every midnight, but it will hang. In the notification area the icon will be "unclickable" but show a tooltip stating that it's comparing the last backup. It will hang there for several days if not killed manually (using htop, oder whatever).

Revision history for this message
cliff6056 (cliff6056) wrote : Re: [Bug 489385] [NEW] Back In Time schedule hangs, but "manual" backup works

Hello Jan. I had the same symptoms using Sidux and KDE4 (441628). I
installed backintime-gnome (yeh it pulled in a bunch of other gnome
packages) but it seems to work just fine. For your info.

Jan Schnackenberg wrote:
> <pre wrap>Public bug reported:
>
> Using Kubuntu 9.10 and the le-web repository. Installed versions
> (backintime-common and backintime-kde) are 0.9.26-3.
>
> If I start backintime from the commandline, the KDE4-frontend comes up.
> Clicking the "Backup"-Icon starts the backup-process which will work
> correctly.
>
> I have configured a daily backup-schedule. "crontab -l" gives:
>
> @daily nice -n 19 /usr/bin/backintime --backup-job &gt;/dev/null
> 2&gt;&amp;1
>
> Unfortunately this does _not_ seem to work. The backup-process starts,
> correctly, every midnight, but it will hang. In the notification area
> the icon will be "unclickable" but show a tooltip stating that it's
> comparing the last backup. It will hang there for several days if not
> killed manually (using htop, oder whatever).
>
> ** Affects: backintime
> Importance: Undecided
> Status: New
>
> </pre></body>
> </html>
> </html>

Revision history for this message
Dan (danleweb) wrote :

BIT log using syslog.
Please check your syslog for lines containing "backintime".

Revision history for this message
Jan Schnackenberg (yehaa) wrote :
Download full text (5.0 KiB)

These are the lines from last night (I edited the "include-folders" for privacy):

Nov 29 00:00:01 UltraSnake backintime (jan): INFO: Lock
Nov 29 00:00:01 UltraSnake backintime (jan): INFO: Include folders: [****]
Nov 29 00:00:01 UltraSnake backintime (jan): INFO: Ignore folders: []
Nov 29 00:00:01 UltraSnake backintime (jan): INFO: Last snapshots: {}
Nov 29 00:00:01 UltraSnake backintime (jan): INFO: [KDE4Plugin.Systray.run]
Nov 29 00:00:01 UltraSnake backintime (jan): INFO: Compare with old snapshot: 20091128-000001
Nov 29 00:00:02 UltraSnake backintime (jan): INFO: [KDE4Plugin.Systray.run] begin loop

That's it. Nothing after that.

The "funny" thing is this. On Nov 27th I did start BackInTime manually at 22:56:36 as seen in the log:

Nov 27 22:56:36 UltraSnake backintime (jan): INFO: Lock
Nov 27 22:56:36 UltraSnake backintime (jan): INFO: Include folders: [****]
Nov 27 22:56:36 UltraSnake backintime (jan): INFO: Ignore folders: []
Nov 27 22:56:36 UltraSnake backintime (jan): INFO: Last snapshots: {}
Nov 27 22:56:36 UltraSnake backintime (jan): INFO: [KDE4Plugin.Systray.run]
Nov 27 22:56:37 UltraSnake backintime (jan): INFO: Compare with old snapshot: 20091119-000002
Nov 27 22:56:37 UltraSnake backintime (jan): INFO: [KDE4Plugin.Systray.run] begin loop
Nov 27 22:57:08 UltraSnake backintime (jan): INFO: Command "rsync -aEAX -i --dry-run --chmod=Fa-w,D+w --whole-file --delete --exclude="/Files/BackupCD/BackInTimeJan" --exclude="/home/jan/.local/share/backintime" --include="****" returns 0
Nov 27 22:57:08 UltraSnake backintime (jan): INFO: Create hard-links
Nov 27 23:00:50 UltraSnake backintime (jan): INFO: Command "cp -al "/Files/BackupCD/BackInTimeJan/backintime/20091119-000002/backup/"* "/Files/BackupCD/BackInTimeJan/backintime/new_snapshot/backup/"" returns 0
Nov 27 23:00:50 UltraSnake backintime (jan): INFO: Call rsync to take the snapshot
Nov 27 23:11:24 UltraSnake backintime (jan): INFO: Command "rsync -aEAX -v --delete-excluded --chmod=Fa-w,D+w --whole-file --delete --exclude="/Files/BackupCD/BackInTimeJan" --exclude="/home/jan/.local/share/backintime" --include="****" --exclude="*" / "/Files/BackupCD/BackInTimeJan/backintime/new_snapshot/backup/"" returns 0
Nov 27 23:11:24 UltraSnake backintime (jan): INFO: Save permissions
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: Remove backups older than: 19991127-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep all >= 20091126-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20091116-000000 and < 20091123-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20091109-000000 and < 20091116-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20090101-000000 and < 20090201-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20090201-000000 and < 20090301-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20090301-000000 and < 20090401-000000
Nov 27 23:12:10 UltraSnake backintime (jan): INFO: [smart remove] keep first >= 20090401-000000 and < 20090501-000000
Nov 27 23:12:10 UltraSna...

Read more...

Revision history for this message
Dan (danleweb) wrote :

Looks like a crash !

Revision history for this message
Jan Schnackenberg (yehaa) wrote :

Well... Whatever it is, the program keeps "running" for days, if not terminated.

I'll see tonight if it's currently running (after last night) and will post the process-tree. Maybe you can see if there's something missing there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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