| Author |
Message
|
| Sam Uppu |
 Posted: Thu Aug 06, 2009 7:05 am Post subject: FFST to analyze |
 |
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
Hi,
We are running on solaris sparc 10 and MQ version 7.0.0.2
I see this FDC and not sure what caused this to generate.
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wed August 05 2009 19:44:08 CDT |
| UTC Time :- 1249519448.148213 |
| UTC Time Offset :- -300 (CST) |
| Host Name :- rsk0stl5 |
| Operating System :- SunOS 5.10 |
| PIDS :- 5724H7223 |
| LVLS :- 7.0.0.2 |
| Product Long Name :- WebSphere MQ for Solaris (SPARC platform) |
| Vendor :- IBM |
| Probe Id :- XC338001 |
| Application Name :- MQM |
| Component :- xehAsySignalHandler |
| SCCS Info :- lib/cs/unix/amqxerrx.c, 1.229.1.4 |
| Line Number :- 705 |
| Build Date :- Jul 23 2009 |
| CMVC level :- p700-002-090421 |
| Build Type :- IKAP - (Production) |
| UserID :- 00050089 (mqm) |
| Program Name :- runmqsc |
| Addressing mode :- 64-bit |
| Process :- 26306 |
| Thread :- 2 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 0.0.0-0 |
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6209 |
| Probe Severity :- 3 |
| Probe Description :- AMQ6209: An unexpected asynchronous signal (15 : |
| SIGTERM) has been received and ignored. |
| FDCSequenceNumber :- 0 |
| Arith1 :- 15 f |
| Arith2 :- 10448 28d0 |
| Comment1 :- SIGTERM |
| Comment2 :- Signal sent by pid 10448 |
| |
+-----------------------------------------------------------------------------+
ffstsummary is showing this:
ffstsummary AMQ26306.0.FDC
AMQ26306.0.FDC 2009/08/05 19:44:08.148213-5 runmqsc 26306 2 XC338001 xehAsySignalHandler xecE_W_UNEXPECTED_ASYNC_SIGNAL OK
Can you guys throw some light on this error?.
Thanks. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Aug 06, 2009 7:13 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Someone tried to force end runmqsc. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Thu Aug 06, 2009 7:26 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| mqjeff wrote: |
| Someone tried to force end runmqsc. |
Thanks Jeff.
Not sure what caused this. Do you think the below scenario may cause this type of error:
I am on the server and runmqsc to the Qmgr. If all of a sudden I lost my network connectivity to the server. That may cause this kind of force ending runmqsc?.
Thanks. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Thu Aug 06, 2009 7:44 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
reboot?
What is the uptime? |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Thu Aug 06, 2009 7:48 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| JosephGramig wrote: |
reboot?
What is the uptime? |
uptime
10:47am up 11 day(s), 11:36, 10 users, load average: 5.25, 3.85, 5.07
. system boot Jul 25 23:10
They are rebooted couple of days ago.
Thanks. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Aug 06, 2009 4:12 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| mqjeff wrote: |
| Someone tried to force end runmqsc. |
I think that effect can be obtained on Solaris by typing control codes (^C, ^Z) into an interactive runmqsc rather than using the 'end' command to leave the program.
_________________
Glenn |
|
| Back to top |
|
|
| vol |
| Posted: Thu Aug 06, 2009 11:08 pm Post subject: |
|
|
Acolyte
Joined: 01 Feb 2009
Posts: 69
|
Complete analysis:
Process 10448
| Quote: |
| Signal sent by pid 10448 |
sent async signal SIGTERM (15)
| Quote: |
An unexpected asynchronous signal (15 : |
| SIGTERM) has been received and ignored |
to runmqsc process PID 26306.
15 is the default signal, so some user on the system running in PID 10448, probably a shell, issued a 'kill 26306' command.
This is not a WMQ error. |
|
| Back to top |
|
|
|
|
