Directory page in Hipchat Server is inaccessible with error code 503

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

This is for an outdated version of Hipchat Server

 This article applies to a version of Hipchat Server which will be deprecated soon. After that period the version will no longer be supported.

When will my version be deprecated?

The following versions have been deprecated:

  • Hipchat Server 1.3 (EOL Date: Aug 17, 2017)
  • Hipchat Server 2.0 (EOL Date: Jun 17, 2018)
  • Hipchat Server 2.1 (EOL Date: Dec 8, 2018)

The following version will be deprecated soon:

  • Hipchat Server 2.2 (EOL Date: May 30, 2019)

You can read more about Atlassian's End of Life policy here.

You should upgrade to a more recent version of Hipchat Server as soon as you can to take advantage of new features, and security and bug fixes.

Problem

Directory page in Hipchat Server becomes inaccessible and admin will see this error after a server upgrade:

Due to this, admin won't be able to manage directory integrations. However, user authentication is working as per normal.

The following appears in the /var/log/atlassian-crowd.log

2016-06-22 05:16:49,066 localhost-startStop-1 ERROR [crowd.console.listener.StartupListener] License not found
2016-06-22 05:16:49,067 localhost-startStop-1 INFO [crowd.console.listener.StartupListener] License is invalid. Upgrades were not performed.
.....
2016-07-13 09:18:33,515 http-bio-8095-exec-26 ERROR [atlassian.plugin.servlet.ServletModuleContainerServlet] Request processing failed; nested exception is org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Server returned error code = 503 for URI : http://localhost:8095/crowd/services/SecurityServer. Check server logs for details
org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Server returned error code = 503 for URI : http://localhost:8095/crowd/services/SecurityServer. Check server logs for details
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:583)
	at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:620)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
Caused by: org.codehaus.xfire.fault.XFireFault: Server returned error code = 503 for URI : http://localhost:8095/crowd/services/SecurityServer. Check server logs for details
	at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:83)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
	at org.codehaus.xfire.client.Client.invoke(Client.java:336)
	at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
	... 120 more
Caused by: org.codehaus.xfire.XFireRuntimeException: Server returned error code = 503 for URI : http://localhost:8095/crowd/services/SecurityServer. Check server logs for details
	at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:130)
	at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
	at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
	at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
	at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
	... 123 more

Cause

The problem stemmed from a changed in the Crowd license key and it isn't using the default expected one. It could happen due to the following reasons:

  • Cause #1: The Crowd license key in /etc/crowd/crowd.cfg.xml does not match the license key in /hipchat-scm/chef-repo/cookbooks/hipchat_crowd/attributes/default.rb

  • Cause #2: The wrong license key is in /etc/chef/solo.json which overrides the Crowd license key in /etc/crowd/crowd.cfg.xml every time Chef (configuration manager) runs or when the server is rebooted

Resolution

Resolution #1

Double check Crowd license key in the following files and see if they're a match:

  • /hipchat-scm/chef-repo/cookbooks/hipchat_crowd/attributes/default.rb

  • /etc/crowd/crowd.cfg.xml

/hipchat-scm/chef-repo/cookbooks/hipchat_crowd/attributes/default.rb is expected to have the license key starting with "AAABMg0ODAoPeNp9kNF....." while etc/crowd/crowd.cfg.xml has a different (wrong) license key. If you see this, proceed with the following steps to resolve the issue:

Run the following commands from server terminal to re-run Chef (configuration manager) so the correct license key in /hipchat-scm/chef-repo/cookbooks/hipchat_crowd/attributes/default.rb will be applied to etc/crowd/crowd.cfg.xml followed by Crowd service restart:

sudo dont-blame-hipchat
cs
service crowd restart

Resolution #2

Double check /etc/chef/solo.json and make sure there isn't an existing license key there which match the wrong license key in /etc/crowd/crowd.cfg.xml. If there is, use text editor like vi or nano from server terminal to remove the unwanted license section from this file and run the following commands to re-run Chef (configuration manager) so the correct license key in /hipchat-scm/chef-repo/cookbooks/hipchat_crowd/attributes/default.rb will be applied to etc/crowd/crowd.cfg.xml without being overridden by any other license key stored in /etc/chef/solo.json followed by Crowd service restart:

sudo dont-blame-hipchat
cs
service crowd restart

If issue is not resolved with the suggested resolutions above or you need our assistance to verify this, please contact Hipchat Server Support.

 

Last modified on Nov 2, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.