On Mon, Feb 20, 2006 at 10:04:50AM -0600, james cooke wrote:
On Sun, Feb 19, 2006 at 08:33:37PM -0600, james cooke wrote:
> After running for awhile(it seem to vary) I'm getting this
> Feb 20 03:05:47 akm authdaemond: vmysql: sql error: MySQL
> has gone away
> If I restart authlib I'm able to connect again for awhile,
> thing occurs.
> This is only with imap connections, pop3 works fine(using
> Any guidance would be extremely helpful.
> This is on FreeBSD 5.4
"vmysql"? Is this some modified authentication module, or is that
part of vpopmail/vchkpw I guess, it has no problems with pop3 though,
only imap after however long.
I think you already said you were using a different pop3 daemon, not
courier's (which would use the same authdaemond pool).
I suppose the problem could be with
vpopmail or whatever? but I would assume I'd get the same issue with
pop3d if that were the case, since I believe they both authenticate
the same way. I'm a bit out of my element here though so I could(and
probably will) be completely off course.
" I get intermittent authentication problems with vpopmail
This is a known problem with vpopmail 5.2.1 and earlier. You need to
upgrade to 5.2.2 or later, and then recompile courier-authlib."
courier's authdaemond uses vpopmail in an efficient way, holding open the
connection and re-using it many times. Unfortunately, this tends to show up
bugs in vpopmail. Your pop3 client is probably fork()ing and exec()ing a new
vpopmail client for each authentication request, which means it makes a
fresh mysql connection every time.
However, the 'intermittent problem' referred to there is different (a
username buffer was not being initialised properly, rather than a mysql
connection not reconnecting), so this may well be a different bug.
1. Remove vpopmail and install the very latest version
2. Recompile courier-authlib *after* reinstalling vpopmail
3. If the bug is still there, take this to the vpopmail mailing list.