During installation of Confluence 7.2, the server hangs during the setup of the database schema and ends up with a stuck thread. Once the stuck thread recovers and I refresh the page, the batch.css file fails with a 500 error. If I go to the path of the batch.css file, the page says that the container was not started. There are two batch.css files that this happens on: one for the generic style and the other for the setup style.
The server I am running on has 4gb of ram and 3 cpu cores. I've attached the log for Confluence and the stacktrace on the batch.css file.
So it turns out that the problem was not with the amount of RAM or timeouts occurring during the setup. I was accessing the Confluence from behind Cloudflare which automatically caches pages, including the generated `batch.css` and `batch.js` files. By adding a page rule to bypass caching for the application, it fixed everything.
Thanks for trying to help with debugging @brbojorque
Hi, Confluence collaborators! As part of #Confluence-Collaboratory month, we’ve created a very special Mythsbusters segment, where we're dive into an interesting myth and uncover the truth behind i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events