-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Database connection not re-astablished #3023
Comments
So everything is working now it has been restarted and there was only a failure whilst the change was applied and the connection was broken? |
@willpower232 yes, after pod restart everything was working fine. |
@adamcooke Any chance to implement a re-connection. Had the same problem again. All smtp & worker pods have to be restarted to get it working. I'm no ruby developer. But perhaps i should give it a try. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
+1 - this issue also happens to me postal logs:
mariadb logs:
|
We use postal on kubernetes with a managed database from OVH. After OVH applied a security update on the database servers, the smtp server wasn't working anymore.
On smtp client we received:
can't modify frozen String: "end of file reached"
Here is a log from one smtp session:
Here is the evidence for the database change:
The other pods for web & worker pods have restarted after the database change. So there was no problem.
Expected behaviour
Database connection should be restored.
Environment details
The text was updated successfully, but these errors were encountered: