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. It is working fine > but when i migrate the CLusterIP the syslog-ng daemon doesn’t recognize the > new IP Address and is not recieving any messages. > > > > What could be the correct way to cluster syslog-ng? My first idea ist o > clone syslog-ng and to include it into the grp_MySQL to make sure it gets > restarted when the CLusterIP migrates.
Groups can't contain clones. But yes, making it a cloned resource that it ordered to start after the IP should do it. > Maybe some of you got a better idea > or hints on how to make sure that syslog gets restarted on ip migration. _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
