On Sat, 14 Jul 2012 10:23:52 +0100, Brian wrote:
> On Fri 13 Jul 2012 at 17:27:11 +0000, Camaleón wrote:
>
>> Mmm, there's still a FAILED message BUT now rsyslog is not listed, just
>> the other two proccesses:
>>
>> init-+-exe
>> |-rc---startpar---sendsigs---pstree
>> |-rpcbind
>>
>> So, now I have to find why these are failing to be properly stopped but
>> well, at least now I know the listed processes are indeed the ones that
>> hang. Thanks, that makes debugging a bit more easy :-)
>
> I should have said our messages are similar rather than the same. Mine
> begins
>
> init-+-logsave
>
> and does not contain -rpcbind. I wonder what 'exe' is. Running pstree
> might help to identify it. /etc/init.d/sendsigs is also worth looking
> at.
Good idea... let's see:
hpc03@stt300:~$ pstree -p | grep -e exe -e rpcbind -e rsyslogd
|-exe(2920)
|-rpcbind(1200)
|-rsyslogd(1413)-+-{rsyslogd}(1414)
| |-{rsyslogd}(1415)
| `-{rsyslogd}(1416)
hpc03@stt300:~$ ps aux | grep -e 2920 -e 1200 -e 1413
root 1200 0.0 0.0 2352 708 ? Ss 12:34 0:00 /sbin/rpcbind
-w
root 1413 0.0 0.0 28940 1652 ? Sl 12:34 0:00
/usr/sbin/rsyslogd -c5
hpc03 2920 0.0 0.0 264 100 ? S 12:40 0:00
gnome-pty-helper
So now we know who they are I how to find out why they fail to be stopped >:-?
Greetings,
--
Camaleón
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jtrjaa$36q$3...@dough.gmane.org
