Database logging dies when station pc is left on over night

[ShaneDonn]

Hi,

I have a test sequence that logs to a MYSQL database using the TestStand "Database Options" logger.

When the OI (Full Features Labview OI) is left open with the test sequence loaded overnight - the logger fails to record data to the database on the first and consecutive UUTS tested in the morning - a system reboot fixed the issue.

Any debug advice on this issue?

Thanks & Regards,

Shane.

[pfhenry21]

it seems that there's kind of timeout on the database connection, to avoid that you must keep it alive like a request or something...

[Brandon_B]

Hello Shane,

So is the test running over night, or is the sequence just loaded?  Also, are you closing connection to the database, because it sounds to me like it is a timeout issue.

Regards,

[ShaneDonn]

Hi,

Test are not running overnight only the sequence is left loaded.

I am not closing the connection to the database - I let TestStand take care of all the database connection/logging..

Is there a setting I need to set in TestStand to force it to open the connection if necessary or something I need to change in the config of the MYSL database/server?

Thanks,

Shane.

[Brandon_B]

Hello Shane,

There isn't a way to change the timeout via TestStand, but there might be a way to change it in your database.  It probably isn't the best practice to try and leave the connection open the whole time though, because there are more factors than just a timeout that can cause it to be closed.

Regards,