Hi, This is not a Suse discussion, but maybe you can help me with this.. I'm using Suse 10.1 and heartbeat-2.0.7 with older ha.cf method config (not using xml files) All works fine... My only problem, is when a service fails to start (or stop) For example, if apache2 fails, all the other services will be stopped too. Simulation: #My haresources: server1 192.168.0.1 drbddisk::home Filesystem::/dev/drbd0::/home::reiserfs apache2 spamd clamd cron #My ha.cf: debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 2 deadtime 20 warntime 10 initdead 20 udpport 694 baud 19200 auto_failback on node server1 node server2 respawn hacluster /usr/lib/heartbeat/ipfail The problem: My apache2 is misconfigured and fail to start. So, all others services in haresource will be stoped by heartbeat and server1 go to foreing mode: #ha-log Filesystem[15478]: 2007/02/15_14:39:52 INFO: Filesystem Success ResourceManager[14765]: 2007/02/15_14:39:52 info: Running /etc/init.d/apache2 start ResourceManager[14765]: 2007/02/15_14:39:52 ERROR: Return code 1 from /etc/init.d/apache2 ResourceManager[14765]: 2007/02/15_14:39:52 CRIT: Giving up resources due to failure of apache2 ResourceManager[14765]: 2007/02/15_14:39:52 info: Releasing resource group: server1 192.168.0.1 drbddisk::home Filesystem::/dev/drbd0::/home::reiserfs apache2 clamd spamd cron ResourceManager[14765]: 2007/02/15_14:39:52 info: Running /etc/init.d/cron stop ResourceManager[14765]: 2007/02/15_14:40:03 info: Running /etc/init.d/clamd stop ResourceManager[14765]: 2007/02/15_14:39:53 info: Running /etc/init.d/spamd stop heartbeat[14593]: 2007/02/15_14:39:58 info: Local Resource acquisition completed. (none) heartbeat[14593]: 2007/02/15_14:39:58 info: local resource transition completed. ResourceManager[14765]: 2007/02/15_14:40:03 info: Running /etc/init.d/apache2 stop hb_standby[16453]: 2007/02/15_14:40:37 Going standby [foreign]. heartbeat[14593]: 2007/02/15_14:40:38 info: server1 wants to go standby [foreign] As all can see, heartbeat tries to start apache2, but it fail... However, all other services will be stoped too and server1 goes to standby mode. What can I do to ignore apache2 (or others services) failures? I can't I can't leave my server down just because apache2 (or others less important services) failed to start... I used Suse 10.0 with heartbeat 1.2 and don't have this problem ... Any tips? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org