[OpenAFS] Re: Salvager running repeatedly

2010-03-25 Thread Andrew Deason
On Thu, 25 Mar 2010 10:51:39 +0200 (EET) Atro Tossavainen wrote: > I'm OK with printing out a trace - but I'll need a little handholding > here. Sure. At least to start, just: # /opt/SUNWspro/bin/dbx /path/to/old/fileserver /path/to/core [blah blah blah] (dbx) where will give some useful outpu

Re: [OpenAFS] Re: Salvager running repeatedly

2010-03-25 Thread Atro Tossavainen
Andrew, > That's... interesting. Would you be willing to share a core (or at least > the trace from it)? If you're fine with it since it's working now, > that's fine, but it might be nice to know if the core can let us know > what was going on. If we had an OpenAFS support contract with Sine Nomi

[OpenAFS] Re: Salvager running repeatedly

2010-03-24 Thread Andrew Deason
On Wed, 24 Mar 2010 11:29:48 -0400 Dan Hyde wrote: > > > > Absolutely not meant as a personal comment, but it's important to > > remember fileserver cores may contain your cell-wide key, and you > > definitely don't want to share them publicly without verifying that > > they don't. Augh, yes, s

Re: [OpenAFS] Re: Salvager running repeatedly

2010-03-24 Thread Dan Hyde
> > Absolutely not meant as a personal comment, but it's important to > remember fileserver cores may contain your cell-wide key, and you > definitely don't want to share them publicly without verifying that > they don't. And ensure your efforts to remove the KeyFile content do not accidentially

Re: [OpenAFS] Re: Salvager running repeatedly

2010-03-24 Thread Simon Wilkinson
On 24 Mar 2010, at 15:14, Andrew Deason wrote: > > That's... interesting. Would you be willing to share a core Absolutely not meant as a personal comment, but it's important to remember fileserver cores may contain your cell-wide key, and you definitely don't want to share them publicly withou

[OpenAFS] Re: Salvager running repeatedly

2010-03-24 Thread Andrew Deason
On Wed, 24 Mar 2010 15:17:41 +0200 (EET) Atro Tossavainen wrote: > > So there's no FileLog.old that keeps being refreshed with say a > > registration failure? > > Because this sounds like that problem. > > It was that problem. fileserver coredumped at startup regardless of > what it tried to do