OpenVZ Forum


Home » General » Support » Heartbeat configuration for OpenVZ's VE
Heartbeat configuration for OpenVZ's VE [message #43424] Thu, 08 September 2011 15:21 Go to previous message
tdesaules is currently offline  tdesaules
Messages: 2
Registered: September 2011
Junior Member
Hi mates Smile

I have some trouble configuring heartbeat inside a VM... I don't know if it's possible or if someone have made it before beacause I fail...

There is my ha.cf :

logfile         /var/log/ha-log
debug           3
debugfile       /var/log/ha-debug
logfacility     local0
keepalive       2
deadtime        10
initdead        120
bcast           venet0
ucast           venet0          172.16.1.65
udpport         694
auto_failback   on
node            haproxy1
node            haproxy2


And... the log :

Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: info: AUTH: i=3: key = 0x1d93c30, auth=0x7fd3dbd63df0, authname=md5
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: info: Pacemaker support: false
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: WARN: Logging daemon is disabled --enabling logging daemon is recommended
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: info: **************************
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: info: Configuration validated. Starting heartbeat 3.0.4
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1152]: info: Heartbeat Hg Version: node: fcd56a9dd18c286a8c6ad639997a56b5ea40d441
Sep 08 17:19:17 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: heartbeat: version 3.0.4
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: Heartbeat generation: 1315480353
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: UDP Broadcast heartbeat started on port 694 (694) interface venet0
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: UDP Broadcast heartbeat closed on port 694 interface venet0 - Status: 1
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1163]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1164]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1162]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on venet0
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: ucast: bound send socket to device: venet0
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: ucast: bound receive socket to device: venet0
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: glib: ucast: started on port 694 interface venet0 to 172.16.1.65
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1165]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1166]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: G_main_add_SignalHandler: Added signal handler for signal 17
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: Local status now set to: 'up'
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: Link haproxy1.in.unleashedproject.com:venet0 up.
Sep 08 17:19:18 haproxy1.in.unleashedproject.com heartbeat: [1154]: info: Managed write_hostcachedata process 1167 exited with return code 0.
Sep 08 17:19:28 haproxy1.in.unleashedproject.com heartbeat: [1154]: WARN: Gmain_timeout_dispatch: Dispatch function for send local status took too long to execute: 90 ms (> 50 ms) (GSource: 0x1d9c220)
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Emergency Shutdown: Master Control process died.
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Killing pid 1154 with SIGTERM
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Killing pid 1163 with SIGTERM
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Killing pid 1164 with SIGTERM
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Killing pid 1165 with SIGTERM
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Killing pid 1166 with SIGTERM
Sep 08 17:21:19 haproxy1.in.unleashedproject.com heartbeat: [1162]: CRIT: Emergency Shutdown(MCP dead): Killing ourselves.


If someone have any idea Smile thanks

 
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to install OpenVZ on CentOS 6
Next Topic: /dev/shm missing from fedora-15-x86 template
Goto Forum:
  


Current Time: Sun Nov 10 04:34:20 GMT 2024

Total time taken to generate the page: 0.03364 seconds