[Pacemaker] Setting the logfile option in corosync.conf to a directory not created causes corosync to fail to start with non-descriptive parse error...

[Colin Hines]

Just adding this as an FYI if anyone comes across it...

Not creating the logfile directory that is listed in corosync.conf will
create the following log errors and corosync will fail to start (this is
with the latest rpm based builds from http://www.clusterlabs.org/rpm/epel-5/

Apr  8 12:34:24 cvt-db-003 corosync[24350]:   [MAIN  ] Successfully read
main configuration file '/etc/corosync/corosync.conf'.
Apr  8 12:34:24 cvt-db-003 corosync[24350]:   [MAIN  ] parse error in
config: parse error in config: .
Apr  8 12:34:24 cvt-db-003 corosync[24350]:   [MAIN  ] Corosync Cluster
Engine exiting with status 8 at main.c:1397.

c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20110408/4fe128de/attachment.html>