Your message dated Thu, 10 Jan 2019 21:32:58 +0100 with message-id <[email protected]> and subject line configuration problem has caused the Debian Bug report #886406, regarding PID file directory not created by init script 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.) -- 886406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886406 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: burp Version: 2.0.54-1 Severity: normal Hi, When trying to start burp automatically upon boot the PID file directory isn't automatically created, resulting in: root@backup:~# service burp status * burp.service - LSB: backup and restore program Loaded: loaded (/etc/init.d/burp; generated; vendor preset: enabled) Active: active (exited) since Fri 2018-01-05 11:40:28 CET; 2h 8min ago Docs: man:systemd-sysv-generator(8) Tasks: 0 (limit: 4915) CGroup: /system.slice/burp.service Jan 05 11:40:28 backup systemd[1]: Starting LSB: backup and restore program... Jan 05 11:40:28 backup burp[701]: Could not open lock file /var/run/burp/burp.server.pid: No such file or directory Jan 05 11:40:28 backup burp[701]: Could not get lockfile. Jan 05 11:40:28 backup burp[701]: Maybe you do not have permissions to write to /var/run/burp/burp.server.pid. Jan 05 11:40:28 backup burp[663]: Starting burp : failed! Jan 05 11:40:28 backup systemd[1]: Started LSB: backup and restore program. root@backup:~# Since this seems to be a race condition, starting the daemon with the same script later does work ok: root@backup:~# service burp restart root@backup:~# service burp status * burp.service - LSB: backup and restore program Loaded: loaded (/etc/init.d/burp; generated; vendor preset: enabled) Active: active (running) since Fri 2018-01-05 13:48:56 CET; 1s ago Docs: man:systemd-sysv-generator(8) Process: 5928 ExecStop=/etc/init.d/burp stop (code=exited, status=0/SUCCESS) Process: 5936 ExecStart=/etc/init.d/burp start (code=exited, status=0/SUCCESS) Tasks: 1 (limit: 4915) CGroup: /system.slice/burp.service `-5945 /usr/sbin/burp -c /etc/burp/burp-server.conf Jan 05 13:48:56 backup systemd[1]: Stopped LSB: backup and restore program. Jan 05 13:48:56 backup systemd[1]: Starting LSB: backup and restore program... Jan 05 13:48:56 backup burp[5936]: Starting burp :. Jan 05 13:48:56 backup systemd[1]: Started LSB: backup and restore program. root@backup:~# Maybe this should be circumvented by creating a systemd service with proper dependency chain or just hotfixed by the init script creating the required directory before the start-stop-daemon. Best, Kilian
--- End Message ---
--- Begin Message ---This is a configuration problem. Have you checked the config file of a burp server (/etc/burp/burp-server.conf)? Default value is '/var/run/burp.server.pid', not '/var/run/burp/burp.server.pid'. Sorry for the dalay. bye
--- End Message ---
