Pavel, Yes you are right. I don't put the redirection in the script. However, to test it out, I have to reipl the box. As you know, calling the script works everytime except reboot.
Thanks, Ian -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Pavel Tolkachev Sent: Saturday, 3 April 2004 1:26 AM To: [EMAIL PROTECTED] Subject: Re: AW: Boot problem on Solaris: solved but HOW? Hello, Thanks to all who answered! Hubert, thank you, we have it working as well. What we (Ian and I) could not do is to reproduce the problem in a normal (not boot-up) mode to understand its root cause. Tibor, we did not try the early tracing. I am not sure what more information from the script itself I need. We had a pretty good error message from strmqm complaining about not being authorized and the error status (not documented, though: 119. Anyone from IBM?). Gunter, thanks, yes it was one of the last resort ideas to go and compare all the environment -- but I think we have never actually done that. We will try it next time we reboot. Ian, I am not sure why you did not get messages. We created /var/mqm/init_d.log or some similar file at the beginning of the start script, changed its ownership to mqm:mqm and then appended to it the output of all commands, approximately in this manner: echo "will run strmqm..." >> $logFile strmqm ... >> $logFile 2>&1 rc=$? echo "error status $rc" >> $logFile So we had all the output in the log file. I will let the list know if I find the answer.. Cheers, Pavel "Kleinmanns, Hubert" To: [EMAIL PROTECTED] <Hubert.Kleinmanns@ cc: DREGIS.COM> Subject: AW: Boot problem on Solaris: solved but HOW? Sent by: MQSeries List <[EMAIL PROTECTED] AC.AT> 04/02/2004 04:34 AM Please respond to MQSeries List Hi Pavel, Ian, the following script starts my queue manager at boot time on Solaris: ------------------------ #!/bin/ksh # # MQSeries start/stop script # case "$1" in start) echo "Starting MQSeries daemons" su - mqm -c "/opt/mqm/bin/strmqm TESTQM" su - mqm -c "/opt/mqm/bin/strmqcsv TESTQM" ;; stop) echo "Stopping MQSeries daemons" su - mqm -c "/opt/mqm/bin/endmqm -i TESTQM" ;; restart) $0 stop $0 start ;; *) echo "Usage: $0 {start|stop|restart}" exit 1 ;; esac exit 0 ------------------------ On AIX just replace "opt" by "usr". I put this file to the directory "/etc/init.d" with name "mqm" and set up th following links: # ln -s /etc/init.d/mqm /etc/rc1.d/K18mqm # ln -s /etc/init.d/mqm /etc/rc2.d/S94mqm Regards Hubert -----Ursprungliche Nachricht----- Von: Chan, Ian M [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 2. April 2004 02:19 An: [EMAIL PROTECTED] Betreff: Re: Boot problem on Solaris: solved but HOW? Pavel, I want to know the answer too! We have the same problem on Sun Solaris and did the same thing to solve it after upgrading to v5.3 (it works in v5.2 without su mqm). There is even no error message produced in our case. MQ just not started after reboot. We have AIX running MQ v5.3 and startup script works OK even without su mqm. So as mentioned in the FAQ, it only affects Solaris and some Linux. Cheers, Ian -----Original Message----- From: MQSeries List [mailto:[EMAIL PROTECTED] Behalf Of Pavel Tolkachev Sent: Friday, 2 April 2004 9:26 AM To: [EMAIL PROTECTED] Subject: Boot problem on Solaris: solved but HOW? Hello, We had a problem -- with starting MQSeries 5.3 at bootup on Solaris -- actually exactly FAQ problem described in http://www.developer.ibm.com/tech/faq/results/0,1322,1%253A401%253A411%253A1 0%253Amq,00.html#q10 and we solved it all right as FAQ suggested. What drives me crazy, however, is that the problem itself could not be reproduced from the regular command prompt, no matter what command prompt it was. I have sudo root access on the machine and I tried all the ways of creating the process context similar to the boot environment -- like sudo su sudo su -, sudo sh, sudo ksh sudo ksh, then su - etc. etc. etc. We checked euid,egid,uid,gid and everything -- and all that was root and system (most of the time) and still our startup scripts always worked fine from the command line -- but not when system were booting (we added our root in mqm group, that did not help either) -- and the simple trick in the FAQ does the thing. I thought I knew Unix a little bit -- and now I am not sure :-( ... Does anybody have an idea what is the root cause of the problem described in the FAQ entry referred to above and how to reproduce it from the command prompt? What is that in the environment that is different when entering runlevel 3? BTW, the error message we were getting from strmqm was actually different from the one mentioned in the FAQ -- some error status 119 (not documented in Sys Adm Guide). Regards, Pavel -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive -- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com Archive: http://vm.akh-wien.ac.at/MQSeries.archive
