MQSeries.net :: View topic - unable to delete QM

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » unable to delete QM

unable to delete QM

« View previous topic :: View next topic »

Author

Message

Sue_2828

Posted: Sat Feb 14, 2009 10:48 am Post subject: unable to delete QM

Apprentice

Joined: 14 Feb 2009
Posts: 37

Hi guys ,
Please advice me here ,,
I am trying to delete a queue manager on an AIX system. For some reason , I keep getting the following :

p-app-01 # dltmqm USP01
AMQ8101: WebSphere MQ error (893) has occurred.
p-app-01 # strmqm USP01
WebSphere MQ queue manager 'USP01' starting.
AMQ6119: An internal WebSphere MQ error has occurred ()
p-app-01 #

I am not sure what went wrong there and the log doesn't give me much , How can I force delete this queue manager ?

Thanks

Vitor

Posted: Sat Feb 14, 2009 10:57 am Post subject: Re: unable to delete QM

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sue_2828 wrote:

I am not sure what went wrong there and the log doesn't give me much

What little does it give you? Are there any FDC files for the time in question?
_________________
Honesty is the best policy.
Insanity is the best defence.

Sue_2828

Posted: Sat Feb 14, 2009 11:07 am Post subject:

Apprentice

Joined: 14 Feb 2009
Posts: 37

Vitor,
There are FDCs but value is 0 , they are empty .

Al Pacino

Posted: Sat Feb 14, 2009 11:25 am Post subject:

Centurion

Joined: 19 Aug 2005
Posts: 114

There got to be some FDCs , double check again. I have seen this error on windows environment but it was to do with registries. I am not sure if there is a way to force delete the queue manager on AIX .
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them."

Sue_2828

Posted: Sat Feb 14, 2009 11:29 am Post subject:

Apprentice

Joined: 14 Feb 2009
Posts: 37

What if I try to delete the queue manager's directory under /var/mqm/ ? the only place I can see the name of this queue manager is under that directory ? I am sure it is not the write way but what is the best way to clean this since I am not able to delete it or start it using the regular command lines ??

Please help me

Vitor

Posted: Sat Feb 14, 2009 11:34 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sue_2828 wrote:

the only place I can see the name of this queue manager is under that directory ?

It should be in a few other places than that.

Have you tried the commands with mqm? You could have ownership and/or file system issues which could explain the command failures & odd files.

If you can't delete the queue manager with mqm and you're getting zero length FDC files then you need to raise a PMR with IBM. Something has gone badly wrong.
_________________
Honesty is the best policy.
Insanity is the best defence.

exerk

Posted: Sat Feb 14, 2009 11:53 am Post subject:

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

If you're getting zero length FDC files...I've seen this happen quite frequently when there are problems with mounts, so that might be worth a check too.
_________________
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.

Sue_2828

Posted: Sat Feb 14, 2009 11:55 am Post subject:

Apprentice

Joined: 14 Feb 2009
Posts: 37

exerk

Posted: Sat Feb 14, 2009 12:03 pm Post subject:

Jedi Council

Joined: 02 Nov 2006
Posts: 6339

Google gave this for that Probe ID:

Quote:

Problem(Abstract)
Your queue manager ended as a result of the server being rebooted. You restarted your queue manager and noticed many FDCs with probe id XC338001 out of component xehAsySignalHandler.

Cause
The server was rebooted, without shutting down the queue manager.

Resolving the problem
This is working as designed. Shut down your Q_Managers before rebooting the system to avoid these FDC reports.

FDCs report:
Probe XC338001 out of component xehAsySignalHandler. The call to component xehAsySignalHandler returned with xecE_W_UNEXPECTED_ASYNC_SIGNAL, with major error code of SIGTERM.

Additional information
There were many reports of this FDC from various WebSphere MQ processes. These reports were all created within a few seconds. The server was rebooted without shutting down the queue manager. This explains the FDCs. Under these conditions it is expected, and desirable behavior to produce the FDCs.

_________________
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.

Vitor

Posted: Sat Feb 14, 2009 12:06 pm Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

Sue_2828 wrote:

The only thing I can find in the FDCs is the following :

That's pretty much all you ever get!

Nothing useful though really. I'd try the command with mqm then a PMR
_________________
Honesty is the best policy.
Insanity is the best defence.

fjb_saper

Posted: Sat Feb 14, 2009 1:57 pm Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Quote:

Program Name :- runmqlsr_nd |

It looks like the queue manager is not shut down properly. You may still have a listener running for that qmgr.

Why are you trying to delete a qmgr that is not properly shut down?
Is it because you cannot restart it?
When trying to restart the qmgr it may alert you to pids that are preventing a restart. Look at the processes and have the relevant app/system admin shut them down. You should then be able to restart the qmgr. I would go one step further and clean the shared memory before restarting the qmgr.

Have fun

_________________
MQ & Broker admin

sakthi_sarathi

Posted: Thu Feb 19, 2009 2:31 pm Post subject: Look at the processes and have the relevant app/system admin

Novice

Joined: 07 Dec 2008
Posts: 16

I had same kind of issue. Somehow QMGR was hung and when i restart the QMGR (manually killed all mqm pid)it didn't come up, it was saying that one pid still running. But when i check that pid it wasn't owned by mqm user. Here is my question when QMGR shutdown it will termination all the application connection right ? then how other process still running and how it is preventing QMGR come up...?

fjb_saper

Posted: Thu Feb 19, 2009 3:26 pm Post subject: Re: Look at the processes and have the relevant app/system a

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

sakthi_sarathi wrote:

It is running as a different user because it is connected to the qmgr as the user it is running under. Your shared memory is not going to be clean until that process is shutdown. It did not let go of qmgr processes and resources it acquired and as such is preventing your qmgr from coming up.

Get with the app group and find who owns that process. Ask them to recycle their app. That should allow you to bring the qmgr back up.

Enjoy

_________________
MQ & Broker admin

vandi

Posted: Thu Feb 19, 2009 4:12 pm Post subject: Re: unable to delete QM

Acolyte

Joined: 13 Dec 2008
Posts: 67

Sue_2828 wrote:

I think the root is not part of mqm group. When you reboot the server, you will do with root user. At that time, the QMgr is not shutdown before server goes down.
Please make sure that all directories under /var/mqm are owned by mqm.
Also make sure that the QMgr stanza(USP01) exists in mqs.ini(/var/mqm).

Let us know.

Thanks.
Vandi

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » unable to delete QM

Jump to:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Protected by Anti-Spam ACP