| Author |
Message
|
| sumit |
 Posted: Fri Aug 08, 2008 1:13 pm Post subject: Command server getting down. |
 |
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
HI,
My qmgr's command server is getting down. Whenever I login to the server, I need to add my id everytime to mqm gp to access the qmgr objects. As soon as I add it, the command server works fine. But when I logoff from server and login again, I find that the status of command server is 'stopped'.
There is no FDC, there are just error logs displaying the same message accross the log file :
8/8/2008 16:39:22 - Process(2040.22) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
AMQ7227: WebSphere MQ encountered the following network error: The RPC server
is unavailable.
EXPLANATION:
MQ failed to successfully complete a network operation due to the specified
error. If the error is encountered on systems that are part of a Windows 2000
domain it can indicate incorrect DNS or WINS configuration.
ACTION:
Ensure that your network is functioning correctly. On the Windows platform
check DNS and/or WINS settings to ensure that domain controllers, used for
authentication or authorisation functions, are accessible.
I am using MQ v6.0.2.3 on Windows 2003 Server.
I tried to google it and it says that the user must be a part of mqm group, this is what I am.
Any pointers??? 
_________________
Regards
Sumit |
|
| Back to top |
|
 |
| sami.stormrage |
| Posted: Sat Aug 09, 2008 12:45 pm Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
Is it a config managers Queuemanager?
Was there any microsoft patch applied?
Check if there are any errors in the Event and security logs.
And user in the sense, MUSR_MQADIMIN should be in the mqm group.
_________________
*forgetting everything  * |
|
| Back to top |
|
|
| sumit |
| Posted: Sat Aug 09, 2008 1:14 pm Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Quote: |
| Is it a config managers Queuemanager? |
no, its not a config manager, its a queue manager which is a part of cluster and some application interact with this in API mode.
| Quote: |
| Was there any microsoft patch applied? |
Something I am not sure of. Need to check with network team. But how a patch can effect a queue manager to behave in this way?
| Quote: |
Check if there are any errors in the Event and security logs.
|
Checked but didn't find anything significant. Errors are also pointing the queue manager restart. This shows the server might have been rebooted. But even after restart, the command server should start.
| Quote: |
| And user in the sense, MUSR_MQADIMIN should be in the mqm group. |
It is a part of mqm group. I have even added my id in 'users' as well as in mqm group.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| sumit |
| Posted: Sat Aug 09, 2008 1:19 pm Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
And another surprising thing is that when I login to the server and tried to access the queue manager, its not allowing to access it.
C:\>runmqsc Test
5724-H72 (C) Copyright IBM Corp. 1994, 2004. ALL RIGHTS RESERVED.
Starting MQSC for queue manager Test.
AMQ8135: Not authorized.
No MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
I need to remove my id from mqm and then add it back to mqm to make it work!!!! 
If there is a problem with my access or id, then it should not even work when I add my id again in mqm gp. 
_________________
Regards
Sumit |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Aug 10, 2008 4:17 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Read up on Domain accounts versus local accounts, which I think is your issue here.
The Quick Beginnings manual, Security considerations and Configuring WebSphere MQ accounts are the most pertinent sections.
_________________
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 |
|
|
| sami.stormrage |
| Posted: Sun Aug 10, 2008 8:43 am Post subject: |
|
|
Disciple
Joined: 25 Jun 2008
Posts: 186
Location: Bangalore/Singapore
|
Yeah!! even we faced a similar issue on one on our windows servers.. think there is something going on when the server is rebooted. And there was a bad patch from microsoft which started it all.. ...
_________________
*forgetting everything * |
|
| Back to top |
|
|
| ranganathan |
| Posted: Mon Aug 11, 2008 7:25 am Post subject: |
|
|
Centurion
Joined: 03 Jul 2008
Posts: 104
|
| exerk wrote: |
Read up on Domain accounts versus local accounts, which I think is your issue here.
The Quick Beginnings manual, Security considerations and Configuring WebSphere MQ accounts are the most pertinent sections. |
I concur with Exerk.. unless you take all the considerations while installing MQ in a domain, many problems arise if you configure MQ in a network. Please read the platform specific Quick Beginnings manual.
Note: When i faced a problem akin to the one above.. as a workaround i created a local account in my machine and configured all the stuff.  |
|
| Back to top |
|
|
| sumit |
| Posted: Tue Aug 12, 2008 11:59 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| Quote: |
| Note: When i faced a problem akin to the one above.. as a workaround i created a local account in my machine and configured all the stuff. |
I already have my local account as a part of mqm group. But I have to delete and add that everytime I login into the server.
| Quote: |
| The Quick Beginnings manual, Security considerations and Configuring WebSphere MQ accounts are the most pertinent sections. |
This section talks about the domain controller, which is not applicable in this scenerio.
Well, regarding a bad Windows patch that can cause this problem... I hope in that case it should not work even when I add my id again in mqm group. But I can't deny its occurance too. I am in contact with server team to know about any patching.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Aug 12, 2008 12:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The original post said:
| Quote: |
8/8/2008 16:39:22 - Process(2040.22) User(MUSR_MQADMIN) Program(amqzlaa0.exe)
AMQ7227: WebSphere MQ encountered the following network error: The RPC server is unavailable.
|
Now the RPC server is a windows OS part and has nothing to do with the MQ Command server!
If windows is not running correctly why would you expect MQ to be running correctly on the box?
Fix the windows problem first! 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| sumit |
| Posted: Thu Aug 14, 2008 11:42 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
Thanks fjb_saper for your advise.
Although there was no patch applied to the server, somehow the command server is running proeprly. I believe the problem with Windows has been rectified.
_________________
Regards
Sumit |
|
| Back to top |
|
|
|
|
