Casper 8.51 upgrade... JSS web app still showing old version?

[daworley]

Hey all, curious if I'm doing something wrong.

I was running JSS 8.43 and then ran the package installer that I downloaded today to bring everything up to 8.51. The package ran and said it ran fine.

I quit Safari, then restarted tomcat, restarted Safari... dealt with the new self-signed certificate squawk in Safari... but the info at the top of the Safari page (the name of the site) still says 8.43. Verified on a different computer that Safari does not seem to know that the JSS should be version 8.51.

Rebooted, same same. Am I missing something?

My JSS is a 10.6.8 Server running on a Core2Duo Mac Mini.

[tsd25108]

When you go to settings then click About JSS under the search topics does it say 8.51?

[daworley]

Yes, indeed it does.
::scratches head::

I re-ran the installer again in case of some odd error that didn't show up, but same behavior still.

Console logs (jamf, installer, system) aren't very helpful.

[rockpapergoat]

there's an xml file in the tomcat web app directory that they probably forgot to update. just change it. it's cosmetic.

[mm2270]

Almost sounds like the web app isn't reporting its version number properly to the browser. Have you logged into your JSS with something other than Safari, like Firefox, to rule out a browser specific issue?
From what you've written, it sounds like the upgrade went fine.

It will be a while before we upgrade to 8.51 so I can't verify anything on my end.

[rockpapergoat]

see this: https://jamfnation.jamfsoftware.com/discussion.html?id=3094

also, jamf needs to fix it.

[rockpapergoat]

just re-downloaded the mac installer, and the version's correct under /Library/Tomcat/webapps/ROOT/WEB-INF/xml/version.xml, so maybe it's cached. try another browser or lynx/curl or something.

[k12techman]

I have the same "cosmetic" problem. Except that when I try to use the new 8.51 tools like CasperAdmin, I get a "mismatch in version" error. My JSS says it is at 8.4 still and I don't even see the newest features that were supposed to come with this revision.

[daworley]

@k12techman:
Bingo. Same here.

[taugust04 · Accepted solution]

I had the same issue upgrading from 8.43. With some assistance from JAMF support, I did the following:

- backup the jss database
- stop the tomcat service:
sudo launchctl unload /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
- move the following files and folders out of the jss webapps folder (I placed them on the Desktop):
/Library/JSS/Tomcat/webapps/ROOT
/Library/JSS/Tomcat/webapps/ROOT.war

I also added the following step before installing:
- delete any package receipts and boms in /private/var/db/receipts that begin with com.jamfsoftware.*

I then installed the update, rebooted the server, and everything was displaying the proper version, and no I longer received any of the mismatch errors. After checking to see that everything was working fine I deleted the ROOT folder and ROOT.war file that I had moved onto the Desktop.

Hopefully this helps.

-Ted

[jhbush]

This worked for me. JSS on Xserve upgraded since 8.3x

Instructions to get the JSS on
JAMF's instance of Tomcat.
1. Stop the Tomcat service via Terminal with: sudo launchctl unload
/Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
2. From the server's HD, find the /Library/Tomcat folder and make a copy
of it on the Desktop in case we need to recover.
3. In the /Library/Tomcat folder on the server HD, browse to the Webapps
folder, and delete the ROOT folder and the ROOT.war file.
4. Run the JSSInstaller.mpkg that came in the Casper Suite 8.5 DMG. This
will install our version of Tomcat and switch the JSS over to this instead
of the old built-in one, as well as start the Tomcat service back up.
5. Once the install process is complete, log into the JSS web app.
6. Click on the Settings menu, and right underneath that, there is an
About JSS link. In here, click on JSS Summary. Leave all the default
options checked, and Create Summary. In the report, look for the Web
Application Environment section. We should see a line about the Tomcat
version being 7.0.26.
7. We will need to re-create the built-in Tomcat Web Server Certificate.
In the JSS, click on Settings, General Settings, then the Server
Configuration tab. We should see a blue link to Re-create the cert from
the built in CA. Click on this, then Save. We will now need to restart the
Tomcat process from Terminal.
8. This upgrade process likely wiped out the Tomcat memory settings. We
have two options here. We can either edit the
com.jamfsoftware.tomcat.plist file again, or we can use the
JSSDatabaseUtil.jar. In this program, we should see a Utilities menu in
the upper menu bar. Through here, we can stop and start Tomcat and MySQL,
as well as change the settings for Tomcat and MySQL.

[taugust04]

I can confirm that I had to re-adjust my Tomcat memory and certificate settings after using this process to install the JSS upgrade.

-Ted

[k12techman]

I was having problems enrolling 10.7 clients and self service on iOS devices previously enrolled was not functioning correctly. I can confirm that recreating the certificate and then bumping Tomcat fixed my problem.

[jarednichols]

Just upgraded my 8.43 JSS to 8.51 with no issue. Windows 2008 R2

[Macintosh_HD]

I had the same issue when upgrading from 8.43 to 8.52 and I found the following:

-The files ROOT.war and ROOT on the /Library/Tomcat/webapps folder had wrong permissions since Tomcat requires the _appserver permissions to work. For example: drwxr-xr-x 15 root _appserveradm 510 Apr 4 13:59 ROOT
-rw-r--r-- 1 admin wheel 32877144 Jan 19 09:02 ROOT.war

I performed the following steps to fix this issue:
-Backup the JAMF database.
-Stop Tomcat: sudo launchctl unload /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
-Backup the Tomcat Folder: ditto -V /Library/Tomcat/ ~/Desktop/Tomcat
-Changed the permissions on the webapp folder: sudo chown -R _appserver:_appserveradm /Library/Tomcat/webapps
-Install the JSS Installer.mpkg package.

This steps were taken on Mac OS X 10.6.8 Server.