Package: openafs-fileserver Version: 1.4.12.1+dfsg-4 After rebooting one of my OpenAFS servers (that was set up to acquire its IP address through DHCP) I found (reproducibly, on that particular server) that all BOS-controlled services ended up being stopped after too many failures to start. Running "bos start localhost <instance> -localauth" was enough to recover.
A look at the logs convinced me that the services failed because they were trying to start before the server had an IP address. Switching to a static configuration in /etc/network/interfaces has cured the problem. /etc/init.d/openafs-fileserver, which starts bosserver, has a Required-Start: $remote_fs $network $time $named and /etc/insserv.conf defines $network as "+networking +ifupdown". /etc/init.d/networking runs "ifup -a". Apparently this can return before the interface(s) is(are) actually usable. Is this bosserver's or ifup's fault? This isn't entirely clear to me (and I see there is a five-year-old important bug against ifupdown, #418326, which also touches on whether "ifup -a" should wait until the interfaces are fully up) but I suspect it may be unrealistic to make "ifup -a" block for too long waiting on an interface. Pragmatically, then, one would like for bosserver to make a fresh attempt at starting these services whenever an interface becomes ready. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
