Bacula daemons are not started during system boot

Bug #442125 reported by Lupe Christoph
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bacula (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: bacula

Since my upgrade to Karmic Beta, the bacula daemons are not started automatically during system boot. I can start them when the system is running with no problems.

Since I don't understand upstart yet, I would like to ask for advice how one debugs upstart problems. For now I will assume that something in the bacula init scripts prevents them from running correctly.

ProblemType: Bug
Architecture: amd64
Date: Sun Oct 4 13:05:22 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: fglrx
Package: bacula (not installed)
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SourcePackage: bacula
Uname: Linux 2.6.31-11-generic x86_64

Revision history for this message
Lupe Christoph (lupe) wrote :
Revision history for this message
Chuck Short (zulcss) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in bacula (Ubuntu):
status: New → Incomplete
Revision history for this message
Lupe Christoph (lupe) wrote :

1. Is this reproducible?
Yes, it is.

2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
Well, this machine has been running Ubuntu and bacula for quite some time, so I can't be really sure that I'm not missing something.

I can tell you that I deinstalled bacula-director-mysql bacula-director-common bacula-fd bacula-sd bacula-sd-mysql and removed the init scripts. Dunno why these were not deinstalled. They are considered part of the configuration, and I did not use --purge.

Then, I installed those packages again and rebooted. No bacula process was started, but I must admit that bacula-sd and bacula-fd had no chance of being started because the installation did not install the start scripts. Probably again because I did not use --purge when I removed the packages.

I'm sorry that I don't have the time to experiment some more. And I don't want to lose my bacula configuration.

Revision history for this message
Lupe Christoph (lupe) wrote :

I just realized that because the init scripts are part of the configuration, they will probably not be replaced by an upgrade, so I'm still running init scripts from Intrepid or even earlier.

Revision history for this message
Mathias Gug (mathiaz) wrote : Re: [Bug 442125] Re: Bacula daemons are not started during system boot

Hi,

On Sun, Oct 04, 2009 at 08:51:16PM -0000, Lupe Christoph wrote:
> I can tell you that I deinstalled bacula-director-mysql bacula-director-
> common bacula-fd bacula-sd bacula-sd-mysql and removed the init scripts.
> Dunno why these were not deinstalled. They are considered part of the
> configuration, and I did not use --purge.

Init scripts are part of the package configuration. Symlinks in rc*/
should be removed on package removal, however init scripts should be
only remove on purge.

> Then, I installed those packages again and rebooted. No bacula process
> was started, but I must admit that bacula-sd and bacula-fd had no chance
> of being started because the installation did not install the start
> scripts. Probably again because I did not use --purge when I removed the
> packages.
>

Since you've manually deleted the init script after package removal, a
reinstall won't setup the rc*/ symlink again.

To fix the issue you need to manually reinstall the init script
(extracting from the package) and reinstall the bacula packages.

Marking Invalid as this is a user error.

  status invalid

--
Mathias Gug
Ubuntu Developer http://www.ubuntu.com

Changed in bacula (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.