PLEASE HELP - cyrusdb errors after power failure

[Shawn Sivy]

Thanks Simon.  I did upgrade to 2.2.8 later in the day.  I think our 
problems may have had a basis in the 2.2.5 version we were running, but 
I also think the power outage and filesystem errors also played a big 
role.  For those who would like to know, most of the IOERRORs I was 
getting were tracked down to corrupted quota files (quotalegacy 
format).  Either cyrus or the power failure caused a bunch to be 
truncated so that the second line in the quota file didn't include the 
end-of-line character or may have been empty.  I simply removed those 
quota files and used a perl script I have to set the quota (similar to 
how cyradm does it) which recreated the file.

I also ran into a weird issue where a "find" command or an "ls" command 
would say files weren't found or didn't exist, but using vi or similar, 
I could access them.  There were IOERRORs in the imapd.log file about 
these missing files too, usually a message file.  I found that on Sun 
Solaris 8 and 9, there is a patch that needs to be applied when a 
filesystem has lots of files, like a cyrus server.  It has to do with 
DNLC which can't handle the large number of files unless the patch is 
applied or the workaround (turning off DNLC) is used.  For those 
interested, the SunSolve SRDB article is 76085 and the patch (for 
Solaris 9) is 113073-13.

  -Shawn

Simon Matter wrote:

>>We recently had a power failure during a storm and the server required
>>an fsck before it would mount up the file systems (eventhough I did have
>>logging/journaling turned on).  After running 2 fscks it seems clean,
>>but there are issue with the cyrus files themselves.  I had a problem
>>with the mailboxes.db and the .seen files.  I converted all these to
>>"flat" using cvt_cyrusdb and back again to skiplist (I removed the
>>originals before converting back).  However, I'm still getting a lot of
>>cyrusdb errors via the imap, pop3 and lmtpunix processes.  I tried
>>reconstructing those accounts with the errors but the problem returns in
>>a short period of time.  I notice that there is the cyrus.index.NEW and
>>cyrus.cache.NEW files in the directory with their mail files.  Running
>>reconstruct removed them but they return with the next set of errors.
>>So, it seems something else is causing the process to fail and leave the
>>.NEW files around.  I also tried removing the .NEW and the cyrus.cache
>>and cyrus.index files totally before running a reconstruct, but that
>>didn't seem to help.  Any other suggestion on things to look at or try.
>>
>>We are running cyrus 2.2.5 (I know ... I should upgrade to 2.2.8) on
>>    
>>
>
>I'm not sure but you may be hit now by the problem introduced after 2.2.3
>which are all solved with 2.2.8. That's why I _strongly_ recommend to
>upgrade before you try anything else!
>
>Simon
>
>  
>
>>Solaris 9.  Everything was working great before the power failure.
>>Here's some of the error messages.
>>
>>Aug 13 10:46:05 cyrus pop3[6427]: [ID 237943 local6.notice] login:
>>somewhereat.TCNJ.EDU [192.168.1.1] mary plaintext User logged in
>>Aug 13 10:46:26 cyrus lmtpunix[25811]: [ID 335833 local6.error] DBERROR:
>>error fetching user.mary: cyrusdb error
>>Aug 13 10:46:26 cyrus lmtpunix[25811]: [ID 860734 local6.debug]
>>verify_user(user.mary) failed: System I/O error
>>
>>Aug 13 10:47:46 cyrus imap[26412]: [ID 277583 local6.notice] login:
>>mymail.TCNJ.EDU [192.168.100.1] kirk plaintext User logged in
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 335833 local6.error] DBERROR:
>>error fetching user.kirk: cyrusdb error
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 677757 local6.debug] seen_db:
>>user kirk opened /var/imap/user/k/kirk.seen
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 335833 local6.error] DBERROR:
>>error fetching user.kirk: cyrusdb error
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 736213 local6.debug] open: user
>>kirk opened INBOX
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 335833 local6.error] DBERROR:
>>error fetching user.kirk: cyrusdb error
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 736213 local6.debug] open: user
>>kirk opened INBOX
>>Aug 13 10:47:48 cyrus imap[26412]: [ID 335833 local6.error] DBERROR:
>>error fetching user.kirk: cyrusdb error
>>
>>Any help would be greatly appreciated!
>>
>>  -Shawn Sivy
>>   The College of New Jersey
>>
>>
>>---
>>Cyrus Home Page: http://asg.web.cmu.edu/cyrus
>>Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
>>List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
>>
>>
>>    
>>
>
>  
>

---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html