| Author |
Message
|
| MillsPerry |
 Posted: Thu Jan 08, 2004 1:02 pm Post subject: MQSeries 5.3 CSD05 Doesn't automatically restart on Win2k |
 |
|
Acolyte
Joined: 08 Oct 2001
Posts: 59
Location: ZyQuest, inc.
|
We have upgraded several queue managers to v5.3 CSD05. Once we did this we discovered that they no longer auto restart when the server is restarted.
In the Windows Services window, we set the IBM MQSeries service to start automatically.
In the MQSeries Services window, we set the queue manager and each component service to start automatically. Recovery is set to restart after 1 minute for 3 attempts.
These are the same settings we had for v5.2 and they worked for us then. Has anyone else had this problem, and is there a solution? |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu Jan 08, 2004 7:32 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Do you see anything in the error logs like the following? I am trying to solve the same problem.
| Code: |
----- amqrcdfa.c : 2132 -------------------------------------------------------
01/06/2004 23:41:53
AMQ7880: Error code 20 starting QM3/Command Server WebSphere MQ service.
EXPLANATION:
The service was unable to start QM3/Command Server. The error message reported
was as follows: Process could not be started - return code 20
ACTION:
Use WebSphere MQ Services to investigate why the service could not begin. If
recovery for this service is active, MQ will attempt to recover.
-------------------------------------------------------------------------------
|
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| Carl Bloy |
| Posted: Fri Jan 09, 2004 1:04 am Post subject: MQSeries 5.3 CSD05 Doesn't automatically restart on Win2k |
|
|
Acolyte
Joined: 16 Dec 2003
Posts: 69
Location: England
|
The coulc be an issue with web Administration which used to be part of MQSeries.
When you upgrade to MQSeries 5.3 web administration is supposed to be uninstalled, but it leaves the registry entires. This is cretainly a problem we faced and modifying the registry entries resolved the problem.
Key Name: HKEY_LOCAL_MACHINE\SOFTWARE\IBM\MQSeries\CurrentVersion\Configuration\WebAdministration
Class Name: <NO CLASS>
Last Write Time: 05/11/2003 - 14:42
Value 0
Name: Trace
Type: REG_SZ
Data: no
Value 1
Name: WebServerRoot
Type: REG_SZ
Data: no
certainly worht trying... |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Jan 09, 2004 2:31 am Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Peter - When you see the r/c 20 starting the command server service, is it actually started (see the process manager for amqpcsea). The 'normal' cause is the service has lost track of what it has started, not something we have pinned down but normally harmless.
I also read somewhere (unconfirmed) that making the MQ Service depend on another service helps with this (Browser or Server service? Cant remember - must be getting old!). |
|
| Back to top |
|
|
| KingMoonMan |
| Posted: Fri Jan 09, 2004 11:03 am Post subject: |
|
|
Newbie
Joined: 31 Jan 2003
Posts: 5
|
I'm having the same issue with the r/c 20 starting the command server service. After performing the upgrade to 5.3 csd 05 from 5.2.1, the service fails to start automatically on reboot. I checked my registry, and I still do have a web administration key - with a startup value of 1.
Should I delete the entire key (WebAdministration), or just change the startup to 0? On another server that never had web admin service running the queue manager starts normally on boot, so I believe this may be a resolution.
Thanks. |
|
| Back to top |
|
|
| Prahasith |
| Posted: Fri Jan 09, 2004 12:13 pm Post subject: |
|
|
Disciple
Joined: 16 May 2003
Posts: 184
Location: Kansas City
|
1. net stop "IBM MQSeries"
2. regedit -> WebAdministration, delete the key
3. Reboot the system |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jan 09, 2004 12:43 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
the service fails to start automatically on reboot
|
Did it really fail to eventually come up? Anytime I get this error in the error log, I go check the command server, and it is really running.
I saw that on my PC (5.3 CSD05 Win2000 SP4) with 4 QMs, if I reboot the system with MQ Services (in the MS Services GUI) set to manual, nothing comes up as expected. Then if I right click on QM1 and select start, I see that it is OK after a minute. BUT if I go look in Event Viewer, I see that services tried to start the command server and failed for QM1, QM2, QM3 and QM4, and then finally started QM1. The error log at this point has 4 Error 20 errors for the 4 command servers. But QM1 and its command server, listener and channel init are all fine. There are now 4 amqxssvn.exe running in Task Manager.
If I start QM2(and QM3 and QM4) thru the MQServices GUI, it comes up clean, no errors in the log or event viewer. But there are now 13 amqxssvn.exe proccesses running.
This happens consistently.
Sometimes I can get the following to happen:
I start all my QMs theu the MQServices GUI, and MQSereries as a Windows service is still set to manual and stopped in the MS services GUI. If at this point I start the MQ service thru the MS services GUI, it crashes the listeners and channel inits. If you try and restart them, they won't. Turns out task manager shows them still running, but MQServices doesn't recognize them. I have to manually kill them, then restart them for the QM again. There are Error 20 errors pointing at the listener and the channel init at this point in the logs.
This is a legitamate bug I think, that does not fix itself.
The command server error 20 message is legit, because for some reason services is trying to start the command server b4 the QM, but luckily it seems to correct itself.
As far as the solution above with the registry hack: If I never used the Web Administrator, would I still need to do this?
I always completely uninstalled 5.2.1, dleted the directories, and then rebooted before installing 5.3. Would I still need to do this registry fix?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| JasonE |
| Posted: Fri Jan 09, 2004 2:02 pm Post subject: |
|
|
Grand Master
Joined: 03 Nov 2003
Posts: 1220
Location: Hursley
|
Something isnt right - For your first issue, I tried your exact sequence on my machine and guess what - no problems! Typical, that r/c 20 one bugs me as I have seen it mentioned loads of times but never been able to reproduce it. Problem is to debug it'll take a number of iterations of debug code 
If the problem persists at fixpack 6 (there's some new tracing in there which would help), I might be persuadable to look through a couple of traces to see what is going on. To be honest if its recreatable, I would suggest a pmr (IBM problem report) though. Wait for fixpack 6 first if you dont mind, as it'll make life easier.
Are you getting into the machine via windows termina services? What id is mq running under (dcomcnfg - identity of mqseries services).
As to the web admin - You cant *delete* the key as we keep putting it back if I recall correctly (from memory - I'm at home now!), just make sure its deleted when you try the install... |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Fri Jan 09, 2004 3:59 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| Quote: |
Are you getting into the machine via windows termina services? What id is mq running under (dcomcnfg - identity of mqseries services).
|
Never thru Windows Terminal Services, always thru pcanywhere. The above test was done on my local machine though.
The UserID MQ is running under is MUSR_MQADMIN.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
