Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When the DB connection is bad, it is not reaped and reconnected, but continues giving errors [moved] #15

Closed
julienschmidt opened this issue Jan 5, 2013 · 0 comments
Milestone

Comments

@julienschmidt
Copy link
Member

This is Issue 15 moved from a Google Code project.
Added by 2012-10-17T14:23:23.000Z by julian.morrison.
Please review that bug for more context and additional comments, but update this bug.
Closed (Duplicate).

Original labels: Type-Defect, Priority-Medium

Original description

<b>Problem summary:</b>
I had a &quot;too many open connections&quot; error on MySQL. The sql.DB connections I had open started giving errors like

    [MySQL] 2012/10/17 15:12:58 packets:102 write tcp 127.0.0.1:3306: broken pipe

They did not reconnect.

<b>Used go-mysql-version (e.g. May 26, 2012):</b>
May 30, 2012

<b>MySQL-Server version (e.g. MySQL-Server 5.5 or MariaDB 5.1):</b>
MySQL-Server 5.5.24

<b>Used Operation System (e.g. Windows 7 64bit, Ubuntu 12.04 64bit):</b>
Ubuntu 12.04 32bit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant