ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » General IBM MQ Support » Queue manager status ended unexpectly

Post new topic  Reply to topic
 Queue manager status ended unexpectly « View previous topic :: View next topic » 
Author Message
thimerion
PostPosted: Thu Aug 16, 2007 12:45 am    Post subject: Queue manager status ended unexpectly Reply with quote

Acolyte

Joined: 08 May 2007
Posts: 67
Location: Belgium

All,

We had an issue that the queue manager stopped and remained in status ended unexpectly ...

We had to restart it again, but have no clue why it ended.

My questions are:
- Where can we find more detail about why it ended? In the error logs we only see errors about connections that could not be made and channels that ended. --> Should not bring the QM down I'd say.
- We are missing a couple of error logs (see below), why can that be?
- Can we enlarge the error logs size or make it linear?

Some extra info:

What I noticed in the logfiles:

AMQERR03.LOG.backup.log: starts at '08/13/07 05:04:28' and ends at '08/14/07 02:44:41'
AMQERR02.LOG.backup.log: starts at '08/14/07 08:36:11' and ends at '08/14/07 08:53:43'
AMQERR01.LOG.backup.log: starts at '08/14/07 08:53:44' and ends at '08/14/07 08:59:51'

So as you can see we're missing the errors between '08/14/07 02:44:41' and '08/14/07 08:36:11'.

And 'AMQERR02.LOG.backup.log' starts with an error 'Channel program 'SYSTEM.ADMIN.SVRCONN' ended abnormally.' referring to an earlier error. (ACTION:
Look at previous error messages for channel program 'SYSTEM.ADMIN.SVRCONN' in the error files to determine the cause of the failure.)

So I suppose we're missing the logs to get the actual root cause.

Normally the other errors that can be found, shouldn't result in Q manager going down.

A million thanks for reading this qtn.
Back to top
View user's profile Send private message
sidharth_bora
PostPosted: Thu Aug 16, 2007 1:05 am    Post subject: Reply with quote

Voyager

Joined: 24 Nov 2005
Posts: 87

Hi,

Are there any FDC. ?

regds
Sid
Back to top
View user's profile Send private message
thimerion
PostPosted: Thu Aug 16, 2007 1:29 am    Post subject: Reply with quote

Acolyte

Joined: 08 May 2007
Posts: 67
Location: Belgium

sidharth_bora wrote:
Hi,

Are there any FDC. ?

regds
Sid


Yes,
four of those things are generated:
-rw-r--r-- 1 mqm mqm 54300 Aug 14 08:24 AMQ19395.0.FDC
-rw-r--r-- 1 mqm mqm 62092 Aug 14 08:24 AMQ19393.0.FDC
-rw-r--r-- 1 mqm mqm 48452 Aug 14 09:14 AMQ21748.0.FDC
-rw-r--r-- 1 mqm mqm 11451 Aug 14 16:26 AMQ20704.0.FDC

$ grep Probe AMQ19395.0.FDC AMQ19393.0.FDC AMQ21748.0.FDC AMQ20704.0.FDC
AMQ19395.0.FDC:| Probe Id :- HL149111 |
AMQ19395.0.FDC:| Probe Type :- MSGAMQ000E |
AMQ19395.0.FDC:| Probe Severity :- 4 |
AMQ19395.0.FDC:| Probe Description :- AMQ6090: WebSphere MQ was unable to display an error |
AMQ19395.0.FDC:| Probe Id :- XC028018 |
AMQ19395.0.FDC:| Probe Type :- INCORROUT |
AMQ19395.0.FDC:| Probe Severity :- 2 |
AMQ19395.0.FDC:| Probe Description :- AMQ6125: An internal WebSphere MQ error has occurred. |
AMQ19395.0.FDC:| Probe Id :- XC130003 |
AMQ19395.0.FDC:| Probe Type :- HALT6109 |
AMQ19395.0.FDC:| Probe Severity :- 1 |
AMQ19395.0.FDC:| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
AMQ19393.0.FDC:| Probe Id :- ZX005020 |
AMQ19393.0.FDC:| Probe Type :- MSGAMQ5008 |
AMQ19393.0.FDC:| Probe Severity :- 2 |
AMQ19393.0.FDC:| Probe Description :- AMQ5008: An essential WebSphere MQ process 19395 |
AMQ19393.0.FDC:| Probe Id :- ZX005025 |
AMQ19393.0.FDC:| Probe Type :- MSGAMQ5008 |
AMQ19393.0.FDC:| Probe Severity :- 2 |
AMQ19393.0.FDC:| Probe Description :- AMQ5008: An essential WebSphere MQ process 19397 |
AMQ21748.0.FDC:| Probe Id :- XC338001 |
AMQ21748.0.FDC:| Probe Type :- MSGAMQ6209 |
AMQ21748.0.FDC:| Probe Severity :- 3 |
AMQ21748.0.FDC:| Probe Description :- AMQ6209: An unexpected asynchronous signal (2 : |
AMQ21748.0.FDC:| Probe Id :- XC338001 |
AMQ21748.0.FDC:| Probe Type :- MSGAMQ6209 |
AMQ21748.0.FDC:| Probe Severity :- 3 |
AMQ21748.0.FDC:| Probe Description :- AMQ6209: An unexpected asynchronous signal (2 : |
AMQ21748.0.FDC:| Probe Id :- XC338001 |
AMQ21748.0.FDC:| Probe Type :- MSGAMQ6209 |
AMQ21748.0.FDC:| Probe Severity :- 3 |
AMQ21748.0.FDC:| Probe Description :- AMQ6209: An unexpected asynchronous signal (1 : |
AMQ20704.0.FDC:| Probe Id :- XC338001 |
AMQ20704.0.FDC:| Probe Type :- MSGAMQ6209 |
AMQ20704.0.FDC:| Probe Severity :- 3 |
AMQ20704.0.FDC:| Probe Description :- AMQ6209: An unexpected asynchronous signal (1 : |
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Aug 16, 2007 1:41 am    Post subject: Reply with quote

Grand High Poobah

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

You don't say what version of MQ you're on, but a lot of those FDC probes are claimed as fixed in some of the v5.3 CSDs.

If you're not on the latest version, you might want to update.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Gaya3
PostPosted: Thu Aug 16, 2007 1:43 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

Hi

http://www-1.ibm.com/support/docview.wss?uid=swg21193049

http://www-1.ibm.com/support/docview.wss?uid=swg1IY66326

http://www-1.ibm.com/support/docview.wss?uid=swg21178058


Search the probe ids in google and get it..

I suspect you restarted your machine with out shutting down your queue manager
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
thimerion
PostPosted: Thu Aug 16, 2007 2:16 am    Post subject: thanks Reply with quote

Acolyte

Joined: 08 May 2007
Posts: 67
Location: Belgium

Thanks for taking me to the right direction.

Looking at the probe id's I also can see the system was low on kernel resources.

I will also take a look what patches that are available.

Tim
Back to top
View user's profile Send private message
thimerion
PostPosted: Thu Aug 16, 2007 3:07 am    Post subject: Error logs Reply with quote

Acolyte

Joined: 08 May 2007
Posts: 67
Location: Belgium

To all,

Anyone an idea why we have a gap of couple of hours in the error logs as described above ?

Tim


Last edited by thimerion on Thu Aug 16, 2007 3:52 am; edited 1 time in total
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Thu Aug 16, 2007 3:49 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Please don't post in big letters.

Maybe there was nothing to log during that gap.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
thimerion
PostPosted: Thu Aug 16, 2007 4:13 am    Post subject: there was Reply with quote

Acolyte

Joined: 08 May 2007
Posts: 67
Location: Belgium

That is impossible, because it was logging every quarter of an hour several channel errors which could not connect.

Can it be a consequence of circular logging ? I would think that it then deletes the oldest log to start a new log, but it did delete one in between I suppose.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » General IBM MQ Support » Queue manager status ended unexpectly
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
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.