| Author |
Message
|
| mreddington |
 Posted: Mon Dec 18, 2006 1:38 pm Post subject: Some Process Stopped/Killed accidentally |
 |
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
Hi all,
i am unable to start my queue manager (strmqm) or display queue manager list (dspmq)...
I am now wondering if some process has been accidentally killed/stopped without notice. I am saying this because, when i display process with amq* (ps -ef | grep amq*) nothing displays and the command prompt goes to the next line. So, is there any way to start the missing processes required for MQ to work properly (so that i can start my queue manager and work on it)
Please advise on this...
Thank you |
|
| Back to top |
|
 |
| wschutz |
| Posted: Mon Dec 18, 2006 1:56 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
No, there is no "background process" that should be running ... what happens when you try strmqm and dspmq? (and it would be nice to know what unix this is and what version/csd of mq)
_________________
-wayne |
|
| Back to top |
|
|
| mreddington |
| Posted: Mon Dec 18, 2006 1:59 pm Post subject: Hi |
|
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
When i try strmqm QMName, the command just hangs there at the prompt and nothing happens then. (i mean inorder to come out of it, i have to forcefully come out that using ctrl+Z).
There are some fdc files being created in the error directory though!!. it goes like this:
+---------------------------------------------------------------------------
|
| WebSphere MQ First Failure Symptom Report
| =========================================
|
| Date/Time :- Monday December 18 15:23:14 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 :- dspmq
| Addressing mode :- 64-bit
| Process :- 13036
| Thread :- 2
| Major Errorcode :- xecE_W_UNEXPECTED_ASYNC_SIGNAL
| Minor Errorcode :- OK
| Probe Type :- MSGAMQ6209
| Probe Severity :- 3
| Probe Description :- AMQ6209: An unexpected asynchronous signal (1 :
| SIGHUP) has been received and ignored.
| FDCSequenceNumber :- 0
| Arith1 :- 1 1
| Arith2 :- 13013 32d5
| Comment1 :- SIGHUP
| Comment2 :- Signal sent by pid 13013
| Comment3 :- ksh
|
I appreciate your support in resolving this issue...
Thank you |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Mon Dec 18, 2006 4:09 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Please don't double-post.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Mon Dec 18, 2006 5:34 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Did it EVER work?
Is there anything in the MQ error logs ....
I think the FFST is being written becuase of your ctrl-c/z.
_________________
-wayne |
|
| Back to top |
|
|
| mreddington |
| Posted: Tue Dec 19, 2006 6:43 am Post subject: Sorry |
|
|
Voyager
Joined: 14 Aug 2006
Posts: 78
|
| Sorry about the double posting.. I'll take measures not to do that again in the future. |
|
| Back to top |
|
|
|
|
