Hi, On Tue, Apr 20, 2010 at 04:07:40PM -0700, Sid Stuart wrote: > Hi, > > I'm trying to debug a problem with Heartbeat 3.0.3-1 and Pacemaker 1.0.8-5. > I have logd configured and it is writing to the log file, but the messages > from heartbeat seem to be truncated. For example, > > Apr 19 15:13:36 kong102.kongregate.com logd: [3606]: info: > logd_term_write_action: received SIGTERM > Apr 19 15:13:36 kong102.kongregate.com logd: [3606]: info: Exiting write > process > Apr 19 15:13:40 kong102.kongregate.com logd: [3936]: info: logd started with > /etc/logd.cf. > Apr 19 15:13:40 kong102.kongregate.com logd: [3937]: info: > G_main_add_SignalHandler: Added signal handler for signal 15 > Apr 19 15:13:40 kong102.kongregate.com logd: [3936]: info: > G_main_add_SignalHandler: Added signal handler for signal 15 > Apr 19 15:13:51 kong102.kongregate.com heartbeat: [3991]: info: > Apr 19 15:13:52 kong102.kongregate.com heartbeat: [3992]: info: > Apr 19 15:15:52 kong102.kongregate.com heartbeat: [3992]: WARN: > Apr 19 15:15:52 kong102.kongregate.com heartbeat: [3992]: info: > Apr 19 15:15:52 kong102.kongregate.com cib: [4052]: info: > Apr 19 15:15:52 kong102.kongregate.com attrd: [4055]: info: > > > Is there a switch somewhere that turns on the full message?
What happens if you log directly to syslog, without logd? You can just stop logd, the logging library will notice and use syslog. Thanks, Dejan > Sid > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
