[Linux-HA] Heartbeat Logging

Andrew Beekhof beekhof at gmail.com
Fri Jan 19 06:54:40 MST 2007


On 1/19/07, Andrew Beekhof <beekhof at gmail.com> wrote:
> On 1/18/07, Florent Bouron <florent.bouron at sytec.co.nz> wrote:
> > Hi Andrew,
> >
> > Yep, I've read it and I've tried to apply want I understood from it.
> > I actually understood that :
> >         - nothing need to be defined in ha.cf except "use_logd on". Is
> > "debug 0" still required ?
>
> i think thats the default so, no.
>
> >         - /etc/logd.cf receives the log configuration
>
> if you mean s/receives/contains/ then yes
>
> > and should not include any logfacility directive to disable syslog.
>
> where did you find that?
>
> >         - However, the ha_logd.cf example indicates that the default
> > facility is local7
> > Here are my conf files : it looks like even with nothing, messages are
> > to be sent to syslog ???
>
> i just poked around in the code and it does seem that there is no way
> to not log to syslog.
>
> sigh.
>
> i'll see what i can do...

ok, see the following two commits:
  http://hg.beekhof.net/lha/crm-dev/rev/1b4161dc0042
  http://hg.beekhof.net/lha/crm-dev/rev/effbf74e7cad

they will allow you to set "log_facility none" in ha.cf or logd.cf and
achieve the behavior you're after.

>
> >
> > ----------------------------
> > ha.cf :
> > use_logd on
> > debug 0
> > keepalive 1 # 1 second
> > deadtime 10
> > initdead 80
> > mcast eth1 224.0.0.18 694 1 0
> > node BBBB AAAA
> > crm yes
> > auto_failback yes
> > coredumps true
> > compression    bz2
> >
> > ----------------------------
> > logd.cf :
> > debugfile /var/log/heartbeat/ha-debug
> > logfile   /var/log/heartbeat/ha-log
> >
> > Any comments appreciated.
> >
> > Thanks,
> > Florent
> >
> > -----Original Message-----
> > From: linux-ha-bounces at lists.linux-ha.org
> > [mailto:linux-ha-bounces at lists.linux-ha.org] On Behalf Of Andrew Beekhof
> > Sent: Monday, 15 January 2007 8:34 a.m.
> > To: General Linux-HA mailing list
> > Subject: Re: [Linux-HA] Heartbeat Logging
> >
> > On 1/14/07, Andrew Beekhof <beekhof at gmail.com> wrote:
> > > On 1/12/07, Florent Bouron <florent.bouron at sytec.co.nz> wrote:
> > > > Hi there,
> > > >
> > > > I've finalised my heartbeat 2.x setup and I'm really happy with
> > > > everything except the logging.
> > > >
> > > > We basically have got some monitoring hosts that collect every
> > > > syslog events and process them and Heartbeat is generating such a
> > > > big volume of logs that our systems are overloaded and become
> > unstable because of it.
> > > >
> > > > I'm trying to figure out a way of removing the heartbeat logging
> > > > from syslog.
> > >
> > > i _highly_ recommend syslog-ng for what its worth
> > >
> > > > Correct me if I'm wrong but it seems that heartbeat is using ha_logd
> >
> > > > and responds to the debug 0 directive but also that the other
> > > > processes (tengine, crmd, ...) are still generating their own logs
> > > > and send them directly to syslog.
> > >
> > > (baring some bug I'm not aware of...) the crmd, tengine etc all obey
> > > the directives in ha.cf including debug level and where logging should
> >
> > > be sent.
> >
> > have you read the following page?  it might help a little.
> >    http://linux-ha.org/ha.cf#use_logd
> >
> > > > I'm a bit surprised by this behaviour
> > >
> > > not more than i would be
> > >
> > > > and I'm sure someone has already
> > > > figured out a way of acheiving what I'm trying to do.
> > > >
> > > > Thanks,
> > > > Florent
> > > > </PRE><div
> > > > style="color:navy;font-size:7pt;font-family:Arial">WARNING This
> > > > email contains information that is CONFIDENTIAL and may be subject
> > > > to LEGAL PRIVILEGE. If you are not the intended recipient, you must
> > > > not peruse, use, disseminate, distribute or copy this email or
> > > > attachments. If you have received this in error, please notify us
> > > > immediately by return email, facsimile or telephone (call us
> > > > collect) and delete this email. Thank you.<br>SYTEC RESOURCES
> > > > LIMITED ACCEPTS NO RESPONSIBILITY FOR CHANGES MADE TO THIS EMAIL OR
> > > > TO ANY ATTACHMENTS AFTER TRANSMISSION FROM SYTEC RESOURCES
> > > > LIMITED.</div> _______________________________________________
> > > > Linux-HA mailing list
> > > > Linux-HA at lists.linux-ha.org
> > > > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > > > See also: http://linux-ha.org/ReportingProblems
> > > >
> > >
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA at lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
> > __________________________________________________________________
> >   This email has been scanned by the DMZGlobal Business Quality
> >               Electronic Messaging Suite.
> > Please see http://www.dmzglobal.com/services/bqem.htm for details.
> > __________________________________________________________________
> >
> >
> > WARNING This email contains information that is CONFIDENTIAL and may be subject to LEGAL PRIVILEGE. If you are not the intended recipient, you must not peruse, use, disseminate, distribute or copy  this email or attachments. If you have received this in error, please notify us immediately by  return email, facsimile or telephone (call us collect) and delete this email. Thank you. SYTEC RESOURCES LIMITED ACCEPTS NO RESPONSIBILITY FOR CHANGES MADE TO THIS EMAIL OR TO ANY ATTACHMENTS AFTER TRANSMISSION FROM SYTEC RESOURCES LIMITED.
> > _______________________________________________
> > Linux-HA mailing list
> > Linux-HA at lists.linux-ha.org
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> >
>


More information about the Linux-HA mailing list