| Author |
Message
|
| premkumar |
 Posted: Wed Oct 06, 2004 10:05 pm Post subject: TRIGGER MONITOR IS NOT GETTING STARTED |
 |
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
hi all,
I am starting the trigger monitor from mqm user login in AIX environment through cron. The command is ..
"nohup runmqtrm -m P.BLR.FDM.02 -q PBLRFDM02.INITQ&"
The above command is executed through cron by the file name runtrig.sh(which contails the above command)
I am able to see the process running for the above command but nohup.out file is not created and triggering process is also not happening.
If i kill the process and run the same script manually it is fine. I am facing this problem only when i put it as a cron job.
Please help me out.
Thanks in advance.
Premkumar.S
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
 |
| siliconfish |
| Posted: Wed Oct 06, 2004 11:06 pm Post subject: |
|
|
Master
Joined: 12 Aug 2002
Posts: 203
Location: USA
|
why are u running trigger monitor as cron job?
_________________
siliconfish |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Thu Oct 07, 2004 5:31 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
|
| Back to top |
|
|
| premkumar |
| Posted: Thu Oct 07, 2004 8:22 pm Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
Hi Roger,
i am starting the Trigger Monitor with the QueueManager Start up script only. The start up script is schedueld in cron.
Please find my start up script QMStartUp.sh(This script has been scheduled in cron).
The OS used is AIX 5.2 and QMQ 5.2 version. i am facing this problem after upgrading the OS and WMQ.
If i start the startup script manually the triggermonitor is generation nohup.out and triggering is also fine.
f the script has been scheduled in cron the Queuemanager is getting started but the triggermonitor is not creating the file nohup.out and triggering process is also not happening.but i am able to see that trigger process is running(ps -ef | grep runmqtrm).
QMStartUp.sh
echo 'dis qmgr' | runmqsc P.BLR.FDM.02 > /dev/null 2>&1
fn_ret=$?
if [ $fn_ret = 0 ]
then
echo "Queue Manager $qmgr Already Running"
else
rm nohup.out
strmqm P.BLR.FDM.02 # To start FDM Queue Manager
strmqcsv P.BLR.FDM.02 # To start FDM Command Server
nohup runmqtrm -m P.BLR.FDM.02 -q PBLRFDM02.INITQ& # To start FDM Trigger Monitor
fi
Hope the u understand my problem...
Thanks and Regards,
Premkumar.S
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
|
| siliconfish |
| Posted: Thu Oct 07, 2004 9:26 pm Post subject: |
|
|
Master
Joined: 12 Aug 2002
Posts: 203
Location: USA
|
runmqtrm is not process of queue manager, and it may run even if the queue manager is ended.
u have to also check if the runmqtrm is running before starting it.
_________________
siliconfish |
|
| Back to top |
|
|
| premkumar |
| Posted: Thu Oct 07, 2004 11:44 pm Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
The Server itself gets restarted...I have also cheked there is no trigger monitor process is running...
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Fri Oct 08, 2004 7:26 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
Well, if you are rebooting the box then why don't you let the OS execute your startup script??????? (and not use cron)
Here's a script that I use on Solaris called: S91mqm-XXXXXX and it is stored in /etc/rc3.d It works just fine (I don't use nohup for runmqtrm):
| Code: |
#!/sbin/sh
#
#
# Startup script for XXXXXX queue manager
case "$1" in
'start')
su - mqm -c "cd /opt/mqm/bin; ./strmqm XXXXXX "
su - mqm -c "cd /opt/mqm/bin; ./strmqcsv XXXXXX "
su - mqm -c "cd /opt/mqm/bin; ./runmqlsr -m XXXXXX -t TCP -p 1415 & "
su - mqm -c "cd /opt/mqm/bin; ./runmqchi -m XXXXXX &"
su - mqm -c "cd /opt/mqm/bin; ./runmqtrm -m XXXXXX &"
;;
'stop')
su - mqm -c "cd /opt/mqm/bin; ./endmqm -i XXXXXX"
su - mqm -c "cd /opt/mqm/bin; ./endmqlsr -m XXXXXX &"
;;
*)
echo "Usage: $0 { start | stop }"
exit 1
;;
esac
exit 0 |
Hope that helps.
Regards,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
| Anirud |
| Posted: Fri Oct 08, 2004 11:10 am Post subject: |
|
|
Master
Joined: 12 Feb 2004
Posts: 285
Location: Vermont
|
| I have a script like what Roger mentioned on AIX (except that it is usr/mqm/bin instead of opt/mqm/bin). It is working fine. If I were you, I would use the same. |
|
| Back to top |
|
|
| premkumar |
| Posted: Wed Oct 13, 2004 12:48 am Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
Hi,
i have put the script in OS Start script. Still i am facing the same problem.
The process for the trigger monitor is runnining but nohup.out file is not getting created. The triggering process is also is not triggered. When i kill and run the same command it is fine.
How to check the triggermonitor process has been started successfully with out errors?
regards,
Premkumar.S
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
|
| Manikandan |
| Posted: Wed Oct 13, 2004 2:45 am Post subject: |
|
|
Voyager
Joined: 07 Jul 2004
Posts: 78
|
It is better you have a working dir
Here in your script who knows where the nohup.out is generated.the file is generated somewhere else
you can modify the script as
modify from
---------------
nohup runmqtrm -m P.BLR.FDM.02 -q PBLRFDM02.INITQ&
to
--
cd <somedir>
nohup /opt/mqm/bin/runmqtrm ..... &
Now the nohup would be created in the <somedir> |
|
| Back to top |
|
|
| premkumar |
| Posted: Wed Oct 13, 2004 3:49 am Post subject: |
|
|
Apprentice
Joined: 24 Feb 2004
Posts: 40
|
Hi Manikandan,
The problem is the messages are not get triggered, even though the trigger monitor is running. The nohup.out is the ony source i can check the message is triggereing properly or not. nohup.out is not created any where.
Regards,
Premkumar.S
_________________
Thanks and Regards,
Premkumar.S |
|
| Back to top |
|
|
| vennela |
| Posted: Wed Oct 13, 2004 4:30 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Try this
| Code: |
| nohup runmqtrm -m TEST -q SYSTEM.DEFAULT.INITIATION.QUEUE > /tmp/mqseries.nohup 2>&1 & |
|
|
| Back to top |
|
|
| RogerLacroix |
| Posted: Wed Oct 13, 2004 8:28 am Post subject: |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
Hi,
IF you copied my startup script EXACTLY (did not add the nohup command) then the nohup.out file is created (on Solaris) in the /export/home/mqm directory.
Another way to verify that the trigger monitor is running, is to do the following command:
| Code: |
| ps -ef | grep runmqtrm |
Note: Most triggering errors have nothing to do with the trigger monitor. Usually, there is a problem with the setup of the triggered queue or the Process definition.
i.e.
- Did you provide a INITQ in the triggered queue? Does it match the INITQ that the trigger monitor is using?
- Did you remember to set TRIGGER (turn triggering on) for the trigger queue?
- Does the Process definition specified in the trigger queue actually exist?
- Are there any messages in the Dead Letter Queue? RC=265?
- - If RC=265, then the APPLID has an invalid PATH and / or executable name.
- Is the triggered task a very long running program? If so, did you put an '&' in the Environment Data field? This will release it to the background? Because the trigger monitor invokes the triggered program synchronously, if you don't put the '&'. In other words, it WAITS.
and finally, did you read Jeff's post?
http://www.mqseries.net/phpBB2/viewtopic.php?t=12988
Hope that helps.
Regard,
Roger Lacroix
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
|
|
|
