Bug #22158 | Errors in init_connect terminate connections silently | ||
---|---|---|---|
Submitted: | 9 Sep 2006 8:37 | Modified: | 24 Jan 2007 0:26 |
Reporter: | Hartmut Holzgraefe | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: General | Severity: | S3 (Non-critical) |
Version: | 5.0bk | OS: | Linux (linux) |
Assigned to: | Ramil Kalimullin | CPU Architecture: | Any |
[9 Sep 2006 8:37]
Hartmut Holzgraefe
[24 Oct 2006 8:39]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/14228 ChangeSet@1.2323, 2006-10-24 13:39:03+05:00, ramil@mysql.com +1 -0 Fix for bug #22158: Errors in init_connect terminate connections silently We set thd->net.vio= 0 to forbid sending result of the init_connect execution to client. As a side effect we don't log possible errors.
[26 Oct 2006 11:22]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/14418 ChangeSet@1.2323, 2006-10-26 14:51:34+05:00, ramil@mysql.com +1 -0 Fix for bug #22158: Errors in init_connect terminate connections silently When executing the init_connect statement, thd->net.vio is set to 0, to forbid sending any results to the client. As a side effect we don't log possible errors, either. Now we write warnings to the error log if an init_connect query fails.
[24 Jan 2007 0:26]
Paul DuBois
Noted in 5.0.30, 5.1.13 changelogs. If an init_connect SQL statement produced an error, the connection was silently terminated with no error message. Now the server writes a warning to the error log.