Re: [Pacemaker] syslog-ng as resource / how to make sure it gets restarted

On Fri, Oct 1, 2010 at 9:41 AM, Koch, Sebastian sebastian.k...@netzwerk.de wrote: Hi Andrew, thanks for your answer. I still need syslog-ng to restart on all nodes after the ClusterIp moved. I tried it like this: Resource: primitive res_SyslogNG lsb:syslog-ng \     op monitor

Re: [Pacemaker] syslog-ng as resource / how to make sure it gets restarted

Hi Andrew, thanks for your answer. I still need syslog-ng to restart on all nodes after the ClusterIp moved. I tried it like this: Resource: primitive res_SyslogNG lsb:syslog-ng \ op monitor interval=15s timeout=20s start-delay=15s Clone: clone cl-SyslogNG

Re: [Pacemaker] syslog-ng as resource / how to make sure it gets restarted

Hello, i now edited the syslog-ng Debian Init Script to fit the LSB spec. Now it should be cluster ready. See the new Script version below. Feedback is appreciated and I hope it helps somebody.

Re: [Pacemaker] syslog-ng as resource / how to make sure it gets restarted

On Mon, Jun 28, 2010 at 10:52 AM, Koch, Sebastian sebastian.k...@netzwerk.de wrote: Hi, i got a loggin application that is running on a active passive LAMP Cluster. The server is working as a logging server form my infrastructure. I configured syslog-ng to listen on all open ip addresses.

[Pacemaker] syslog-ng as resource / how to make sure it gets restarted

Hi, i got a loggin application that is running on a active passive LAMP Cluster. The server is working as a logging server form my infrastructure. I configured syslog-ng to listen on all open ip addresses. It is working fine but when i migrate the CLusterIP the syslog-ng daemon doesn't

Re: [Pacemaker] syslog-ng as resource / how to make sure it gets restarted

Oh i forgot to include my setup: Last updated: Mon Jun 28 10:51:02 2010 Stack: openais Current DC: pilot01-node2 - partition with quorum Version: 1.0.8-2c98138c2f070fcb6ddeab1084154cffbf44ba75 2 Nodes configured, 2 expected votes 4 Resources configured.