unable to open Berkeley

[Dan White]

On 21/06/10 11:05 -0700, Gary Smith wrote:
>Okay, I'm running pam_mysql/nss_mysql on this test box.  Both POP3 and IMAP are configured and seem to be working just fine.  They have been doing so for some time (12+ months).  While trouble shooting a script connection problem I found these entries in the log file.  Looking into production, I also have these same entries.  Indeed /etc/sasldb2 doesn't exist but it doesn't seem to impact login or user accounts. 
>
>So, the question is why?  How do I fix this warning or make it go away?  It is happening roughly every 10 minutes.  I don't know if it's related to a connection of a user checking his/her email or something else.  On production there are about 10 connected users at any one given time on POP3 but the timing is still about every 10 minutes.
>
>Jun 21 08:45:41 hostdev14 pop3[32139]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 08:50:52 hostdev14 pop3[32531]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 08:52:06 hostdev14 pop3[32531]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:02:05 hostdev14 pop3[553]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:12:07 hostdev14 pop3[938]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:22:07 hostdev14 pop3[1657]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:32:07 hostdev14 pop3[1814]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:42:07 hostdev14 pop3[2623]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 09:52:07 hostdev14 pop3[2971]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 10:02:07 hostdev14 pop3[3299]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 10:09:05 hostdev14 ntpd[1739]: synchronized to LOCAL(0), stratum 10
>Jun 21 10:12:07 hostdev14 pop3[3494]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 10:22:08 hostdev14 pop3[3635]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 10:32:08 hostdev14 pop3[3852]: unable to open Berkeley db /etc/sasldb2: No such file or directory
>Jun 21 10:42:07 hostdev14 pop3[4035]: unable to open Berkeley db /etc/sasldb2: No such file or directory

You are probably seeing this message each time a new process is spawned,
and your auxprop plugin(s) are initialized.

As long as you do not need the sasldb auxprop plugin, you can ignore those
log entries. If you are using 'sasl_pwcheck_method: saslauth' (or any
method other than auxprop), and you only support the plaintext
authentication mechanisms, then you shouldn't need it.

To make it go away, you could recompile Cyrus SASL without the sasldb
auxprop plugin, or you could create an empty berkeley db database in
/etc/sasldb2:

echo '!' | saslpasswd2 -c 'no:such:user'
saslpasswd2 -d 'no:such:user'

-- 
Dan White