<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
Great, thanks so much for the responses!<font size="2">
<br />
<br />
<br />Kenneth M
DeChick
<br />Linux Systems
Administrator
<br />Community Computer Service,
Inc.
<br />(315)-255-1751
ext154
<br />http://www.medent.com
<br />kend@medent.com
<br />Registered Linux User
#497318
<br />-- -- -- -- -- -- -- -- -- --
--
<br />
"You canna change the laws of physics, Captain; I've got to have
thirty
minutes!
"
<br />
<br />.
<center><img src="https://www.medent.com/openwebmail/images/defmailsig.jpg" /></center>
<br />
<br /><b>----------
Original Message
-----------</b>
<br />
From: Dejan Muhamedagic <dejanmm@fastmail.fm>
<br />
To: pacemaker@clusterlabs.org, kend@medent.com
<br />
Sent: Fri, 29 Jan 2010 16:21:46 +0100
<br />
Subject: Re: [Pacemaker] Question on logd
<br />
<br />> Hi,
<br />>
<br />>
On Fri, Jan 29, 2010 at 10:10:48AM -0500, Ken Dechick wrote:
<br />>
> Thanks for the response Andrew.
<br />>
>
<br />>
> I have:
<br />>
> cluster-glue-1.0.1-1.el5
<br />>
> cluster-glue-libs-1.0.1-1.el5
<br />>
> Installed, but there is no /usr/share/doc/glue* directory at
<br />>
> all. Forgot to mention I did an 'updatedb && locate ha_logd.cf'
<br />>
> on my systems and this example file is just plain not present
<br />>
> anywhere. I checked my current repositories and there is no
<br />>
> mention of any other cluster-glue packages (ie: there is no
<br />>
> cluster-glue-docs*.rpm) available.
<br />>
<br />>
Don't know what does it look like in that package. In the one
<br />>
which is soon to be released it will be here:
<br />>
<br />>
/usr/share/doc/packages/cluster-glue/logd.cf
<br />>
<br />>
(give or take distribution idiosyncrasies)
<br />>
<br />>
> I will setup based on the listing you provided. One other thing
<br />>
> I would like to mention just so it's out there: there is a
<br />>
> /etc/init.d/logd but by default after install it is not ready
<br />>
> to use. I had to: 'chkconfig --add logd' before I could get it
<br />>
> to come up at boot. Shouldn't this have been done as part of
<br />>
> the installation from rpm?? There was a time not too long ago
<br />>
> when I had to do the same for heartbeat, but that appears to
<br />>
> have been fixed in the 3.0.1-1 version I use now.
<br />>
<br />>
This has also been fixed in the meantime, so logd will run by
<br />>
default on boot.
<br />>
<br />>
Thanks,
<br />>
<br />>
Dejan
<br />>
<br />>
> Thanks!
<br />>
>
<br />>
> Kenneth M DeChick
<br />>
> Linux Systems Administrator
<br />>
> Community Computer Service, Inc.
<br />>
> (315)-255-1751 ext154
<br />>
> <a target="_blank" href="http://www.medent.com/">http://www.medent.com</a>
<br />>
> kend@medent.com
<br />>
> Registered Linux User #497318
<br />>
> -- -- -- -- -- -- -- -- -- -- --
<br />>
> "You canna change the laws of physics, Captain; I've got to have
thirtyminutes! "
<br />>
>
<br />>
> .
<br />>
>
<br />>
> ---------- Original Message -----------
<br />>
> From: Andrew Beekhof <andrew@beekhof.net>
<br />>
> To: pacemaker@clusterlabs.org, kend@medent.com
<br />>
> Sent: Fri, 29 Jan 2010 09:00:47 +0100
<br />>
> Subject: Re: [Pacemaker] Question on logd
<br />>
>
<br />>
> > On Thu, Jan 28, 2010 at 10:04 PM, Ken Dechick <kend@medent.com>
wrote:
<br />>
> >
<br />>
> > Hi eveyone,
<br />>
> >
<br />>
> > I have spent the better part of the afternoon searching for an answer
as to why I get " logd is not running" errors constantly.
<br />>
> > Using: DRBD: 8.3.6, Heartbeat 3.0.1-1 Pacemaker 1.0.6 on CentOS 5.3
x86_64
<br />>
> >
<br />>
> > It looks like the problem may be simply that I have no logd config
file. All the documentation suggests that I can find a sample config file with
the other heartbeat docs (/usr/share/docs/heartbeat-3.0.1 in my case), but this
file does not exist on my systems (have 3 clusters up and running - it's not on
any of them). I dig all kinds of web searches today and I cannot locate listing
of how this file needs to be setup. Can someone help point me in the right
direction here? Over and over the docs recommend that you use logd on over the
old system of individual log, and debug files, but I can't start logd without
a config!!
<br />>
> >
<br />>
> >
<br />>
> > Perhaps try /usr/share/docs/*glue* instead.
<br />>
> > I'd expect that to be part of the cluster-glue packages now.
<br />>
> >
<br />>
> > At any rate, here's the contents:
<br />>
> >
<br />>
> > # File to write debug messages to
<br />>
> > # Default: /var/log/ha-debug
<br />>
> > #debugfile /var/log/ha-debug
<br />>
> >
<br />>
> > #
<br />>
> > #
<br />>
> > # File to write other messages to
<br />>
> > # Default: /var/log/ha-log
<br />>
> > #logfile /var/log/ha-log
<br />>
> >
<br />>
> > #
<br />>
> > #
<br />>
> > # Facility to use for syslog()/logger
<br />>
> > # Default: daemon
<br />>
> > #logfacility daemon
<br />>
> >
<br />>
> > # Entity to be shown at beginning of a message
<br />>
> > # for logging daemon
<br />>
> > # Default: "logd"
<br />>
> > #entity logd
<br />>
> >
<br />>
> > # Do we register to apphbd
<br />>
> > # Default: no
<br />>
> > #useapphbd no
<br />>
> >
<br />>
> > # There are two processes running for logging daemon
<br />>
> > # 1. parent process which reads messages from all client channels
<br />>
> > # and writes them to the child process
<br />>
> > #
<br />>
> > # 2. the child process which reads messages from the parent process
through IPC
<br />>
> > # and writes them to syslog/disk
<br />>
> >
<br />>
> > # set the send queue length from the parent process to the child
process
<br />>
> > #
<br />>
> > #sendqlen 256
<br />>
> >
<br />>
> > # set the recv queue length in child process
<br />>
> > #
<br />>
> > #recvqlen 256
<br />>
> ------- End of Original Message -------
<br />>
>
<br />>
> This message has been scanned for viruses and dangerous content by
MailScanner, SpamAssassin & ClamAV. <BR>
<br />>
> <BR>
<br />>
> This message and any attachments may contain information that is protected
by law as privileged and confidential, and is transmitted for the sole use
<BR>
<br />>
> of the intended recipient(s). If you are not the intended recipient, you
are hereby notified that any use, dissemination, copying or retention of this
e-mail <BR>
<br />>
> or the information contained herein is strictly prohibited. If you received
this e-mail in error, please immediately notify the sender by e-mail, and
permanently <BR>
<br />>
> delete this e-mail. <BR>
<br />>
>
<br />>
<br />>
> _______________________________________________
<br />>
> Pacemaker mailing list
<br />>
> Pacemaker@oss.clusterlabs.org
<br />>
> <a target="_blank" href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a>
<br /><b>------- End of Original Message
-------</b>
<br />
</font>
</BODY>
</HTML>
This message has been scanned for viruses and dangerous content by MailScanner, SpamAssassin & ClamAV. <BR>
<BR>
This message and any attachments may contain information that is protected by law as privileged and confidential, and is transmitted for the sole use <BR>
of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, copying or retention of this e-mail <BR>
or the information contained herein is strictly prohibited. If you received this e-mail in error, please immediately notify the sender by e-mail, and permanently <BR>
delete this e-mail. <BR>