OpenVZ Forum: Support » Heartbeat configuration for OpenVZ's VE

Home » General » Support » Heartbeat configuration for OpenVZ's VE

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Heartbeat configuration for OpenVZ's VE [message #43424]

Thu, 08 September 2011 15:21

tdesaules
Messages: 2
Registered: September 2011

Junior Member

Hi mates

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

Report message to a moderator

Re: Heartbeat configuration for OpenVZ's VE [message #43431 is a reply to message #43424]

Fri, 09 September 2011 11:29

seanfulton
Messages: 105
Registered: May 2007

Senior Member

We use heartbeat to pair more than 50 nodes. I compared my config to yours. I have bcast commented out, and I have two ucast entries, both venet0 but one for each IP in the cluster (ie, local IP and remote IP). We have have a ping_group of four IP addresses to try to avoid deadlock.

The messages from your /var/log/messages file, the only one I think is relevant is about the response taking too long. That means that this node is not getting a response from the remote node quickly enough. Operation not permitted stuff--I have been getting that for four years; no idea what it means, but it doesn't affect heartbeat.

Can you post your haresources file?

Also, make sure the files are *identical* between the two hosts.

sean

Report message to a moderator

Re: Heartbeat configuration for OpenVZ's VE [message #43443 is a reply to message #43431]

Fri, 09 September 2011 16:30

tdesaules
Messages: 2
Registered: September 2011

Junior Member

I made some change.

I create two network :
a Virtual Ethernet device in 10.0.0.X for heartbeat
a Virtual network device in 172.16.1.X for all

haresources :

haproxy1.in.unleashedproject.com        10.0.0.4

When I start heartbeat I have :

Starting High-Availability services: IPaddr[3690]: INFO:  Resource is stopped

And My log again :

Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: info: AUTH: i=3: key = 0x165bde0, auth=0x7fdff9155df0, authname=md5
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: info: Pacemaker support: false
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: WARN: Logging daemon is disabled --enabling logging daemon is recommended
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: info: **************************
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: info: Configuration validated. Starting heartbeat 3.0.4
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5074]: info: Heartbeat Hg Version: node: fcd56a9dd18c286a8c6ad639997a56b5ea40d441
Sep 09 18:26:54 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: heartbeat: version 3.0.4
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: Heartbeat generation: 1315480365
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth0
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: glib: UDP Broadcast heartbeat closed on port 694 interface eth0 - Status: 1
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5086]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: G_main_add_SignalHandler: Added signal handler for signal 17
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5085]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5084]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: Local status now set to: 'up'
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: Link haproxy1.in.unleashedproject.com:eth0 up.
Sep 09 18:26:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: info: Managed write_hostcachedata process 5087 exited with return code 0.
Sep 09 18:28:55 haproxy1.in.unleashedproject.com heartbeat: [5076]: WARN: node haproxy2.in.unleashedproject.com: is dead
Sep 09 18:28:56 haproxy1.in.unleashedproject.com heartbeat: [5084]: CRIT: Emergency Shutdown: Master Control process died.
Sep 09 18:28:56 haproxy1.in.unleashedproject.com heartbeat: [5084]: CRIT: Killing pid 5076 with SIGTERM
Sep 09 18:28:56 haproxy1.in.unleashedproject.com heartbeat: [5084]: CRIT: Killing pid 5085 with SIGTERM
Sep 09 18:28:56 haproxy1.in.unleashedproject.com heartbeat: [5084]: CRIT: Killing pid 5086 with SIGTERM
Sep 09 18:28:56 haproxy1.in.unleashedproject.com heartbeat: [5084]: CRIT: Emergency Shutdown(MCP dead): Killing ourselves.

And /var/log/message

Sep  9 18:26:54 haproxy1 heartbeat: [5074]: info: AUTH: i=3: key = 0x165bde0, auth=0x7fdff9155df0, authname=md5
Sep  9 18:26:54 haproxy1 heartbeat: [5074]: info: Pacemaker support: false
Sep  9 18:26:54 haproxy1 heartbeat: [5074]: WARN: Logging daemon is disabled --enabling logging daemon is recommended
Sep  9 18:26:54 haproxy1 heartbeat: [5074]: info: **************************
Sep  9 18:26:54 haproxy1 heartbeat: [5074]: info: Configuration validated. Starting heartbeat 3.0.4
Sep  9 18:26:54 haproxy1 heartbeat: [5074]: info: Heartbeat Hg Version: node: fcd56a9dd18c286a8c6ad639997a56b5ea40d441
Sep  9 18:26:54 haproxy1 heartbeat: [5076]: info: heartbeat: version 3.0.4
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: Heartbeat generation: 1315480365
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth0
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: glib: UDP Broadcast heartbeat closed on port 694 interface eth0 - Status: 1
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep  9 18:26:55 haproxy1 heartbeat: [5086]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: G_main_add_TriggerHandler: Added signal manual handler
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: G_main_add_SignalHandler: Added signal handler for signal 17
Sep  9 18:26:55 haproxy1 heartbeat: [5085]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep  9 18:26:55 haproxy1 heartbeat: [5084]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: ERROR: Unable to set scheduler parameters.: Operation not permitted
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: Local status now set to: 'up'
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: Link haproxy1.in.unleashedproject.com:eth0 up.
Sep  9 18:26:55 haproxy1 heartbeat: [5076]: info: Managed write_hostcachedata process 5087 exited with return code 0.
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:41 haproxy1 out of memory [5076]
Sep  9 18:28:43 haproxy1 out of memory [5076]
Sep  9 18:28:43 haproxy1 out of memory [5076]
Sep  9 18:28:43 haproxy1 out of memory [5076]
Sep  9 18:28:45 haproxy1 out of memory [5076]
Sep  9 18:28:45 haproxy1 out of memory [5076]
Sep  9 18:28:45 haproxy1 out of memory [5076]
Sep  9 18:28:47 haproxy1 out of memory [5076]
Sep  9 18:28:47 haproxy1 out of memory [5076]
Sep  9 18:28:47 haproxy1 out of memory [5076]
Sep  9 18:28:49 haproxy1 out of memory [5076]
Sep  9 18:28:49 haproxy1 out of memory [5076]
Sep  9 18:28:49 haproxy1 out of memory [5076]
Sep  9 18:28:51 haproxy1 out of memory [5076]
Sep  9 18:28:51 haproxy1 out of memory [5076]
Sep  9 18:28:51 haproxy1 out of memory [5076]
Sep  9 18:28:53 haproxy1 out of memory [5076]
Sep  9 18:28:53 haproxy1 out of memory [5076]
Sep  9 18:28:53 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:55 haproxy1 out of memory [5076]
Sep  9 18:28:56 haproxy1 heartbeat: [5084]: CRIT: Emergency Shutdown: Master Control process died.
Sep  9 18:28:56 haproxy1 heartbeat: [5084]: CRIT: Killing pid 5076 with SIGTERM
Sep  9 18:28:56 haproxy1 heartbeat: [5084]: CRIT: Killing pid 5085 with SIGTERM
Sep  9 18:28:56 haproxy1 heartbeat: [5084]: CRIT: Killing pid 5086 with SIGTERM
Sep  9 18:28:56 haproxy1 heartbeat: [5084]: CRIT: Emergency Shutdown(MCP dead): Killing ourselves.

I hate this out of memory. ...

[ Show the rest of the message ]

[Updated on: Fri, 09 September 2011 16:32]

Report message to a moderator

Re: Heartbeat configuration for OpenVZ's VE [message #43448 is a reply to message #43443]

Fri, 09 September 2011 23:01

seanfulton
Messages: 105
Registered: May 2007

Senior Member

My haresources has the following format:

primary-node IPaddr3::74.201.40.2 mon

IPadd3 is the heartbeat script to start/stop/monitor the ip address of 74.201.40.2 and mon is a program that runs when the IP is up (mon runs, when it "dies" heartbeat will fail).

I'm not familiar with the syntax you are using. It may be a mistake, or it may be correct, I am not sure. I don't think the OOM errors have anything to do with OpenVZ per se. If your haresources is correct (and it very well may be, I don't know all the configs, then you may just have too little memory allocated to the VE. Did you check /proc/user_beancounters on the host?

If you are getting errors there, do yourself a favor and don't try to tweak the settings yourself--it is very complicated. The secret I found in a couple of posts is to use vzsplit. If you want to put 5 VEs on this machine, just do vzsplit -n 5 -f 5 (I think check the man page) and it will create a ve-5.conf config file in /etc/vz/conf. Then you can do vzctl set <VEID> --applyconfig 5 --save (again, I am not on a machine right now to check the syntax, but you can put it together) and it will config your VE with 1/5 of the resources on the machine. Solves a lot of problems.

sean

Report message to a moderator

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

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Sep 27 05:22:37 GMT 2024

Total time taken to generate the page: 0.04285 seconds