Public bug reported:
service scripts for bacula-director, bacula-sd und bacula-fd don't stop,
reload or give status when the respective daemon is launched on a
different port (directive dirport, sdport, fdport).
The cause is that the start script generates a PID file with the port
number in its name. Despite of that, the stop, reload and status
function of the init script queries for a PID with the default port in
the PID file name:
status_of_proc -p /var/run/bacula/bacula-sd.9103.pid /usr/sbin/bacula-sd
bacula-sd
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: bacula (not installed)
ProcVersionSignature: Ubuntu 3.5.0-49.74~precise1-generic 3.5.7.32
Uname: Linux 3.5.0-49-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
Date: Mon May 19 16:34:29 2014
InstallationMedia: Ubuntu-Server 12.04.2 LTS Precise Pangolin - Release amd64
(20130214)
MarkForUpload: True
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/usr/bin/fizsh
SourcePackage: bacula
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: bacula (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug precise
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bacula in Ubuntu.
https://bugs.launchpad.net/bugs/1320906
Title:
Bacula init scripts don't stop, status, reload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1320906/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
