| Author |
Message
|
| elikatz |
 Posted: Sat Oct 17, 2009 3:39 pm Post subject: amq 7467 and amq 7468 are not written to AMQERRXX.LOG |
 |
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
hi all,
I have a windows 2003 cluster machine running MQ 5.3 (CDS 12) with linear logs.
I'm trying to use SupportPac ms0l in order to keep the disk space in good condition.
It looks like the 7467 and 7648 messages are not written to the logs files (only to the windows event logs) so basically this SupportPac is not useful...
how do I allow message to be in the logs?
thanks,
Eli |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Sun Oct 18, 2009 1:48 am Post subject: Re: amq 7467 and amq 7468 are not written to AMQERRXX.LOG |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| elikatz wrote: |
hi all,
I have a windows 2003 cluster machine running MQ 5.3 (CDS 12) with linear logs.
I'm trying to use SupportPac ms0l in order to keep the disk space in good condition.
It looks like the 7467 and 7648 messages are not written to the logs files (only to the windows event logs) so basically this SupportPac is not useful...
how do I allow message to be in the logs?
thanks,
Eli |
Could be that they are written to the logs but the logs are just wrapping too fast. (High volume or number of attempts to connect while qmgr is down?)
There are new commands, on qmstatus, I believe which will tell you what the log status is (restart and recovery). With that you can do some maintenance (manually) until automatic can resume. (I myself use sp MS0L for LL maintenance on Unix).
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| exerk |
| Posted: Sun Oct 18, 2009 2:51 am Post subject: Re: amq 7467 and amq 7468 are not written to AMQERRXX.LOG |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| fjb_saper wrote: |
| ...There are new commands, on qmstatus, I believe which will tell you what the log status is (restart and recovery)... |
fjb_saper, I believe those enhancements only appeared from V6.0 onwards.
Eli, are your logs rolling very quickly? Has someone 'elected' to suppress or exclude those messages? (not sure whether that can be done for 7467's and 7468's, and not in a position to test it at the moment)
_________________
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 |
|
|
| fjb_saper |
| Posted: Sun Oct 18, 2009 1:56 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You're right that's only in V6 onwards. However rcdmqimg with the -l parm I believe will also give you that information... Of course you need the qmgr running for that.
Have fun
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| elikatz |
| Posted: Mon Oct 19, 2009 11:45 am Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
fjb_saper and exerk,
thanks for your response.
the file is not being filled to fast.
under qmgr properties there is 'Events' tab, maybe i should enable something there?
currently only stop/start events is enabled. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Oct 19, 2009 10:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| elikatz wrote: |
fjb_saper and exerk,
thanks for your response.
the file is not being filled to fast.
under qmgr properties there is 'Events' tab, maybe i should enable something there?
currently only stop/start events is enabled. |
That should have nothing to do with it.
What did running rcdmqimg with -l flag tell you?
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| elikatz |
| Posted: Thu Oct 22, 2009 5:00 am Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
Media image for object QM1, type qmgr recorded.
AMQ7467: The oldest log file required to start queue manager QM1 is S0000000.LOG.
AMQ7468: The oldest log file required to perform media recovery of queue manager QM1 is S000000
0.LOG. |
|
| Back to top |
|
|
| exerk |
| Posted: Thu Oct 22, 2009 5:35 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
Looks to me like there are no transactions occurring whatosever...
_________________
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 |
|
|
| bruce2359 |
| Posted: Thu Oct 22, 2009 6:54 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| only to the windows event logs |
This is a wonderful feature that allows for automation to recognize when a log segment is no longer required, so that it can be archived.
I suppose that this was done 1) because customers begged and screamed that there is value in knowing when logs are no longer necessary; and 2) disk space is a finite resource.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| elikatz |
| Posted: Fri Oct 23, 2009 4:06 pm Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
and if this is the output:
rcdmqimg -l -m QM -t qmgr
Media image for object QM, type qmgr recorded.
AMQ7467: The oldest log file required to start queue manager QMis S002296
1.LOG.
AMQ7468: The oldest log file required to perform media recovery of queue manager
QMis S0000000.LOG.
?? |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 23, 2009 4:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elikatz wrote: |
AMQ7468: The oldest log file required to perform media recovery of queue manager
QMis S0000000.LOG. |
Because only the qmgr object is on the more recent log file. You either need more commands, or specify "all" on the -t parameter.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| elikatz |
| Posted: Fri Oct 23, 2009 4:57 pm Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
I just run the ms0l and got the following output:
2009-10-23 20:55:46.716 :: com.ibm.ms0l.MqLinearLogfileMaint :: Restart and/or recovery log file(s)
not found. Likely error reading AMQERR01.LOG. Attempt rerun to resolve.
MS0L ABORTED!
any suggestions? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 23, 2009 6:24 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| elikatz wrote: |
I just run the ms0l and got the following output:
2009-10-23 20:55:46.716 :: com.ibm.ms0l.MqLinearLogfileMaint :: Restart and/or recovery log file(s)
not found. Likely error reading AMQERR01.LOG. Attempt rerun to resolve.
MS0L ABORTED!
any suggestions? |
Do you have the log files in the default location? If not do you have a symlink that simulates the default location to the real location...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| elikatz |
| Posted: Sat Oct 24, 2009 8:52 am Post subject: |
|
|
Voyager
Joined: 24 Feb 2009
Posts: 86
|
I didn't find any problem with the paths, here is the full log of the run:
| Code: |
F:\MQ_log_cleanup\ms0l\ms0l>mqllm.bat TRPSFXPB
F:\MQ_log_cleanup\ms0l\ms0l>echo off
2009-10-24 12:50:18.033 :: MS0L Parsing input...
2009-10-24 12:50:18.049 :: MS0L Logfile initialized at: F:\MQ_log_cleanup\usr\log\mqllm_TRPSFXPB.log
2009-10-24 12:50:18.049 :: MS0L MQ Linear Logfile Maintenance Initializing
2009-10-24 12:50:18.049 :: Starting MQ Linear Logfile Maintenance for Queue Manager: TRPSFXPB
2009-10-24 12:50:18.049 :: Unable to load Prior Execution Values File from F:\Program Files\IBM\WebSphere MQ\log\TRPSFXP
B\active\MS0L_lastRun.properties
2009-10-24 12:50:18.049 :: Execution of MS0L will be based on the following parameters:
*** Program Arguments:
Queue Manager Name [-q ] TRPSFXPB
Base MQ Product Directory [-d ] F:\Program Files\IBM\WebSphere MQ
MQ Logfile Location Path [-lp] F:\Program Files\IBM\WebSphere MQ\log\TRPSFXPB\active
MS0L Output Log filename [-l ] F:\MQ_log_cleanup\usr\log\mqllm_TRPSFXPB.log
Archive Output Directory [-a ] F:\MQ_log_cleanup\usr\archive
Temporary Output Directory [-t ] F:\MQ_log_cleanup\usr\TEMP
Windows Machine Name [-m ] <UNSET>
Maximum Wrap Gap [-w ] 1
*** Configurations & Settings:
MQ Configuration File F:\MQ_log_cleanup\usr\TEMP\MQRegValues.TRPSFXPB.txt
MQ Logfile Type [linear/circular] LINEAR
Queue Manager Path F:\Program Files\IBM\WebSphere MQ\qmgrs\TRPSFXPB
Error Log Path F:\Program Files\IBM\WebSphere MQ\qmgrs\TRPSFXPB\errors
Previous run values [log values] F:\Program Files\IBM\WebSphere MQ\log\TRPSFXPB\active\MS0L_lastRun.properties
Previous Restart Logfile <UNSET>
Previous Recovery Logfile <UNSET>
2009-10-24 12:50:18.049 :: Temporary Directory Specified: F:\MQ_log_cleanup\usr\TEMP
2009-10-24 12:50:18.080 :: Removing temporary MQ Error log file: F:\MQ_log_cleanup\usr\TEMP\AMQERR01.LOG
2009-10-24 12:50:18.080 :: The oldest file required for restart is "S0022967.LOG
2009-10-24 12:50:18.096 :: The oldest file required for recovery is "S0000000.LOG
2009-10-24 12:50:18.096 :: Checking for removable log files at: F:\Program Files\IBM\WebSphere MQ\log\TRPSFXPB\active
2009-10-24 12:50:18.330 :: com.ibm.ms0l.MqLinearLogfileMaint :: Restart and/or recovery log file(s) not found. Likely error reading AMQERR01.LOG. Attempt rerun to resolve.
MS0L ABORTED!
F:\MQ_log_cleanup\ms0l\ms0l> |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Oct 24, 2009 10:47 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| elikatz wrote: |
| Likely error reading AMQERR01.LOG. Attempt rerun to resolve. |
This looks like a good place to start. For instance, does the user running the script have read permission on this file?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
