Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

atlassian-confluence.log throws hipchat error

Mark Plimley December 20, 2017

I have Jira 7.1.4 and Service Desk 3.8.2 installed and running. I completed the installation of Confluence 6.6.0. I did not knowingly install hipchat. The atlassian-confluence.log is reporting the following errors on startup:

2017-12-20 13:21:03,948 ERROR [localhost-startStop-6] [hipchat.spacetoroom.service.SpaceToRoomNotificationService] hipChatNotifications Failed to obtain hipchat notifications for event com.atlassian.plugin.event.events.PluginFrameworkShutdownEvent@cb90691: service proxy has been destroyed
2017-12-20 13:21:03,964 WARN [localhost-startStop-6] [confluence.util.profiling.DurationThresholdWarningTimingHelperFactory] logMessage Execution time for publishing event com.atlassian.plugin.event.events.PluginFrameworkShutdownEvent@cb90691 took 17879 ms (warning threshold is 5000 ms)
2017-12-20 13:21:04,058 ERROR [localhost-startStop-6] [atlassian.confluence.setup.ConfluenceListableBeanFactory] destroyBean Destroy method on bean with name 'contentPropertyService' threw an exception
com.atlassian.util.concurrent.LazyReference$InitializationException: java.lang.IllegalStateException: Unable to create a tracker when osgi is not running

I am not able to connect a browser to port 8090 where confluence is listening.

I am not interested in using hipchat, at least not yet. 

Does anyone have any suggestions to resolve these issues?

Regards,

Mark Plimley

1 answer

0 votes
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 20, 2017

Hi Mark,

I understand you were able to install Confluence but after a restart, it is unreachable.

I think the Hipchat errors are a red herring. They seem to be just saying the plugin cannot be started which is usually the result of another, earlier error.

Please check the logs for any errors after the line "Starting Confluence 6.6.0".

In addition to the atlassian-confluence.log there are logs in <confluence_install_dir>/logs. If the instance is unreachable on port 8090 the install directory logs may be of help.

What happens when you direct your browser to the base URL of Confluence? Is there an error message?

If Confluence is running on Windows, is the service started?

If you are running Confluence on Linux, is the process being stopped?

Thanks,

Ann

Mark Plimley December 20, 2017

Ann,

Thanks for replying. I'm running on Windows & the service is running and not stopping.

I had tried to connect from a different computer, and maybe that was the real problem. I had just installed Apache and configured it as a reverse proxy to Jira Service Desk and Confluence. When I access from a browser on the server, I do get a Confluence login prompt and can login now. I updated the base URLs.

So I guess I can ignore the ERROR messages in the logs. The web app I am familiar with usually requires us to resolve ERROR messages. Is there a way to fix the configuration to eliminate the ERROR messages?

Regards,

Mark

AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 28, 2017

l agree that we should either eliminate the ERRORs or verify that they are benign. Now that everything is all set as far as accessing the instance, please restart the service and check whether the errors are logged again. Check the <confluece_home>atlassian.confluence.log between the entry "Starting Confluence' and the line "Confluence  is ready to serve.

Please post any error messages you find.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events