| Author |
Message
|
| Ward |
 Posted: Thu Feb 24, 2005 3:46 am Post subject: command server doesn't start |
 |
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
Hi,
For one of the 4 queue managers on our AIX machine the command server doesn't want to start anymore. (the other 3 are OK)
All commands strmqcsv, endmqcsv and dspmqcsv give the same error message:
AMQ8101: WebSphere MQ error (20806210) has occurred.
mqrc -m 6210 gives me:
545284624 0x20806210 xecX_E_NO_SUCH_EXTENT
Not that this means anything to me...
Looking in the qmstatus.ini file showed me that the CmdSvrStatus=Running. Changing that to Ended doesn't change a thing...
We have MQSeries 5.3 with CSD05
Can anyone help me ?
Cheers,
Ward. |
|
| Back to top |
|
 |
| JT |
| Posted: Thu Feb 24, 2005 9:07 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
| Ward |
| Posted: Thu Feb 24, 2005 9:35 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
| No FDC's at all, nothing in the logs... |
|
| Back to top |
|
|
| PGoodhart |
| Posted: Thu Feb 24, 2005 9:45 am Post subject: |
|
|
Master
Joined: 17 Jun 2004
Posts: 278
Location: Harrisburg PA
|
Are your filesystems full?
run the command "df" to check..
_________________
Patrick Goodhart
MQ Admin/Web Developer/Consultant
WebSphere Application Server Admin |
|
| Back to top |
|
|
| Ward |
| Posted: Thu Feb 24, 2005 10:12 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
hiya,
good point, so just checked...
unfortunately there's ample space available... and we still have the problem
Cheers,
Ward |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Thu Feb 24, 2005 10:17 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Ward
I may be barking up the wrong tree here, but have you got sufficient memory available? I sort of recall (many beers ago) that there were some issues being caused like this when memory became tight. |
|
| Back to top |
|
|
| Ward |
| Posted: Fri Feb 25, 2005 1:31 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
another good point, but since we upgraded the machine about 6 months we haven't had any memory problems anymore...
any other suggestions anyone ?
Cheers, Ward |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Feb 25, 2005 2:28 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
Does the directory name in mqs.ini, and the directory name itself, match the qmgr name?
For example, mqs.ini should look like this:
| Quote: |
QueueManager:
Name=NG1
Prefix=/var/mqm
Directory=NG1
|
and the directory in /var/mqm/qmgrs should be called NG1 |
|
| Back to top |
|
|
| Ward |
| Posted: Fri Feb 25, 2005 2:48 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
hiya,
The name is the same but I found something else in the mqs.ini. For this particular queue manager (and only for this one) there is an extra line in the queue manager stanza stating a IPCCBaseAddress. So it looks like this:
| Quote: |
QueueManager:
Name=NG1
Prefix=/MQHA/NG1/data
IPCCBaseAddress=11
Directory=NG1 |
Maybe it has nothing to do with the problem but I don't know what it's for...
Cheers,
Ward |
|
| Back to top |
|
|
| clindsey |
| Posted: Fri Feb 25, 2005 5:26 am Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
| Quote: |
IPCCBaseAddress=11
|
This does not affect your currect problem. This stanza was needed with WMQ 5.2 to select a specific shared memory segment. The shared memory model is different in 5.3 so you can safely delete this line.
It is surprizing that you do not get an FDC on this. I suspect you will need to collect an MQ trace of the scenario and open a PMR with IBM support to analyze it.
Charlie |
|
| Back to top |
|
|
| malammik |
| Posted: Fri Feb 25, 2005 6:45 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
| Ward |
| Posted: Fri Feb 25, 2005 8:35 am Post subject: |
|
|
Voyager
Joined: 27 Jun 2001
Posts: 98
Location: Europe
|
Hiya,
Thanks for all the replies.
I've opened a PMR. They suggested the following:
| Quote: |
Can you check the SYSTEM.ADMIN.COMMAND.QUEUE is not open in exclusive by
other application (check with "dis qstatus" command). look also the qdepth
of the queue (to see if there are many msgs or not)
Can you check also there is no mismatch in qm.ini file for MQI001P qmgr.
Be sure also you start the command server with an authorise userid.
if all is correct, stop qmgr, run "amqiclen -x -m MQI001P", which will
clean ipc resources from memory if there are.
Start qmgr and try to start the command server.
|
This cleaning of the IPC recources did the trick for us...
Problem solved.
Cheers,
Ward |
|
| Back to top |
|
|
|
|
