Posted: Tue Jan 27, 2004 10:59 pm Post subject: AMQ6119: with semop while strmqm in AIX.
Apprentice
Joined: 14 Aug 2002 Posts: 27 Location: Bangalore
Hi,
I have upgraded MQ from ver 5.1 to 5.3 successfully. while starting the qmgr I am getting error below. We are using HACMP. The Active (Primary) server was successfully upgraded & started the qmgr. But the Standby (Secondary) server after swing over gives the problem while starting, creating & displaying qmgrs. The errors are listed below. Appreciate if any one can suggest on the same.
AMQ6119: An internal WebSphere MQ error has occurred ('22 - A system call received a parameter that is not val' from semop.)
EXPLANATION:
MQ detected an unexpected error when calling the operating system. The MQ error recording routine has been called.
And content of the FDC file is below.
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Wednesday January 28 03:05:51 TAIST 2004 |
| Host Name :- mqp00 (AIX 4.3) |
| PIDS :- 5724B4101 |
| LVLS :- 530.5 CSD05 |
| Product Long Name :- WebSphere MQ for AIX |
| Vendor :- IBM |
| Probe Id :- XY326211 |
| Application Name :- MQM |
| Component :- AccessSubpoolsLock |
| Build Date :- Sep 27 2003 |
| CMVC level :- p530-05-L030926 |
| Build Type :- IKAP - (Production) |
| UserID :- 00001000 (mqm) |
| Program Name :- strmqm |
| Process :- 00023788 |
| Thread :- 00000001 |
| QueueManager :- QPMSD01 |
| 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 semget.) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 22 16 |
| Comment1 :- '22 - A system call received a parameter that is not |
| val' from |
Thanks in advanced.
Eknath _________________ Eknath Vashishtha
Joined: 16 May 2003 Posts: 184 Location: Kansas City
This is what I found on IBM site
Quote:
The FDC showed that semget is failing with EINVAL in AccessSubpoolsock. Normally this is due to previous semaphores or shared memory existing for MQSeries but we eliminated that possibility with the ipcrm command.
From the man pages semget can return EINVAL for an existing semaphore ID if the "number of semaphores" parameter passed to it is more than the number of semaphores that do exist for that id. Hence, this error is consistent with a key clash. WMQ chooses the key based on the inode for mqs.ini, so the simplest solution in this case was the following:
ls -ild /var/mqm/mqs.ini
cp /var/mqm/mqs.ini /var/mqm/temp.ini
rm /var/mqm/mqs.ini
mv /var/mqm/temp.ini /var/mqm/mqs.ini
ls -ild /var/mqm/mqs.ini
This should result in the inode key for mqs.ini being changed which should avoid this clash.
Known problem, Workaround as follows:
ls -ild /var/mqm/mqs.ini
cp /var/mqm/mqs.ini /var/mqm/temp.ini
rm /var/mqm/mqs.ini
mv /var/mqm/temp.ini
/var/mqm/mqs.ini
ls -ild /var/mqm/mqs.ini
This should result in the inode key for mqs.ini being changes which should avoid this clash.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum