Unreliable scheduled backups in conjunction with MySQL 5.6 and JSS version 9.5 and higher

bluebox
New Contributor III

Hi All,

Since version 9.5 of JSS we see randomly failing scheduled backups JSSDB should execute. There is another thread that points to a newer version of Tomcat introduced with JSS 9.5 and/or version 5.6 of MySQL that are likely to be the cause for the problem. Currently we see the problem also with the latest JSS version (v9.72). So far the suggestions were to downgrade to MySQL v5.5 or write a launchd to stop Tomcat before the scheduled backup starts. Neither suggested solution is something we consider currently. Anyone who came across this problem and if so, did you find a more elegant solution?

Alex

7 REPLIES 7

GabeShack
Valued Contributor III

I would suggest working with your support specialist as this took months for us to get working properly after I installed the newer sql. We eventually had to roll back to 5.5 to get it all to work again.

We found the only way to get backups to complete was to stop the tomcat service altogether, then perform a manual backup then you can start tomcat again and it should work.

Gabe Shackney
Princeton Public Schools

Gabe Shackney
Princeton Public Schools

bluebox
New Contributor III

Hi Gabe,

Thanks for your reply! What a wonderful outlook. *irony off

The fun thing here is that we use SQL Server v5.6 since we got the Casper Suite in 2013. It worked fine just until this year....

Alex

tron_jones
Release Candidate Programs Tester

We ran into the problem as well a while back when we upgraded to mySQL v5.6.xx. There was a certain table in the database that was causing the backups to fail for scheduled only. After working with support they were able to run some commands and clean up the database, which fixed the problem for us.

GabeShack
Valued Contributor III

I was trying to remember what version of the JSS we used when we started seeing this issue because I think in one update it turned out that the JSS installer uses a newer version of Tomcat that just didn't play nice with the newer version of mySQL.

Gabe Shackney
Princeton Public Schools

Gabe Shackney
Princeton Public Schools

bluebox
New Contributor III

I did some further investigation and it looks like it's related to setups that have OS X as host OS and MySQL in version 5.6 installed. Please see here: http://bugs.mysql.com/bug.php?id=71960 and it's originating thread here on JamFNation: https://jamfnation.jamfsoftware.com/discussion.html?id=6493

The only thing here is that we don't have that heavy load that's mentioned in the other thread here. I'll now contact JamF support about it and if adding the line : table_open_cache = 512 to the my.conf file would be something that's worth trying.

bentoms
Release Candidate Programs Tester

We're running 9.72 with MySQL 5.6 & Java 8 on 10.10.3 OSX Server.

Nightly backups are working fine. JSS utility backs up, & restarts JSS as ordered.

Perhaps strict mode is an issue?

Aziz
Valued Contributor

Same as @bentoms

Nightly backup are fine. JSS 9.72, MySQL 5.6.25 and Java 8 Update 45.

Screenshot of the email I received last night.

34ae3cd22be24daa8633a04b59f8385e