Posted on 09-08-2013 12:34 AM
We recently decided to upgrade our test environment to Casper 9. It did not go well. As it turns out, if your JSS is operating in clustered mode then you have to upgrade the cluster master first.
Where this was throwing us off is that we periodically copy a dump of the live production database off to our test database and import that. There is a line in our automated script that should disable clustering mode on that database before we restart the tomcat process.
To quote Nicky (who we got this from):
Totally. Just run this command in mysql and restart tomcat: update jss_cluster_settings set clustered = 0;
Turns out our implementation of this command wasn't working!
Enough of our test environment issues. What have I learned? In a multiple JSS environment, upgrade the cluster master first then the others!
Solved! Go to Solution.
Posted on 09-08-2013 07:09 PM
Thanks Richard.
For v8.6x (probably the 8.xx) you can use the command given below;
if you are logged in as the root DB user
# Use your JSS database
mysql> USE 'jamfsoftware';
# Disable clustering
mysql> UPDATE jss_settings SET clustered = 0;
You might need to change the database name from jamfsoftware to your database name.
Posted on 09-08-2013 07:09 PM
Thanks Richard.
For v8.6x (probably the 8.xx) you can use the command given below;
if you are logged in as the root DB user
# Use your JSS database
mysql> USE 'jamfsoftware';
# Disable clustering
mysql> UPDATE jss_settings SET clustered = 0;
You might need to change the database name from jamfsoftware to your database name.
Posted on 09-09-2013 09:15 AM
You're very welcome!