| Author |
Message
|
| Vinny P |
 Posted: Wed Jan 14, 2009 10:43 am Post subject: Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
 |
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
| We recently had a command server process become "unstoppable" under OSS. We are running v5.3 on a HPNS (Tandem). We need to upgrade to 5.3.1.4 but since MQ thinks the command server is up we can't issue a strmqm,endmqm,stpmqcsv or strmqcsv therefore we can't upgrade. Is there a way to make MQ think the command server is stopped? Is there a way around this so we can stop and start our q-manager? HPNS has told us that the only way to get rid of the unstoppable process is to reload the cpu it running in we can't do that for 2 weeks. |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Wed Jan 14, 2009 11:54 am Post subject: Re: Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vinny P wrote: |
| We recently had a command server process become "unstoppable" |
I get that way with too much Red Bull.
Try Get Inhibiting the SYSTEM.ADMIN.COMMAND.QUEUE via runmqsc. That should cause it to end.
Warning: Try this on a test system first. I make no guarantees that his will work or not make things even worse for you.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jan 14, 2009 12:00 pm Post subject: Re: Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| PeterPotkay wrote: |
| I get that way with too much Red Bull. |
"Too much" Red Bull? What is this strange, alien concept?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vinny P |
| Posted: Wed Jan 14, 2009 12:51 pm Post subject: |
|
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
I forgot to mention that the q-manager is stopped so I can not issue runmqsc commands. I can not start the q-manager due to the following eloquent error:
strmqm TSYS3QM1
AMQ8041: The queue manager cannot be restarted or deleted because processes,
that were previously connected, are still running.
Process 0,471 $Z7F8 OSS(872939646) is still running.
AMQ7018: The queue manager operation cannot be completed.
I too get somewhat "unstoppable" but not with Red Bull, Sobe "No Fear"... |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jan 14, 2009 1:27 pm Post subject: Re: Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| "Too much" Red Bull? What is this strange, alien concept? |
It's the exact opposite of "Too Much Beer". |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 14, 2009 3:00 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Vinny P wrote: |
AMQ8041: The queue manager cannot be restarted or deleted because processes,
that were previously connected, are still running.
Process 0,471 $Z7F8 OSS(872939646) is still running.
|
Is this process still actually running? ps -ef|grep
If yes, kill -9?
If no, did you run amqiclen?
Is what I suggesting even valid for your O/S?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Vinny P |
| Posted: Thu Jan 15, 2009 7:11 am Post subject: |
|
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
| Yes, we attempted a kill -9 but it didn't work. The amqiclen utility is not available on the HPNS O/S. I am thinking that we will have to reload the cpu. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 15, 2009 7:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Vinny P wrote: |
| Yes, we attempted a kill -9 but it didn't work. |
If kill -9 has failed, that's about as unstopable as it gets. Time to reach for the power cable...... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vinny P |
| Posted: Thu Jan 15, 2009 7:33 am Post subject: |
|
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
That is what we were told by HP but we had hoped we could get away with making MQ think that the command server was stopped.
When starting a q-manager, what steps does the strmqm take to verify all processes are stopped? Is there some file or program we could alter or temporarily remove so that we could hopefully start the q-manager which would start another command server process?
I really don't want to tell management that we have to halt a cpu..... |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Jan 15, 2009 7:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Vinny P wrote: |
When starting a q-manager, what steps does the strmqm take to verify all processes are stopped? Is there some file or program we could alter or temporarily remove so that we could hopefully start the q-manager which would start another command server process?
|
That's a question for a passing IBMer. In your position I'd raise a PMR and ask directly.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Jan 15, 2009 8:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
There is documentation on manually stopping a queue manager.
How useful that is for HPNSK/NSS is a different question. |
|
| Back to top |
|
|
| hankknowles |
| Posted: Thu Jan 15, 2009 9:13 am Post subject: |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| mqjeff wrote: |
There is documentation on manually stopping a queue manager.
How useful that is for HPNSK/NSS is a different question. |
Bad NEWS had a few unstoppables ended up cold loading the existing image.
OSS unstoppable really are unstopable - we did fake out the qmanager start but it was failing on the tcplis00 process!
Take the pain stop the box restart it will be worth the time -  |
|
| Back to top |
|
|
| Vinny P |
| Posted: Thu Jan 15, 2009 9:31 am Post subject: |
|
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
Thanks for all your help guys. I will definitely be using this website more often. I have gotten more help in less than a day here than I would have gotten in a week opening a PMR.
I have already broken the news and we have a CPU reload scheduled to get rid of the truly "UNSTOPPABLE" process.... |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Jan 16, 2009 10:18 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| Vinny P wrote: |
I forgot to mention that the q-manager is stopped so I can not issue runmqsc commands. I can not start the q-manager due to the following eloquent error:
strmqm TSYS3QM1
AMQ8041: The queue manager cannot be restarted or deleted because processes,
that were previously connected, are still running.
Process 0,471 $Z7F8 OSS(872939646) is still running.
AMQ7018: The queue manager operation cannot be completed.
I too get somewhat "unstoppable" but not with Red Bull, Sobe "No Fear"... |
And a STOP $Z7F8 (or stop 0,471) under guardian don't work?? |
|
| Back to top |
|
|
| LuisFer |
| Posted: Fri Jan 16, 2009 11:12 am Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
In our experience is not recommended a Reload of CPU 0 on Tandem (cpu 0 contains special microcode).
We prefer a Cold Load (but i don´t remember when we do the last Cold Load... ah yes on 14 September 2006 and our v 5.1 QMgrs working fine from. ( Lovely NSK  )) |
|
| Back to top |
|
|
|
|
