On Tue, Jan 26, 2010 at 04:25:44PM +0000, Maros Timko wrote: > Hi all, > > I downloaded latest EPEL Pacemaker/Heartbeat RPMS. After installing on > CentOS 5.4 I found that the heartbeat will not start correctly because > of missing directory /var/run/heartbeat/crm: > Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: debug: > Setting message filter mode > Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: debug: > Setting message signal > Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: debug: > Waiting for messages... > Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: ERROR: > socket_wait_conn_new: trying to create in > /var/run/heartbeat/crm/outdater bind:: No such file or directory > Jan 26 11:37:33 vsp7 /usr/lib64/heartbeat/dopd: [11357]: ERROR: Can't > create wait channel of type uds: Resource temporarily unavailable > Jan 26 11:37:33 vsp7 heartbeat: [10516]: WARN: Managed > /usr/lib64/heartbeat/dopd process 11357 exited with return code 1. > Jan 26 11:37:33 vsp7 heartbeat: [10516]: ERROR: Respawning client > "/usr/lib64/heartbeat/dopd ": > Jan 26 11:37:33 vsp7 heartbeat: [10516]: info: Starting child client > "/usr/lib64/heartbeat/dopd " (24,24) > > So far I am using a workaround to create it. Will newer version of > heartbeat create it correctly? Or is it not supported configuration to > use DOPD anymore? > > # rpm -qa|grep heartbeat > heartbeat-3.0.1-1.el5.x86_64 > heartbeat-libs-3.0.1-1.el5.x86_64
On Debian, and presumably other distros too, there is a presumption that /var/run and /var/lock may be on tempoary file systems. Thus any files and directories need to be created after boot time. That is to say, they generally ought to be created in an init script rather than by a package. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
