It's actually possible we are using BDB - earlier in the mail server's
life we moved it from a PowerPC G5 Xserve to the Intel Xserve, and we
needed to work around the endian issues inherent in some part of the
mail server, so I recall converting a database in some direction,
either from BDB to skiplist or vice-versa. My memory escapes me now
as to which way we went, though. How would I check?
--
Josh Whitver
whitverj@xxxxxxxxxxxxxxxxxxx / josh@xxxxxxxxxxx
(If you can't hear me, it's because I'm in parentheses)
On Feb 11, 2009, at 8:40 PM, Bron Gondwana wrote:
>
> On Tue, 10 Feb 2009 15:59:09 -0600, "Josh Whitver" <whitverj@xxxxxxxxxxxxxxxxxxx
> > said:
>> Whenever an IMAP connection is attempted, I see this in the log:
>> Feb 10 09:14:17 urbandale imap[34508]: DBERROR: error fetching user.
>> [username]: cyrusdb error
>
> OK - there are two spots in the code that can produce exactly that
> error message. One is in BDB, which I assume you're not using. The
> other is in mboxlist (latest CVS changes this one to "error fetching
> mboxlist user.[username]: [error]" to be clearer!)
>
> So, it's in mboxlist_mylookup. The specific error is being returned
> by:
>
> if (wrlock) {
> r = DB->fetchlock(mbdb, name, namelen, &data, &datalen, tid);
> } else {
> r = DB->fetch(mbdb, name, namelen, &data, &datalen, tid);
> }
>
> ...
>
> default:
> syslog(LOG_ERR, "DBERROR: error fetching mboxlist %s: %s",
> name, cyrusdb_strerror(r));
> return IMAP_IOERROR;
> break;
>
> Sorry I didn't get back to you before. I really don't think I can
> debug this any further without a copy of your mailboxes.db file.
>
> I assume you've ruled out filesystem corruption by checking syslog/
> dmesg/
> whatever for signs of bad blocks?
>
> Bron.
> --
> Bron Gondwana
> brong@xxxxxxxxxxx
>
>
----
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
