Recommended log rotation setup for online.log and
Justin asked how best to rotate the Informix online.log and the Connection Manager log daily, worried that the Linux logrotate utility would misbehave because the engine holds the log file open. Art Kagel explained that Informix does not keep the message log open (it opens, writes, closes each time), so logrotate is safe; you can either disable the built-in online_log_rotate task and let logrotate handle both files, or extend the Informix task. Justin chose logrotate for both. The thread then drifted into debate over whether CentOS, being uncertified for Informix, could cause IBM support problems.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi, I'd like to do daily rotations our online log and our connection manager log. I noticed that there is a task name 'online_log_rotate' that will manage the online log, but I don't see one for managing the connection manager log. I'd like to avoid having multiple log rotation mechanisms, so I'm considering ignoring the online_log_rotate task and just using the Linux logrotate utility, but I'm worried it might cause strange behavior (logrotate expects the log file to not be open, and can do weird things if it is). Am I being overly cautious here? What is the current recommended setup for rotating the online log and connection manager logs? CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR primary, 1 HDR secondary, 1 RSS
Justin: Informix does not keep the log open. It is open, written, then closed. You can prove this by renaming the current message log file and forcing a checkpoint or logical log change. The engine will create a new message log file for the next message. So, you can either disable the log rotate task (assuming it is currently active) and use Linux's logrotate for both or you can enhance the log rotate task in Informix to rotate both logs for you. Your choice. Art Art S. Kagel, Principal Consultant ASK Database Management Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < jkillen@allamericanasphalt.com> wrote: > Hi, > > I'd like to do daily rotations our online log and our connection manager > log. > I noticed that there is a task name 'online_log_rotate' that will manage > the > online log, but I don't see one for managing the connection manager log. > I'd > like to avoid having multiple log rotation mechanisms, so I'm considering > ignoring the online_log_rotate task and just using the Linux logrotate > utility, but I'm worried it might cause strange behavior (logrotate expects > the log file to not be open, and can do weird things if it is). > > Am I being overly cautious here? What is the current recommended setup for > rotating the online log and connection manager logs? > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR primary, 1 HDR > secondary, 1 RSS > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --089e0158aef4a297b004f4d11591
Good to know. I don't really want to go poking around with built-in Informix tasks, so I'll be taking the less intrusive path and setting up logrotate for both. Thanks Art! -Justin > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Art > Kagel > Sent: Monday, March 17, 2014 10:53 AM > To: ids@iiug.org > Subject: Re: Recommended log rotation setup for online..... [32727] > > Justin: > > Informix does not keep the log open. It is open, written, then closed. > You can prove this by renaming the current message log file and forcing > a checkpoint or logical log change. The engine will create a new message > log file for the next message. > > So, you can either disable the log rotate task (assuming it is currently > active) and use Linux's logrotate for both or you can enhance the log > rotate task in Informix to rotate both logs for you. Your choice. > > Art > > Art S. Kagel, Principal Consultant > ASK Database Management > > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on the IIUG, nor any other organization with which I am > associated either explicitly, implicitly, or by inference. Neither do > those opinions reflect those of other individuals affiliated with any > entity with which I am affiliated nor those of the entities themselves. > > On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < > jkillen@allamericanasphalt.com> wrote: > > > Hi, > > > > I'd like to do daily rotations our online log and our connection manager > > log. > > I noticed that there is a task name 'online_log_rotate' that will manage > > the > > online log, but I don't see one for managing the connection manager log. > > I'd > > like to avoid having multiple log rotation mechanisms, so I'm > considering > > ignoring the online_log_rotate task and just using the Linux logrotate > > utility, but I'm worried it might cause strange behavior (logrotate > expects > > the log file to not be open, and can do weird things if it is). > > > > Am I being overly cautious here? What is the current recommended setup > for > > rotating the online log and connection manager logs? > > > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR primary, 1 > HDR > > secondary, 1 RSS > > > > > > > > > ************************************************************************** > ***** > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --089e0158aef4a297b004f4d11591 > > > ************************************************************************** > ***** > Forum Note: Use "Reply" to post a response in the discussion forum.
Another good point that you should consider: use a supported Linux distro, instead of CentOS, which is not. Regards. Alexandre Marini IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 IBM Information Management Informix Technical Professional IBM Infosphere DataStage Technical Professional Informix Senior DBA - Orizon Brasil BRIUG website administrator Informix independent consultant > To: ids@iiug.org > From: art.kagel@gmail.com > Subject: Re: Recommended log rotation setup for online..... [32727] > Date: Mon, 17 Mar 2014 13:52:40 -0400 > > Justin: > > Informix does not keep the log open. It is open, written, then closed. > You can prove this by renaming the current message log file and forcing > a checkpoint or logical log change. The engine will create a new message > log file for the next message. > > So, you can either disable the log rotate task (assuming it is currently > active) and use Linux's logrotate for both or you can enhance the log > rotate task in Informix to rotate both logs for you. Your choice. > > Art > > Art S. Kagel, Principal Consultant > ASK Database Management > > Blog: http://informix-myview.blogspot.com/ > > Disclaimer: Please keep in mind that my own opinions are my own opinions > and do not reflect on the IIUG, nor any other organization with which I am > associated either explicitly, implicitly, or by inference. Neither do > those opinions reflect those of other individuals affiliated with any > entity with which I am affiliated nor those of the entities themselves. > > On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < > jkillen@allamericanasphalt.com> wrote: > > > Hi, > > > > I'd like to do daily rotations our online log and our connection manager > > log. > > I noticed that there is a task name 'online_log_rotate' that will manage > > the > > online log, but I don't see one for managing the connection manager log. > > I'd > > like to avoid having multiple log rotation mechanisms, so I'm considering > > ignoring the online_log_rotate task and just using the Linux logrotate > > utility, but I'm worried it might cause strange behavior (logrotate expects > > the log file to not be open, and can do weird things if it is). > > > > Am I being overly cautious here? What is the current recommended setup for > > rotating the online log and connection manager logs? > > > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR primary, 1 HDR > > secondary, 1 RSS > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > --089e0158aef4a297b004f4d11591 > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Alexandre, It was considered: http://www.iiug.org/forums/ids/index.cgi/read/30181 Due to community endorsement and lack of any substantial negative comments, CentOS was chosen over RHEL. -Justin > -----Original Message----- > From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > Alexandre Marini > Sent: Monday, March 17, 2014 11:50 AM > To: ids@iiug.org > Subject: RE: Recommended log rotation setup for online..... [32729] > > Another good point that you should consider: use a supported Linux distro, > instead of CentOS, which is not. > > Regards. > > Alexandre Marini > IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 > > IBM Information Management Informix Technical Professional > > IBM Infosphere DataStage Technical Professional > Informix Senior DBA - Orizon Brasil > BRIUG website administrator > Informix independent consultant > > > To: ids@iiug.org > > From: art.kagel@gmail.com > > Subject: Re: Recommended log rotation setup for online..... [32727] > > Date: Mon, 17 Mar 2014 13:52:40 -0400 > > > > Justin: > > > > Informix does not keep the log open. It is open, written, then closed. > > You can prove this by renaming the current message log file and forcing > > a checkpoint or logical log change. The engine will create a new message > > log file for the next message. > > > > So, you can either disable the log rotate task (assuming it is currently > > active) and use Linux's logrotate for both or you can enhance the log > > rotate task in Informix to rotate both logs for you. Your choice. > > > > Art > > > > Art S. Kagel, Principal Consultant > > ASK Database Management > > > > Blog: http://informix-myview.blogspot.com/ > > > > Disclaimer: Please keep in mind that my own opinions are my own opinions > > and do not reflect on the IIUG, nor any other organization with which I > am > > associated either explicitly, implicitly, or by inference. Neither do > > those opinions reflect those of other individuals affiliated with any > > entity with which I am affiliated nor those of the entities themselves. > > > > On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < > > jkillen@allamericanasphalt.com> wrote: > > > > > Hi, > > > > > > I'd like to do daily rotations our online log and our connection > manager > > > log. > > > I noticed that there is a task name 'online_log_rotate' that will > manage > > > the > > > online log, but I don't see one for managing the connection manager > log. > > > I'd > > > like to avoid having multiple log rotation mechanisms, so I'm > considering > > > ignoring the online_log_rotate task and just using the Linux logrotate > > > utility, but I'm worried it might cause strange behavior (logrotate > expects > > > the log file to not be open, and can do weird things if it is). > > > > > > Am I being overly cautious here? What is the current recommended setup > for > > > rotating the online log and connection manager logs? > > > > > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR primary, > 1 > HDR > > > secondary, 1 RSS > > > > > > > > > > > > > > > ************************************************************************** > ***** > > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > > > > > --089e0158aef4a297b004f4d11591 > > > > > > > ************************************************************************** > ***** > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > ************************************************************************** > ***** > Forum Note: Use "Reply" to post a response in the discussion forum.
We use CentOS and Fedora all the time and have found them to be no less stable than RH Cheers Paul > Alexandre, > > It was considered: http://www.iiug.org/forums/ids/index.cgi/read/30181 > > Due to community endorsement and lack of any substantial negative > comments, > CentOS was chosen over RHEL. > > -Justin > >> -----Original Message----- >> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of >> Alexandre Marini >> Sent: Monday, March 17, 2014 11:50 AM >> To: ids@iiug.org >> Subject: RE: Recommended log rotation setup for online..... [32729] >> >> Another good point that you should consider: use a supported Linux >> distro, >> instead of CentOS, which is not. >> >> Regards. >> >> Alexandre Marini >> IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 >> >> IBM Information Management Informix Technical Professional >> >> IBM Infosphere DataStage Technical Professional >> Informix Senior DBA - Orizon Brasil >> BRIUG website administrator >> Informix independent consultant >> >> > To: ids@iiug.org >> > From: art.kagel@gmail.com >> > Subject: Re: Recommended log rotation setup for online..... [32727] >> > Date: Mon, 17 Mar 2014 13:52:40 -0400 >> > >> > Justin: >> > >> > Informix does not keep the log open. It is open, written, then closed. >> > You can prove this by renaming the current message log file and >> forcing >> > a checkpoint or logical log change. The engine will create a new >> message >> > log file for the next message. >> > >> > So, you can either disable the log rotate task (assuming it is >> currently >> > active) and use Linux's logrotate for both or you can enhance the log >> > rotate task in Informix to rotate both logs for you. Your choice. >> > >> > Art >> > >> > Art S. Kagel, Principal Consultant >> > ASK Database Management >> > >> > Blog: http://informix-myview.blogspot.com/ >> > >> > Disclaimer: Please keep in mind that my own opinions are my own >> opinions >> > and do not reflect on the IIUG, nor any other organization with which >> I >> am >> > associated either explicitly, implicitly, or by inference. Neither do >> > those opinions reflect those of other individuals affiliated with any >> > entity with which I am affiliated nor those of the entities >> themselves. >> > >> > On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < >> > jkillen@allamericanasphalt.com> wrote: >> > >> > > Hi, >> > > >> > > I'd like to do daily rotations our online log and our connection >> manager >> > > log. >> > > I noticed that there is a task name 'online_log_rotate' that will >> manage >> > > the >> > > online log, but I don't see one for managing the connection manager >> log. >> > > I'd >> > > like to avoid having multiple log rotation mechanisms, so I'm >> considering >> > > ignoring the online_log_rotate task and just using the Linux >> logrotate >> > > utility, but I'm worried it might cause strange behavior (logrotate >> expects >> > > the log file to not be open, and can do weird things if it is). >> > > >> > > Am I being overly cautious here? What is the current recommended >> setup >> for >> > > rotating the online log and connection manager logs? >> > > >> > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR >> primary, >> 1 >> HDR >> > > secondary, 1 RSS >> > > >> > > >> > > >> > > >> > >> ************************************************************************** >> ***** >> > > Forum Note: Use "Reply" to post a response in the discussion forum. >> > > >> > > >> > >> > --089e0158aef4a297b004f4d11591 >> > >> > >> > >> ************************************************************************** >> ***** >> > Forum Note: Use "Reply" to post a response in the discussion forum. >> > >> >> >> ************************************************************************** >> ***** >> Forum Note: Use "Reply" to post a response in the discussion forum. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > -- Paul Watson Tel: +1 913-674-0360 Mob: +1 913-387-7529 Web: www.oninit.com Failure is not as frightening as regret. If you want to improve, be content to be thought foolish and stupid. What this country needs are more unemployed politicians
Hi, Paul. I´m absolutely not considering the confidence of CentOS. Just a comment in case of a serious issue concerning an OS related problem. He might have a trouble if the remote support team access his environment, and see that he is not using a certified OS. Just that. CentOS is a great OS, but unfortunately not certified. That is what I should write before. Hope it helps, regards. Alexandre Marini IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 IBM Information Management Informix Technical Professional IBM Infosphere DataStage Technical Professional Informix Senior DBA - Orizon Brasil BRIUG website administrator Informix independent consultant > To: ids@iiug.org > From: paul@oninit.com > Subject: RE: Recommended log rotation setup for online..... [32731] > Date: Mon, 17 Mar 2014 15:36:08 -0400 > > We use CentOS and Fedora all the time and have found them to be no less > stable than RH > > Cheers > Paul > > > Alexandre, > > > > It was considered: http://www.iiug.org/forums/ids/index.cgi/read/30181 > > > > Due to community endorsement and lack of any substantial negative > > comments, > > CentOS was chosen over RHEL. > > > > -Justin > > > >> -----Original Message----- > >> From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of > >> Alexandre Marini > >> Sent: Monday, March 17, 2014 11:50 AM > >> To: ids@iiug.org > >> Subject: RE: Recommended log rotation setup for online..... [32729] > >> > >> Another good point that you should consider: use a supported Linux > >> distro, > >> instead of CentOS, which is not. > >> > >> Regards. > >> > >> Alexandre Marini > >> IBM Informix Certified Professional v10 / v11.50 / v11.70 / v12.10 > >> > >> IBM Information Management Informix Technical Professional > >> > >> IBM Infosphere DataStage Technical Professional > >> Informix Senior DBA - Orizon Brasil > >> BRIUG website administrator > >> Informix independent consultant > >> > >> > To: ids@iiug.org > >> > From: art.kagel@gmail.com > >> > Subject: Re: Recommended log rotation setup for online..... [32727] > >> > Date: Mon, 17 Mar 2014 13:52:40 -0400 > >> > > >> > Justin: > >> > > >> > Informix does not keep the log open. It is open, written, then closed. > >> > You can prove this by renaming the current message log file and > >> forcing > >> > a checkpoint or logical log change. The engine will create a new > >> message > >> > log file for the next message. > >> > > >> > So, you can either disable the log rotate task (assuming it is > >> currently > >> > active) and use Linux's logrotate for both or you can enhance the log > >> > rotate task in Informix to rotate both logs for you. Your choice. > >> > > >> > Art > >> > > >> > Art S. Kagel, Principal Consultant > >> > ASK Database Management > >> > > >> > Blog: http://informix-myview.blogspot.com/ > >> > > >> > Disclaimer: Please keep in mind that my own opinions are my own > >> opinions > >> > and do not reflect on the IIUG, nor any other organization with which > >> I > >> am > >> > associated either explicitly, implicitly, or by inference. Neither do > >> > those opinions reflect those of other individuals affiliated with any > >> > entity with which I am affiliated nor those of the entities > >> themselves. > >> > > >> > On Mon, Mar 17, 2014 at 1:27 PM, Justin Killen < > >> > jkillen@allamericanasphalt.com> wrote: > >> > > >> > > Hi, > >> > > > >> > > I'd like to do daily rotations our online log and our connection > >> manager > >> > > log. > >> > > I noticed that there is a task name 'online_log_rotate' that will > >> manage > >> > > the > >> > > online log, but I don't see one for managing the connection manager > >> log. > >> > > I'd > >> > > like to avoid having multiple log rotation mechanisms, so I'm > >> considering > >> > > ignoring the online_log_rotate task and just using the Linux > >> logrotate > >> > > utility, but I'm worried it might cause strange behavior (logrotate > >> expects > >> > > the log file to not be open, and can do weird things if it is). > >> > > > >> > > Am I being overly cautious here? What is the current recommended > >> setup > >> for > >> > > rotating the online log and connection manager logs? > >> > > > >> > > CentOS 6.5 (Linux) - Informix 12.10.FC1WE cluster with 1 HDR > >> primary, > >> 1 > >> HDR > >> > > secondary, 1 RSS > >> > > > >> > > > >> > > > >> > > > >> > > >> ************************************************************************** > >> ***** > >> > > Forum Note: Use "Reply" to post a response in the discussion forum. > >> > > > >> > > > >> > > >> > --089e0158aef4a297b004f4d11591 > >> > > >> > > >> > > >> ************************************************************************** > >> ***** > >> > Forum Note: Use "Reply" to post a response in the discussion forum. > >> > > >> > >> > >> ************************************************************************** > >> ***** > >> Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > -- > Paul Watson > Tel: +1 913-674-0360 > Mob: +1 913-387-7529 > Web: www.oninit.com > > Failure is not as frightening as regret. > If you want to improve, be content to be thought foolish and stupid. > What this country needs are more unemployed politicians > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
>> We use CentOS and Fedora all the time and have found them to be no less stable than RH I agree with this as far as it goes, but 2 other reasons you might consider a supported "flavour" are: 1. If your system supports a business function which is heavily-regulated in terms of security patch requirement, eg PCI-DSS 2. Technically IBM support might refuse help if you're not a supported distro. I have raised calls for CentOS systems with no issues in the past so accept that the probability is remote. Depends how paranoid you are!