-
Notifications
You must be signed in to change notification settings - Fork 92
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
Can't reconnect until invalid transaction is rolled back #38
Comments
Thanks for submission! We will start looking into it ASAP. We have not seen such behavior in our setup where unfortunately we always use PostgreSQL (native or Amazon RDS). Few requests from our side:
|
@EinsteinGit there should be an SQL exception just about that error you posted. Could you please find it? |
Unfortunately log file was erased on restart. I'll append log file tomorrow. MySQL version 5.1.73 (came with yum for my version of CentOS) The defaults.yml file looks as follows:domain: "localhost:9000" persistence_api: auth_api: logging: hooks: |
Here is the log since yesterday's restart:
|
@EinsteinGit a few things I noticed:
|
Thanks for looking at the logs.
|
@EinsteinGit thanks for the details! Maybe it is indeed MySQL session issue, I'll try to verify that. We're using OpenTAXII mostly with PostgreSQL and there were no issues like that reported. |
According to MySQL docs, the server variable wait_timeout - "the number of seconds the server waits for activity on a noninteractive connection before closing it" - has a default value of 8 hrs which explains why MySQL was not reachable after overnight inactivity. I set its value to a larger interval in /etc/my.cnf , and it is now working fine after a night of inactivity. |
OpenTaxii server responds with ERROR to all requests following some period of inactivity - e.g. overnight. The only fix is to kill and restart the OpenTaxii server.
Using OpenTaxii with MySQL.
The error "Can't reconnect until invalid transaction is rolled back" features in the log files.
The text was updated successfully, but these errors were encountered: