| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vinny P |
 Posted: Fri Jan 16, 2009 11:36 am Post subject: |
 |
|
Newbie
Joined: 14 Jan 2009
Posts: 6
|
| We tried everything known to the HPNS world to stop that process but nothing worked. It was due to a CPU 0 failure in November that we are in this predicament. In our 24/7 environment, cold loads are not smiled upon. It actually took an act of Congress to get the CPU reload approved. |
|
| Back to top |
|
 |
| LuisFer |
| Posted: Fri Jan 16, 2009 12:08 pm Post subject: |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| If i remember well, on the INUG web page there was an utilility (a guardian KILL) that was able to "kill" a process when the STOP do not work, (i don´t probe it) |
|
| Back to top |
|
|
| hankknowles |
| Posted: Fri Jan 16, 2009 12:26 pm Post subject: |
|
|
Centurion
Joined: 18 Aug 2003
Posts: 114
|
| LuisFer wrote: |
| 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?? |
Yeah CPU 0 reload could be real bad thing to do - cold load this baby and when it comes back don't start the qmanager but maybe a cleanup of fractured code and pointers within mq here is what I have done to clean things up. The following files can be deleted but mq rebuilds when the qmanager starts
n = cpunumber thus C0000100
In the qmanager subvolume delete ZWMQBIN
Cn*
Ln*
Sn*
In the qmanager subvolume there are similar like named files that should disappear when the qmanager stops if not delete them there is a file name SZ000100 DON'T PURGE THIS ONE
Also before you restart make sure the the pathway servers do not run in CPU0 or 1 and also in oss there is a control file you can edit and make sure all the cpu references also don't have cpu 0.
/var/mqm/qmgrs/name/QMPROC.ini |
|
| Back to top |
|
|
| BWick |
| Posted: Fri Feb 06, 2009 10:55 am Post subject: |
|
|
Newbie
Joined: 19 Dec 2008
Posts: 3
Location: New York, NY
|
I read through this post fairly quickly but I ran into a similar issue upgrading from 5.3 on Linux RedHat 3. All mq procs were killed, nothing showed up in ps -ef for mq. ipcs -a was clean. Turned out by deleting everything but the qmanager directory in /var/mqm/qmgrs I was able to continue with the install. For some reason there was a qm.ini file in /var/mqm/qmgrs along with the queue manager file and @SYSTEM. removing qm.in and @SYSTEM solved the issue for me.
Just my 2 cents, hope that helps. |
|
| Back to top |
|
|
| exerk |
| Posted: Fri Feb 06, 2009 2:45 pm Post subject: Re: Unstoppable Command Server Process in OSS (MQv5.3 HPNS) |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| mqjeff wrote: |
| Vitor wrote: |
| "Too much" Red Bull? What is this strange, alien concept? |
It's the exact opposite of "Too Much Beer". |
What is this strange concept of "Too Much Beer" ? 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
