| Author |
Message
|
| lequimm |
 Posted: Wed Oct 12, 2005 4:13 am Post subject: [newbe] how to test if a config manager is runnning |
 |
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
hello,
I have in the toolkot to connect to a config manager to deploy a flow. But the config manager is not responding. How can I know that the config manager is well running or not to know if the problem is from my pc or from the config manager. Is there a command running on the host of the config manager to test that ?
thank's in advance, |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Oct 12, 2005 4:15 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
mqsilist will show you the status of any configmgr/broker processes on a machine.
What does the Toolkit show you, when you try to connect, that tells you the configmgr is not responding?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:19 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
he tell me : an exception occured while communicating with the configuration manager on xxxxxx.
Reason : websphere studio is experiencing problems communicating with the configuration manager on xxxxxx |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:21 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
i have just run mqsilist and I see the config manager running, strange  ,... |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:25 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
I see BIP8099I in front of the queue manager name, is it normal ?
when i want to stop the queue manager with mqsistop -i queuemanager name it don't find the queue manager. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 4:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay. You need to be a little more specific about your output.
mqsistop doesn't stop the queue manager, and doesn't use the queue manager name.
mqsistop -i is an immediate stop, and is only used to stop a broker, and should only be used if nothing else has worked.
You should look, carefully, at the system log of the configuration manager machine.
You should also confirm that the configmgr's queue manager has an active listener running on the port you configured.
Also, is this a *new* installation, or an existing installation that previously worked?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:41 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
thank's for the explanations  .
the installation is not a first install and runned before.
for the queue manager of the config manager is it listed with mqsilist ? because with mqsilist I see only one broker and the config manager. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:45 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
I have a strange message when typing mqsistop ConfigMgr or mqsistart :
"a previous command was issued to stop this component or it has never been started. this component may be started, changed or deleted.
I think that the mqsistop -i has not good ended  . |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 4:46 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
mqsilist doesn't show you anything about queue managers.
try "dspmq".
Also, what platform are you running on? I'm guessing windows, since I'm assuming this is not v6. But I don't want to make too many assumptions.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:48 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
yes it is on window .
the dspmq command gave me the qmanager |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 4:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Okay. So the queue manager is running, and the configmgr is running.
Are there errors in the Event Log -> Application Log from WBIMB?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 4:59 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
yep ! there is an error in the eventvwr !
[ConfigMgr]Error in call NetUserGetLocalGroups() to the NT security domain with return code 5. A component of WebSphere Business Integration Message Brokers is attempting to call the NT security domain. The security subsystem returned an error code. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:04 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
ah!
Restart the configmgr. It has lost it's connection to the domain controller, and needs to be restarted before it can reestablish this and authorize anyone.
If this happens more than once in the next few months, you should open a PMR with IBM.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| lequimm |
| Posted: Wed Oct 12, 2005 5:55 am Post subject: |
|
|
Apprentice
Joined: 18 Aug 2005
Posts: 26
|
I have tried to restart the CM, but there is something strange. The stop command block, the CM is marqued as running in mqsilist. it is also marqued as running when i type mqsistart ConfigMgr, but in the service of windows it is marqued as not running .
There is also maybe another reason to this problem, the security is chaning where I work, maybe they have do some changes that affect the access to the CM, ... |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Oct 12, 2005 5:58 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
well, it might take a while to stop.
You can also attempt to kill the configmgr process itself, but you're better off seeing if mqsistop will complete.
And then, if the broker is not a production broker, it might be better to just reboot the entire machine.
Also, if the security domain is still unavailable, then configmgr won't be able to authorize your shutdown... so check to see if those guys are done their work, too!
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
