MonitorWare Knowledge Base

Hi,

Using EventReporter 6.4, I have about 150 servers logging to a mysql database on a linux box. The servers are on different subnets, the table is large, about 9377718 rows.

I'm getting lots of these:
Error while applying an action - skipping this action. Error is 'ODBC Error Code: 'S1T00' ODBC Error Description: '[MySQL][ODBC 3.51 Driver]Can't connect to MySQL server

Has anyone seen this before, and have a solution? Is it a MySQL driver issue? Any ideas?

Thanks in advance,

Dave

Hi,

the database has possible become to large.
I did some research and error code "S1T00" together with Mysql means "Timeout expired". So the database maybe needs to long now to answer to insert requests. A number rows confirms this, 9377718 rows... this database must be approx. 10-20 GB large.

I highly recommend to delete/backup old data. I am sorry but I have no better answer at the moment.

best regards,
Andre Lorbach

Thanks for your prompt response.

The database is 3 GB in size which should not be too big (you state 10-20 GB). Even when it was less than 1 GB I was still getting the error messages.

Any other help would be great!

Thanks,

Dave

Dave,

just to do a check: would it be possible that you insert a test record e.g. with phpMyAdmin - and take the time? I would just like to see how long it takes to insert the record and thus hopefully get a clue why the connection times out.

Rainer

I should also add that other servers are logging errors (not odbc connect errors) at the exact same time, so the db is up and accepting connections.

Thanks,

Dave

Dave,

this brings us further. Would it be possible that you enable debug logging (in general settings) and send us the debug log to support@adiscon.com. Please be sure that at least one error occurs during the run. Also make sure to activate maximum debug logging. The debug log can eventually provide further detail.

And - just to check: are you using the exact same settings on the other machines that do not experience any problems?

Rainer

It took less than a second. That actually supprised me, but that's how long it took.

Thanks,

Dave

I'll enable debugging. How big does the log get? I will turn it on on one of the servers that is having the issue, but it doesn't happen every day.

Thanks,

Dave

"And - just to check: are you using the exact same settings on the other machines that do not experience any problems? "

I have a few servers logging this error, but none at exactly the same time. Since the mysql server is accessable when I get the error (evident since other servers are logging to the db) and inserting rows is fast might it be an issue with the connect wait time or some other issue with the eventlogger program? I am going to be enabling the debug log on a system later this week/early next week. After sending the log how long should I expect to wait until hearing some sort of answer? My company has paid for support so perhaps there is another way I should be dealing with this issue?

Thanks,

Dave

Dave,

if you have purchased UpgradeInsurance, you should mail the debug log to support@adiscon.com AND indicate your UpgradeInsurance ID. That will definitely give your request priority.

The exact turn-around time depends on what we see in the log. Typically, we can provide a suggestion within a day or so, but sometimes it is hard to find anything in the log. In such cases, it might be necessary to provide an instrumented build. Anyhow, maximum debug log is quite verbose, so we are positive we can extract some useful information from it.

Rainer

For all others who might run into this Problem.

It seems to be caused by a MySQL ODBCClient bug that has been fixed in the latest release.

The bug description can be found here:
http://bugs.mysql.com/bug.php?id=7802

The solution is: Update the MySQL ODBC Driver from 3.51.x to 3.51.11

The latest MySQL ODBC Driver Version can be found here:
http://dev.mysql.com/downloads/connector/odbc/3.51.html

best regards,
Andre Lorbach