Init script fails to start at all if not set to start on boot

Bug #1557163 reported by chasemp on 2016-03-14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
corosync (Ubuntu)

Bug Description

Details on the installed package:

labtestvirt2001:~# aptitude show corosync
Package: corosync
State: installed
Automatically installed: no
Version: 2.3.3-1ubuntu1
Priority: optional
Section: admin
Maintainer: Ubuntu Developers <email address hidden>
Architecture: amd64
Uncompressed Size: 1,001 k

Details on the OS:

Linux labtestvirt2001 3.16.0-62-generic #83~14.04.1-Ubuntu SMP Fri Feb 26 22:52:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Ubuntu 14.04.4 LTS \n \l


When I installed the corosync package and tried to start it there was no output and it returned exit code 0. After some digging I see the following in the init script:

if [ "$START" != "yes" ]; then
        exit 0

When I look in /etc/default/corosync I see:

# start corosync at boot [yes|no]

The 'START' param is only meant to affect behavior on boot in the init script provided the service will not start at all unless the service is set to start on boot. If I change the config to:

# start corosync at boot [yes|no]

I am then able to start the package normally from the command line.

This bug is old and refers to variables set by /etc/default. Nevertheless, even back then, it would not be fixed because having it NOT TO start without end-user action is the desirable behaviour. With that, I'm closing this as won't fix and wrapping up all old bugs into the Ubuntu HA effort. Thanks for reporting this.

Changed in corosync (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers