Author |
Message
|
sandiksk |
Posted: Fri Oct 07, 2005 5:26 am Post subject: lot of fdcs being created |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
hey guys could you tell me what could be the reason for these fdcs.
MQ-5.3.8
os - AIX
and a lot more fdcs like these are created. I restarted mq and its working fine now. but can u tell me why these fdcs are being created
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Friday October 07 08:50:27 EDT 2005 |
| Host Name :- S0010822 |
| PIDS :- 5765B73 |
| LVLS :- 500 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC175012 |
| Application Name :- MQM |
| Component :- xllSemReq |
| Build Date :- Jul 13 1999 |
+-----------------------------------------------------------------------------+
| |
| MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Friday October 07 08:50:27 EDT 2005 |
| Host Name :- S0010822 |
| PIDS :- 5765B73 |
| LVLS :- 500 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC175012 |
| Application Name :- MQM |
| Component :- xllSemReq |
| Build Date :- Jul 13 1999 |
| UserID :- 00000512 (mqm) |
| Process :- 00098316 |
| Thread :- 00000001 |
| QueueManager :- N0822ST1 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal MQSeries error has occurred ('An |
| identifier does not exist.' from semop.) |
| Comment1 :- 'An identifier does not exist.' from semop. |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
riiInitiator
MQGET
zstMQGET
ziiMQGET
ziiSendReceiveAgent
zcpReceiveOnLink
xcsWaitEventSem
xllSemReq
xcsFFST
MQM Trace History
<-- xllSemReq rc=OK
<-- xcsRequestMutexSem rc=OK
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal MQSeries error has occurred ('An |
| identifier does not exist.' from semop.) |
| Comment1 :- 'An identifier does not exist.' from semop. |
| |
| |
+-----------------------------------------------------------------------------+
MQM Function Stack
riiInitiator
MQGET
zstMQGET
ziiMQGET
ziiSendReceiveAgent
zcpReceiveOnLink
xcsWaitEventSem
xllSemReq
xcsFFST |
|
Back to top |
|
 |
sandiksk |
Posted: Fri Oct 07, 2005 5:35 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
These are the errors in the error log
10/07/05 08:50:33
AMQ6184: An internal MQSeries error has occurred on queue manager N*****.
EXPLANATION:
An error has been detected, and the MQSeries error recording routine has been
called. The failing process is process 98316.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved.
-------------------------------------------------------------------------------
10/07/05 08:50:33
AMQ6119: An internal MQSeries error has occurred ('A system call received a
parameter that is not val' from semop.)
EXPLANATION:
MQSeries detected an unexpected error when calling the operating system. The
MQSeries error recording routine has been called.
ACTION:
Use the standard facilities supplied with your system to record the problem
identifier, and to save the generated output files. Contact your IBM support
center. Do not discard these files until the problem has been resolved. |
|
Back to top |
|
 |
ramires |
Posted: Fri Oct 07, 2005 6:16 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
Hmm... your fdc shows a level 5.0.0 queue manager, a 5.3.7 (my case) has fdc's like this:
| PIDS :- 5724B4101
| LVLS :- 530.7 CSD07
| Product Long Name :- WebSphere MQ for AIX
| Vendor :- IBM
Old libraries? You may have some kind of bad MQ setup, can this be possible?
Regards |
|
Back to top |
|
 |
sandiksk |
Posted: Fri Oct 07, 2005 6:31 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
well thats not possible because its been working fine for a while now. we have mq 5.3.8, not sure whats causing the problem.
=>mqver
Name: WebSphere MQ
Version: 530.8 CSD08
CMVC level: p530-08-L040921
do u know what this means
'A system call received a parameter that is not val' from semop.
In the start up log this what it syas
Bringing up MQseries. . .
/usr/local/bin/monproc: Invalid number (0) of "MQSERIES amqzlaa0" process(es)
/usr/local/bin/monproc: rc = 1
/usr/local/bin/monproc: Invalid number (0) of "MQSERIES amqzfuma" process(es)
/usr/local/bin/monproc: rc = 1
can anyone tell me what this means  |
|
Back to top |
|
 |
ramires |
Posted: Fri Oct 07, 2005 6:49 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
|
Back to top |
|
 |
hopsala |
Posted: Fri Oct 07, 2005 7:08 am Post subject: |
|
|
 Guardian
Joined: 24 Sep 2004 Posts: 960
|
Did you make sure all mq processes are down before starting the qm? Methinks orphan processes are left running from your last endmqm.
Did you set up all necessary kernel parameters (as noted in Quick Beginnings for AIX)?
Did you try ipcrm and amqiclen?
Search this site for these topics, you may find relevant info. Keep us posted. |
|
Back to top |
|
 |
sandiksk |
Posted: Fri Oct 07, 2005 7:19 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
yeah i did make sure that all the processors are down, before restarting.
Well its working fine after restart, i just want to know why it caused such errors.
ramires wrote
Quote: |
Those errors, in that start up log, are when you do a "strmqm <qmgr name>"? |
when i (mqadmin) restart mq, it went smoothly, but some other guys at help desk tried it before me...it had the errors which is
Bringing up MQseries. . .
/usr/local/bin/monproc: Invalid number (0) of "MQSERIES amqzlaa0" process(es)
/usr/local/bin/monproc: rc = 1
/usr/local/bin/monproc: Invalid number (0) of "MQSERIES amqzfuma" process(es)
/usr/local/bin/monproc: rc = 1
What i am guessing is they probably did not start it through mqm(may they did it throuch root).
OR
system resorces where not available at that time
correct me if i am wrong |
|
Back to top |
|
 |
mq_abcd |
Posted: Fri Oct 07, 2005 7:22 am Post subject: |
|
|
 Acolyte
Joined: 13 Jun 2004 Posts: 69
|
Quote: |
MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Friday October 07 08:50:27 EDT 2005 |
| Host Name :- S0010822 |
| PIDS :- 5765B73 |
| LVLS :- 500 |
|
Quote: |
=>mqver
Name: WebSphere MQ
Version: 530.8 CSD08
CMVC level: p530-08-L040921
|
Are both from.. same m/c..
If so.. then.. you got bigger problems.. GOOD LUCK
Check other FDC's on this m/c created a while back.. you may get a clue.. |
|
Back to top |
|
 |
ramires |
Posted: Fri Oct 07, 2005 7:27 am Post subject: |
|
|
Knight
Joined: 24 Jun 2001 Posts: 523 Location: Portugal - Lisboa
|
sandiksk:
Quote: |
/usr/local/bin/monproc: Invalid number (0) of "MQSERIES amqzlaa0" process(es)
/usr/local/bin/monproc: rc = 1
|
this is not output from MQ, it looks like something (a script) writes to the terminal. It's impssible to say the reason for the "invalid number of processes" |
|
Back to top |
|
 |
sandiksk |
Posted: Fri Oct 07, 2005 8:30 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
mq_abcd wrote
Quote: |
Are both from.. same m/c..
If so.. then.. you got bigger problems.. GOOD LUCK
Check other FDC's on this m/c created a while back.. you may get a clue.. |
no they are from different mchine. i gave the general level for a similar box.
on this one i am not able to do dspmq and mqver
=>mqver
ksh: mqver: not found. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Oct 07, 2005 8:59 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
mqver is not supported at 5.00 level....
You really need to make sure the start is as clean as possible and done by a member of the mqm group...
Enjoy  |
|
Back to top |
|
 |
sandiksk |
Posted: Fri Oct 07, 2005 11:04 am Post subject: |
|
|
Centurion
Joined: 08 Jun 2005 Posts: 133
|
one more interesting thing is ,
when i see the list of mq processes running , i dont see amqzfuma running. Is this not available in 5.0 version |
|
Back to top |
|
 |
jon |
Posted: Thu Jul 23, 2009 3:33 am Post subject: A system call received a parameter that is not val' from sem |
|
|
 Apprentice
Joined: 17 May 2009 Posts: 32
|
Hello Friends,
I am also getting the same error, please have a look at my FDC's -
Quote: |
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thursday July 23 19:15:38 TAIST 2009 |
| Host Name :- DG070 (AIX 5.2) |
| PIDS :- 5724B4101 |
| LVLS :- 530.8 CSD08 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XC175012 |
| Application Name :- MQM |
| Component :- xllSemReq |
| Build Date :- Sep 21 2004 |
| CMVC level :- p530-08-L040921 |
| Build Type :- IKAP - (Production) |
| UserID :- 00000232 (jonmqm) |
| Program Name :- runmqchi |
| Process :- 03035358 |
| Thread :- 00000001 |
| Major Errorcode :- xecF_E_UNEXPECTED_SYSTEM_RC |
| Minor Errorcode :- OK |
| Probe Type :- MSGAMQ6119 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6119: An internal WebSphere MQ error has occurred |
| ('22 - A system call received a parameter that is not val' from semop.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 22 16 |
| Comment1 :- '22 - A system call received a parameter that is not |
| val' from |
| |
+-----------------------------------------------------------------------------+
|
as you can see our client is using outdated version of MQ -530.8 CSD08.
I suspect this as the root cause of problem, if anybody can point me in right direction it would be helpful. |
|
Back to top |
|
 |
Vitor |
Posted: Thu Jul 23, 2009 3:46 am Post subject: Re: A system call received a parameter that is not val' from |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
jon wrote: |
as you can see our client is using outdated version of MQ -530.8 CSD08.
I suspect this as the root cause of problem, if anybody can point me in right direction it would be helpful. |
Upgrade. v5.3 is not just outdated it's out of support.
CSD08 is actually withdrawn by IBM because it's problematic. If your client insists on using v5.3 then they should apply the latest maintenance.
You could also point out that if they moved to a supported level they could get advice from IBM rather than a volunteer forum. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
aditya.aggarwal |
Posted: Thu Jul 23, 2009 7:42 am Post subject: |
|
|
 Master
Joined: 13 Jan 2009 Posts: 252
|
sandiksks wrote:
Quote: |
MQSeries First Failure Symptom Report |
| ===================================== |
| |
| Date/Time :- Friday October 07 08:50:27 EDT 2005 |
| Host Name :- S0010822 |
| PIDS :- 5765B73 |
| LVLS :- 500 |
| Product Long Name :- MQSeries for AIX |
| Vendor :- IBM |
| Probe Id :- XC175012 |
| Application Name :- MQM |
| Component :- xllSemReq |
| Build Date :- Jul 13 1999 | |
Quote: |
well thats not possible because its been working fine for a while now. we have mq 5.3.8, not sure whats causing the problem.
mqver
Name: WebSphere MQ
Version: 530.8 CSD08
CMVC level: p530-08-L040921
|
Quote: |
one more interesting thing is ,
when i see the list of mq processes running , i dont see amqzfuma running. Is this not available in 5.0 version |
Why FDC is showing MQ Version 5.0, but mqver is showing MQ V5.3+CSD8....? Are you taking about different servers?
if servers are same then does it means you start getting FDC after upgrading MQ from V5 to V5.3? if yes then you need to check the seamop.. values according to manuals for Mq V5.3 on Aix...
amqzfuma was not avialable in MQ V5. so it is not a problem.
OVERALL i can say that there is some problem in your semop values.... plz check and verify it.
Cheers,
Aditya |
|
Back to top |
|
 |
|