[Bug 783011] New: Recent bacula packages from Archiving:/Backup have systemd problems with /var/run
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c0 Summary: Recent bacula packages from Archiving:/Backup have systemd problems with /var/run Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: openSUSE 12.1 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jpschewe@mtu.net QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20100101 Firefox/15.0.1 I recently updated to bacula 5.2.12-222.1 from http://ftp.suse.de/pub/opensuse/repositories/Archiving:/Backup:/Factory/open... and found that systemd hangs for a couple of minutes and then kills off the bacula processes when trying to start them. It seems that the .service files and bacula are pointing to /var/run/bacula and our old config files point to /var/run. This prevents bacula from starting. By removing /var/run/bacula and making it a symlink to /var/run the services now start. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c Christian Boltz <suse-beta@cboltz.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |suse-beta@cboltz.de AssignedTo|bnc-team-screening@forge.pr |philipp.storz@dass-it.de |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c1 Stefan Münkner <stefan.muenkner@mx.uni-saarland.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan.muenkner@mx.uni-saar | |land.de --- Comment #1 from Stefan Münkner <stefan.muenkner@mx.uni-saarland.de> 2012-12-18 17:24:13 UTC --- I had the same problems, with some more information. The reason for this seems, that in 12.1 the bacula daemons are expected to create their PID files in /var/run/bacula, in fact they try to create it in /var/run. So systemd cannot find the PID-files and thus cannot restart the daemons or recognize that they have been succesfully started. Changing the path to the PID files in the respective /lib/systemd/system/bacula-{dir,fd,sd}.service alone does not help either since the director and the storage daemon are forked and run both under User=bacula Group=bacula both have no permission to write into /var/run and so both daemons are not started. Some logs from my server (after setting -d3 for bacula-dir): Dec 18 18:00:33 BaculaServer bacula-dir[7975]: bacula-dir: dird_conf.c:1886-0 runscript cmd=/usr/lib64/bacula/list-media.sh type=| Dec 18 18:00:33 BaculaServer bacula-dir[7975]: 18-Dec 18:00 bacula-dir: ERROR TERMINATION at bsys.c:498 Dec 18 18:00:33 BaculaServer bacula-dir[7975]: Could not open pid file. /var/run/bacula-dir.9101.pid ERR=Permission denied Dec 18 18:00:33 BaculaServer systemd[1]: PID file /var/run/bacula-dir.9101.pid not readable (yet?) after start. Dec 18 18:00:33 BaculaServer systemd[1]: bacula-dir.service never wrote its PID file. Failing. Dec 18 18:00:33 BaculaServer systemd[1]: Unit bacula-dir.service entered failed state. My workaround was to modify the *.service files and set the location of the PID files to /var/run/bacula-dir.9101.pid /var/run/bacula-sd.9102.pid /var/run/bacula-fd.9103.pid for the respective daemon. Additionally, I set User=root instead of User=bacula for the sd and dir. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c2 --- Comment #2 from Stefan Münkner <stefan.muenkner@mx.uni-saarland.de> 2013-01-31 12:49:23 UTC --- After going through the configuration files I could fix this issue by explicitely setting the run files to be created in /var/run/bacula, for all daemons. The problem here arises because the systemd bacula-xyz.service file are configured with one location of the PID files and in the bacula-xyz.conf files something else could be required. I am not certain that systemd is a step forward. I think this one could be closed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c Marc Chamberlin <marc@marcchamberlin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |807951 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=783011 https://bugzilla.novell.com/show_bug.cgi?id=783011#c3 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |bruno@ioda-net.ch Resolution| |FIXED --- Comment #3 from Bruno Friedmann <bruno@ioda-net.ch> 2013-04-28 10:05:07 UTC --- Fixed in 5.2.13 + new packaging. bacula rpm create tmp dir in /var/run/bacula ( But existing configuration has to be checked by administrator ) Thus the daemon can run with bacula user and not root Services files are not correct Closing bug -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com