Author |
Message
|
Gaya3 |
Posted: Wed Apr 02, 2008 8:35 pm Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
My third turn:
1. what is the default authorization given for this particular queue manager? (OAM)
I want to know are there any root privileges has given to mqm.
2. Please try crtmqm sample and let me know the results, if it didnt create, then OAM has to refreshed.
Regards
Gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Challenger |
Posted: Thu Apr 03, 2008 2:00 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
gbaddeley wrote: |
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) |
Sorry, I couldn't find a way to display this any better. Note: /opt/mqm and /var/mqm are local filesysystems, while /home/mqm is a mount from remote storage.
mqm:/home/mqm>df -k
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/bootdg/rootvol 8268461 3753046 4432731 46% /
/proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
fd 0 0 0 0% /dev/fd
/dev/vx/dsk/bootdg/var 8268461 1620815 6564962 20% /var
swap 41114944 40 41114904 1% /var/run
/dev/vx/dsk/bootdg/export 92365779 6654667 84787455 8% /export
swap 41115736 832 41114904 1% /tmp
/export/optmqm 92365779 6654667 84787455 8% /opt/mqm
/export/varmqm 92365779 6654667 84787455 8% /var/mqm
/export/u01 92365779 6654667 84787455 8% /u01
ieeprodhome:/prodhome/home/mqm 847034984 798291456 48743528 95% /home/mqm
Comparison of kernel settings to Quick Beginnings shows that two settings was missed during upgrade:
--semsys:seminfo_semmnu was 1024
but should have been = 16384
--maxuprc was 800
but should have been = 1024
Queue managers were quiesced. Kernel settings were adjusted as above and the server was rebooted. Unlike the original event where queue managers were not started all at once, this time the queue managers were immediately restarted, with CHALLENGE first. It failed to start. The other nine queue managers also failed to start.
All ten queue managers had to be started with a different user ID, changing the presenting problem from one to all ten queue managers failing to start as 'mqm'. |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Apr 03, 2008 2:16 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
Gaya3 wrote: |
My third turn:
1. what is the default authorization given for this particular queue manager? (OAM)
I want to know are there any root privileges has given to mqm.
2. Please try crtmqm sample and let me know the results, if it didnt create, then OAM has to refreshed.
Regards
Gayathri |
Please answer this _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
Challenger |
Posted: Thu Apr 03, 2008 5:22 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
Please read the PM I sent asking for clarification of question #1.
And don't be snippy with the Challenger.  |
|
Back to top |
|
 |
Gaya3 |
Posted: Thu Apr 03, 2008 5:35 am Post subject: |
|
|
 Jedi
Joined: 12 Sep 2006 Posts: 2493 Location: Boston, US
|
have sent you the reply too
Regards
gayathri _________________ Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
Back to top |
|
 |
mehedi |
Posted: Thu Apr 03, 2008 6:28 am Post subject: |
|
|
Centurion
Joined: 11 Nov 2001 Posts: 102 Location: PSTech
|
Run these commands in the sequence specified
1. strmqtrc -m CHALLENGE -t all
2. strmqm CHALLENGE
3. endmqtrc -m CHALLENGE
4. dspmqtrc AMQppppp.qq.TRC ( to format trace output)
Trace data will be stored in /var/mqm/errors directory
AMQppppp.qq.TRC
Either post the output or review it and post anything you think is relevant.
Thanks
Mehedi |
|
Back to top |
|
 |
Challenger |
Posted: Thu Apr 03, 2008 8:22 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
Gaya3 wrote: |
1. what is the default authorization given for this particular queue manager? (OAM)
I want to know are there any root privileges has given to mqm.
2. Please try crtmqm sample and let me know the results, if it didnt create, then OAM has to refreshed.
|
I am still working with Gaya3 to understand the output requested in the first question.
For the second question:
The new queue manager is created successfully.
mqm:/home/mqm>crtmqm sample
WebSphere MQ queue manager created.
Creating or replacing default objects for sample.
Default objects statistics : 40 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
It is displayed successfully with dspmq.
mqm:/home/mqm>dspmq
QMNAME(sample)
But it cannot be started by the user 'mqm'.
mqm:/home/mqm>strmqm sample
mqm:/home/mqm> |
|
Back to top |
|
 |
Challenger |
Posted: Thu Apr 03, 2008 8:49 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
mehedi wrote: |
Run these commands in the sequence specified
1. strmqtrc -m CHALLENGE -t all
2. strmqm CHALLENGE
3. endmqtrc -m CHALLENGE
4. dspmqtrc AMQppppp.qq.TRC ( to format trace output)
Either post the output or review it and post anything you think is relevant.
|
L3 had us run a trace using these parameters:
strmqtrc -e -t all -t detail
L3 provided these comments after review of the trace:
By looking into the trace for strmqm, the strmqm process received a SIGBUS signal causing strmqm to terminate. Hence the queue manager failed to start. I have tested the queue manager provided by the customer. I am able to start without any problem in our test system. I am not able to speculate any reason from the analysis done so far for the failure in customer's system.
Is this good information for you? I can run another trace as you've asked, if you wish. |
|
Back to top |
|
 |
gbaddeley |
Posted: Thu Apr 03, 2008 5:02 pm Post subject: |
|
|
 Jedi Knight
Joined: 25 Mar 2003 Posts: 2538 Location: Melbourne, Australia
|
SIGBUS indicates a cpu hardware exception, say a byte alignment condition has not been met, like storing an 8 byte data item not on an 8 byte address boundary.
1. Has something crazy happened like Solaris has been booted into 32 bit mode rather than 64 bit?? |
|
Back to top |
|
 |
mehedi |
Posted: Thu Apr 03, 2008 5:31 pm Post subject: |
|
|
Centurion
Joined: 11 Nov 2001 Posts: 102 Location: PSTech
|
This is from the "quick beginnings for Solaris" manual.
The section headlined "Implications of a 64-bit queue manager"
"
When using the new 64-bit queue manager, the use of the LIBPATH and LD_LIBRARY_PATH environment variable is not advised. Setting these environment variables might result in you not being able to run any WebSphere® MQ commands. " .. and more
Are either of these variables set for the 'mqm' user ? If they are unset them.
Thanks
Mehedi |
|
Back to top |
|
 |
mehedi |
Posted: Thu Apr 03, 2008 5:34 pm Post subject: |
|
|
Centurion
Joined: 11 Nov 2001 Posts: 102 Location: PSTech
|
Please post the ouput of
1. set command for the 'mqm' user
2. set command for userid used to successfully start queue managers
Thanks
Mehedi |
|
Back to top |
|
 |
Challenger |
Posted: Fri Apr 04, 2008 8:02 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
[quote="Gaya3"]
Gaya3 wrote: |
1. what is the default authorization given for this particular queue manager? (OAM)
|
When v6 was installed, we said "yes" to all setuid as needed by the product.
Also, the 'mqm' ID is a NIS-based user, and it is used successfully to start queue managers on other servers. |
|
Back to top |
|
 |
Challenger |
Posted: Fri Apr 04, 2008 8:12 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
gbaddeley wrote: |
SIGBUS indicates a cpu hardware exception, say a byte alignment condition has not been met, like storing an 8 byte data item not on an 8 byte address boundary.
1. Has something crazy happened like Solaris has been booted into 32 bit mode rather than 64 bit?? |
I like your creative thinking!
The operating system is running in 64-bit mode.
The Challenger wishes to be forthcoming, and not try to trick anyone. So I will tell you that I think L3's analysis of the trace was superficial. I am willing to format the trace files for your review, but I will tell you that it is not the key to solving this problem. |
|
Back to top |
|
 |
Challenger |
Posted: Fri Apr 04, 2008 11:07 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
mehedi wrote: |
When using the new 64-bit queue manager, the use of the LIBPATH and LD_LIBRARY_PATH environment variable is not advised. Setting these environment variables might result in you not being able to run any WebSphere® MQ commands. " .. and more
Are either of these variables set for the 'mqm' user ? If they are unset them. |
Neither of these variables are set for the 'mqm' user. |
|
Back to top |
|
 |
Challenger |
Posted: Fri Apr 04, 2008 11:20 am Post subject: |
|
|
 Centurion
Joined: 31 Mar 2008 Posts: 115
|
mehedi wrote: |
Please post the ouput of
1. set command for the 'mqm' user
2. set command for userid used to successfully start queue managers
|
mqm user environment
HZ=
LC_COLLATE=en_US.ISO8859-1
LC_CTYPE=en_US.ISO8859-1
LC_MESSAGES=C
LC_MONETARY=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
LOGNAME=mqm
MAIL=/var/mail/mqm
PATH=.:/opt/sfw/bin:/opt/mqm/bin:/opt/mqm/samp/bin:/usr/bin:
PS1=mqm:$PWD>
SHELL=/bin/sh
TERM=xterm
TZ=US/Central
environment of user that works
_=/usr/bin/env
LC_MONETARY=en_US.ISO8859-1
SSH_TTY=/dev/pts/1
PATH=/usr/bin:/usr/sbin:/opt/sfw/bin:/var/mqm:/var/wmqi:/opt/mqm/bin:/var/mqm/utilities:/opt/mqm/samp/bin:/usr/bin
LOGNAME=challenger
MAIL=/var/mail//challenger
PS1=$USER:$PWD>
USER=challenger
LC_MESSAGES=C
LC_CTYPE=en_US.ISO8859-1
SHELL=/bin/ksh
HOME=/home/challenger
LC_COLLATE=en_US.ISO8859-1
LC_NUMERIC=en_US.ISO8859-1
SSH_CONNECTION=000.000.000.000 4597 000.000.000.00022
SSH_CLIENT=000.000.000.000 4597 22
TERM=xterm
PWD=/home/challenger
TZ=US/Central
Last edited by Challenger on Sun Apr 06, 2008 12:19 pm; edited 1 time in total |
|
Back to top |
|
 |
|