Yes, both services/servers (mysql server and ossec server) are on the same system - communication via tcp 127.0.0.1 as we are in testing for the moment. Also logs of mysql server gives no indication on the error. And moreover, the failure of connection is in the same second as the succesful connection, which make me thick of some kind of timeout reached for the prevoius connection and the fisrt try to issue the querry after this timeout end up in error (if the application considered the connection to db already available).
Anyway, for the moment I did not received the error anymore and no relevant changes were made as far as I can imagine... Thanks for the answer, if while testing other features reapers this problem I will let you know. Adi -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of dan (ddp) Sent: Thursday, May 20, 2010 3:46 PM To: [email protected] Subject: Re: [ossec-list] ossec-dbd(5203): ERROR: Error executing query Look at your mysql logs. It looks like the dbd process just lost its connection to the database. Are these processes on the same server? On Thu, May 20, 2010 at 3:49 AM, Adi CHIRU <[email protected]> wrote: > Hi everyone, > > > > I found this error in my logs on server: > > > > 2010/05/20 09:05:02 ossec-dbd(5203): ERROR: Error executing query 'SELECT id > FROM location WHERE name = '(client0) 10.5.5.203->/var/log/secure' AND > server_id = '1' LIMIT 1'. Error: 'MySQL server has gone away'. > > 2010/05/20 09:05:02 ossec-dbd(5209): INFO: Closing connection to database. > > 2010/05/20 09:05:02 ossec-dbd(5210): INFO: Attempting to reconnect to > database. > > 2010/05/20 09:05:02 ossec-dbd: Connected to database 'ossecdb' at > '127.0.0.1'. > > > > After the error, in the same second, the connection closes, another one is > attepted and end up successful. > > Running the query manualy gives a result as expected, without errors... > > > > Do you have any idea why this happen? > > > > Thanks, > > Adi
