Your message dated Fri, 8 Jul 2016 20:21:55 +0200
with message-id <[email protected]>
and subject line Re: /etc/init.d/o2cb: o2cb fail at startup, unable to bind net
interface.
has caused the Debian Bug report #741650,
regarding /etc/init.d/o2cb: o2cb fail at startup, unable to bind net interface.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
741650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741650
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ocfs2-tools
Version: 1.6.4-1+deb7u1
Severity: normal
File: /etc/init.d/o2cb
Dear Maintainer,
the o2cb always fails at startup, because it is unable to bind the network
interface, so the machine does not join the cluster. It seems that the
interface is not usable when needed so I usually get this error:
- o2net: Error -99 while binding socket
The script /etc/init.d/o2cb is correctly called after the network setup script,
but this does not seem to be enough. I have been able to solve the problem by
adding a sleep of a few seconds at the beginning of the function "online_o2cb";
a nicer solution would be to add a check that the interface is up and
configured.
Anyway, thank you for your effort with Debian.
Have a nice day, Maurizio.
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ocfs2-tools depends on:
ii debconf [debconf-2.0] 1.5.49
ii libc6 2.13-38+deb7u1
ii libcomerr2 1.42.5-1.1
ii libglib2.0-0 2.33.12+really2.32.4-5
ii libncurses5 5.9-10
ii libreadline6 6.2+dfsg-0.1
ii libtinfo5 5.9-10
ii libuuid1 2.20.1-5.3
ii psmisc 22.19-1+deb7u1
ocfs2-tools recommends no packages.
Versions of packages ocfs2-tools suggests:
pn ocfs2-tools-cman <none>
pn ocfs2-tools-pacemaker <none>
ii ocfs2console 1.6.4-1+deb7u1
-- debconf information:
ocfs2-tools/clustername: ocfs2
ocfs2-tools/heartbeat_threshold: 31
ocfs2-tools/idle_timeout: 30000
ocfs2-tools/reconnect_delay: 2000
ocfs2-tools/init: false
ocfs2-tools/keepalive_delay: 2000
--- End Message ---
--- Begin Message ---
On Fri, Jul 08, 2016 at 06:22:33PM +0200, Maurizio Cimaschi wrote:
> The cluster does not exist anymore, but the problem was probably due to
> the the fact that the cluster was using DHCP for network configuration. I
> agree that is not recomandable for server, but the cluster was intended for
> testing purpose e not for production environment.
>
> It is clearly a minor bug that could be closed, but inserting a hook in
> the dhclient (man dhclient-script for details) script directory to reload
> the o2cb may solve this issue.
Thank you for the additional info. I think the cluster software like ocfs2
assumes static IPs because it depends on a stable network to work properly.
So at this point I will close this and not add any additional complexity into
the ocfs2 package.
--
Valentin
--- End Message ---
