Re: Bad index files.

2004-03-15 Thread Earl R Shannon
Hello, Sadly we rotate the log files every 10 days, and any logs during the time frame for this have rotated out. And we don't know how to replicate the problem short of stopping the server. Which we don't want to do just to troubleshoot this. :) And I can't check to see if both the index files y

Re: Bad index files.

2004-03-03 Thread Earl R Shannon
Hello, No. Solaris 7 and 8, using UFS with noatime as an option at mount time. The filesystems are volume slices of a RAID on a T3 attached via a Fibre SAN. The stop/start is when this seems to happen. Is it not possible that imapd processes are being SIGKILLed and leaving the index files in an un

Re: Bad index files.

2004-03-03 Thread Rob Siemborski
On Wed, 3 Mar 2004, Earl R Shannon wrote: > The stop/start is when this seems to happen. Is it not possible that > imapd processes are being SIGKILLed and leaving the index files > in an untenable state? The "running" index files are never updated directly -- the .NEW files are written out, and t

Re: Bad index files.

2004-03-03 Thread Earl R Shannon
Hello, Answers to queries below their respective question. Rob Siemborski wrote: On Wed, 3 Mar 2004, Earl R Shannon wrote: Well, then. I'm at a loss to understand the behavior we see. Users can't connect to their account. Go look and see the .NEW files. Hm. Run a reconstruct and the .NEW files

Re: Bad index files.

2004-03-03 Thread Rob Siemborski
On Wed, 3 Mar 2004, Earl R Shannon wrote: > > It sounds like the index files themselves are corrupt, but the existence > > of .new files are almost certainly a red herring. > > > If so, how can we prevent the corruption from occuring? It always > seems to appear when we shut down the cyrus process

Re: Bad index files.

2004-03-03 Thread Earl R Shannon
Hello, Well, then. I'm at a loss to understand the behavior we see. Users can't connect to their account. Go look and see the .NEW files. Hm. Run a reconstruct and the .NEW files go away. User problem fixed. Perhaps you can offer me an alternative explanation for the behavior and we can fix what

Re: Bad index files.

2004-03-03 Thread Rob Siemborski
On Wed, 3 Mar 2004, Earl R Shannon wrote: > Well, then. I'm at a loss to understand the behavior we see. > > Users can't connect to their account. > Go look and see the .NEW files. Hm. > Run a reconstruct and the .NEW files go away. > User problem fixed. > > Perhaps you can offer me an alternative

Re: Bad index files.

2004-03-03 Thread Rob Siemborski
On Wed, 3 Mar 2004, Earl R Shannon wrote: > The index files suffixed with .NEW are left behind apparently in some > unrecoverable state. If not fixed with a reconstruct the user is unable > to access their account. The .NEW files should be totally ignored by any running cyrus instance (well, exce