| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| AMQ8041 Error - Unable to start Queue Manager |
« View previous topic :: View next topic » |
| Author |
Message
|
| Riley |
 Posted: Fri Jan 18, 2002 1:08 pm Post subject: |
 |
|
Newbie
Joined: 16 Jan 2002
Posts: 6
Location: NYC
|
I'm running MQSeries on HP UNIX as well as Solaris. The systems were rebooted over the weekend. I was able to cleanly start my Queue Manager on Monday and stop it without incident. However, when I tried to restart the Queue Manager, I got the following error:
AMQ8041: The queue manager cannot be restarted or deleted because processes,that were previously connected, are still running.
Process 26916 is still running.
Process 25518 is still running.
Process 25523 is still running.
Process 29891 is still running.
Process 25511 is still running.
Process 5625 is still running.
Process 19720 is still running.
Process 17725 is still running.
Process 7569 is still running.
Process 27857 is still running.
Process 21182 is still running.
AMQ7018: The queue manager operation cannot be completed.
I checked, these processes are in no way related to MQSeries. None of them are owned by anyone in the mqm group, some are even owned by root. According to IBM, their solution is to "Stop the processes and try to start the queue manager." Or, failing that, reboot the system. This same thing also happened after a weekend reboot of the Solaris system.
Is it possible the rebooting corrupted MQSeries?
|
|
| Back to top |
|
 |
| bower5932 |
| Posted: Fri Jan 18, 2002 3:52 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
My guess would be that the reboot was done without shutting down MQSeries gracefully. This being the case, there are probably some semaphores and shared memory segments laying around. You should be able to use ipcs and ipcrm to display and remove them. I would guess that all of the processes listed as running is being caused because pid's have been reused. Hope this helps.
[ This Message was edited by: bower5932 on 2002-01-18 15:52 ] |
|
| Back to top |
|
|
| Mike.WG.Moody |
| Posted: Mon Jan 28, 2002 3:10 am Post subject: |
|
|
Newbie
Joined: 16 Dec 2001
Posts: 7
|
We see this type of behaviour quite often on Solaris and sometimes on AIX.
I agree it is normally after an untidy shutdown.
It becomes real problem with multiple queue managers on a box because all the
IPCS resources are own by 'mqm' for and you can't tell good from bad.
Drop me an e-mail - got a couple of scripts to help clear up the mess. |
|
| Back to top |
|
|
| mqonnet |
| Posted: Mon Jul 21, 2003 10:15 am Post subject: |
|
|
Grand Master
Joined: 18 Feb 2002
Posts: 1114
Location: Boston, Ma, Usa.
|
This is an old one, but i wanted to add something to this thread. I was searching for AMQ8041 and found this.
One of the most common reasons that raise this error is, you end your qmgr without ending or killing all your outstanding runmqsc sessions that you might have started in different windows. Stop/kill them and you can restart your qm just fine.
I faced this today and thought would share this, but saw that there were threads with this amq* error already, so am just appending to it.
Cheers
Kumar |
|
| Back to top |
|
|
| Leafar |
| Posted: Mon Jul 21, 2003 11:22 am Post subject: |
|
|
Acolyte
Joined: 03 Apr 2003
Posts: 74
Location: Buenos Aires
|
If you have only a qmgr on this machine, you can try this
shut down te qmgr with endmq
for f in `ipcs -s | grep mqm | awk '{print $2}' `
do
ipcrm -s $f
done
This will remove ALL semaphores belowed by the user mqm
then repalce ipcs -s with ipcs -m and ipcrm -s with ipcrm -m
Saludos
Rafael |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
