Verify and troubleshoot your Hipchat Data Center deployment

Before you allow users in to your Hipchat Data Center deployment, you should do a verification pass to make sure that everything is configured and working appropriately. This page contains a checklist that we hope will help you verify the deployment, and catch any errors before you open the deployment to users.

On this page:

Verification checklist

Test your deployment to make sure that all of the functionality is working as intended. You should confirm that:

☐ users can log in using your organization's auth source

☐ users can view (and if enabled, edit) their profile information

☐ users can send and receive messages in chat rooms

☐ emoticons are working in chat messages

☐ any integrations that are enabled are working

☐ users can upload and view files

☐ users can search for messages in their chat history

☐ if enabled, users can send and receive 1-to-1 chats

☐ if enabled, video chat is working

Troubleshooting and logs

Log files are available in the /var/log/ directory of each node.  The Hipchat service logs can be found inside /var/log/hipchat/.

Once per day, the log files from each node are copied to the /file_store/shared/logs subdirectory of your network-attached storage volume. They follow a /YYYYMMDD/machineid/log-files naming convention.

Configuration management is managed by chef-solo. It is run at boot, upgrade, and during service restarts. You can find the chef-solo log file in at /var/log/chef.log

To retrieve all your logs, run  hipchat log -r  on each node. This copies the logs to the  /file_store/shared/logs folder, which you can then compress and include with your support request. 

tip/resting Created with Sketch.

If you need to open a Support request, make sure you download and attach your logs if possible. This helps us speed up the troubleshooting process.

Last modified on Nov 30, 2017

Was this helpful?

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