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

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

[Message index]

		Heartbeat configuration for OpenVZ's VE By: tdesaules on Thu, 08 September 2011 15:21
		Re: Heartbeat configuration for OpenVZ's VE By: seanfulton on Fri, 09 September 2011 11:29
		Re: Heartbeat configuration for OpenVZ's VE By: tdesaules on Fri, 09 September 2011 16:30
		Re: Heartbeat configuration for OpenVZ's VE By: seanfulton on Fri, 09 September 2011 23:01

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: Thu Jul 10 00:34:22 GMT 2025

Total time taken to generate the page: 0.03006 seconds