Bug#604682: backup-manager: no easy way to debug faulty commands
On 2010-11-23 16:11 +0100, Xavier Bestel wrote: > -d doesn't say much, apart from printing the useless logfiles: I guess there's a reason why this option is not documented. But I think setting BM_LOGGER_LEVEL="debug" would log the actual commands being run to syslog. > Maybe that part: "$command $file_to_create "$target" > $logfile" should > be expanded before being printed ? Yes, but this is not under backup-manager's control. The command is only printed because it segfaults, and apparently bash does not expand variables in such a situation. Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#604682: backup-manager: no easy way to debug faulty commands
On Tue, 2010-11-23 at 15:51 +0100, Sven Joachim wrote: > BTW, what are your tar and libc6 versions? libc6 is 2.11.2-7 tar was 1.23-3, and I tried 1.25-2 with not much success. Xav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#604682: backup-manager: no easy way to debug faulty commands
On Tue, 2010-11-23 at 15:51 +0100, Sven Joachim wrote: > On 2010-11-23 14:44 +0100, Xavier Bestel wrote: > > Is there an easy way to debug it ? > > You could set BM_LOGGER_LEVEL to "debug", maybe that helps. There is > also an undocumented "-d|--debug" option for backup-manager. Otherwise, > insert a "set -x" at the beginning of /usr/bin/backup-manager and you > will be overwhelmed by its verbosity. ;-) -d doesn't say much, apart from printing the useless logfiles: [r...@awak:~]$ LANG=C backup-manager -v -d When validating the configuration file /etc/backup-manager.conf, 1 warnings were found. /bin/tar: Removing leading `/' from member names /mnt/backup/awak-boot.20101123.tar.gz: ok (0M, cce53a1524d08bbb94b340b8bec82075) /bin/tar: Removing leading `//' from member names /usr/share/backup-manager/backup-methods.sh: line 605: 32181 Segmentation fault $command $file_to_create "$target" > $logfile 2>&1 Unable to create "/mnt/backup/awak.20101123.tar.gz", check /tmp/bm-tarball.log.0kNKAd /bin/tar: Removing leading `/' from member names /bin/tar: /home/xav/.bogofilter/wordlist.db: file changed as we read it Tar reported a file changed during archive creation. /mnt/backup/awak-home.20101123.tar.gz: ok (387M, 9423aead90d47fcbe8416ffce6e868dc) Unable to find the md5 hash of file "/mnt/backup/awak-home.20101101.master.tar.gz" in file "/mnt/backup/awak-20101101.md5". Unable to find the md5 hash of file "/mnt/backup/awak-home.20101102.tar.gz" in file "/mnt/backup/awak-20101102.md5". 1 error occurred during the tarball generation. sh -x, of course works (thanks for the hint). I've got my command: /bin/tar --listed-incremental /mnt/backup/awak.incremental.bin --one-file-system -p -c -z -f /mnt/backup/awak.20101123.tar.gz but it's not that easy to parse :) Maybe that part: "$command $file_to_create "$target" > $logfile" should be expanded before being printed ? I'll send a bugreport for tar. Thanks, Xav -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#604682: backup-manager: no easy way to debug faulty commands
On 2010-11-23 14:44 +0100, Xavier Bestel wrote: > Package: backup-manager > Version: 0.7.9-3 > Severity: wishlist > > > Hi, > > I don't know why, but since 2 days the tar commands segfaults. I'd like to > debug why, but I don't know how to launch it, BM doesn't give enough info: > > [r...@awak:~]$ LANG=C backup-manager -v > When validating the configuration file /etc/backup-manager.conf, 1 warnings > were found. > /mnt/backup/awak-boot.20101123.tar.gz: ok (0M, > 262209eb997126fd42acc214edefc581) > /usr/share/backup-manager/backup-methods.sh: line 605: 29229 Segmentation > fault $command $file_to_create "$target" > $logfile 2>&1 > Unable to create "/mnt/backup/awak.20101123.tar.gz", check > /tmp/bm-tarball.log.KZlLhk > /mnt/backup/awak-home.20101123.tar.gz: ok (319M, > fafbbe5d97116877f92221591619b1f4) > Unable to find the md5 hash of file > "/mnt/backup/awak-home.20101101.master.tar.gz" in file > "/mnt/backup/awak-20101101.md5". > Unable to find the md5 hash of file "/mnt/backup/awak-home.20101102.tar.gz" > in file "/mnt/backup/awak-20101102.md5". > 1 error occurred during the tarball generation. > [r...@awak:~]$ cat /tmp/bm-tarball.log.KZlLhk > /bin/tar: Removing leading `//' from member names > [r...@awak:~]$ > > Is there an easy way to debug it ? You could set BM_LOGGER_LEVEL to "debug", maybe that helps. There is also an undocumented "-d|--debug" option for backup-manager. Otherwise, insert a "set -x" at the beginning of /usr/bin/backup-manager and you will be overwhelmed by its verbosity. ;-) BTW, what are your tar and libc6 versions? Cheers, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#604682: backup-manager: no easy way to debug faulty commands
Package: backup-manager Version: 0.7.9-3 Severity: wishlist Hi, I don't know why, but since 2 days the tar commands segfaults. I'd like to debug why, but I don't know how to launch it, BM doesn't give enough info: [r...@awak:~]$ LANG=C backup-manager -v When validating the configuration file /etc/backup-manager.conf, 1 warnings were found. /mnt/backup/awak-boot.20101123.tar.gz: ok (0M, 262209eb997126fd42acc214edefc581) /usr/share/backup-manager/backup-methods.sh: line 605: 29229 Segmentation fault $command $file_to_create "$target" > $logfile 2>&1 Unable to create "/mnt/backup/awak.20101123.tar.gz", check /tmp/bm-tarball.log.KZlLhk /mnt/backup/awak-home.20101123.tar.gz: ok (319M, fafbbe5d97116877f92221591619b1f4) Unable to find the md5 hash of file "/mnt/backup/awak-home.20101101.master.tar.gz" in file "/mnt/backup/awak-20101101.md5". Unable to find the md5 hash of file "/mnt/backup/awak-home.20101102.tar.gz" in file "/mnt/backup/awak-20101102.md5". 1 error occurred during the tarball generation. [r...@awak:~]$ cat /tmp/bm-tarball.log.KZlLhk /bin/tar: Removing leading `//' from member names [r...@awak:~]$ Is there an easy way to debug it ? Thanks, Xav -- System Information: Debian Release: squeeze/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing'), (50, 'unstable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.36-trunk-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages backup-manager depends on: ii debconf [debconf-2.0]1.5.36 Debian configuration management sy ii findutils4.4.2-1+b1 utilities for finding files--find, ii ucf 3.0025+nmu1 Update Configuration File: preserv backup-manager recommends no packages. Versions of packages backup-manager suggests: pn anacron(no description available) pn backup-manager-doc (no description available) pn dar(no description available) pn dvd+rw-tools (no description available) ii genisoimage 9:1.1.11-1 Creates ISO-9660 CD-ROM filesystem ii gettext-base0.18.1.1-3 GNU Internationalization utilities pn libfile-slurp-perl (no description available) pn libnet-amazon-s3-perl (no description available) ii openssh-client 1:5.5p1-5+b1 secure shell (SSH) client, for sec ii perl5.10.1-16Larry Wall's Practical Extraction pn wodim (no description available) pn zip(no description available) -- debconf information: backup-manager/upload-key: backup-manager/name-format: long backup-manager/upload-hosts: backup-manager/upload-user-ftp: * backup-manager/cron_frequency: daily backup-manager/cron_d_remove_deprecated: false * backup-manager/blacklist: /mnt /tmp /proc /sys /dev /lib/init/rw /var/lib/nfs/rpc_pipefs * backup-manager/time-to-live: 100 backup-manager/burning-maxsize: backup-manager/encryption_recipient: backup-manager/transfert_mode: backup-manager/dump_symlinks: false backup-manager/upload-user-scp: backup-manager/burning-device: backup-manager/upload-dir: * backup-manager/enable_encryption: false * backup-manager/directories: /boot / /home * backup-manager/repo_group: root backup-manager/filetype: tar.gz * backup-manager/repo_user: root * backup-manager/backup-repository: /mnt/backup backup-manager/burning-method: backup-manager/burning-enabled: false backup-manager/want_to_upload: false -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
