Skip to main content
Question

Upgrade to version 9.01 Hangs on JSS Startup

  • September 5, 2013
  • 10 replies
  • 66 views

Forum|alt.badge.img+2

I attempted to upgrade to Casper 9.01 and it has been stuck on JSS Startup - Cleansing data for upgrade (66% Complete). I have tried to reboot a couple times and it keeps coming back to this.

Anyone else have this issue?

Peter

10 replies

Forum|alt.badge.img+15
  • Contributor
  • September 5, 2013

Stop Tomcat, and restart MySQL. After MySQL is running again, open terminal and repair the database

mysqlcheck -repair jamfsoftware -u root -p


Forum|alt.badge.img+17
  • Employee
  • September 5, 2013

Hello ppickering!

The upgrade process moving to 9.x from the 8 series changes the database schema, and introduces some optimizations as well. From an upgrade standpoint, this means that the upgrade process is taking longer than what we've seen in previous upgrades. This can depend on the size of the organization, etc.

During the upgrade process, please do not restart Tomcat or the upgrade process. If the upgrade seems to have hung, please reach out and contact Support to work through some steps to ensure the process has hung before restarting the upgrade process.

Thanks!


Forum|alt.badge.img+18
  • Valued Contributor
  • November 25, 2013

I have this happening on a JSS that went through the entire upgrade process yesterday going from 8.73 to 9.22. Did the upgrade yesterday and it seemed totally smooth. Ran fine for the start of the day and then it became unresponsive at some point so it was restarted. Then it ran great for the rest of the day. About 30 minutes ago it became unresponsive again so it was restarted. Upon this restart if you go to the web app it is just stuck at JSS Startup and "Checking for tables to rename..." I've let it sit there for a while just to see if it does anything. But the progress bar really hasn't moved. I have a backup of my 8.73 database that I made before the upgrade and a backup of my 9.22 database that ran automatically last night. I have an email and call into support.


Forum|alt.badge.img+18
  • Valued Contributor
  • November 26, 2013

Jamf Support called me back and got me up and running. Using the mysqlcheck did the trick. My 9.21 JSS is back and running. Hopefully it will stay that way ! Big thanks to Jamf for the quick call back.


Forum|alt.badge.img+11
  • Contributor
  • January 7, 2014

Getting repeated syntax errors trying to run mysqlcheck on MySQL 5.5 (ex: ERROR 1064 (42000): You have an error in your SQL syntax...)

Stupid question, but am I including the root password at the end of the following command? The MySQL reference page are suggesting different flags/options (http://dev.mysql.com/doc/refman/5.5/en/mysqlcheck.html). Here's what I'm entering (though tried a variety of different variants).

mysqlcheck -repair jamfsoftware -u root -p;

Forum|alt.badge.img+18
  • Valued Contributor
  • January 7, 2014

I ran it like this. You an use the root user or even the jamfsoftware user. It will ask for the password.

mysqlcheck -u root -p --repair jamfsoftware

mysqlcheck -u jamfsoftware -p --repair jamfsoftware


Forum|alt.badge.img+11
  • Contributor
  • January 7, 2014

Sadly, same commands fail on my end @rcorbin. Same syntax errors.

Are you running this in the MySQL command line? Are you on v5.5?


Forum|alt.badge.img+11
  • Contributor
  • January 7, 2014

OK, that was it. Don't run this in the MySQL console, run in standard Command Prompt.

Doh.


Forum|alt.badge.img+12
  • Valued Contributor
  • February 14, 2014

I'm running a v9.24 test environment on a Mini (OS 10.9.1 Server) and am attempting to repair the database after a failed import of our 8.73 production database backup.

I continuously get the following error using either "root" or "jamfsoftware" as the user.

sh-3.2# /usr/local/mysql-5.6.16-osx10.7-x86_64/bin/mysqlcheck -u jamfsoftware -p --repair jamfsoftware
Enter password: /usr/local/mysql-5.6.16-osx10.7-x86_64/bin/mysqlcheck: Got error: 1045: Access denied for user 'jamfsoftware'@'localhost' (using password: YES) when trying to connect
sh-3.2#

There must be some syntax I am missing that is causing it to use "YES" as the password even though I am entering the correct root password.

Any help would be greatly appreciated.


Forum|alt.badge.img+15
  • Contributor
  • February 14, 2014

make sure you grant all permission on the jamf database

GRANT ALL ON jamfsoftware.* TO 'jamfsoftware'@localhost IDENTIFIED BY 'jamfsw03';