| Author |
Message
|
| tgunasek |
 Posted: Thu Jun 30, 2011 7:50 am Post subject: Unable to restart MQ Queue Managers |
 |
|
Newbie
Joined: 30 Jun 2011
Posts: 2
|
Any assistance in understanding the cause of the Queue Manager Startup failure below would be much appreciated.
We are currently unable to restart any of the existing Queue Managers currently configured on the following MQ Server (v7.0.1.2). The day before these errors occurred certain user permissions were changes on the machine hosting MQ. However these have now been reverted and the server machine restarted. Can anyone shed any light on what the cause of this failure may be? Along with any information on resolution?
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu June 30 2011 15:13:57 GMT Daylight Time |
| UTC Time :- 1309443237.905000 |
| UTC Time Offset :- 60 (GMT Daylight Time) |
| Host Name :- UKMDxxxxxxx01 |
| Operating System :- Windows Server 2003, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.2 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- XY509007 |
| Application Name :- MQM |
| Component :- xcsOpenFileLock |
| SCCS Info :- lib/cs/pc/winnt/amqxnfln.c, 1.14.1.3 |
| Line Number :- 295 |
| Build Date :- May 6 2010 |
| CMVC level :- p701-102-100504 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00005276 |
| Thread :- 00000001 |
| QueueManager :- QM_DTF_ST |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 2.0.0-10148 |
| Last HSHMEMB :- 4.0.0-22612 |
| 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 |
| (WinNT error 5 from CreateFile.) |
| FDCSequenceNumber :- 0 |
| Comment1 :- WinNT error 5 from CreateFile. |
| |
| Comment2 :- Access is denied. |
| |
| |
+-----------------------------------------------------------------------------+
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Thu June 30 2011 15:13:57 GMT Daylight Time |
| UTC Time :- 1309443237.921000 |
| UTC Time Offset :- 60 (GMT Daylight Time) |
| Host Name :- UKMDxxxxxxx01 |
| Operating System :- Windows Server 2003, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.2 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZT374000 |
| Application Name :- MQM |
| Component :- zutRequestQMFileLocks |
| SCCS Info :- lib/zu/amqzutf0.c, 1.10.1.3 |
| Line Number :- 317 |
| Build Date :- May 6 2010 |
| CMVC level :- p701-102-100504 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00005276 |
| Thread :- 00000001 |
| QueueManager :- QM_DTF_ST |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 2.0.0-10148 |
| Last HSHMEMB :- 4.0.0-22612 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- xecN_E_FILE_ERROR |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (20806279) |
| FDCSequenceNumber :- 1 |
| Arith1 :- 545284729 20806279 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
 |
| Vitor |
| Posted: Thu Jun 30, 2011 8:13 am Post subject: Re: Unable to restart MQ Queue Managers |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| contact admin wrote: |
| Can anyone shed any light on what the cause of this failure may be? |
It's clear the process is bouncing off Windows trying to create or open it's files. Is the disc for any queue manager files local to the server or remote (for example the log files on a network drive for failover)? Could you have stale file lock or handles somewhere?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 30, 2011 1:26 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
Component :- xcsOpenFileLock
Comment1 :- WinNT error 5 from CreateFile. |
| |
| Comment2 :- Access is denied. | |
Or possibly permission bits issue. Did you or someone else fiddle with them?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Jun 30, 2011 2:11 pm Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Or you started the queue manager with a UserID that does not have the appropriate permission to certain MQ directories. Is the queue manager running under "MUSR_MQADMIN" UserID?
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| tgunasek |
| Posted: Fri Jul 01, 2011 7:11 am Post subject: |
|
|
Newbie
Joined: 30 Jun 2011
Posts: 2
|
Just to give further background information, this problem arose after the network administration team changed certain remote user access permissions to the machine (removing Admin rights) as well as to certain specific windows folders (by only granting read/write access to remote users on a folder by folder basis). However the MUSR_MQADMIN user permissions were not changed according to the information provided by them.
Either way they say that they have now reverted those changes for us to try and resolve this problem. Unfortunately this hasn't had the desired effect. Note that after comparing the Windows permissions granted to the "C:\Program Files\IBM\WebSphere MQ" folder against another Windows MQ Server, I noticed that the MQM group did not have full control to that folder on this machine so have now granted this. The error seen now when attempting to startup existing QM's is "AMQ7017 - LOG_NOT_AVAILABLE" and the failure report is as follows:
Note that new QM's can be created/started/stopped without a problem. It's just those QM's that were there before this that we cannot restart.
One other question I have is, does the MUSR_MQADMIN user need to belong to Administrators group on Windows or should it just belong to the MQM group?
+-----------------------------------------------------------------------------+
| |
| WebSphere MQ First Failure Symptom Report |
| ========================================= |
| |
| Date/Time :- Fri July 01 2011 14:44:14 GMT Daylight Time |
| UTC Time :- 1309527854.179000 |
| UTC Time Offset :- 60 (GMT Daylight Time) |
| Host Name :- UKMDxxxxxxx01 |
| Operating System :- Windows Server 2003, Build 3790: SP2 |
| PIDS :- 5724H7220 |
| LVLS :- 7.0.1.2 |
| Product Long Name :- WebSphere MQ for Windows |
| Vendor :- IBM |
| Probe Id :- ZX146001 |
| Application Name :- MQM |
| Component :- zxcStartupLogic |
| SCCS Info :- cmd/zmain/amqzxma0.c, 1.264.1.3 |
| Line Number :- 3308 |
| Build Date :- May 6 2010 |
| CMVC level :- p701-102-100504 |
| Build Type :- IKAP - (Production) |
| UserID :- MUSR_MQADMIN |
| Process Name :- C:\Program Files\IBM\WebSphere MQ\bin\amqzxma0.exe |
| Addressing mode :- 32-bit |
| Process :- 00011232 |
| Thread :- 00000001 |
| QueueManager :- QM_DTF_DEV |
| UserApp :- FALSE |
| ConnId(1) IPCC :- 2 |
| ConnId(2) QM :- 2 |
| ConnId(3) QM-P :- 2 |
| ConnId(4) App :- 2 |
| Last HQC :- 0.0.0-0 |
| Last HSHMEMB :- 2.4.4-1340 |
| Major Errorcode :- xecF_E_UNEXPECTED_RC |
| Minor Errorcode :- lpiRC_LOG_NOT_AVAILABLE |
| Probe Type :- MSGAMQ6118 |
| Probe Severity :- 2 |
| Probe Description :- AMQ6118: An internal WebSphere MQ error has occurred |
| (7017) |
| FDCSequenceNumber :- 0 |
| Arith1 :- 28695 7017 |
| |
+-----------------------------------------------------------------------------+ |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 01, 2011 9:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
Permission bits should NOT be changed anywhere in the WMQ paths. Installation and qmgr creation sets the rwx bits appropriately for WMQs use. Sysadmins access WMQ resources through admin commands - authorized my MQM group membership; while end-users access WMQ resources via MQI calls. End users should NEVER be in the MQM group.
| Quote: |
| Minor Errorcode :- lpiRC_LOG_NOT_AVAILABLE | |
Pretty clear.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Fri Jul 01, 2011 9:45 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9471
Location: US: west coast, almost. Otherwise, enroute.
|
| contact admin wrote: |
...
Either way they say that they have now reverted those changes for us to try and resolve this problem. |
And you believe them?
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
