<HTML>
<HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
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 all. Forgot to mention I did an 'updatedb && locate ha_logd.cf' on my systems and this example file is just plain not present anywhere. I checked my current repositories and there is no mention of any other cluster-glue packages (ie: there is no cluster-glue-docs*.rpm) available.
<br />
<br />I will setup based on the listing you provided. One other thing I would like to mention just so it's out there: there is a /etc/init.d/logd but by default after install it is not ready to use. I had to: 'chkconfig --add logd' before I could get it to come up at boot. Shouldn't this have been done as part of the installation from rpm?? There was a time not too long ago when I had to do the same for heartbeat, but that appears to have been fixed in the 3.0.1-1 version I use now.
<br />
<br />
<br />
<br />Thanks!
<br /><font size="2">
<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: 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 <span dir="ltr"><<a href="mailto:kend@medent.com">kend@medent.com</a>></span> wrote:
<br />>
<blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<br />>
<font size="2">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 />> </font></blockquote>
<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 />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>File to write debug messages to
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Default:
/var/log/ha-debug
<br />> #debugfile /var/log/ha-debug
<br />>
<br />> #
<br />> #
<br />> #
<span style="white-space: pre;" class="Apple-tab-span"> </span>File to write other
messages to
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Default:
/var/log/ha-log
<br />> #logfile<span style="white-space: pre;" class="Apple-tab-span"> </span>/var/log/ha-log
<br />>
<br />> #
<br />>
#
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Facility
to use for
syslog()/logger
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Default:
daemon
<br />> #logfacility<span style="white-space: pre;" class="Apple-tab-span"> </span>daemon
<br />>
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Entity to be shown at
beginning of a
message
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>for
logging daemon
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>Default: "logd"
<br />> #entity
logd
<br />>
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Do we register to apphbd
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>Default: no
<br />>
#useapphbd
no
<br />>
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>There are two processes running for logging
daemon
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>1. parent process which reads messages from all
client
channels
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>and
writes them to the child process
<br />> #
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>2. the child process
which reads messages from the parent process through
IPC
<br />> # <span style="white-space: pre;" class="Apple-tab-span"> </span>and
writes them to syslog/disk
<br />>
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>set the send queue length from the parent
process to the child
process
<br />> #
<br />> #sendqlen 256
<br />>
<br />> #<span style="white-space: pre;" class="Apple-tab-span"> </span>set the recv queue length
in child process
<br />> #
<br />> #recvqlen 256
<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>