| Author |
Message
|
| thravi |
 Posted: Mon Nov 08, 2004 9:34 am Post subject: Please help me understand this FDC |
 |
|
Novice
Joined: 16 Jul 2004
Posts: 13
|
Hi,
Following FDC has been generated. I can't figure out what it means. Can anybody help me..
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Monday November 08 02:51:17 GMT 2004 |
| Host Name :- ss55pinvmsg01 (SunOS 5. |
| PIDS :- 5724B4103 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for Sun Solaris |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00062644 (mcquser) |
| Program Name :- runmqsc |
| Process :- 00009271 |
| 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 :- 2 2 |
| Arith2 :- 9271 2437 |
| Comment1 :- SIGINT |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xcsFreeMem
} xcsFreeMem rc=OK
{ xehAsySignalMonitor
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsFFST
Process Control Block
ff0a66f0 58494850 00000AA0 00002437 00000000 XIHP... ..$7....
ff0a6700 00000002 00022120 00022C08 00000000 ......! ..,.....
ff0a6710 00000000 00000001 00000001 00010000 ................
ff0a6720 00000400 FEDD0000 00000000 00000000 ....þÝ..........
ff0a6730 00000000 00000000 00000000 00000000 ................
ff0a6740 to ff0a6b10 suppressed, 62 lines same as above
ff0a6b20 00000000 00000000 00000000 FFFFFFFF ................
ff0a6b30 00000000 00000000 00000000 00000000 ................
ff0a6b40 00000001 00000001 00000000 00000000 ................
ff0a6b50 00000008 FEF9D108 00000000 00000000 ....þùÑ.........
ff0a6b60 00000000 00000000 00000000 00000000 ................
ff0a6b70 00000008 FEF9D108 00000000 00000000 ....þùÑ.........
ff0a6b80 00000000 00000000 00000000 00000000 ................
ff0a6b90 00000008 FEF9D108 00000000 00000000 ....þùÑ.........
ff0a6ba0 00000000 00000000 00000000 00000000 ................
ff0a6bb0 to ff0a6bc0 suppressed, 2 lines same as above
ff0a6bd0 00000008 FEF9D108 00000000 00000000 ....þùÑ.........
ff0a6be0 00000000 00000000 00000000 00000000 ................
ff0a6bf0 00000008 FEF9D108 00000000 00000000 ....þùÑ.........
ff0a6c00 00000000 00000000 00000000 00000000 ................
ff0a6c10 00000000 00000001 00000000 00000000 ................
ff0a6c20 00000000 00000000 00000000 00000000 ................
ff0a6c30 to ff0a6cd0 suppressed, 11 lines same as above
ff0a6ce0 00000002 00026060 00000000 00000001 ......``........
ff0a6cf0 00022B70 00000000 00000000 00000000 ..+p............
ff0a6d00 00000000 00004356 00000000 00000000 ......CV........
ff0a6d10 00000000 00000001 00000001 00000000 ................
ff0a6d20 00000000 00000000 00000000 00000000 ................
ff0a6d30 00000000 00000000 00000000 00000000 ................
ff0a6d40 00021CE8 00000000 00000000 00000000 ...è............
ff0a6d50 00000000 00000000 00000000 00000000 ................
ff0a6d60 to ff0a7180 suppressed, 67 lines same as above
Common Services Control Block
23700 58494820 000008B0 00000001 00000001 XIH ...°........
23710 00000000 00000000 6D637175 73657200 ........mcquser.
23720 0000F4B6 00000333 00000000 00000000 ..ô¶...3........
23730 00028070 000240B0 00024180 00024060 ...p..@°..A...@`
23740 00000000 00000003 2F766172 2F6D716D ......../var/mqm
23750 00000000 00000000 00000000 00000000 ................
23760 to 23f90 suppressed, 132 lines same as above
23fa0 00000000 00000000 00000000 00028070 ...............p
Thread Control Block
22c00 58494854 00000A48 XIHT...H
22c10 00000002 00000000 00000000 00022120 ..............!
22c20 00000000 00000000 00000010 00000001 ................
22c30 00000000 00000001 00000001 00000000 ................
22c40 00000000 00000000 00000000 00000000 ................
22c50 to 22e30 suppressed, 31 lines same as above
22e40 00000000 00000000 FFFFFFFF 00000000 ................
22e50 00000000 00000000 00000000 00000000 ................
22e60 00000004 00000000 00000000 00000000 ................
22e70 00000000 00000000 00000000 00000000 ................
22e80 00000000 00000000 00000000 00000000 ................
22e90 00000000 00000001 00000000 00000000 ................
22ea0 00000000 00000000 00000000 00000000 ................
22eb0 to 22ed0 suppressed, 3 lines same as above
22ee0 FF0869BC 00000000 00000000 00000000 ..i¼............
22ef0 00000000 00000000 00000000 00000000 ................
22f00 to 230b0 suppressed, 28 lines same as above
230c0 FF0A5B98 00000000 00000000 00000000 ..[.............
230d0 00000000 00000000 00000000 00000000 ................
230e0 to 23100 suppressed, 3 lines same as above
23110 00000000 F0005D0B F0005D0C F0005C03 ....ð.].ð.].ð.\.
23120 F0005C02 F0005C16 F0005C73 F00060F6 ð.\.ð.\.ð.\sð.`ö
23130 00000000 00000000 00000000 00000000 ................
23140 to 231c0 suppressed, 9 lines same as above
231d0 00000000 00000000 00000000 F0005D04 ............ð.].
231e0 00005D04 F0005C06 00005C06 F0005D0B ..].ð.\...\.ð.].
231f0 F00060B3 000060B3 F00060B4 000060B4 ð.`³..`³ð.`´..`´
23200 F0005D27 00005D27 F0005D0C F00060B3 ð.]'..]'ð.].ð.`³
23210 000060B3 F0005C03 F00060B3 000060B3 ..`³ð.\.ð.`³..`³
23220 F0005D7D F0005D59 00005D59 F0005C16 ð.]}ð.]Y..]Yð.\.
23230 F0005C73 F00060F6 000060F6 00005C73 ð.\sð.`ö..`ö..\s
23240 00005C16 00005D7D F0005D7D F0005D59 ..\...]}ð.]}ð.]Y
23250 00005D59 F0005C16 F0005C73 F00060F6 ..]Yð.\.ð.\sð.`ö
23260 000060F6 00005C73 00005C16 00005D7D ..`ö..\s..\...]}
23270 F00060F6 000060F6 F0005C13 00005C13 ð.`ö..`öð.\...\.
23280 F0005C13 00005C13 F0005C13 00005C13 ð.\...\.ð.\...\.
23290 F0005C13 00005C13 F0005C13 00005C13 ð.\...\.ð.\...\.
232a0 F0005C02 00005C02 F0005C02 00005C02 ð.\...\.ð.\...\.
232b0 F0005C02 00005C02 00000000 00000000 ð.\...\.........
232c0 00000000 00000000 00000000 00000000 ................
232d0 to 235c0 suppressed, 48 lines same as above
235d0 00000037 00000017 00000000 00000000 ...7............
235e0 00000000 00000000 00000000 00000000 ................
235f0 to 23640 suppressed, 6 lines same as above
Component Dumps (Thread 00000002)
------------------------------------- |
|
| Back to top |
|
 |
| csmith28 |
| Posted: Mon Nov 08, 2004 10:04 am Post subject: |
|
|
Grand Master
Joined: 15 Jul 2003
Posts: 1196
Location: Arizona
|
Explanation: Process &2 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 WebSphere MQ.
User Response: Determine the source of the signal and prevent it from re-occurring.
Odd, most of the hits I am getting in response to searching on that Probe ID and Message ID are related to MQ5.2 problems.
Has anything happened recently, like an un-gracefull restart of the MQManager?
_________________
Yes, I am an agent of Satan but my duties are largely ceremonial. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 08, 2004 10:19 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Since the process in question is runmqsc, I suspect that this is a user caused error.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thravi |
| Posted: Mon Nov 08, 2004 11:20 am Post subject: |
|
|
Novice
Joined: 16 Jul 2004
Posts: 13
|
No csmith28, there hasn't been any ungraceful restart.
Hi Jeff,
what do you mean by user caused error. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Mon Nov 08, 2004 11:23 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| You probably ended runmqsc in a less than graceful manner (ie, Ctrl-C). |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Nov 08, 2004 12:01 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| UserID :- 00062644 (mcquser) |
I don't know if it matters but is mcquser part of mqm group |
|
| Back to top |
|
|
| thravi |
| Posted: Mon Nov 08, 2004 12:14 pm Post subject: |
|
|
Novice
Joined: 16 Jul 2004
Posts: 13
|
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 08, 2004 1:02 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
We had some weird FDC's (over a 1000) when we restarted MQ with CSD08.
After the shutdown with CSD07 we installed CSD08. Just as a precaution we checked ipcc memory with all qmgrs down and still saw some claimed by mqm.
We had to reboot the unix box (AIX) before being able to run CSD08 correctly. Have not seen any FDC's since the reboot.
Enjoy  |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Nov 08, 2004 1:05 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Again, this FDC is being generated by runmqsc.
Unless you are using runmqsc in some sort of production level scripting context, don't worry about this FDC. Some user somewhere killed runmqsc in an inappropriate way, and this FDC was thrown.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Nov 08, 2004 1:25 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
Jeff,
That's my point exactly. even a simple runmqsc, regardless of whether we really checked things with it or not threw FDCs...
It really was because we restarted MQ in CSD08 without a clear ipcc memory. At that point we did not even see some commands like dspmq anymore and endmqm seemed to have no effect regardless of the parameter (-p).
Rebooted the box (to clear the memory confusion) and everything worked fine. No more problems or FDC's...
In his FDC he states CSD08 but does not specify whether it is a recent upgrade or not. We upgraded 2 machines last week. None of them had a clear ipcc so we rebooted them. But the behavior with CSD08 running before reboot was wastly different. On one it did not allow me to start a second qmgr, on the other we saw some of the weird stuff mentioned above. I was lucky I caught it before we started real work on the boxes (DEV).
Since the reboot fixing the memory problem we have not seen any FDCs and CSD08 is working fine.
So working as designed: yes. However be cautious when upgrading to CSD08. Check your ipcc memory when all qmgrs are down. If it is not clear of any MQ processes (mqm) you might have to kill them or reboot the box. |
|
| Back to top |
|
|
| Nigelg |
| Posted: Tue Nov 09, 2004 12:51 am Post subject: |
|
|
Grand Master
Joined: 02 Aug 2004
Posts: 1046
|
| fjb, you are missing the point here. runmqsc did not throw FDCs arbitrarily, it did so in response to a user actoin, either pressing ^C in the app or sending SIGINT to the PID. |
|
| Back to top |
|
|
| thravi |
| Posted: Tue Nov 09, 2004 5:13 am Post subject: |
|
|
Novice
Joined: 16 Jul 2004
Posts: 13
|
| Thanks for all the replies. I guess one of the putty sessions timed out and runmqsc got killed and an FDC was created. |
|
| Back to top |
|
|
| Anirud |
| Posted: Tue Nov 09, 2004 8:42 am Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
set environment variable EXTSHM=ON in the .profile of the userid.
We had some FDC's generated (AIX, MQ5.3, CSD07) because of runmqsc but with a different probe id. We got this fixed after setting the environment variable.
Hope this helps. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Nov 09, 2004 1:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| Nigelg wrote: |
| fjb, you are missing the point here. runmqsc did not throw FDCs arbitrarily, it did so in response to a user action, either pressing ^C in the app or sending SIGINT to the PID. |
Nigel, Maybe I am a little bit naive but I would not leave a runmqsc open.
Most of my commands are stored in files anyway. So with redirection this is not much of a problem.
But yes you are completely right and my apologies to both you and Jeff. |
|
| Back to top |
|
|
| clindsey |
| Posted: Tue Nov 09, 2004 2:24 pm Post subject: |
|
|
Knight
Joined: 12 Jul 2002
Posts: 586
Location: Dallas, Tx
|
| Quote: |
Nigel, Maybe I am a little bit naive but I would not leave a runmqsc open.
Most of my commands are stored in files anyway. So with redirection this is not much of a problem.
|
If you exit runmqsc by entering "end" you will not get this FDC. You get the FDC by hitting control-C (send SIGINT to application) to exit runmqsc.
Charlie |
|
| Back to top |
|
|
|
|
