On Mon, Oct 5, 2009 at 4:53 PM, Johan Verrept <johan.verr...@able.be> wrote: > On Mon, 2009-10-05 at 16:30 +0200, Colin wrote: > >> - The pacemaker-heartbeat installation, with "crm yes" in >> /etc/ha.d/ha.cf, does not seem to start pacemaker, at least a crm_mon >> just hangs trying to connect to the cluster (the documentation doesn't >> give any hint on how to check), and a little bit later the machine >> reboots with >> >> Message from sysl...@cluster0 at Oct 5 16:06:49 ... >> heartbeat: [2821]: EMERG: Rebooting system. Reason: /usr/lib/heartbeat/cib > > Check all the necessary paths. If the processes cannot write to their > respective dirs they refuse to start and if pacemaker cannot start all > the necessary processes, the node is rebooted. At least you know now > that pacemaker is actually started :) > If you see no errors, reconfigure your syslog to allow more messages. > Usually, these are created when doing a "make install"
I'm trying really hard to RTFM, but haven't found anything that is even half complete and/or correct. Which are the "necessary paths"? Which processes should there even be? Anyhow, thanks for the hint, I hadn't looked for errors regarding directories because I had assumed (wrongly) that the Debian packages would include all necessary directories. Now I found this: Oct 5 16:06:46 cluster0 attrd: [2838]: ERROR: socket_wait_conn_new: trying to create in /var/run/crm/attrd bind:: No such file or directory Oct 5 16:06:46 cluster0 attrd: [2838]: ERROR: wait_channel_init: Can't create wait channel of type uds: No such file or directory (2) (Since "attrd" is not mentioned anywhere in the included documentation I will look at the source, or use try and error to find out the correct ownership of this directory.) Thanks, Colin _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
