JSS 9.100.0 Upgrade Problems

@MrP Before calling Jamf out, have you tried forcing the page to refresh? Most of the time, these are just page caching issues. It's a little annoying, but not sure I'd call it a glaring issue.

Yes, clearing my cache resolved the issue. If they had tested and seen that this was going to be a problem, they could have programmatically adjusted their cache expiration parameters, or at least notified us in the update download page that we should expect to clear our caches. None of the log sorting worked properly during this time and I was in the middle of a major issue on my end. Taking my time away from pressing issues to resolve something they should have been on top of is not acceptable to me. Period.

https://www.merriam-webster.com/dictionary/glaring

Jamf, please do not hire any additional program mangers, please continue your hiring as you see fit.

There is a reason Jamf is the industry leader and while this might meet the dictionary definition "glaring" I don't care about superficial issues like this, and I am almost 100% sure that most Jamf customers agree. I would also go as far as most Jamf customers would prioritize issues like this as the very last thing on the list of issue to get fix.

IMO

C

PS This is also not the correct place to post issues like this, the JSS has had this behavior after most updates. You are asking for a Feature Request to change a known behavior.

Its a web site. You are creating a new web site at the same address. Your browser might be cached with the old site settings. You could be upgrading from any version to this version and hit different issues for the same reason. Clearing the cache or trying a different browser would be standard troubleshooting steps for most technicians.

Upgrade to 9.100.0 working fine 24 hours later. All clustered servers upgraded successfully and were immediately aware.

We are trying to upgrade but receiving this error:

Updating init.d script...
Copying backup of Tomcat (/usr/local/jss/tomcat) to /usr/local/jss/backups/tomcat/2017-08-08_10-36-56...
Upgrading Tomcat...
Copying Tomcat files...
Setting permissions...
Restoring /usr/local/jss/tomcat/tomcat/conf/*.xml...
[Fatal Error] server.xml:74:2: XML document structures must start and end within the same entity.
Detected previously installed Tomcat version: 8
Skipping PermGen check because Java 8 was found...
Restoring /usr/local/jss/tomcat/tomcat/bin/setenv.sh to /usr/local/jss/tomcat/bin/setenv.sh...
Applying server.xslt to server.xml...
Error: Could not apply server.xslt transforms to server.xml

Any ideas?

the product issue for Linux upgraded JDS not working is PI-004248. If you are on Linux and upgrade the JSS to 9.100 the recommendation is to not upgrade the JDS

@vp18 I saw "Error: Could not apply server.xslt transforms to server.xml"
when I had a broken server.xml

The jssinstaller.run needs a correct /usr/local/jss/tomcat/, because it makes a backup and after upgrading wants to restore the settings from the backuped server.xml

So check your /usr/local/jss/tomcat/tomcat/conf/*.xml
if they are brocken manually restore a good backup from /usr/local/jss/backups/tomcat/2017-xxxxxxx/tomcat/conf
and check permissions.

That helped me getting jssinstaller.run to work again.
Best
Michael

PS: Check your disk usage - running out of disk during upgrade broke my system once...

Jamf decided to just completely remove JDS from the Assets page without any statement. I'm not happy with how they take care of this issue and how they communicate.

Read more here: JDS Installer 9.101.0 Not Available for Download