| Author |
Message
|
| alora |
 Posted: Thu Mar 02, 2006 7:56 am Post subject: Cannot get started at reboot ; Command line works OK |
 |
|
Newbie
Joined: 02 Mar 2006
Posts: 3
|
Operating System - Solaris 10
MQ Series Version - V6
History:
1. I recently upgraded from solaris 8 => 10 & MQ 5.3 => 6
2. I can start MQ from the command line (As user root the proceses run as mqm)
3. I cannot start MQ as user mqm like i used to in the previous versions?
4. The mqseries /etc/init.d/mqseries script only starts the following two processes at system boot:
# ps -ef | grep mqm
mqm 980 1 0 12:49:34 ? 0:00 runmqlsr -t tcp -m CORP.WS.TEST
mqm 982 980 0 12:49:34 ? 0:00 /opt/mqm/bin/amqzmgr0 -m CORP.WS.TEST
#
5. When running the script manually all of the required processes are created:
# ps -ef | grep mqm
mqm 1130 1 0 12:53:37 pts/1 0:00 runmqlsr -t tcp -m CORP.WS.TEST
mqm 1116 1 1 12:53:34 ? 0:00 amqzxma0 -m CORP.WS.TEST
mqm 1132 1 0 12:53:40 pts/1 0:00 runmqchl -c WS.TO.AS400 -m CORP.WS.TEST
root 1139 1054 0 12:53:49 pts/1 0:00 grep mqm
mqm 1117 1116 0 12:53:34 ? 0:00 /opt/mqm/bin/amqzfuma -m CORP.WS.TEST
mqm 1118 1116 0 12:53:34 ? 0:00 amqzmuc0 -m CORP.WS.TEST
mqm 1119 1116 0 12:53:34 ? 0:00 amqzmur0 -m CORP.WS.TEST
mqm 1120 1116 0 12:53:35 ? 0:00 /opt/mqm/bin/amqrrmfa -t2332800 -s2592000 -p2592000 -g5184000 -c3600 -m CORP.WS
mqm 1121 1116 0 12:53:35 ? 0:00 /opt/mqm/bin/amqzdmaa -m CORP.WS.TEST
mqm 1122 1116 0 12:53:35 ? 0:00 /opt/mqm/bin/amqzmgr0 -m CORP.WS.TEST
mqm 1127 1116 0 12:53:36 ? 0:00 amqzlaa0 -mCORP.WS.TEST -fip0
mqm 1128 1122 0 12:53:36 ? 0:00 /opt/mqm/bin/runmqchi -m CORP.WS.TEST -r
mqm 1129 1122 0 12:53:36 ? 0:00 /opt/mqm/bin/amqpcsea CORP.WS.TEST
mqm 1134 1116 0 12:53:40 ? 0:00 amqzlaa0 -mCORP.WS.TEST -fip1 |
|
| Back to top |
|
 |
| wschutz |
| Posted: Thu Mar 02, 2006 8:26 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
3. I cannot start MQ as user mqm like i used to in the previous versions?
|
lets start with that problem... what happens when you enter strmqm? (paste the output), is there anything in AMQERR01.LOG and any ffst (*FDC) files produced?
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 02, 2006 8:42 am Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| alora wrote: |
4. The mqseries /etc/init.d/mqseries script only starts the following two processes at system boot:
# ps -ef | grep mqm
mqm 980 1 0 12:49:34 ? 0:00 runmqlsr -t tcp -m CORP.WS.TEST
mqm 982 980 0 12:49:34 ? 0:00 /opt/mqm/bin/amqzmgr0 -m CORP.WS.TEST |
Could it be that this init.d script runs too early in the bootup process? It's possible that some of the OS services required by MQ are not started or available at the precise time strmqm is called by your script, if it runs too early. Make the qmgr startup script one of the very last things to run. |
|
| Back to top |
|
|
| alora |
| Posted: Thu Mar 02, 2006 12:01 pm Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 3
|
| mvic wrote: |
| alora wrote: |
4. The mqseries /etc/init.d/mqseries script only starts the following two processes at system boot:
# ps -ef | grep mqm
mqm 980 1 0 12:49:34 ? 0:00 runmqlsr -t tcp -m CORP.WS.TEST
mqm 982 980 0 12:49:34 ? 0:00 /opt/mqm/bin/amqzmgr0 -m CORP.WS.TEST |
Could it be that this init.d script runs too early in the bootup process? It's possible that some of the OS services required by MQ are not started or available at the precise time strmqm is called by your script, if it runs too early. Make the qmgr startup script one of the very last things to run. |
I made sure that MQ is the last process that is started in /etc/rc3.d/S991mqseries |
|
| Back to top |
|
|
| mvic |
| Posted: Thu Mar 02, 2006 1:04 pm Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| alora wrote: |
| I made sure that MQ is the last process that is started in /etc/rc3.d/S991mqseries |
And I assume (though you didn't say) that you still see the very same symptoms?
OK, well instead of strmqm QMNAME try
| Code: |
| truss -aefld -otrussoutputfile strmqm QMNAME |
and read the contents of trussoutputfile in case it gives any hints about how the other MQ processes died, and when.
Did you look in the syslog output and/or any other location where init.d outputs go? |
|
| Back to top |
|
|
| alora |
| Posted: Fri Mar 03, 2006 1:59 am Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Newbie
Joined: 02 Mar 2006
Posts: 3
|
| mvic wrote: |
| alora wrote: |
4. The mqseries /etc/init.d/mqseries script only starts the following two processes at system boot:
# ps -ef | grep mqm
mqm 980 1 0 12:49:34 ? 0:00 runmqlsr -t tcp -m CORP.WS.TEST
mqm 982 980 0 12:49:34 ? 0:00 /opt/mqm/bin/amqzmgr0 -m CORP.WS.TEST |
Could it be that this init.d script runs too early in the bootup process? It's possible that some of the OS services required by MQ are not started or available at the precise time strmqm is called by your script, if it runs too early. Make the qmgr startup script one of the very last things to run. |
I'm not sure if the new features of Solaris 10 inetconv & inetadm has to be configured to work with starting up services like MQ?
I am an old-school < Solaris 9 person !! |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Mar 03, 2006 2:18 am Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| alora wrote: |
| I'm not sure if the new features of Solaris 10 inetconv & inetadm has to be configured to work with starting up services like MQ? |
I doubt it. You said strmqm worked after the system had started. So the question is, why did it not work at the time it is tried from init.d. Did you try the truss command?
(Also inet* sounds like inetd - presumably these things relate only to inetd or its "modern" equivalent. NB. The queue manager startup itself - which appears not to work in your specific case - does not rely on any networking services, so I wouldn't expect inetd setup to have caused this). |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Mar 03, 2006 2:38 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
can you post you init.d script here? (perhaps the problem is related to #3 above)
_________________
-wayne |
|
| Back to top |
|
|
| mvic |
| Posted: Fri Mar 03, 2006 3:08 am Post subject: Re: Cannot get started at reboot ; Command line works OK |
|
|
Jedi
Joined: 09 Mar 2004
Posts: 2080
|
| alora wrote: |
| 3. I cannot start MQ as user mqm like i used to in the previous versions? |
Good point Wayne.
This sounds strange, but is the mqm user in the mqm group on this machine? |
|
| Back to top |
|
|
| csaunders |
| Posted: Wed Mar 08, 2006 12:53 pm Post subject: |
|
|
Acolyte
Joined: 27 Mar 2003
Posts: 64
Location: Arlington, Va
|
| yeah if you dont specifically su to mqm in your init scripts, it will try and start it as root, and if root is not in the group mqm, it will not have permission to start |
|
| Back to top |
|
|
| bobw2829 |
| Posted: Wed Mar 15, 2006 6:59 am Post subject: |
|
|
Newbie
Joined: 15 Mar 2006
Posts: 2
|
Hi All,
I'm also working on this problem with alora. One of the things I believe is the problem may be the /etc/projects configuration. Here's some interesting info from IBM:
| Quote: |
Solaris 10 does not have "rlim_fd_max" or "rlim_fd_cur" settings.
However, it does have a "process.max-file-descriptor" setting. This new setting provides a huge amount of flexibility. This flexibility brings with it some risk of inadvertent resource limitation. That risk has always been there, in that the qmgr could be started from a shell with an overly restrictive ulimit setting. But now, you also have to worry about whether your "project" settings also limit resources.
Our customers have two basic ways of configuring their systems under this regime:
1) Ensure that all limitations are generally set to suitably unrestrictive values. To do this, you need to find the full list of Solaris "projects" that exist on the system: type "projects -l". Then you need to use the "projmod" command to set the projects to have suitably unrestrictive settings.
or
2) Ensure that all limitations are set to suitably unrestrictive values, for all users who will be executing WMQ commands or starting applications that will be connecting to WMQ. This also applies to the starting of applications that may themselves start other applications that connect to WMQ.
Since it can be difficult to ensure that (2) completely covers all eventualities, choosing (1) is more likely to avoid the possibility of inadvertently encountering a resource restriction. This is a less "controlled" approach but in practice provides less opportunity for failure.
The command to modify the "process.max-file-descriptor" setting is:
projmod -s -K 'process.max-file-descriptor=(basic,10000,deny)' PROJ
where PROJ is the name of a project.
|
I tried using the projmod command using "default" for project name to no avail. I'm going to post the startup scripts in the following reply.
Thanks,
Bob |
|
| Back to top |
|
|
| bobw2829 |
| Posted: Wed Mar 15, 2006 7:19 am Post subject: |
|
|
Newbie
Joined: 15 Mar 2006
Posts: 2
|
|
| Back to top |
|
|
|
|
