Well, late last night I upgraded our server. Before: - cyrus-sasl post-1.5.27 cvs snapshot from 20010809 - cyrus-imapd cvs snapshot from 20011120 - berkeley db 3.3.11
After: - cyrus-sasl 2.1.0 - cyrus-imapd cvs snapshot from 20020119 - berkeley db 4.0.14 All of this was compiled on Solaris 8 with the newer binaries compiled with gcc-3.0.3. We're using saslauthd with '-a shadow' (LDAP ultimately being used). Previously we would see the occasional 'DBERROR db3: X lockers' for some number of X. This X value would increase, but also decrease. Consequently I never really worried about it. However, since the upgrade I have yet see this number decrease. It now seems to be ever increasing. Before restarting the servers this morning I saw a syslog output of 'DBERROR db3: 4052 lockers'. Could this be symptomatic of something more serious, or just a bug in accounting? But perhaps more disturbing is that saslauthd appears to be freezing up. I haven't been able to detect a pattern yet, but saslauthd seems to stop handling requests. The daemons are still running, but there is a flood of 'cannot connect to saslauthd server'. I then have to stop saslauthd and restart it. I've had to do this something like 4 times now since the upgrade. Seems odd since we're using sasl in a rather simplistic way, and saslauthd worked just fine prior to 2.1.0. Maybe my problem is that I didn't get THAT from CVS? ;-) Now to do some digging. -- Amos
