[27460] in Athena Bugs

home help back first fref pref prev next nref lref last post

Re: OpenAFS sometimes fails to start on Lucid

daemon@ATHENA.MIT.EDU (Geoffrey Thomas)
Sun Jun 20 22:02:55 2010

Date: Sun, 20 Jun 2010 22:02:52 -0400 (EDT)
From: Geoffrey Thomas <geofft@mit.edu>
To: bugs@mit.edu
In-Reply-To: <alpine.DEB.1.10.1006160305530.30104@dr-wily.mit.edu>
Message-ID: <alpine.DEB.1.10.1006202201270.9112@dr-wily.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Errors-To: bugs-bounces@mit.edu

To follow up on this, the /mit automounter also failed to start. My 
current runing theory is that occasionally Upstart's init decides that 
starting legacy /etc/rc*.d jobs is beneath its station and just doesn't.

-- 
Geoffrey Thomas
geofft@mit.edu

On Wed, 16 Jun 2010, Geoffrey Thomas wrote:

> I have essentially Ubuntu Server (10.04/Lucid) running on my laptop, with 
> wireless configured in /etc/network/interfaces to automatically start, and 
> with the default Ubuntu splash and debathena-openafs-config installed. Once 
> every several boots, openafs-client just won't have started (aklog will fail 
> with an error indicating it's not running), and there's no evidence in 
> /var/log/boot.log that it ever tried, not even "Starting AFS services:". 
> /etc/init.d/openafs-client and /etc/rc2.d/S25openafs-client look fine, as do 
> /etc/openafs/afs.conf{,.client}. What's going on?
>
> If it's relevant, this might be more likely when I've been rebooting a lot 
> (to test grub config); perhaps I've also held down shift during the boot, but 
> that really really shouldn't be relevant for userspace initialization.
>
> -- 
> Geoffrey Thomas
> geofft@mit.edu
>

home help back first fref pref prev next nref lref last post