Start/Stop script /etc/init.d/zabbix-agent returns 1 when should return 0

Bug #1109077 reported by Sam Zaydel on 2013-01-29
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
zabbix (Ubuntu)
Undecided
Unassigned

Bug Description

While the zabbix-agent successfully starts and stops, the script returns a `1`. This prevents the package from being correctly removed or upgraded, all of which require that stop return a 0.

## On Stop ##
rtconf@rts-wmububench-01:~$ sudo /etc/init.d/zabbix-agent stop; echo $?; ps -ef|grep zabbix
1
rtconf 6693 1969 0 12:01 pts/2 00:00:00 grep --color=auto zabbix

## On Start ##
rtconf@rts-wmububench-01:~$ sudo /etc/init.d/zabbix-agent start; echo $?; ps -ef|grep zabbix
1
zabbix 6701 1 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
zabbix 6702 6701 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
zabbix 6703 6701 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
zabbix 6704 6701 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
zabbix 6705 6701 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
zabbix 6706 6701 0 12:01 ? 00:00:00 /usr/sbin/zabbix_agentd
rtconf 6708 1969 0 12:01 pts/2 00:00:00 grep --color=auto zabbix

As we can see here, we are returning a 1, when obviously things are working. Simply adding `true` at the end of the start/stop clauses fixes this problem, but it is clearly an ugly hack that will hide real issues.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in zabbix (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers