Skip to main content
Solved

Upgrade to 9.11 broke clustering

  • September 24, 2013
  • 4 replies
  • 30 views

easyedc
Forum|alt.badge.img+16

Anyone else lose their clustering config when upgrading to v.9.11?

Best answer by easyedc

got this note from Support.

If we go into the Database.xml on the DMZ server, is it pointed to the right database? We should be able to find it in: /usr/local/jss/tomcat/webapps/ROOT/WEB-INF/xml Sometimes those settings get cleared out during an upgrade. Let us know if this is configured properly (if it is, let's try restarting Tomcat on that server) and we can dig a little deeper if this doesn't fix the issue.

Pointed to the internal server's IP and restarted tomcat. Fixed it.

4 replies

Forum|alt.badge.img+18
  • Valued Contributor
  • September 24, 2013

mine stayed cluster aware.


easyedc
Forum|alt.badge.img+16
  • Author
  • Esteemed Contributor
  • September 24, 2013

I'm still cluster aware, but my DMZ server isn't trying to talk to my Internal. Doing some digging and hopefully JAMF support can find a quick solution if I can't.


Forum|alt.badge.img+7
  • Contributor
  • September 24, 2013

My guys at JAMF recommended that I disable clustering before upgrading... I'm not quite brave enough to try it yet.


easyedc
Forum|alt.badge.img+16
  • Author
  • Esteemed Contributor
  • Answer
  • September 24, 2013

got this note from Support.

If we go into the Database.xml on the DMZ server, is it pointed to the right database? We should be able to find it in: /usr/local/jss/tomcat/webapps/ROOT/WEB-INF/xml Sometimes those settings get cleared out during an upgrade. Let us know if this is configured properly (if it is, let's try restarting Tomcat on that server) and we can dig a little deeper if this doesn't fix the issue.

Pointed to the internal server's IP and restarted tomcat. Fixed it.