| Author |
Message
|
| shanu |
 Posted: Thu Aug 17, 2006 12:49 am Post subject: FDC Generated in AIX Unix |
 |
|
Acolyte
Joined: 03 Jun 2006
Posts: 60
Location: India
|
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday August 17 10:49:54 PAKST 2006 |
| Host Name :- Regatta1 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.7 CSD07 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC267011 |
| Application Name :- MQM |
| Component :- xehAsySignalMonitor |
| Build Date :- May 27 2004 |
| CMVC level :- p530-07-L040527 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000007 (MQADMIN) |
| Program Name :- amqrmppa |
| Process :- 00081570 |
| Thread :- 00000002 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6109: An internal WebSphere MQ error has occurred. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 33 21 |
| Arith2 :- 81570 13ea2 |
| Comment1 :- SIGDANGER |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xehAsySignalMonitor
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsReleaseThreadMutexSem
--} xcsReleaseThreadMutexSem rc=OK
-} xehHandleAsySignal rc=OK
-{ xcsFFST
Component Dumps (Thread 00000002)
-------------------------------------
$ Probe Id :- XC267011
Application Name :- MQMksh: Probe: not found.
$
ksh: Application: not found.
$
$
$ ls
history2408 nohup.out |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Aug 17, 2006 1:20 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
What version of MQ? What CSDs? Under what circumstances is the FDC produced? Anything? 
Specificlly, if you're on 5.3 with CSD 5 or lower:
a) Why????
b) Is this relevant?
http://www-1.ibm.com/support/docview.wss?uid=swg1IY41943
(See IY44839)
More details please?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Aug 17, 2006 1:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| Quote: |
| | LVLS :- 530.7 CSD07 | |
A newer CSD is in order, at some point.
| Quote: |
| | Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL | |
Someone sent a process a signal that it wasn't expecting.
| Quote: |
| | Comment1 :- SIGDANGER | |
SIGDANGER has to do with running out of paging space. Are you running out of paging space?
| Quote: |
| Probe Id :- XC267011 | |
I searched IBM's website for this, and didn't find anything relevant to SIGDANGER.
If you don't think you're running low on paging space, then you should open a PMR. And plan to apply CSD12 soon.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Aug 17, 2006 1:43 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jefflowrey wrote: |
| Quote: |
| | LVLS :- 530.7 CSD07 | |
A newer CSD is in order, at some point.
|
I need new batteries in these glasses, or more coffeee 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Aug 17, 2006 5:41 am Post subject: Re: FDC Generated in AIX Unix |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| shanu wrote: |
| xehAsySignalMonitor / xecE_W_UNEXPECTED_ASYNC_SIGNAL |
MQ processes ignore most asynchronous signals most of the time. But most of the time they also write out an FDC to keep a record of the fact the signal was received. This can be of use, in your specific case, for example - it could give a warning of the precursors of a very big system-wide problem (eg. the system is running out of virtual memory). Other occasions these FDCs can be written is on systems that are shut down without first ending queue managers, listeners etc. Many systems send SIGTERM to all running processes as part of the first stage of shutdown. MQ ignores these, but writes the FDCs. If you ever need to present a problem description to MQ support engineers, these FDCs can be very helpful in pinpointing what actions were taken against MQ processes by administrators or the system. So, keep them archived and safe, just like the other contents of /var/mqm/errors. |
|
| Back to top |
|
|
| shanu |
| Posted: Thu Aug 17, 2006 5:25 pm Post subject: |
|
|
Acolyte
Joined: 03 Jun 2006
Posts: 60
Location: India
|
Here are version details.
Name: WebSphere MQ
Version: 530.7 CSD07
CMVC level: p530-07-L040527
BuildType: IKAP - (Production)
We have some MQ programs to read and write from/into the queues. These java programs are placed in the /mqm folder. While MQ is installed in /var partition
The disk space was completed utilized for this "mqm" partition yesterday.
Could this have caused the problem?
Thanks
Shanu |
|
| Back to top |
|
|
| Nigelg |
| Posted: Fri Aug 18, 2006 12:22 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
No.
You already have the answer - SIGDANGER is sent by AIX to all processes when the system as a whole is low on paging space.
_________________
MQSeries.net helps those who help themselves.. |
|
| Back to top |
|
|
|
|
