This bug only surfaces on systems using systemd and bacula as a client only. When the system is starting with bacula the following units fail with the respective error messages (short and inline): * systemd-tmpfiles-clean.service Mar 15 10:18:32 elijah systemd[1]: Starting Cleanup of Temporary Directories... Mar 15 10:18:32 elijah systemd-tmpfiles[6376]: [/usr/lib64/tmpfiles.d/bacula.conf:2] Unknown user 'bacula'. Mar 15 10:18:32 elijah systemd[1]: systemd-tmpfiles-clean.service: Main process exited, code=exited, status=1/FAILURE Mar 15 10:18:32 elijah systemd[1]: Failed to start Cleanup of Temporary Directories. Mar 15 10:18:32 elijah systemd[1]: systemd-tmpfiles-clean.service: Unit entered failed state. Mar 15 10:18:32 elijah systemd[1]: systemd-tmpfiles-clean.service: Failed with result 'exit-code'. * systemd-tmpfiles-setup.service Mar 15 10:02:56 elijah systemd[1]: Starting Create Volatile Files and Directories... Mar 15 10:02:56 elijah systemd-tmpfiles[1651]: [/usr/lib64/tmpfiles.d/bacula.conf:2] Unknown user 'bacula'. Mar 15 10:02:56 elijah systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Mar 15 10:02:56 elijah systemd[1]: Failed to start Create Volatile Files and Directories. Mar 15 10:02:56 elijah systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Mar 15 10:02:56 elijah systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. This appears to be due to the condition of only creating the bacula user when bacula-clientonly is **not** set. I'm not sure where the tmpfiles definitions are coming from (I can confirm they're provided by the bacula package but don't see them in the install portion of the ebuild). I'm not sure if the solution is to unconditionally create the user or remove the tmpfile configuration. My guess would be the latter as those tmpfile configurations look strange. They setup /var/run owned by bacula which I don't believe is desired behavior.
/me grumbles something about assigning your own bugs
Can you please provide some information about the version we are talking about? Thanks.
Ah, yes, I've noticed this on my running system with version 5.2.13-r3, but last time I looked at the ebuilds, it appeared that it affected recent versions as well. I can double check this if you like. Let me know if any other information would be useful.
(In reply to Alex Brandt from comment #3) > Ah, yes, I've noticed this on my running system with version 5.2.13-r3, but > last time I looked at the ebuilds, it appeared that it affected recent > versions as well. I can double check this if you like. > > Let me know if any other information would be useful. Please recheck it for the 7.4 version. I can not observe the behaviour here. Maybe you have some old tmpfiles around. In the new version they got dropped for some time already. Thanks.
Hey Thomas, Unfortunately, my configuration requires the 5.x series of bacula and I haven't had time to rectify that lately. Let me know if you want to work on a fix for 5.x. I understand if you don't and I'll try to re-visit this bug when I get time to update my systems to 7.x.
(In reply to Alex Brandt from comment #5) > Hey Thomas, > > Unfortunately, my configuration requires the 5.x series of bacula and I > haven't had time to rectify that lately. Let me know if you want to work on > a fix for 5.x. I understand if you don't and I'll try to re-visit this bug > when I get time to update my systems to 7.x. Seems it was an old bug (Bug 528398) we fixed for bacula-7.0.5-r1 but forgot to back port to the 5.2.x series. Sorry. Please update to bacula-5.2.13-r4, which should fix the problem. Reopen the bug if there are still problems.
Ah, that's awesome. Thanks Thomas!
