Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28353 - [bacula] rc.d script fail on restart and stop

Attached to Project: Community Packages
Opened by Mark (fiddlinmacx) - Friday, 10 February 2012, 18:32 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Thursday, 16 February 2012, 07:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture i686
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
rc.d restart bacula-dir FAILs
rc.d stop bacula-dir FAILs too
- the rc.d scripts are looking in /var/run/bacula/ for the lock files
they're actually in /var/run/

Additional info:
latest package


Steps to reproduce:
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Thursday, 16 February 2012, 07:02 GMT
Reason for closing:  Works for me
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 12 February 2012, 09:59 GMT
Can you manually stop the daemons this one time and start them again using the rc.d scripts? I'm sorry this was a rough transition. However, it should keep working fine after doing an upgrade and system restart.
Comment by Mark (fiddlinmacx) - Tuesday, 14 February 2012, 19:07 GMT
I tried stopping them manually and starting them with the scripts. They're still putting the run files in /var/run and not in /var/run/bacula. I really don't want to have to restart my system. Is that necessary?
Comment by Alexander F. Rødseth (xyproto) - Tuesday, 14 February 2012, 20:17 GMT
Mark, perhaps you could create a symbolic link in the mean while (if you don't want to reboot and that's the only solution that's currently offered)?
Something like: ln -s /var/run /var/run/bacula
Comment by Mark (fiddlinmacx) - Tuesday, 14 February 2012, 20:47 GMT
I rebooted, and the behaviour is the same. You're right, the rc.d scripts look OK, but the files are still being created in /var/run, not in /var/run/bacula. I can function just fine like this ;-), but I'm trying to figure out what's going on.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 15 February 2012, 10:51 GMT
Sorry, I absolutely cannot recreate this. I installed bacula-5.2.5-3 in a fresh system, did sudo rc.d start bacula-dir. ls /var/run/bacula/ shows
bacula-dir.9101.pid.

Stopping and restarting works just fine. In Arch, /var/run is a symlink to /run, is that not the case for you?
Comment by Sven-Hendrik Haase (Svenstaro) - Thursday, 16 February 2012, 07:02 GMT
I will close this for now until you or somebody else can add more info to point out the nature of this bug.

Loading...