| Author |
Message
|
| jeevan |
 Posted: Sun Jun 21, 2009 3:08 pm Post subject: Error log file size(amqerr01/02/03) |
 |
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
We talk a lot about the mq log files. But, I have never read about the error log file size. Can we change the size of these error log files (amqerr01/02/03.log)
What is the default size for MQ5.3 and MQ6?
how in actual practice the archived log is maintained?
Thanks |
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Sun Jun 21, 2009 3:32 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
Yes, you can change the size of these logs. Its in the manuals on how to do this.
Default size is 256K.
There is no archived error log. There are 3 circular MQ errors logs for the MQ server, and the 3 circular error logs for each QM.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Sun Jun 21, 2009 4:18 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| PeterPotkay wrote: |
Yes, you can change the size of these logs. Its in the manuals on how to do this.
Default size is 256K.
There is no archived error log. There are 3 circular MQ errors logs for the MQ server, and the 3 circular error logs for each QM. |
And 3 circular logs for the "system" in /var/mqm/qmgrs/@SYSTEM/errors, but I've rarely looked at them. I think they are mainly used for channel related problems that don't resolve to a particular qmgr.
_________________
Glenn |
|
| Back to top |
|
|
| jeevan |
| Posted: Sun Jun 21, 2009 6:41 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| PeterPotkay wrote: |
Yes, you can change the size of these logs. Its in the manuals on how to do this.
Default size is 256K.
There is no archived error log. There are 3 circular MQ errors logs for the MQ server, and the 3 circular error logs for each QM. |
Thank you Peter. I have two more questions. Does it require a bouncing qmgr? Is there any limit except the disk size? I have to do it in prod. Is there any care (seems simply a parameter change but ..)that has to be taken?
Thanks a lot |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun Jun 21, 2009 9:41 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jeevan wrote: |
| I have to do it in prod. |
Slightly off topic but:
a) Would your time not be better spent working out why you have so many errors in a production environment, rather than ensuring you have room to hold them?
b) Why is there a requirement to archive errors? Granted you'll probably have a need to track & report errors but typically there's a system that holds trouble tickets for that. Relevant bits of error log can be stored in there surely?
I feel I'm missing the point here 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Jun 22, 2009 12:42 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| jeevan wrote: |
| Does it require a bouncing qmgr? |
Changing the log size, log count etc. can be done and make sure you bounce the respective queue manager.
(You'll find posts in the forum, related to the 'logs and its size to be changed' with lots of discussion on it and with note 'Log file size change is not advisable' .)
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Jun 22, 2009 1:10 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| Quote: |
I have to do it in prod.
|
But surely you will test in a pre prod enviornment first?
| shashivarungupta wrote: |
note 'Log file size change is not advisable' .) |
Even for the error log files? I can see the point for the transaction log files but not sure why this would be the case for the error logs? |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Mon Jun 22, 2009 1:18 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| WMBDEV1 wrote: |
| shashivarungupta wrote: |
note 'Log file size change is not advisable' .) |
Even for the error log files? I can see the point for the transaction log files but not sure why this would be the case for the error logs? |
for logs at /var/mqm/qmgrs/QMGR/errors/
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| WMBDEV1 |
| Posted: Mon Jun 22, 2009 1:30 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009
Posts: 888
Location: UK
|
| shashivarungupta wrote: |
| WMBDEV1 wrote: |
| shashivarungupta wrote: |
note 'Log file size change is not advisable' .) |
Even for the error log files? I can see the point for the transaction log files but not sure why this would be the case for the error logs? |
for logs at /var/mqm/qmgrs/QMGR/errors/
|
and so why is this not advisable? Where is it advised against? Or is it just a fear passed down from generation to generation without people really knowing why is it so?
Ta muchly |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Jun 22, 2009 7:10 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Vitor wrote: |
| jeevan wrote: |
| I have to do it in prod. |
Slightly off topic but:
a) Would your time not be better spent working out why you have so many errors in a production environment, rather than ensuring you have room to hold them?
b) Why is there a requirement to archive errors? Granted you'll probably have a need to track & report errors but typically there's a system that holds trouble tickets for that. Relevant bits of error log can be stored in there surely?
I feel I'm missing the point here |
Vitor,
Very good questions. In fact, my colleague used to work in production. He is out sick and I have to look at now. I was involved in building the evnironment but he was supporting the prod and I was supporting the test.
We are experiencing some problem in our production ( slow sla) for last two weeks. Our support team asked me whether they can look at the log file of the 4th. it was just yesterday. I do not know the history why so many years this need was not felt and neither the error file size was increased nor a archiving the old log file was felt. But I have to do it now.
For the time being, I am copying the errro log file giving them
the date stamp once the error 01 replaces the error02 and error02 replaces error03. But I thought to ask the gropu how people practice this need. I do not think it is only my requirements many people might have done this already.
I think I answered your questions.
thanks once again, |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Jun 22, 2009 7:16 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| WMBDEV1 wrote: |
| shashivarungupta wrote: |
| WMBDEV1 wrote: |
| shashivarungupta wrote: |
note 'Log file size change is not advisable' .) |
Even for the error log files? I can see the point for the transaction log files but not sure why this would be the case for the error logs? |
for logs at /var/mqm/qmgrs/QMGR/errors/
|
and so why is this not advisable? Where is it advised against? Or is it just a fear passed down from generation to generation without people really knowing why is it so?
Ta muchly |
Very good point.
unlike the changing the log file, changing the size of tge error log file \qmgrs\mqgr\error\amqerr01\020\3) is simply changing a qmgr parameter. I asked because I wanted to know how people are doing as I am doing this for the first time and in production environment. I need to be carefull. If something goes wrong, it will be a big trouble. MQ runs many mission critical applications in the company. |
|
| Back to top |
|
|
| sumit |
| Posted: Mon Jun 22, 2009 8:16 am Post subject: |
|
|
Partisan
Joined: 19 Jan 2006
Posts: 398
|
| jeevan wrote: |
| I need to be carefull. If something goes wrong, it will be a big trouble. MQ runs many mission critical applications in the company. |
I believe you know this very well that if your system is a mission critical prod, then you first try stuff on a Dev or Test server.
| jeevan wrote: |
| Our support team asked me whether they can look at the log file of the 4th. |
This is not in response to your original question, but why does support team need a log which is very old. If the issue is still there, they you can see it's entries in the fresh log.
_________________
Regards
Sumit |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Mon Jun 22, 2009 9:53 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| sumit wrote: |
| jeevan wrote: |
| Our support team asked me whether they can look at the log file of the 4th. |
This is not in response to your original question, but why does support team need a log which is very old. If the issue is still there, they you can see it's entries in the fresh log. |
Knowing when the error first occured and what other errors occured at the same time is useful information.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 22, 2009 10:01 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| PeterPotkay wrote: |
| Knowing when the error first occured and what other errors occured at the same time is useful information. |
Maintaining a tape backup of AMQERR0* files may not be the best way to discover or preserve that information, however. |
|
| Back to top |
|
|
| jeevan |
| Posted: Mon Jun 22, 2009 10:50 am Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| sumit wrote: |
| jeevan wrote: |
| I need to be carefull. If something goes wrong, it will be a big trouble. MQ runs many mission critical applications in the company. |
I believe you know this very well that if your system is a mission critical prod, then you first try stuff on a Dev or Test server.
| jeevan wrote: |
| Our support team asked me whether they can look at the log file of the 4th. |
This is not in response to your original question, but why does support team need a log which is very old. If the issue is still there, they you can see it's entries in the fresh log. |
I know that I need to do this first in test before I do on prod. But still I wanted to know any pitfall.
We have once done log file changes( not error log but the LOG with cool boot way) When we tested it in TESt environment, it worked okay. When my colleague implemented it in prod, it did not work. So, he has to recreate queue manager and all the connections etc. That is why I am asking how problematic is it. I know this is different than the changing the log file, but still wanted to get feedback who have implemented.
thanks |
|
| Back to top |
|
|
|
|
