| Author |
Message
|
| mreddington |
 Posted: Mon Dec 18, 2006 12:16 pm Post subject: Probe Id: XC338001 on Sun box |
 |
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
Hi all,
I applied RP2 for MQ version 6.0 on Sun box. I stopped the queue manager before applying RP2. Unfortunately i forgot to stop the listeners, but RP2 was installed succesfully and when i display dspmqver i am able to see 6.0.2.0.
Now when i want to start the queue manager (strmqm QMName), it just hangs there without doing anything. I went and checked the errors directory only to find out there are FDC files being created.
Please see the FDC file below: (i only had some portion cut/pasted here)How do I go about it now? Is there anything i can do to resolve this issue?
Your advise is highly appreciatable. Thanks a lot in advance..
+----------------------------------------------------------------------------
|
| WebSphere MQ First Failure Symptom Report
| =========================================
|
| Date/Time :- Monday December 18 13:50:37 CST 2006
| Host Name :- dkds0548 (SunOS 5.10)
| PIDS :- 5724H7203
| LVLS :- 6.0.2.0
| 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.214.1.4
| Line Number :- 737
| Build Date :- Sep 21 2006
| CMVC level :- p600-200-060921
| Build Type :- IKAP - (Production)
| UserID :- 00027327 (mqm)
| Program Name :- strmqm
| Addressing mode :- 64-bit
| Process :- 11716
| Thread :- 3
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6209
| Probe Severity :- 3
| Probe Description :- AMQ6209: An unexpected asynchronous signal (2 :
| SIGINT) has been received and ignored.
| FDCSequenceNumber :- 0
| Arith1 :- 2 2
| Comment1 :- SIGINT
| Comment2 :- Signal sent by pid 0
| Comment3 :- sched
|
+----------------------------------------------------------------------------
MQM Function Stack
xehAsySignalMonitor
xehHandleAsySignal
xcsFFST
MQM Trace History
{ xppInitialiseDestructorRegistrations
} xppInitialiseDestructorRegistrations rc=OK
{ xcsFreeMem
} xcsFreeMem rc=OK
{ xcsIsEnvironment
} xcsIsEnvironment rc=OK
{ xehAsySignalMonitor
-{ xcsRequestThreadMutexSem
-} xcsRequestThreadMutexSem rc=OK
-{ xcsReleaseThreadMutexSem
-} xcsReleaseThreadMutexSem rc=OK
-{ xcsIsEnvironment
-} xcsIsEnvironment rc=OK
-{ xppPostAsySigMonThread
-} xppPostAsySigMonThread rc=OK
Data: 0x00000002
-{ xehHandleAsySignal
--{ xcsRequestThreadMutexSem
--} xcsRequestThreadMutexSem rc=OK
--{ xcsQueryProcessDetails
--} xcsQueryProcessDetails rc=OK
--{ xcsFFST
Code (siginfo_t) structure
ffffffff7c50ee50 00000002 00007FFF ........
ffffffff7c50ee60 00000000 00000000 00000000 00000000 ................
ffffffff7c50ee70 to ffffffff7c50eea0 suppressed, 4 lines same as above
ffffffff7c50eeb0 00000000 00000000 FFFFFFFF 7F605000 .............`P.
ffffffff7c50eec0 00000000 7F605000 00000000 001BFEF4 .....`P.......■⌠
ffffffff7c50eed0 00000000 00005000 00000000 00005000 ......P.......P.
ffffffff7c50eee0 00000000 000052C8 FFFFFFFF 7EA9A728 ......R╚....~⌐º(
ffffffff7c50eef0 00000001 001377F0 FFFFFFFF 7C50F300 ......w≡....|P≤.
ffffffff7c50ef00 FFFFFFFF 7C50EE58 00000000 00000000 ....|PεX........
ffffffff7c50ef10 00000000 00000100 00000000 000002E0 ...............α
ffffffff7c50ef20 00000000 00000002 00000008 7EB006D0 ............~░.╨
ffffffff7c50ef30 FFFFFFFF 7D7C164C FFBFFEFF 0000FFFF ....}|.L.┐■.....
ffffffff7c50ef40 00000000 00000000 00000008 7EB006D0 ............~░.╨
ffffffff7c50ef50 FFFFFFFF 7E860108 ....~Ã¥..
Process Control Block
100136c90 58494850 00000B08 00002DC4 00000000 XIHP......-─....
100136ca0 00000003 00000000 00000001 00142620 ..............&
100136cb0 00000001 00139820 00000000 00000000 ......ÿ ........
100136cc0 00000000 00000000 00000001 00000001 ................
100136cd0 0000000B 00000000 FFFFFFFF 7C800000 ............|Ç..
100136ce0 00000000 00000000 00000000 00000000 ................
100136cf0 to 1001370d0 suppressed, 63 lines same as above
1001370e0 00000000 FFFFFFFF FFFFFFFF 00000000 ................
1001370f0 00000000 00000000 00000001 FFFFFFFE ...............■
100137100 00000001 00000000 00000000 00000000 ................
100137110 00000018 00000000 FFFFFFFF 7E85F1C0 ............~à ±└
100137120 00000000 00000000 00000000 00000000 ................
100137130 00000018 00000000 FFFFFFFF 7E85F1C0 ............~à ±└
100137140 00000000 00000000 00000000 00000000 ................
100137150 00000018 00000000 FFFFFFFF 7E85F1C0 ............~à ±└
************************************************************ |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Mon Dec 18, 2006 9:05 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
This is due to you killed the queue manager.
1. here the question is how you stopped the queue managers
Solution
1. Stop your queue managers using endmqm -c <QMGR_NAME>
2. The execute strmqm -c <QMGR_NAME>
3. Then strmqm <QMGR_NAME>
and plz let us know the status.
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| mreddington |
| Posted: Tue Dec 19, 2006 6:41 am Post subject: Thank you |
|
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
Hi Gayathri,
Thank you for your reply. Before applying RP2, i ended the queue manager with the command, endmqm <QMGRName>
Now the question is, i have to bring the queue manager up. I followed your commands to start the queue manager, but still it hangs. Whenever i try any command, it creates FDC files in the errors diretory (/var/mqm/errors).
The last few lines of the queue manager error log shows this:
----- amqrmrsa.c : 468 --------------------------------------------------------
12/18/06 13:45:00 - Process(24583.14) User(mqm) Program(runmqlsr_nd)
AMQ9508: Program cannot connect to the queue manager.
EXPLANATION:
The connection attempt to queue manager '1IP01ADV' failed with reason code
2059.
ACTION:
Ensure that the queue manager is available and operational.
----- amqrmsaa.c : 442 --------------------------------------------------------
12/18/06 13:45:00 - Process(24583.14) User(mqm) Program(runmqlsr_nd)
AMQ9999: Channel program ended abnormally.
EXPLANATION:
Channel program 'DMON.1IP01ADV' ended abnormally.
ACTION:
Look at previous error messages for channel program 'DMON.1IP01ADV' in the
error files to determine the cause of the failure.
----- amqrmrsa.c : 468 --------------------------------------------------------
12/18/06 13:53:02 - Process(24029.1) User(mqm) Program(amqzmgr0)
AMQ5027: The Listener 'SYSTEM.LISTENER.TCP.3' has ended. ProcessId(24583).
EXPLANATION:
The Listener process has ended.
ACTION:
None.
-------------------------------------------------------------------------------
12/18/06 13:53:11 - Process(24029.1) User(mqm) Program(amqzmgr0)
AMQ5027: The Listener 'SYSTEM.LISTENER.TCP.1' has ended. ProcessId(24282).
EXPLANATION:
The Listener process has ended.
ACTION:
None.
------------------------------------------------------------------------------- |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Dec 19, 2006 6:53 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Hi
Are you migrated from the previous MQ series?
create another queue manager and see whether that is working or not
Is the FDC error is same as you pasted above.
Thanks and Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Dec 19, 2006 7:09 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| Have you tried rebooting? |
|
| Back to top |
|
|
| mreddington |
| Posted: Tue Dec 19, 2006 9:16 am Post subject: Thanks |
|
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
I tried creating other queue manager, it still hangs as before. I also thought of the option to reboot the system, but i guess the application people are not willing for that at this time. The FDC files are the same as the ones i posted above.
I found one solution for this from IBM (they are not sure either) but wanted me to try this... They want me to clear the IPC resources for mqm on the box. I do see some resouces when i issue "ipcs | grep mqm"
The output is shown below:
dkds0548:/mqadmin->ipcs | grep mqm
m 16777251 0x359c0107 --rw-rw-rw- mqm mqm
m 16777250 0x359c0106 --rw------- mqm mqm
m 16777249 0x359c0105 --rw------- mqm mqm
m 16777248 0x359c00e2 --rw------- mqm mqm
m 16777246 0x359c00b5 --rw------- mqm mqm
m 16777220 0x359c0095 --rw------- mqm mqm
m 0 0x75a40002 --rw-rw-rw- mqm mqm
s 14 0x359c003a --ra-ra---- mqm mqm
s 13 0x359c0015 --ra-ra---- mqm mqm
s 12 0x359c0008 --ra-ra---- mqm mqm
s 11 0x35a40002 --ra-ra-ra- mqm mqm
and when i issue amqiclen command to clean the resources, it hangs as before...
dkds0548:/mqadmin->/opt/mqm/bin/amqiclen -x
^Z[1] + Stopped (SIGTSTP) /opt/mqm/bin/amqiclen -x
This is the current status... |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Tue Dec 19, 2006 9:32 am Post subject: Re: Thanks |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3265
Location: London, ON Canada
|
| mreddington wrote: |
and when i issue amqiclen command to clean the resources, it hangs as before...
dkds0548:/mqadmin->/opt/mqm/bin/amqiclen -x
^Z[1] + Stopped (SIGTSTP) /opt/mqm/bin/amqiclen -x
|
Ok, do the following:
(1) Make absolutely sure no MQ process is running:
(2) Run the following command:
| Code: |
| ipcs -a | grep mqm | awk '{printf( "-%s %s ", $1, $2 )}' | xargs ipcrm |
(3) Disable MQ from auto-starting
(4) Reboot the server
(5) After reboot, try a simple command like: dspmqver. If successful, start your queue managers.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| kevinf2349 |
| Posted: Tue Dec 19, 2006 9:39 am Post subject: Re: Thanks |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
| RogerLacroix wrote: |
(4) Reboot the server
|
| Quote: |
| I also thought of the option to reboot the system, but i guess the application people are not willing for that at this time. |
If the server/Queue managers are FUBAR why wouldn't they let you reboot it? |
|
| Back to top |
|
|
|
|
