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.

Sign up for GitHub

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

Jump to bottom

Intermittent "broken pipe" issue from mysql. #4713

Closed
reasonerjt opened this issue Apr 18, 2018 · 0 comments · Fixed by #4719
Closed

Intermittent "broken pipe" issue from mysql. #4713

reasonerjt opened this issue Apr 18, 2018 · 0 comments · Fixed by #4719
Assignees
@reasonerjt
Labels
priority/medium

Comments

@reasonerjt
Copy link

reasonerjt commented Apr 18, 2018 •
edited

This is observed on one of test env:
A container that connected to DB intermittently print such error to the log

Apr 18 00:15:18 172.17.0.1 ui[10984]: [mysql] 2018/04/18 07:15:18 packets.go:33: unexpected EOF
Apr 18 00:15:18 172.17.0.1 ui[10984]: [mysql] 2018/04/18 07:15:18 packets.go:130: write tcp 172.17.0.7:34546->172.17.0.5:3306: write: broken pipe
Apr 18 00:15:18 172.17.0.1 ui[10984]: [mysql] 2018/04/18 07:15:18 packets.go:33: unexpected EOF
Apr 18 00:15:18 172.17.0.1 ui[10984]: [mysql] 2018/04/18 07:15:18 packets.go:130: write tcp 172.17.0.7:34528->172.17.0.5:3306: write: broken pipe

On the same env I don't see the error in clair, so this also be related to the impl of MariaDB.
This maybe due to some network issue and can be mitigated by some setting in the DB driver, however this error is not seen on the longevity or any other env yet.

I don't see any loss of data either.

Setting this a low priority and will escalate if this is seen in other env.
@reasonerjt reasonerjt self-assigned this Apr 18, 2018
reasonerjt pushed a commit to reasonerjt/harbor that referenced this issue Apr 18, 2018
Fix intermittent broken pipe issue in log
7fa8261 
This commit fixes goharbor#4713, by adopting the suggested fix in:
go-sql-driver/mysql#529
When creating the DB instance in orm, call `SetConnMaxLifetime()`
@reasonerjt reasonerjt mentioned this issue Apr 18, 2018
Merged
@jowko jowko mentioned this issue Jun 24, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reasonerjt reasonerjt

Labels
priority/medium
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix intermittent broken pipe issue in log reasonerjt/harbor
1 participant
@reasonerjt