Re: [Pacemaker] Preventing resource from becoming inactive

Hallöchen! David Mohr writes: > On Tue, 10 Aug 2010 07:56:47 +0200, Torsten Bronger > wrote: > >> Sometimes Pacemaker just switches off my Lighttpd. It becomes >> inactive and is never reanimated. Only restarting the Heartbeat >> service helps. How can I tell Pa

[Pacemaker] Preventing resource from becoming inactive

t;20s" group lighty_group Public-IP lighty clone pingclone pingd meta globally-unique="false" location lighty-on-connected-node lighty_group \ rule $id="lighty-on-connected-node-rule" -inf: not_defined pingd or pingd lte 0 Tschö, Torsten. -- Torsten Bronger,

Re: [Pacemaker] Lighty doesn't come up always

of our trouble: pingd seems to be too late. I just dropped the "not_defined pingd" and it works. That's okay: The probability that the external interface is broken _and_ pingd is broken is small enough. Tschö, Torsten. -- Torsten Bronger, aquisgrana, europa vetus

Re: [Pacemaker] Lighty doesn't come up always

Hallöchen! Dr. Michael Schwartzkopff writes: > Am Dienstag, den 06.07.2010, 10:28 +0200 schrieb Torsten Bronger: > >> We have a two-node cluster with a virtual IP and Lighty running >> on that node which has this IP currently. Thus, our >> configuration says: >>

Re: [Pacemaker] Lighty doesn't come up always

Hallöchen! Raoul Bhatia [IPAX] writes: > On 07/06/2010 10:28 AM, Torsten Bronger wrote: > >> We have a two-node cluster with a virtual IP and Lighty running on >> that node which has this IP currently. Thus, our configuration >> says: >> >> node $id=&q

[Pacemaker] Lighty doesn't come up always

r_0 (node=mandy, call=3, rc=1, status=complete): unknown error What does this "unknown error" mean? I is not further explained in the log files, neither in Heartbeat's nor in Lighty's. Well, in Lighty's, there's nothing about errors at all. If I restart