| Author |
Message
|
| jhaavinash |
 Posted: Fri Dec 17, 2004 4:29 am Post subject: kill signal 30(urgent) |
 |
|
Novice
Joined: 17 Dec 2004
Posts: 15
Location: Sweden
|
Greetings e'bdy.
Our production MQ has gone nuts!
Almost everyweekend it generates following error and a big FDC file (around 28 MB). Find the extract of error and FDC. Does 'ne bdy has any clue??
Error :
AMQ6183: An internal MQSeries error has occurred.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 72936.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
*************************************
AMQ6209: An unexpected asynchronous signal (30) has been received and ignored.
EXPLANATION:
Process 72936 received an unexpected asynchronous signal and ignored it. This
has not caused an error but the source of the signal should be determined as it
is likely that the signal has been generated externally to MQSeries. Use the
UNIX system command kill with option -l to determine the symbolic name for
signal 30.
ACTION:
Determine the source of the signal and prevent it from re-occurring.
*************************
FDC file header:
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Wednesday December 15 XX:XX:XX NFT 2004 |
| Host Name :- ******* (AIX 5.1) |
| PIDS :- 5765B73 |
| LVLS :- 520 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| Build Date :- Aug 1 2002 |
| CMVC level :- p520-CSD05G |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (root) |
| Program Name :- amqcrsta_nd |
| Process :- 00072936 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (30) has |
| been received and ignored. |
| Arith1 :- 30 1e |
| Arith2 :- 72936 11ce8 |
_________________
contact admin Jha
WebSphere MQ grp |
|
| Back to top |
|
 |
| Nigelg |
| Posted: Fri Dec 17, 2004 6:11 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| On AIX signal 30 is SIGUSR1. Somebody or some process is targeting your WMQ processes with a kill -30 command. Your job is to find out who; this is not quite as hard as it sounds, because for the signal to be sent to amqcrsta it must eitehr be root or somebody in the mqm group. |
|
| Back to top |
|
|
| jhaavinash |
| Posted: Fri Dec 17, 2004 6:16 am Post subject: |
|
|
Novice
Joined: 17 Dec 2004
Posts: 15
Location: Sweden
|
Yes you are correct. But im not quite sure what i should do to exactly pinpoint the user/process which is causing trouble. Can you help?
_________________
contact admin Jha
WebSphere MQ grp |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Dec 17, 2004 6:17 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I would see if you have some scripts scheduled to perform backups, that may be attempting to shut down MQ somehow before a backup is performed.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| jhaavinash |
| Posted: Fri Dec 17, 2004 6:58 am Post subject: |
|
|
Novice
Joined: 17 Dec 2004
Posts: 15
Location: Sweden
|
But i've already checked for that possibility. Don't we have a way to exactly pinpoint which process/user is the actual reason?
_________________
contact admin Jha
WebSphere MQ grp |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Dec 17, 2004 7:09 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| No that is up to you. The FFST just shows that somebody is doing it, but it does not contain any information about who. |
|
| Back to top |
|
|
|
|
