Author |
Message
|
paustin_ours |
Posted: Thu Sep 26, 2013 7:49 am Post subject: active logs |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
persistent messages are written to active log and then to q file.
I have a q with 600 thousand messages but small ones. There is more than enof space in the logs for that but I am seeing the logs are full and it is getting written over and over again.
any ideas where I can look why?
no idea why there are so much data getting written to the logs. |
|
Back to top |
|
 |
bruce2359 |
Posted: Thu Sep 26, 2013 8:20 am Post subject: Re: active logs |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
paustin_ours wrote: |
persistent messages are written to active log and then to q file.
I have a q with 600 thousand messages but small ones. There is more than enof space in the logs for that but I am seeing the logs are full and it is getting written over and over again.
any ideas where I can look why?
no idea why there are so much data getting written to the logs. |
How big are your logs?
How small? 1Meg? 10bytes?
What does 'and it is getting written over and over again' mean? _________________ 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 |
|
 |
exerk |
Posted: Thu Sep 26, 2013 8:44 am Post subject: Re: active logs |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
paustin_ours wrote: |
persistent messages are written to active log and then to q file. |
Yes to the first, not necessarily to the second.
paustin_ours wrote: |
I have a q with 600 thousand messages but small ones. |
And you have determined that they are all persistent messages how?
paustin_ours wrote: |
There is more than enof space in the logs for that but I am seeing the logs are full and it is getting written over and over again. |
Circular logging does that, it's why they're called circular...
paustin_ours wrote: |
any ideas where I can look why? |
The Info Centre perhaps? Lots of good information about logging in there...
paustin_ours wrote: |
no idea why there are so much data getting written to the logs. |
You should, if you're the admin responsible for the queue manager; you should know the profiles and idiosyncrasies of any connecting applications. _________________ 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 |
|
 |
paustin_ours |
Posted: Thu Sep 26, 2013 8:45 am Post subject: |
|
|
Yatiri
Joined: 19 May 2004 Posts: 667 Location: columbus,oh
|
LogPrimaryFiles=50
LogSecondaryFiles=200
LogFilePages=51200
LogType=LINEAR
LogBufferPages=0
message size 1kb.
there were around 35 log files about 200 mb in size
what i don't understand is the timestamps of the log file looks like there is a log file generated every minute. But then these 35 files are getting replaced with new timestamps after the minute.
log file1 200mb 10:45
logfile2 200mb 10:45
logfile3 200mb 10:46
logfile4 200mb 10:46
logfile5 200mb 10:46
logfile6 200mb 10:47
....
logfile 35 200mb 11:02
after a while these log files are replaced by
log file1 200mb 12:01
...
log file35 200mb 12:10
this is linear logging. I don't understand how the log files are being replaced (if they are being replaced) or maybe the log files are no longer needed and gets deleted and new ones get created.
But the problem is what is writing so much logs and how can i tell what application is writing so much logs.
I would hate to be the person to read this post.
if you can point me to some good(in detail) documentation on how active logs work that would be helpful as well. |
|
Back to top |
|
 |
exerk |
Posted: Thu Sep 26, 2013 8:51 am Post subject: |
|
|
 Jedi Council
Joined: 02 Nov 2006 Posts: 6339
|
I strongly suggest you hit the Info Centre and research Restart and Recovery logs. Also, I suggest that if you have a queue of such depth you give a kick to the owner of the application that should be servicing that queue because if you have to take an image of that deep queue (hint: search on object image too) you'll find that a lot more logs will be cut.
And you can't tell which application is writing to the logs because none of them are - that function is reserved for the queue manager logger process. That said, you should know which application(s) are writing to that queue, or from which queue manager(s) the messages are coming from if distributed. _________________ 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 Sep 26, 2013 10:37 am Post subject: |
|
|
 Poobah
Joined: 05 Jan 2008 Posts: 9469 Location: US: west coast, almost. Otherwise, enroute.
|
Some things to look at/for:
If you believe it might be a local application, are there long-running apps executing?
If you believe it might be messages arriving from other qmgrs, look at channel statistics. If you stop a channel, the inbound messages will end.
If this is new behaviour (or behavior), find out what new applications have been thrust into your environment. _________________ 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 |
|
 |
JosephGramig |
Posted: Thu Sep 26, 2013 10:51 am Post subject: |
|
|
 Grand Master
Joined: 09 Feb 2006 Posts: 1244 Location: Gold Coast of Florida, USA
|
So, when you follow these instructions, does the record media objects work?
Or did you implement the support pac to manage linear logs?
Linear logs don't wrap (well, maybe when the max number S9999999 gets hit). |
|
Back to top |
|
 |
|