Hi,

On Tue, Feb 26, 2008 at 05:21:42PM -0500, Dan Gahlinger wrote:
> I can't get heartbeat to work properly.
> 
> I copied the config from another set of servers that works properly and yet
> this one doesn't.
> 
> it won't create the virtual IP, or start any of the processes it's supposed
> to. and the logs don't say any problems, looks normal.
> Also doesn't setup DRBD properly, though drbd by itself works fine.
> not sure what's wrong with it.
> 
> server 1 dbsrv01 192.168.100.2
> server 2 dbsrv02 192.168.100.3
> virtual ip setup wanted just "dbserver" 192.168.100.10
> 
> haresources:
> dbsrv01 192.168.100.10 drbddisk::r0 Filesystem::/dev/drbd0::/data::reiserfs
> mysql postfix apach
> ha.cf
> logfacility local0
> logfile /var/log/ha-log
> debugfile /var/log/ha-debug
> udpport 694
> keepalive 1
> deadtime 4
> bcast eth2
> node dbsrv01
> node dbsrv02
> auto_failback off
> uuidfrom nodename
> 
> I think it has to do with this-
> 
> info: Running /etc/ha.d/resource.d/Filesystem /dev/drbd0 /data reiserfs stop
> ResourceManager[4311]:  2008/02/26_17:04:00 ERROR: Return code 2 from
> /etc/ha.d/resource.d/Filesystem

Failed stop is really dangerous.

> ResourceManager[4311]:  2008/02/26_17:04:00 ERROR: Resource script for
> Filesystem::/dev/drbd0::/data::reiserfs probably not LSB-compliant.
> ResourceManager[4311]:  2008/02/26_17:04:00 WARN: it
> (Filesystem::/dev/drbd0::/data::reiserfs) MUST succeed on a stop when
> already stopped
> ResourceManager[4311]:  2008/02/26_17:04:00 WARN: Machine reboot narrowly
> avoided!
> ResourceManager[4311]:  2008/02/26_17:04:00 info: Running
> /etc/ha.d/resource.d/drbddisk r0 stop
> ResourceManager[4311]:  2008/02/26_17:04:00 info: Running
> /etc/ha.d/resource.d/IPaddr 192.168.100.10 stop
> IPaddr[4862]:   2008/02/26_17:04:00 INFO:  Success
> heartbeat[4301]: 2008/02/26_17:04:00 info: All HA resources relinquished.
> 
> but I'm not sure  why it's having an issue with drbd filesystem, it's setup
> identically to the other system that's working. (though that is drbd 7 not
> 8). And I get the errors with or without drbd running first.

Can't say what's going on, but you can test your cluster by hand,
i.e. try to start/stop a resource by hand and look for errors.
Once you make sure that all your resources start and stop
properly, you can try to put them in a cluster.

Thanks,

Dejan

> 
> Dan.
> _______________________________________________
> Linux-HA mailing list
> Linux-HA@lists.linux-ha.org
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to