| Author |
Message
|
| Crille76 |
 Posted: Mon Mar 08, 2010 2:21 am Post subject: Problems with MS0L Support pac |
 |
|
Newbie
Joined: 15 Aug 2008
Posts: 9
|
Hello,
I have a QM running in a Windows Cluster, with linear logging.
Current MQ version 7.0.1.1 running on Win 2008 32-bit cluster.
To help clean up the logs automatically, i set up a batch file that runs once every night. First it runs rcdmqimg, then an hour later it runs MS0L (latest sep 2009 version).
This has worked without any problems for many months now, until last week when i discovered that the logs started eating up disk space. And after looking into why, i noticed that MS0L wasn't doing it's job.
It shows the following:
| Quote: |
2010-03-08 10:50:08.784 :: MS0L Parsing input...
2010-03-08 10:50:08.784 :: MS0L Logfile initialized at: G:\backup\mqllm_QM01801.log
2010-03-08 10:50:08.784 :: MS0L MQ Linear Logfile Maintenance Initializing
2010-03-08 10:50:08.784 :: Starting MQ Linear Logfile Maintenance for Queue Manager: QM01801
2010-03-08 10:50:08.784 :: Unable to load Prior Execution Values File from g:\MQDATA\log\QM01801\active\MS0L_lastRun.properties
2010-03-08 10:50:08.784 :: Execution of MS0L will be based on the following parameters:
*** Program Arguments:
Queue Manager Name [-q ] QM01801
Base MQ Product Directory [-d ] g:\MQDATA
MQ Logfile Location Path [-lp] g:\MQDATA\log\QM01801\active
MS0L Output Log filename [-l ] G:\backup\mqllm_QM01801.log
Archive Output Directory [-a ] G:\backup
Temporary Output Directory [-t ] C:\TEMP
Windows Machine Name [-m ] <UNSET>
Maximum Wrap Gap [-w ] 1
*** Configurations & Settings:
MQ Configuration File C:\TEMP\MQRegValues.QM01801.txt
MQ Logfile Type [linear/circular] LINEAR
Queue Manager Path g:\MQDATA\qmgrs\QM01801
Error Log Path g:\MQDATA\qmgrs\QM01801\errors
Previous run values [log values] g:\MQDATA\log\QM01801\active\MS0L_lastRun.properties
Previous Restart Logfile <UNSET>
Previous Recovery Logfile <UNSET>
2010-03-08 10:50:08.800 :: Temporary Directory Specified: C:\TEMP
2010-03-08 10:50:08.831 :: Removing temporary MQ Error log file: C:\TEMP\AMQERR01.LOG
2010-03-08 10:50:08.831 :: com.ibm.ms0l.MqLinearLogfileMaint :: Unable to locate oldest file required for Restart. Process HALTED!
MS0L ABORTED! |
Since this is a Windows cluster, i have run commands to move some of the MQ installation files to the network disc, hence the odd "Base MQ Product Directory".
I cannot understand why it suddenly cannot find the oldest file required. The rcdmqimg command runs fine, and it writes to the event log which the oldest log files are.
And yes i'm working on the currently active node (A/P 2 node cluster).
//Chris |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Mar 08, 2010 8:31 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
You probably need a symlink or equivalent in /var/mqm/log to point to the qmgr's log if it is not in this directory.
On Unix, I always symlink the qmgr's log directory to /var/mqm/log.
I believe MS0L is dependent on this symlink and does not check the qm.ini file to look at where the log actually is. May be an enhancement request for the next version?
As to your problem... make sure the support pack can access the qmgr's error log in the usually expected directory (symlinks etc...).
Make sure that the error file actually contains the messages for media recovery log and restart log. The rest should then work normally.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Mon Mar 08, 2010 10:03 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
My immediate question is - what changed?
Did this...
| Quote: |
| 2010-03-08 10:50:08.784 :: Unable to load Prior Execution Values File from g:\MQDATA\log\QM01801\active\MS0L_lastRun.properties |
...appear before, when it was working?
Is the error log rolling, therefore (as fjb_saper has pointed out) the restart/recovery entries have 'disappeared'?
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Mar 09, 2010 12:00 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
THIS just in on a Technote.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| Crille76 |
| Posted: Tue Mar 09, 2010 12:19 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2008
Posts: 9
|
| exerk wrote: |
| My immediate question is - what changed? |
This is what i'm trying to find out. We had server maintenance on the 14th and as far as i can see, the last time MS0L was run successfully was on the 19th. However there are a number of applications running here, and i'm not the only admin, so i'm mainly trying to gather info right now.
We recently patched to MQ 7.0.1.1 though, maybe that's why. I have to set up a lab server to test this.
| exerk wrote: |
Did this...
Quote:
2010-03-08 10:50:08.784 :: Unable to load Prior Execution Values File from g:\MQDATA\log\QM01801\active\MS0L_lastRun.properties
...appear before, when it was working? |
No. MS0L creates a small log file in the active MQ log folder, where is stores date last run etc. I wanted to see if it created a new one if i removed it from there, however it doesn't. |
|
| Back to top |
|
|
| Crille76 |
| Posted: Thu Mar 11, 2010 3:44 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2008
Posts: 9
|
I have a hard time recreating the problem on my lab server 
Versions of MQ doesn't matter it seems.
Maybe a total queue manager reconstruction will help, getting the logs to start over at 0. Will see on server maintenance, Sunday. |
|
| Back to top |
|
|
| Crille76 |
| Posted: Tue Mar 23, 2010 4:30 am Post subject: |
|
|
Newbie
Joined: 15 Aug 2008
Posts: 9
|
| Apparently, in MQ Version 7.0.1.1, the timestamp entry of the logs were changed. This is what's causing MS0L to fail. There is a new version of the support pac out that fixes the issue. |
|
| Back to top |
|
|
|
|
