Your message dated Thu, 9 Feb 2017 18:08:38 +0100 with message-id <[email protected]> and subject line burp server not removing working links after backup failure has caused the Debian Bug report #824097, regarding burp server not removing working links after backup failure to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 824097: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824097 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: burp Version: 1.3.48-4.1 Severity: normal Dear Maintainer, burp server is not removing /var/spool/burp/<hostname>/working links after backups have failed, even if working_dir_recovery_method = delete is set. So later backup are all failing with error in get_lock_and_clean() because the working link still exists. Is ist possible that this setting is not working, because /var/spool/burp is on NFS storage? I have two other installations with the same settings on local storage where the problem does not accure. Christoph -- System Information: Debian Release: 8.4 APT prefers stable-updates APT policy: (700, 'stable-updates'), (700, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages burp depends on: ii libacl1 2.2.52-2 ii libc6 2.19-18+deb8u4 ii libgcc1 1:4.9.2-10 ii libncurses5 5.9+20140913-1+b1 ii librsync1 0.9.7-10 ii libssl1.0.0 1.0.1k-3+deb8u5 ii libstdc++6 4.9.2-10 ii libtinfo5 5.9+20140913-1+b1 ii zlib1g 1:1.2.8.dfsg-2+b1 burp recommends no packages. burp suggests no packages. -- Configuration Files: /etc/burp/burp-server.conf changed: mode = server port = 4971 status_port = 4972 directory = /var/spool/burp clientconfdir = /etc/burp/clientconfdir pidfile = /var/run/burp.server.pid hardlinked_archive = 0 working_dir_recovery_method = delete max_children = 10 max_status_children = 10 umask = 0022 syslog = 1 stdout = 0 client_can_delete = 1 client_can_force_backup = 1 client_can_list = 1 client_can_restore = 1 client_can_verify = 1 version_warn = 1 keep = 7 keep = 4 keep = 4 ca_conf = /etc/burp/CA.cnf ca_name = burpCA ca_server_name = burpserver ca_burp_ca = /usr/sbin/burp_ca ssl_cert_ca = /etc/burp/ssl_cert_ca.pem ssl_cert = /etc/burp/ssl_cert-server.pem ssl_key = /etc/burp/ssl_cert-server.key ssl_key_password = password ssl_dhfile = /etc/burp/dhfile.pem timer_script = /etc/burp/timer_script timer_arg = 23h timer_arg = Mon,Tue,Wed,Thu,Fri,Sat,Sun,00,01,02,03,05,06,07,08,09,10,11,12,13,14,17,18,19,20,21,22,23 notify_failure_script = /etc/burp/notify_script notify_failure_arg = sendmail -t notify_failure_arg = To: [email protected] notify_failure_arg = From: burp notify_failure_arg = Subject: %b failed: %c %w /etc/default/burp changed: RUN=yes DAEMON_ARGS="-c /etc/burp/burp-server.conf -l /var/log/burp" -- no debconf information<<attachment: martin.vcf>>
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---Package: burp Version: 2.0.54-1 I've tested in NFS environment without this issue.
--- End Message ---
