| Author |
Message
|
| drona_wipro |
 Posted: Fri Jun 11, 2004 4:03 am Post subject: |
 |
|
Apprentice
Joined: 07 May 2004
Posts: 35
Location: London
|
On Friday June 4th 2004
When i am trying to restart the queue manager under mqm user,
user:/var/mqm/qmgrs >strmqm
AMQ8041: The queue manager cannot be restarted or deleted because processes,
that were previously connected, are still running.
Process 8351 is still running.
Process 8346 is still running.
Process 8347 is still running.
Process 8338 is still running.
Process 8140 is still running.
AMQ7018: The queue manager operation cannot be completed.
Then i terminated all the processes shown above(8351, 8346, 8347, 8338, 8140)
from then onwards we are getting this error.. whenever we restart a queue manager under mqm user
user:/var/mqm >strmqm
AMQ6004: An error occurred during MQSeries initialization or ending.
It is creating an FDC with Probe Id ZX005001
from zxcProcessChildren
Probe Description :- AMQ5009: MQSeries agent process 8351 has terminated
This is caused because...
While ending the queue manager, it is trying to clean the process 8351 that no longer exists( already killed the process 8351 on Friday Morning 4th June 2004)
Even after getting the error every time we start the queue manager, it's not generating the FDC(it generated once) and it's not updating the log also.
How to resolve this problem.
_________________
chandra mouli
IBM Certified Specialist on MQSeries/WMQ
IBM Certified Specialist on WebSphere MQ Integrator(WMQI) |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Fri Jun 11, 2004 4:21 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
Donna,
this is the result of 'something' changed.
what you need to find is 'what' changed and 'why'.
you need to do some digging into your change archive for this machine!
Please ask yourself the other questions, and see if you can find the root cause.
Unless you made some change to the MQ configuration or settings I think the root cause has nothing to do with MQ...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| drona_wipro |
| Posted: Fri Jun 11, 2004 4:58 am Post subject: |
|
|
Apprentice
Joined: 07 May 2004
Posts: 35
Location: London
|
under root, it starts the queue manager fine. when coming under mqm , its not starting the queue manager.
What i did is " I added root user to the group mqm"
But it didn't resolve.
_________________
chandra mouli
IBM Certified Specialist on MQSeries/WMQ
IBM Certified Specialist on WebSphere MQ Integrator(WMQI) |
|
| Back to top |
|
|
| Michael Dag |
| Posted: Fri Jun 11, 2004 5:05 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
I think you are missing the point...
what was the situation 3 weeks ago when all was running fine...
what changed between running fine and not starting.
not what did you do afterwards to make it work again...
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 11, 2004 5:28 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| I see you've cleaned up the semaphores and shared memory associated with mqm and performed restarts of the queue manager, have you performed a reboot of the server? Does this issue still exist after the server is bounced? |
|
| Back to top |
|
|
| drona_wipro |
| Posted: Fri Jun 11, 2004 5:43 am Post subject: |
|
|
Apprentice
Joined: 07 May 2004
Posts: 35
Location: London
|
no.. i didn't reboot the server
If i reboot the server, it will solve my problem(means can i able to start the queue manager under mqm user successfully)
_________________
chandra mouli
IBM Certified Specialist on MQSeries/WMQ
IBM Certified Specialist on WebSphere MQ Integrator(WMQI) |
|
| Back to top |
|
|
| JT |
| Posted: Fri Jun 11, 2004 5:49 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| If i reboot the server, it will solve my problem(means can i able to start the queue manager under mqm user successfully) |
My guess would be "yes". Of course you could spend more time investigating what might be a transitory problem, i.e. why process 8351 may not have been cleared properly from the system. |
|
| Back to top |
|
|
|
|
