| Author | Message | 
		
		  | solberj | 
			  
				|  Posted: Tue Apr 16, 2002 10:35 am    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 18 Mar 2002Posts: 18
 Location: Jim Solberg
 
 | 
			  
				| Hi, all... 
 Our Unix (HP-UX) admins just got done changing the mqm UID, and now we can't get the queue manager started (V5.2)...
 
 The strmqm fails with: AMQ6109: An internal MQSeries error has occurred.
 
 In the AMQERR01.LOG, I see:
 
 04/16/02  13:26:51 AMQ6118: An internal MQSeries error has occurred (D)EXPLANATION:An error has been detected, and the MQSeries error recording routine has beencalled.ACTION:Use the standard facilities supplied with your system to record the problemidentifier, and to save the generated output files. Contact your IBM supportcenter.  Do not discard these files until the problem has been resolved.-------------------------------------------------------------------------------
 04/16/02  13:26:52 AMQ6183: An internal MQSeries error has occurred.EXPLANATION:An error has been detected, and the MQSeries error recording routine has beencalled. The failing process is process 10851.ACTION:Use the standard facilities supplied with your system to record the problemidentifier, and to save the generated output files. Contact your IBM supportcenter.  Do not discard these files until the problem has been resolved.-------------------------------------------------------------------------------
 
 
 The FDC looks like:
 
 +-----------------------------------------------------------------------------+|                                                                             || MQSeries First Failure Symptom Report                                       | | =====================================                                       | |                                                                             || Date/Time         :- Tuesday April 16 13:26:52 CDT 2002                     | | Host Name         :- unifi2                                                 | | PIDS              :- 5765B74                                                | | LVLS              :- 510                                                    | | Product Long Name :- MQSeries for HP-UX                                     | | Vendor            :- IBM                                                    | | Probe Id          :- ZS141006                                               | | Application Name  :- MQM                                                    | | Component         :- zslEnqueue                                             | | Build Date        :- May 12 1999                                            | | UserID            :- 00000248 (mqm)                                         | | Program Name      :- strmqm_nd                                              | | Process           :- 00010851                                               | | Thread            :- 00000001                                               | | Major Errorcode   :- xecF_E_UNEXPECTED_RC                                   | | Minor Errorcode   :- Unknown(D)                                             | | Probe Type        :- MSGAMQ6118                                             | | Probe Severity    :- 2                                                      | | Probe Description :- AMQ6118: An internal MQSeries error has occurred (D)   | | Arith1            :- 13 d                                                   | |                                                                             |+-----------------------------------------------------------------------------+MQM Function Stack
 zslEnqueue
 xcsFFST
 
 MQM Trace History
 
 
 Any thoughts???
 
 Thanks in advance,
 
 _________________
 Jim Solberg
 Senior System Architect - Technology Services
 Conseco Finance Corporation
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | solberj | 
			  
				|  Posted: Tue Apr 16, 2002 11:26 am    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 18 Mar 2002Posts: 18
 Location: Jim Solberg
 
 | 
			  
				| Sorry about the format of the FDC log... 
 Could it be that MQ stores UID-based authorities internally??? Would those UID-based authorities be the ones that setmqaut/dspmqaut work on???
 
 We changed back to the original UID, and I can now start the queue manager, but the Unix admins want a consistent UID for MQ across all of our HP-UX boxes so that if we have to do a fail over (via HP ServiceGuard) we don't have authority conflicts...SO...we do have to change the UID for mqm when I come up with a resolution.
 
 Thoughts, anyone???
 
 _________________
 Jim Solberg
 Senior System Architect - Technology Services
 Conseco Finance Corporation
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mrlinux | 
			  
				|  Posted: Tue Apr 16, 2002 11:45 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 14 Feb 2002Posts: 1261
 Location: Detroit,MI USA
 
 | 
			  
				| Well the issue is making sure that all the permissions/ownership's are changed when you change th UID of mqm. So if you just issue chown -R /opt/mqm you will
 disable the suid bit's
 /opt/mqm   some files have the suid bit set
 /var/mqm   some files have the suid bit set
 
 _________________
 Jeff
 
 IBM Certified Developer MQSeries
 IBM Certified Specialist MQSeries
 IBM Certified Solutions Expert MQSeries
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | solberj | 
			  
				|  Posted: Tue Apr 16, 2002 12:12 pm    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 18 Mar 2002Posts: 18
 Location: Jim Solberg
 
 | 
			  
				| Sorry about the format of the FDC log... 
 Could it be that MQ stores UID-based authorities internally??? Would those UID-based authorities be the ones that setmqaut/dspmqaut work on???
 
 We changed back to the original UID, and I can now start the queue manager, but the Unix admins want a consistent UID for MQ across all of our HP-UX boxes so that if we have to do a fail over (via HP ServiceGuard) we don't have authority conflicts...SO...we do have to change the UID for mqm when I come up with a resolution.
 
 Thoughts, anyone???
 
 _________________
 Jim Solberg
 Senior System Architect - Technology Services
 Conseco Finance Corporation
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | solberj | 
			  
				|  Posted: Tue Apr 16, 2002 12:35 pm    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 18 Mar 2002Posts: 18
 Location: Jim Solberg
 
 | 
			  
				| Thanks for the reply, Jeff... 
 I passed the info  on to our admin guys; here's what they told me in response:
 
 They used the HP SAM (like SMITTY) tool to make the change.  The process it went through is roughly the following:
 
 - change the olduid to the newuid in the /etc/passwd file
 - recursively chown from the olduid to user mqm
 
 In a nutshell, they can't think of any reason why this wouldn't work...
 
 I did do a quick check of authorities/ownerships in /var/mqm and /opt/mqm when we first noticed the problem, but nothing jumped out at me...
 
 Regards,
 
 _________________
 Jim Solberg
 Senior System Architect - Technology Services
 Conseco Finance Corporation
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mrlinux | 
			  
				|  Posted: Thu Apr 18, 2002 3:51 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 14 Feb 2002Posts: 1261
 Location: Detroit,MI USA
 
 | 
			  
				| Did you clear Shared memory after the change to the new UID ???? 
 _________________
 Jeff
 
 IBM Certified Developer MQSeries
 IBM Certified Specialist MQSeries
 IBM Certified Solutions Expert MQSeries
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | solberj | 
			  
				|  Posted: Thu Apr 18, 2002 6:32 am    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 18 Mar 2002Posts: 18
 Location: Jim Solberg
 
 | 
			  
				| Jeff, 
 No, we did NOT...can I use ipcrm to do this, or do I have to boot the box???
 
 Thanks,
 
 _________________
 Jim Solberg
 Senior System Architect - Technology Services
 Conseco Finance Corporation
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | mrlinux | 
			  
				|  Posted: Thu Apr 18, 2002 6:52 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 14 Feb 2002Posts: 1261
 Location: Detroit,MI USA
 
 | 
			  
				| ipcrm will work. little script
 
 ipcs | grep mqm | while read type id d3
 do
 ipcrm -$type $id
 done
 
 run the above as mqm
 _________________
 Jeff
 
 IBM Certified Developer MQSeries
 IBM Certified Specialist MQSeries
 IBM Certified Solutions Expert MQSeries
 
 [ This Message was edited by: mrlinux on 2002-04-18 08:03 ]
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |