We have a machine running 6.2.0 that just developed an interesting
problem: the second or third time that qcc is run after a reboot, it
never completes. Pidin shows qcc REPLY blocked on pid 1, followed by
something that is “(Loading)” and READY at priority 9. Of course,
neither of these stuck processes can be killed, and the only solution
I’ve found so far is to run shutdown. Anybody got an ideas?
Murf
Find out who is running ready on priority 10. I remember XPhoton used to run
ready
if the network connection is gone/not ready.
-xtang
John Murphy <murf@perftech.com> wrote in message
news:411396EC.8E8FCC94@perftech.com…
We have a machine running 6.2.0 that just developed an interesting
problem: the second or third time that qcc is run after a reboot, it
never completes. Pidin shows qcc REPLY blocked on pid 1, followed by
something that is “(Loading)” and READY at priority 9. Of course,
neither of these stuck processes can be killed, and the only solution
I’ve found so far is to run shutdown. Anybody got an ideas?Murf
Aha! There’s a telnet session ready on priority 10 - the result of some testing
that obviosuly left things in a nasty state. Killing it solved the problem.
Easy when you know (and rememebr) what to look for!
Thanks for the help!!!
Murf
Xiaodan Tang wrote:
Find out who is running ready on priority 10. I remember XPhoton used to run
ready
if the network connection is gone/not ready.-xtang
John Murphy <> murf@perftech.com> > wrote in message
news:> 411396EC.8E8FCC94@perftech.com> …
We have a machine running 6.2.0 that just developed an interesting
problem: the second or third time that qcc is run after a reboot, it
never completes. Pidin shows qcc REPLY blocked on pid 1, followed by
something that is “(Loading)” and READY at priority 9. Of course,
neither of these stuck processes can be killed, and the only solution
I’ve found so far is to run shutdown. Anybody got an ideas?Murf