Thanks for the response Andrew. I have: cluster-glue-1.0.1-1.el5 cluster-glue-libs-1.0.1-1.el5 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.
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. Thanks! Kenneth M DeChick Linux Systems Administrator Community Computer Service, Inc. (315)-255-1751 ext154 http://www.medent.com k...@medent.com Registered Linux User #497318 -- -- -- -- -- -- -- -- -- -- -- "You canna change the laws of physics, Captain; I've got to have thirtyminutes! " . ---------- Original Message ----------- From: Andrew Beekhof <and...@beekhof.net> To: pacema...@clusterlabs.org, k...@medent.com Sent: Fri, 29 Jan 2010 09:00:47 +0100 Subject: Re: [Pacemaker] Question on logd > On Thu, Jan 28, 2010 at 10:04 PM, Ken Dechick <k...@medent.com> wrote: > > Hi eveyone, > > I have spent the better part of the afternoon searching for an answer as to > why I get " logd is not running" errors constantly. > Using: DRBD: 8.3.6, Heartbeat 3.0.1-1 Pacemaker 1.0.6 on CentOS 5.3 x86_64 > > 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!! > > > Perhaps try /usr/share/docs/*glue* instead. > I'd expect that to be part of the cluster-glue packages now. > > At any rate, here's the contents: > > # File to write debug messages to > # Default: /var/log/ha-debug > #debugfile /var/log/ha-debug > > # > # > # File to write other messages to > # Default: /var/log/ha-log > #logfile /var/log/ha-log > > # > # > # Facility to use for syslog()/logger > # Default: daemon > #logfacility daemon > > # Entity to be shown at beginning of a message > # for logging daemon > # Default: "logd" > #entity logd > > # Do we register to apphbd > # Default: no > #useapphbd no > > # There are two processes running for logging daemon > # 1. parent process which reads messages from all client channels > # and writes them to the child process > # > # 2. the child process which reads messages from the parent process through > IPC > # and writes them to syslog/disk > > # set the send queue length from the parent process to the child process > # > #sendqlen 256 > > # set the recv queue length in child process > # > #recvqlen 256 ------- End of Original Message ------- 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>
_______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
