On Wed, Jun 10, 2009 at 12:52:35PM +0200, Dejan Muhamedagic wrote: > Hi, > > On Wed, Jun 10, 2009 at 12:20:14PM +0200, jeroen groenewegen van der weyden > wrote: > > Hi everybody, > > > > I just experienced a strange behavior, after rebooting our server manual > > the heart beat came not into service after the reboot. The message log > > show Retrying already in use? but in netstat nothing shows up on port > > Did you try lsof or fuser? > > > 694? The nodes were able to see each other. On both nodes services were > > connecting using the same link (br0). > > > > A heartbeart stop/start did not help and resulted in the same log messages > > After the a second reboot the phenomenon was gone > > > > heartbeat V2.99.2 > > openSUSE 11.1 > > > > Anybody seen this before? or know the cause of it? > > No. The only explanation I can imagine is that another process is > using this port.
e.g. rpc mountd is known to do that sometimes. or anything else using rpc portmaper. they are free to choose. most of them _can_ be told to use a fixed port, though. (see man rpc.mountd, -p option) maybe the best solution would be to have heartbeat start earlier, just after network and sshd are up, before any other network services are started, yes, even before portmapper or any rpc services with "arbitrary" ports. or tell portmapper to choose arbitrary ports from above 1024, if that is possible. -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
