Re: NO Login failed: generic failure

[Marc Fournier <scrappy@xxxxxxx>]

On Mar 26, 2014, at 12:54 , Marc Fournier <scrappy@xxxxxxx> wrote:

Mar 26 19:47:17 xxx imap[1448]: Could not open db 

Mar 26 19:47:17 xxx imap[1448]: sql plugin Parse the username sales@xxxxxxxx

Mar 26 19:47:17 xxx imap[1448]: sql plugin try and connect to a host

Mar 26 19:47:17 xxx imap[1448]: sql plugin trying to open db '/var/db/sqlite/mailsys' on host '' 

Mar 26 19:47:17 xxx imap[1448]: begin transaction

Mar 26 19:47:17 xxx imap[1448]: sql plugin create statement from userPassword sales xxx.info

Mar 26 19:47:17 xxx imap[1448]: sql plugin doing query SELECT userPassword FROM sasl_auth WHERE userid = 'sales@xxxxxxxx';

Mar 26 19:47:17 xxx imap[1448]: sql plugin create statement from cmusaslsecretPLAIN sales xxx.info

Mar 26 19:47:17 xxx imap[1448]: sql plugin doing query SELECT cmusaslsecretPLAIN FROM sasl_auth WHERE userid = 'sales@xxxxxxxx';

Mar 26 19:47:17 xxx imap[1448]: sql plugin: no such column: cmusaslsecretPLAIN 

Mar 26 19:47:17 xxx imap[1448]: commit transaction

Mar 26 19:47:17 xxx imap[1448]: sql plugin Parse the username sales@xxxxxxxx

Mar 26 19:47:17 xxx imap[1448]: sql plugin try and connect to a host

Mar 26 19:47:17 xxx imap[1448]: sql plugin trying to open db '/var/db/sqlite/mailsys' on host '' 

‘k, think I got it … tracing “Could not open db” to where it is in the code, turns out it is generated by cyrus-sasl -> sasldb -> db_ndbm.c … but, we don’t *use* sasldb, so why is that error being generated?

Looking on my ‘working system’, there is a /usr/local/etc/sasldb2.db file there, which is why that error isn’t being  generated … so, I just created a ‘dummy’ sasldb2.db file on both of my non-workign systems, and suddenly, it looks like everything is authenticating properly …

Still have to do more testing but … is there some way to *disable* it checking for that file?  I created and then disabled an account in it, so that its got the right structure, so its not too painful of a solution, just not sure why it came up in the first place … when I upgraded the code, the version of cyrus-sasl didn’t change (2.1.16 in both the pre and post upgrade systems, just confirmed), but cyrus-imap went from 2.3 -> 2.4 … so a stricter requirement in 2.4 that I hadn’t seen before … ?

----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus