Summary: | courier-authlib spits the message "Mysql has gone away!" with mysql-5* | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | manolis <manolis> |
Component: | [OLD] Server | Assignee: | Luca Longinotti (RETIRED) <chtekk> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | ian, iggy, jakub, mysql-bugs, net-mail+disabled, swtaylor |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
manolis
2005-12-26 02:30:40 UTC
To start a single threaded MySQL add "one-thread" to your my.cnf But this can only be a "test", sure not a production server (IMHO). If the error is still reproducible mind to re-emerge with "debug" use flag and to follow the upstream instruction on debugging the server. http://dev.mysql.com/doc/refman/5.0/en/debugging-server.html I found a workaround to this issue... If I change in /etc/courier/authlib/authdaemonrc the line: daemons=5 to : daemons=1 the problem dissappears... Ofcourse I have too few vpop users, so I cannot tell if that affects the login when there are thousands of users. after 15 days with my workaround... it works fine... Does the workaround counts as a fix? I have to mark the bug as resolved? Or no? (In reply to comment #3) > after 15 days with my workaround... it works fine... > Does the workaround counts as a fix? > I have to mark the bug as resolved? Or no? > This "solution" works just fine for me on a x86 machine, but on my amd64 server this does not change anything concerning this error message. I still get the error that MySQL has gone away. I need to restart courier-authlib in order to get logins to work again. Either way, I can start more authdaemon-instances or less, just the same: [authdaemond] vmysql: sql error[3]: MySQL server has gone away I use MySQL 5.0.19-r1 though, don't know if the problem is related to that. On the machine I use nptl, but no threads and no ithreads (use-flags). Starting mysql with one-thread doesn't work here, mysql refuses to start. Strange here (amd64) works fine.. mysql starts multithreaded... (In reply to comment #4) > (In reply to comment #3) > > after 15 days with my workaround... it works fine... > > Does the workaround counts as a fix? > > I have to mark the bug as resolved? Or no? > > > This "solution" works just fine for me on a x86 machine, but on my amd64 server > this does not change anything concerning this error message. I still get the > error that MySQL has gone away. I need to restart courier-authlib in order to > get logins to work again. Either way, I can start more authdaemon-instances or > less, just the same: > [authdaemond] vmysql: sql error[3]: MySQL server has gone away > I use MySQL 5.0.19-r1 though, don't know if the problem is related to that. On > the machine I use nptl, but no threads and no ithreads (use-flags). Starting > mysql with one-thread doesn't work here, mysql refuses to start. > .. I use nptl, but no threads and no ithreads (use-flags). Starting
> > mysql with one-thread doesn't work here, mysql refuses to start.
> >
>
I switched to -nptl, same thing! On my AMD64 Server there is no difference using 0, 1 or 5 daemons in authdaemonrc, I need to restart courier-authlib!
Since under those circumstances this can't be considered as a "solution", I might need to consider dropping the use of vpopmail!?...
I can confirm that daemons=1 didn't help me. It does seem to beat the issue if I leave my mail client running, which checks for mail every minute. dev-db/mysql-5.0.21 net-mail/vpopmail-5.4.16 net-libs/courier-authlib-0.58 Any news on this issue ? I have the same problem, I've just changed the daemons=1 to see if it solves the problem. net-mail/vpopmail-5.4.17 net-libs/courier-authlib-0.58 dev-db/mysql-5.0.26 daemons=1 didn't help me. Is this fixed with courier-authlib-0.59.1? Please test with net-libs/courier-authlib-0.59.2, this issue happens randomly with various MySQL using packages... I've had it myself with amavisd-new and others at times, then it just disappears or is fixed by increasing the mysql connection timeout, never was able to pinpoint where the problem really was... :( courier-authlib always worked for me though, can't reproduce this. Best regards, CHTEKK. |