Skip to main content
Question

Installation of JDS 9.61 results in broken JDS

  • November 11, 2014
  • 5 replies
  • 44 views
B
Forum|alt.badge.img+11

Ok, after a few hours of scratching my head, it looks like the installer for JDS 9.61 Linux is somewhat broken, at least on RHEL.
First, the /usr/local/jds/conf/apache_aliases.conf is empty after installation. That seems to be wrong and the contents of that file should look like referenced here:
https://jamfnation.jamfsoftware.com/discussion.html?id=12393
But, restoring that file does not help, Casper Admin still requires password for the webdav and it's still a fail.
Turns out, the installer forgets to reference the conf-file to apache and therefore the webdav shares will never work.
We edited the file /etc/httpd/conf.d/ssl.conf and added:
Include /usr/local/jds/conf/apache_aliases.conf
before the line:
</VirtualHost>
After a restart of apache it all seems to work as expected.
Now, there might be something completley different that is wrong here, but this has fixed it for us.

    5 replies

    I
    Forum|alt.badge.img+7
    • imperatives
    • Contributor
    • November 11, 2014

    Thanks for the post. We are planning on upgrading our JSS(s) and JDS(s) to 9.61 on RHEL 6.5 this week. I'll be sure to add some info if we experience a similar issue.

    R
    Forum|alt.badge.img+7
    • rdwhitt
    • Contributor
    • November 11, 2014

    I upgraded 9.52 to 9.61 and did not experience any issues with existing JDSs running RHEL 6.6, with the exception of the installer wanting 6.4. or 6.5 explicitly (as mentioned in the referenced article). However, I did notice that if I attempted to do a fresh install of the JDS, I saw the same issues with both the apache_aliases.conf and the ssl.conf file.

    J
    Forum|alt.badge.img+13
    • justinrummel
    • Contributor
    • November 11, 2014

    For the past couple of updates I've had to result to a manual install vs. running the Linux Installer by stopping tomcat, removing the existing /usr/local/jss/tomcat/webapps/ROOT folder and ROOT.war file, copying the new ROOT.war file, then restarting tomcat.

    Seems to be a more reliable process than the installer. Just need to watch out for any db updates.

    B
    Forum|alt.badge.img+11
    • bollman
    • Author
    • Contributor
    • November 17, 2014

    Interesting development!
    Today, I got a report that policies were failing and Casper Admin reported no connection with the Distribution Point. Looking into the jdses revealed that once again, the /usr/local/jds/conf/apache_aliases.conf was empty!
    Restoring the file from backup and restarting httpd resumed service but this is somewhat disturbing...

    B
    Forum|alt.badge.img+11
    • bollman
    • Author
    • Contributor
    • December 4, 2014

    9.62 seems to be fixing these issues, although after upgrade to 9.62, I had to go inte the JSS and just "re-save" the JDSes (no changes, just edit and save) to be able to connect to them with casper admin.
    That said, I might have been a little to quick to connect to them with Casper Admin after they re-enrolled.

    Terms & ConditionsCookie settingsAccessibility statement