On Fri, Jan 09, 2009 at 11:39:39AM +0100, Ekkard Gerlach wrote:
> Hi,
>
> heartbeat fails starting vserver "arthur" after a hb_takeover all:
>
> Jan 9 00:46:10 libu1 heartbeat: CRIT: Giving up resources due to failure of vserver::arthur
> Jan 9 00:46:10 libu1 heartbeat: info: Releasing resource group: libu1 drbddisk::vserver-arthur
> Filesystem::/dev/drbd1::/data/arthur::ext3 192.168.0.9 nfs-kernel-server vserver::arthur
> Jan 9 00:46:11 libu1 heartbeat: info: Retrying failed stop operation [vserver::arthur]
that sounds like it is trying to stop it not start it :)
> But vserver "arthur" is starting correctly! Started manually:
>
> libu1:/etc/vservers/misc# vserver arthur start
> Starting system log daemon: syslogd.
> Starting kernel log daemon: klogd.
> Not starting internet superserver: no services enabled.
> Starting periodic command scheduler: crond.
>
> After "server arthur enter" is possible.
> Where could be the fault?
stopping an already stopped guest will fail, so maybe
that is the problem?
> Perhaps I'm in the wrong list here? ;-)
won't hurt to ask the heartbeat folks, but I'm sure
you'll get some hints from Linux-VServer folks using
heartbeat too :)
best,
Herbert
> thx
> Ekkard
>