[Bug 807951] New: Bacula-fd client package missing service shell script file
https://bugzilla.novell.com/show_bug.cgi?id=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c0 Summary: Bacula-fd client package missing service shell script file Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: marc@marcchamberlin.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=528600) --> (http://bugzilla.novell.com/attachment.cgi?id=528600) Attached is the missing shell script file that should be installed in /etc/rc.d User-Agent: Mozilla/5.0 (Windows NT 5.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 I installed just the client for bacula from the opensuse-archiving-backup-x86_64 repository. The client is not installed in the Systems Services (runlevel) because the shell script bacula-fd was not installed in the /etc/rc.d directory, nor were any links set up in the appropriate (rc3.d and rc5.d) runlevel directories. I had to copy an old one over from a previous version of openSuSE in order to get it to work, and set up the runlevels manually. Reproducible: Always Steps to Reproduce: 1. Install the bacula client files only 2. Configure them to connect to the director. 3. try to start by executing rcbacula-fd start Actual Results: No joy in mudville! Cannot start the service because of the aforementioned missing shell script. Expected Results: I expected the bacula-fd service to start. Should also have set links for running in levels 3 and 5 by default. Probably a common problem on all installations of Bacula client packages, not just on the x86-64 platform -- 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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c1 Marc Chamberlin <marc@marcchamberlin.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |783011 --- Comment #1 from Marc Chamberlin <marc@marcchamberlin.com> 2013-03-08 01:40:54 UTC --- In addition to the missing service shell script, the inability to start the bacula-fd client daemon also has the same set of problems as described in bug #783011 as related to just the client daemon files. So I am going to mark this bug as being dependent on bug #783011 being fixed as well. -- 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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c2 --- Comment #2 from Stefan Münkner <stefan.muenkner@mx.uni-saarland.de> 2013-03-08 08:37:03 UTC --- As far as I can tell, the omission of the init-scripts in /etc/ini.d (or /etc/rc.d) was a decision of the maintainers of bacula package, because "systemd will replace init eventually" (actually they expected it to happen in openSuSE 12.2 already). I have been bitten hard by a crash in systemd on my server here lately and I must say since in over 20 years of experience with Linux I have never seen init crash, that systemd crash let me have a closer look on systemd. On a desktop computer systemd has its merits accelerating the boot process and solving some dependencies. But those benefits come at the cost of a much more complex piece of software, depending e.g. on using d-bus (to which systemd could not re-established a connection after the crash, refused to do its job and hence I had to hard reset the server), depending on information like in the above situation (PID-file locations, on which systemd will never get a control, since it is configurable via the daemon's config file, but systemd insists on the PID-file being in that location, otherwise stopping a perfectly running process). I doubt that I will want systemd to be at the heart of process control on a server...... -- 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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c FeiXiang Zhang <fxzhang@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |anicka@suse.com |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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c Bug 807951 depends on bug 783011, which changed state. Bug 783011 Summary: Recent bacula packages from Archiving:/Backup have systemd problems with /var/run http://bugzilla.novell.com/show_bug.cgi?id=783011 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |FIXED -- 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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c3 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bruno@ioda-net.ch --- Comment #3 from Bruno Friedmann <bruno@ioda-net.ch> 2013-04-28 10:13:45 UTC --- Systemd has replaced sysVinit in 12.2 and is the only one available in 12.3 Fixes for systemd services and var/run/bacula have been published For me, this bug has nothing to do with yast2 runlevel ( not being able to manage systemd only service ) It show and report only init script which will not be pick by systemd if a native systemd exist. I let Anna decide of what to do with this. -- 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=807951 https://bugzilla.novell.com/show_bug.cgi?id=807951#c4 Bruno Friedmann <bruno@ioda-net.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution| |WONTFIX --- Comment #4 from Bruno Friedmann <bruno@ioda-net.ch> 2013-12-06 20:26:04 UTC --- 13.1 has a new yast runlevel able to handle correctly systemd service I'm closing it as won't fix. systemd services were adjusted to handle correctly 13.1+ several weeks ago. -- 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