| Author |
Message
|
| Luca81 |
 Posted: Thu Mar 01, 2007 5:21 am Post subject: Error code 20 starting Command Server WebSphere MQ. HELP PLS |
 |
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
Hi all,
I' m new... and my english is not very good... sorry
I have MQ 5.3 and CSD 07... I know that the last is 13 but i'm only a poor consultant  and my boss does not want install the last CSD...
I had a problem while starting MQ in the production environment.
This is the problem
| Code: |
3/1/2007 12:14:21
AMQ7880: Error code 20 starting SWBIMQP1/Command Server WebSphere MQ service.
EXPLANATION:
The service was unable to start SWBIMQP1/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. |
In the same PC i have 2 MQ:
SWBIMQP1 = PRODUCTION
SWBIMQC1 = TEST
SWBIMQC1 is always stopped (Queue Manager, Command Server, Channels Initiators and all listeners are stopped and set "manual")...
We use it is very rare cases...
This morning SWBIMQP1 was stopped and i tryed to turn on it but I had the previous.
Please help me...
If u need more information ask me.
Thx to all |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Thu Mar 01, 2007 5:23 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Why does your boss not want to use CSD13?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Luca81 |
| Posted: Thu Mar 01, 2007 5:26 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| jefflowrey wrote: |
| Why does your boss not want to use CSD13? |
He doesn't want have problems during the installation... and the production evironment works fine with CSD 7. Can be this the problem? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 5:28 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Why was the queue manager stopped, i.e. was it stopped by command or did it crash?
It's also worth displaying the command server status. I have seen the situation where, for bizarre reasons, the queue manager was unable to accept the command server because the start up was not fully completed. Once the start up was completed, recovery brought the command server up.
It's a long shot but worth checking. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 5:29 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Luca81 wrote: |
| jefflowrey wrote: |
| Why does your boss not want to use CSD13? |
He doesn't want have problems during the installation... and the production evironment works fine with CSD 7. Can be this the problem? |
What problems is he expecting? How highly does he rate the risk? How does he rate this against the risk of using a CSD that's as old as the hills?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Luca81 |
| Posted: Thu Mar 01, 2007 5:36 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| Vitor wrote: |
What problems is he expecting? How highly does he rate the risk? How does he rate this against the risk of using a CSD that's as old as the hills? |
I will try to install CSD 13... i will speak with him... but it worked well for a lot of time with CSD 07... I want understant the problem and resolve it |
|
| Back to top |
|
|
| Luca81 |
| Posted: Thu Mar 01, 2007 5:39 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| Vitor wrote: |
Why was the queue manager stopped, i.e. was it stopped by command or did it crash?
It's also worth displaying the command server status. I have seen the situation where, for bizarre reasons, the queue manager was unable to accept the command server because the start up was not fully completed. Once the start up was completed, recovery brought the command server up.
It's a long shot but worth checking. |
The QM was stopped for a creash
THis is the MQ SWBIMQP1 situation:
Queue Manager Running Automatic
Command Server Stopped Automatic
Chanel Initiator Running Automatic
Listeners (4) All Stopped Automatic
If i try to start Command Server or Listener i have the error |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Mar 01, 2007 5:43 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Are there additional errors about trying to start the Command Server?
Are there FDC files that have been created?
Can you bring the queue manager down gracefully after you've tried to start it, and then try starting it again? That is, does endmqm work without needing to force?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Luca81 |
| Posted: Thu Mar 01, 2007 5:51 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| jefflowrey wrote: |
Are there additional errors about trying to start the Command Server?
Are there FDC files that have been created?
Can you bring the queue manager down gracefully after you've tried to start it, and then try starting it again? That is, does endmqm work without needing to force? |
I m not a big expert of MQ... this is not my work... i try help my boss... so be patience with me  sorry.
What are FDC files?
I use only the GUI of MQ... i don t use the command line commands...
I can stop QM and i can start... bui i can t start listeners and command server |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 5:51 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Luca81 wrote: |
The QM was stopped for a creash
|
It's probably worth looking into why it crashed, as this may have a bearing on why bits of it won't restart.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Mar 01, 2007 5:54 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Vitor wrote: |
| Luca81 wrote: |
The QM was stopped for a creash
|
It's probably worth looking into why it crashed, as this may have a bearing on why bits of it won't restart. |
...and you could always explain to your boss that maybe the outage for upgrading to a newer level is now justified  |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 5:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Luca81 wrote: |
What are FDC files?
|
These are files created by the queue manager when it encounters an unexpected condition. In the errors folder in the queue manager file structure IIRC.
| Luca81 wrote: |
I use only the GUI of MQ... i don t use the command line commands...
I can stop QM and i can start... bui i can t start listeners and command server |
You get far more useful options in the command line for this kind of problem situation.
It's also worth mentioning to your boss that if you were on an up to date CSD you could get support from IBM. You can still contact them of course, but all they'll say is "upgrade"
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 5:57 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kevinf2349 wrote: |
| Vitor wrote: |
| Luca81 wrote: |
The QM was stopped for a creash
|
It's probably worth looking into why it crashed, as this may have a bearing on why bits of it won't restart. |
...and you could always explain to your boss that maybe the outage for upgrading to a newer level is now justified |
Good point - if he's worried about the risk, now is the time. It can't get worse....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Luca81 |
| Posted: Thu Mar 01, 2007 6:00 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2007
Posts: 62
|
| Vitor wrote: |
| Luca81 wrote: |
What are FDC files?
|
These are files created by the queue manager when it encounters an unexpected condition. In the errors folder in the queue manager file structure IIRC.
| Luca81 wrote: |
I use only the GUI of MQ... i don t use the command line commands...
I can stop QM and i can start... bui i can t start listeners and command server |
You get far more useful options in the command line for this kind of problem situation.
It's also worth mentioning to your boss that if you were on an up to date CSD you could get support from IBM. You can still contact them of course, but all they'll say is "upgrade" |
ok ok. I copied the error from the FDC file... sorry but I m a noob of MQ .
Yes i know... IBM says "upgrade". I will upgrade but if the error persist? what can i do? |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 01, 2007 6:04 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Luca81 wrote: |
| I will upgrade but if the error persist? what can i do? |
Evaluate the error then, which may be different to the error now. Specifically, if it still happens after upgrade and after you've tried the "down and up" strategy jefflowrey suggested, Google and search this board for the probeId you'll find in the top of the file.
And pass the FDC to IBM of course.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
