Author |
Message
|
thimerion |
Posted: Thu Aug 16, 2007 12:45 am Post subject: Queue manager status ended unexpectly |
|
|
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 |
|
 |
sidharth_bora |
Posted: Thu Aug 16, 2007 1:05 am Post subject: |
|
|
 Voyager
Joined: 24 Nov 2005 Posts: 87
|
Hi,
Are there any FDC. ?
regds
Sid |
|
Back to top |
|
 |
thimerion |
Posted: Thu Aug 16, 2007 1:29 am Post subject: |
|
|
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 |
|
 |
Vitor |
Posted: Thu Aug 16, 2007 1:41 am Post subject: |
|
|
 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 |
|
 |
Gaya3 |
Posted: Thu Aug 16, 2007 1:43 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
|
Back to top |
|
 |
thimerion |
Posted: Thu Aug 16, 2007 2:16 am Post subject: thanks |
|
|
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 |
|
 |
thimerion |
Posted: Thu Aug 16, 2007 3:07 am Post subject: Error logs |
|
|
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 |
|
 |
jefflowrey |
Posted: Thu Aug 16, 2007 3:49 am Post subject: |
|
|
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 |
|
 |
thimerion |
Posted: Thu Aug 16, 2007 4:13 am Post subject: there was |
|
|
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 |
|
 |
|