Your message dated Mon, 28 Feb 2011 15:14:12 +0100
with message-id <[email protected]>
and subject line Re: Bug#615861: rsyslog: status option behaving strange, not
following LSB?
has caused the Debian Bug report #615861,
regarding rsyslog: status option behaving strange, not following LSB?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
615861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615861
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: rsyslog
Version: 5.7.4-2
Severity: normal
# /etc/init.d/rsyslog status
rsyslogd is running.
# echo $?
0
# /etc/init.d/rsyslog stop
Stopping enhanced syslogd: rsyslogd.
# echo $?
0
Ok, but:
# /etc/init.d/rsyslog status
could not access PID file for rsyslogd ... failed!
# echo $?
4
# ls -la /lib/init/rw/sendsigs.omit.d/rsyslog
lrwxrwxrwx 1 root root 21 Feb 28 14:48 /lib/init/rw/sendsigs.omit.d/rsyslog ->
/var/run/rsyslogd.pid
# ls -la /var/run/rsyslogd.pid
ls: cannot access /var/run/rsyslogd.pid: No such file or directory
Hm? I'd expected to get exit code "3" instead:
| If the status action is requested, the init script will return the following
exit status codes.
|
| 0 program is running or service is OK
| 1 program is dead and /var/run pid file exists
| 2 program is dead and /var/lock lock file exists
| 3 program is not running
| 4 program or service status is unknown
--
http://refspecs.freestandards.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
regards,
-mika-
--- End Message ---
--- Begin Message ---
* Michael Biebl <[email protected]> [Mon Feb 28, 2011 at 03:08:00PM +0100]:
> Am 28.02.2011 14:52, schrieb Michael Prokop:
> > # /etc/init.d/rsyslog status
> > could not access PID file for rsyslogd ... failed!
> > # echo $?
> > 4
> > # ls -la /lib/init/rw/sendsigs.omit.d/rsyslog
> > lrwxrwxrwx 1 root root 21 Feb 28 14:48 /lib/init/rw/sendsigs.omit.d/rsyslog
> > -> /var/run/rsyslogd.pid
> > # ls -la /var/run/rsyslogd.pid
> > ls: cannot access /var/run/rsyslogd.pid: No such file or directory
> > Hm? I'd expected to get exit code "3" instead:
> I can not reproduce this problem here.
> If rsyslog is not running and there is no /var/run/rsyslogd.pid:
> # /etc/init.d/rsyslog status
> rsyslogd is not running ... failed!
> # echo $?
> 3
> If there is a dangling symlink /lib/init/rw/sendsigs.omit.d/rsyslog
> there is the same exit code.
> So, maybe your system is probably really in an unknown state :-)
> That said, rsyslog uses the status_of_proc() method from
> /lib/lsb/init-functions (lsb-base). If you think the reported status
> code is wrong, it's best to discuss that with the lsb-base maintainers.
> Could you investigate, why status_of_proc() returns 4 in your case?
> Feel free to reassign, otherwise I'm going to close this bug report
> against rsyslog.
Ah, it's not about rsyslog but about the lsb-base version (somewhere
between 3.2-23.2squeeze1 and 3.2-27), indeed.
Closing this bugreport, will investigate separately regarding
lsb-base.
thanks && regards,
-mika-
signature.asc
Description: Digital signature
--- End Message ---
