-
Notifications
You must be signed in to change notification settings - Fork 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
ossec-dbd not reconnecting after database failure #447
Comments
@atomicturtle Have you seen anything like this you do a fair amount of DB and OSSEC :) |
Yes, there is an internal_options setting to increase the attempts: dbd.reconnect_attempts=10 The error itself is correct, its attempting a TCP connection (it does not use the socket because of the chroot) over 3306 and mysql is not responding. It could happen if mysqld wasnt running, exceeded max connections, firewall rule was blocking the port, etc |
I Just had the same issue and in my case the data table was corrupt show my data table to be corrupt REPAIR TABLE hope this helps you, or points you in the right direction. |
As far as I can tell I had no data corruption. I wondered why ossec couldn't reconnect to the DB even after it was back up. I always had to restart ossec manually to get it reconnected. |
It probably exceeded dbd.reconnect_attempts=10 |
I was babysitting a new server and ran into memory trouble twice. During this I noticed an odd behaviour of ossec-dbd. The mysql server threads where killed at 03:57:53 (out of memory) but in the same second restarted. Ossec looses connectivity for only this query but can't reconnect after this. I have to manually restart ossec in order to reconnect ossec-dbd back to the database.
Can someone else please confirm this behaviour? Do I have to change something on the mysql server side?
The text was updated successfully, but these errors were encountered: