After several weeks of the JSS running without any trouble I can no longer connect to the JSS. I've tried restarting the server/tomcat to no avail, and verified both are running. When running a port scan 8443 is not open. I'm running 8.43 on 10.7.3 Lion on an Xserve. Anyone have any ideas what could cause this or how to restore it? I cannot access the web interface, casper admin, remote, imaging or recon.
Answer
unable to access JSS
+5Best answer by mbales
Found the issue after speaking with JAMF support. The issue seems to be that we had two versions of Tomcat, the one built into the JSS and a vanilla install we had done. It looks like the two versions were causing conflicts and the one built in to the JSS was not launching. After removing the vanilla tomcat install everything worked properly. Thanks for your replies and help.
+351st thing I'd try is restarting tomcat from the JSS Utility. https://jamfnation.jamfsoftware.com/article.html?id=117
+5Restarting tomcat via the JSS database utility did not help. Though the first time i ran it i received an error and found the com.jamfsoftware.tomcat.plist was not in proper xml so I replaced it with a working one from an old version of jss (which was being run on a different machine that has since been decommissioned). Can someone post their com.jamfsoftware.tomcat.plist so I can compare?
+3I have had a similar problem. What has worked so far though only a temp solution to get the system back up and running, was to rerun the JSS installer on the server itself. First backup the root.war and root directory from Tomcat within the JSS directory in the root Library. You'll have to remember to stop Tomcat before running the JSS installer.
The path to the ROOT.war file and ROOT directory would be: /Library/JSS/Tomcat/webapps/
To stop Tomcat in terminal: sudo launchctl unload /Library/LaunchDaemons/com.jamfsoftware.tomcat.plist
+5What do I do with the backed up Root directory and ROOT.war files after the install? Thanks for all your help.
+4What you can do is open the JSS database util and restore the database from a backup.. You should have couple backup in here.. Just point to one whn the system was functioning okay and do a restore.. Restoration could a long time base on the amount of data you have in here.. Best think is to run it over night and everything should be running in the morning... Let know if this approach worked for you
+3The backups are there just if something goes wrong with the re-install. So far I haven't had to drop back to them.
+5restoring the database did not resolve the issue, though it did successfully restore a database from a point when it was working.
+5Found the issue after speaking with JAMF support. The issue seems to be that we had two versions of Tomcat, the one built into the JSS and a vanilla install we had done. It looks like the two versions were causing conflicts and the one built in to the JSS was not launching. After removing the vanilla tomcat install everything worked properly. Thanks for your replies and help.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.