| Author |
Message
|
| Challenger |
 Posted: Tue Apr 01, 2008 4:37 am Post subject: Challenge Question - 04 / 2008 - Week One |
 |
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
April's Challenge is a bit different! and offers you an opportunity for interaction with the Challenger.
We'll state the presenting problem. You may ask questions and/or you may ask for us to run commands to give you more information, and we will post the result. You may ask two questions per post. After your two questions are answered, you are free to post another two questions.
The winner will be chosen based upon the quality of troubleshooting steps and the type of questions asked; and, of course, solving the problem will be a plus. This is a real-life problem that occurred in an MQ production environment.
Presenting problem:
After upgrade from v5.3 CSD13 to v6.0.2.2, nine active queue managers on the server started correctly with the 'mqm' user ID. Later in the day of the upgrade, an attempt was made to start a tenth queue manager, but it would not start as 'mqm'; it had to be started with a different user whose ID is a member of the 'mqm' group.
What additional information do you need to determine what's wrong, what would you try, and how can it be fixed?
Last edited by Challenger on Sun Apr 06, 2008 2:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Tue Apr 01, 2008 4:48 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
Here are my questions?
1. What was the error you got when you try to start queue manager using mqm user?
2. Whats there in error log/any FDC etc ?
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| Challenger |
| Posted: Tue Apr 01, 2008 7:31 am Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
Excellent starting questions for your first two!
The stdout when trying to start the queue manager looks like this:
| Quote: |
mqm:/home/mqm>strmqm CHALLENGE
mqm:/home/mqm>
|
After issuing the strmqm command, we are immediately returned to the command prompt with no stdout at all. It is nearly instantaneous.
There are no FDCs. There is nothing in the queue manager log file.
Last edited by Challenger on Tue Apr 01, 2008 12:04 pm; edited 1 time in total |
|
| Back to top |
|
|
| fschofer |
| Posted: Tue Apr 01, 2008 10:27 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
please post the content of mqs.ini and the qm.ini of the failed queue manager.
Greetings
Frank |
|
| Back to top |
|
|
| Challenger |
| Posted: Tue Apr 01, 2008 12:17 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
mqm:/home/mqm>cat /var/mqm/mqs.ini
#********************************************************************
#*
#* <START_COPYRIGHT>
#* Licensed Materials - Property of IBM
#*
#* 63H9336
#* (C) Copyright IBM Corporation 1994, 2000
#*
#* <END_COPYRIGHT>
#*
#********************************************************************
#***********************************************************************
#* Module Name: mqs.ini
#* Type : WebSphere MQ Machine-wide Configuration File
#* Function : Define WebSphere MQ resources for an entire machine *#
#*
#***********************************************************************
#* Notes :
#* 1) This is the installation time default configuration
#*
#***********************************************************************#
AllQueueManagers:
#********************************************************************#
#* The path to the qmgrs directory, below which queue manager data
#* is stored
#********************************************************************
DefaultPrefix=/var/mqm
ClientExitPath:
ExitsDefaultPath=/var/mqm/exits
LogDefaults:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogDefaultPath=/var/mqm/log
QueueManager:
Name=DHS.TIERS.PRDTRN1
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN1
QueueManager:
Name=DHS.TIERS.PRDTRN2
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN2
QueueManager:
Name=DHS.TIERS.PRDTRN3
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN3
QueueManager:
Name=DHS.TIERS.PRDTRN4
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN4
QueueManager:
Name=DHS.TIERS.TRNPRCT1
Prefix=/var/mqm
Directory=DHS!TIERS!TRNPRCT1
QueueManager:
Name=DHS.TIERS.TRNTEST1
Prefix=/var/mqm
Directory=DHS!TIERS!TRNTEST1
QueueManager:
Name=DHS.TIERS.TRNDEV1
Prefix=/var/mqm
Directory=DHS!TIERS!TRNDEV1
QueueManager:
Name=DHS.TIERS.PRDTRN5
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN5
QueueManager:
Name=DHS.TIERS.PRDTRN6
Prefix=/var/mqm
Directory=DHS!TIERS!PRDTRN6
QueueManager:
Name=CHALLENGE
Prefix=/var/mqm
Directory=CHALLENGE
mqm:/home/mqm>cat /var/mqm/qmgrs/CHALLENGE/qm.ini
#*******************************************************************
#* Module Name: qm.ini
#* Type : WebSphere MQ queue manager configuration file
# Function : Define the configuration of a single queue manager
#*
#*******************************************************************
#* Notes :
#* 1) This file defines the configuration of the queue manager
#*
#*******************************************************************#
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#*
#*
Log:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/CHALLENGE/
LogWriteIntegrity=TripleWrite
Service:
Name=AuthorizationService
EntryPoints=13
ServiceComponent:
Service=AuthorizationService
Name=MQSeries.UNIX.auth.service
Module=/opt/mqm/lib64/amqzfu
ComponentDataSize=0 |
|
| Back to top |
|
|
| Challenger |
| Posted: Tue Apr 01, 2008 12:25 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| After your questions are answered, you are free to post two more! There is no limit to the number of questions a single person can ask, only that you ask them two at a time so that we don't have information overload. |
|
| Back to top |
|
|
| AkankshA |
| Posted: Tue Apr 01, 2008 8:01 pm Post subject: |
|
|
Grand Master
Joined: 12 Jan 2006
Posts: 1494
Location: Singapore
|
1) kindly try the following command using mqm user id and let us know the output...
amqmdain start CHALLENGE
2) Kindly detail the steps you followed for migration... did u do uninstall 5.3 and install v6 or simple upgrade
_________________
Cheers
Last edited by AkankshA on Tue Apr 01, 2008 9:15 pm; edited 1 time in total |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Tue Apr 01, 2008 8:28 pm Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
My second turn: Here are my questions
1. what is the default authorization given (MQ.UNIX.authorization.service) for this particular queue manager?
2. OAM is enabled in this scenario, Will you please remove this stanza and restart the queue manager, So no authorization checks are made at all.
Regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Tue Apr 01, 2008 9:43 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
1. What are the user resource limits for 'mqm', ie the output of the 'ulimit -a' command?
2. What is the Unix operating system and version? |
|
| Back to top |
|
|
| mehedi |
| Posted: Wed Apr 02, 2008 6:28 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2001
Posts: 102
Location: PSTech
|
There were no errors recorded in the MQ logs , no were any fdcs created, and no error messages were output from the the MQ command strmqm.
In this case MQ's error recording facility does not provide any information. I suspect , the error recording facility is itself
is failing to perform its function.
This is the question i am trying to answer
Does MQ user(mqm) have access to resources required to perform these operations. ?
My two questions are -
Is the 'mqm' userid still in the 'mqm' group ?
What are the attributes (group:user) permissions for
these two filesystems /var/mqm (MQ data and logs) and /usr/opt/mqm (mq application files) directory and sub-directory. ?
Regards
Mehedi |
|
| Back to top |
|
|
| Challenger |
| Posted: Wed Apr 02, 2008 7:49 am Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| AkankshA wrote: |
1) kindly try the following command using mqm user id and let us know the output...
amqmdain start CHALLENGE
2) Kindly detail the steps you followed for migration... did u do uninstall 5.3 and install v6 or simple upgrade |
The amqmdain command is not available, as the operating system is Solaris 9.
The recommended upgrade process from Solaris Quick Beginnings was followed. Three servers had been previously upgraded in the same manner (successfully), with a repeatable process having been developed and documented.
v5.3 fixpacks were uninstalled, followed by uninstallation of the base v5.3 product. The uninstallations as well as the installation of v6 was done using the Solaris "pkg" commands. |
|
| Back to top |
|
|
| Challenger |
| Posted: Wed Apr 02, 2008 1:48 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| Gaya3 wrote: |
1. what is the default authorization given (MQ.UNIX.authorization.service) for this particular queue manager?
2. OAM is enabled in this scenario, Will you please remove this stanza and restart the queue manager, So no authorization checks are made at all. |
I am not sure what you mean by your first question. Please clarify.
The contents of qm.ini were altered to be only:
ExitPath:
ExitsDefaultPath=/var/mqm/exits/
ExitsDefaultPath64=/var/mqm/exits64/
#* *#
#* *#
Log:
LogPrimaryFiles=3
LogSecondaryFiles=2
LogFilePages=1024
LogType=CIRCULAR
LogBufferPages=0
LogPath=/var/mqm/log/CHALLENGE/
LogWriteIntegrity=TripleWrite
The result when trying to start the queue manager as 'mqm' is the same as before:
mqm:/home/mqm>strmqm CHALLENGE
mqm:/home/mqm> |
|
| Back to top |
|
|
| Challenger |
| Posted: Wed Apr 02, 2008 1:50 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| gbaddeley wrote: |
1. What are the user resource limits for 'mqm', ie the output of the 'ulimit -a' command?
2. What is the Unix operating system and version? |
mqm:/home/mqm>ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 10000
vmemory(kbytes) unlimited
The operating system is Solaris 9. |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Wed Apr 02, 2008 2:10 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
1. What are the details of all the file systems? (output 'df -k' command)
2. What are the Solaris 9 kernel parameter settings which are relevant to MQ, semxxx, shmxxx and rlim_xxxx ? (commands are on page 14-15 of WMQ for Solaris Quick Beginnings V6.0) |
|
| Back to top |
|
|
| Challenger |
| Posted: Wed Apr 02, 2008 2:28 pm Post subject: |
|
|
Centurion
Joined: 31 Mar 2008
Posts: 115
|
| mehedi wrote: |
This is the question i am trying to answer
Does MQ user(mqm) have access to resources required to perform these operations. ?
My two questions are -
Is the 'mqm' userid still in the 'mqm' group ?
What are the attributes (group:user) permissions for
these two filesystems /var/mqm (MQ data and logs) and /usr/opt/mqm (mq application files) directory and sub-directory. ?
|
The 'mqm' ID is NIS-based; it is not a local ID.
Here is the output of 'mqm' in the NIS passwd file:
mqm:/home/mqm>ypcat passwd | grep mqm
mqm:*****:8014:GROUP WebSphere MQ Admin:/home/mqm:/bin/sh
You'll notice that the primary group is "8014".
Here is the output of the NIS group file:
mqm:/home/mqm>ypcat group | grep mqm
mqm::8014:mqm
You'll notice that the group number is "8014" and the user 'mqm' is a member.
For the sake of space, I won't paste the output of a recursive display of the two filesystems that you mention. Here is the root level:
mqm:/home/mqm>ls -la /var | grep mqm
drwxrwsr-x 13 mqm mqm 512 Apr 1 15:02 mqm
mqm:/home/mqm>ls -la /opt | grep mqm
dr-xr-xr-x 12 mqm mqm 512 Mar 1 09:56 mqm
Note: this is Solaris so the installation directory is /opt/mqm (rather than /usr/opt/mqm.)
Let me offer assurance, also, that the file permissions were thoroughly reviewed (recursively) by IBM tech support and that the permissions are correct and adequate. |
|
| Back to top |
|
|
|
|
