the Hercules 3.09 that comes with Confluence 4.12 is dying in an infinite loop

I just performed an upgrade from confluence 3.4.2 to 4.12,

The confluence is linux based, has enough RAM, enough space on the harddisk, all permissions in the directory are set for the user /group confluence:confluence, it runs behind a webproxy and the internet connection (that works fine, I tested it with the 'find new plugins' function) works vi a proxy on port 8000 Because it is an test system, the mailfunction is disabled

I saw some entries in the atlassian.log file and started the logscanner. But the progress button does not show any progress. I restarted the confluence but with no effect to the logscanner. Then I started the logscanner again, went home and next morning the progress bar shows 'no progress' again.

The atlassian.log says nothing, the catalina.out say s /500page.jsp not found but I am unsure if this is an logscanners output. I don't think so. There is a second message in catalina.out: Too many open files - I am still examine this.

I searched atlassian answers and the net, but did not find an answer. Has someone an idea what is wrong with logscanner?

regards from Hamburg, Kai

2 answers

1 accepted

0 votes
Accepted answer

My Installation works with a proxy and my problems are covered by this issue:

https://confluence.atlassian.com/display/JIRAKB/Hercules+Log+Scanner+Unable+to+Proceed+Past+Zero

The answer is: Currently this plugin does not support proxy configurations, and has a bug raised for this under STP-170 and https://studio.plugins.atlassian.com/browse/STP-190

Hi there,

My first thought when I read your description is that there is a proxy or firewall that is blocking Hercules from calling home, so please ensure that the application can access the following two URLS:

https://confluence.atlassian.com/*
https://jira.atlassian.com/*

Regarding your issue with the too many open files, I believe you will find this document useful in resolving that issue: https://confluence.atlassian.com/display/JIRAKB/Loss+of+Functionality+due+to+Too+Many+Open+Files+Error

All the best,
John

Hi John,

on CentOs a 'ulimit -a' shows me the status (allowd 1024 files) , and an additional entry in /etc/security/limits.conf solved my 'too many open files' problem.:

-> confluence soft nofile 4096 and confluence hard nofile 8192

Thank you for the hint!

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

930 views 13 11
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you