We recently upgraded from 9.87 to 9.96 JSS on Sunday night and since we upgraded our JSS. Our MySQL service terminated or in stopped state 3 times. I have the service to start automatically so after the server restarts or I manually restart the service, it is up and running. But without any indication, our MySQL service is in stopped state.
We are running our JSS and MySQL on Windows Server 2012 R2 server.
Where and what should I be looking for to troubleshoot this issue?
We had the same issue. Our agent had us add these lines to /etc/my.cnf file, right beneath [mysqld]:
innodb_file_per_table = OFF
table_definition_cache = 400
table_open_cache = 400
Seems to have fixed it.
wow... same here since upgrade... i was told the latest version of mysql was the error... downgrade to previous version but still dropping once a while...
What to do if /etc/my.cnf does not exist ?
Wondering if this is still an issue for anyone? Or if you found the solution? I've recently had this issue after upgrading from v9.96 to v9.98. 3 hot fixes later and upgraded to MySQL v5.7. Spun up a whole new server and migrated the JSS to that over the past week, but the issue returned last night. Hoping you might be able to confirm this worked for you. Thanks!
Methinks it's the version of MYSQL.
I'm running 9.98 and have had no issues whatsoever.
I didn't see any benefit in upgrading MYSQL.
I'm currently running V5.5 without issue.
Try a downgrade on a DEV box and see what happens??
Sorry. I realize I wasn't clear regarding the prior post. When I upgraded from JSS v9.96 to v9.98, I had not upgraded MYSQL. It was at version 5.6. After several weeks of the MySQL service stopping every 1-2 days, I tried upgrading MySQL to v5.7. I would find that I couldn't restart the service by itself. It would time out. I would have to reboot the server to get it running again. I'm running the JSS on a Windows 2012 R2 server.