Stash Support Plugin -> 3.5 Caused 500 Error?

Jen Connor August 6, 2014

The most recent plugin upgrade of Stash Support Plugin caused all repositories to have a 500 error on the browse screen. I've tested this in two environments. Stash had to be stopped and restarted which disrupted business.

3 answers

0 votes
ThiagoBomfim
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 9, 2014

It appears that the problem occurred due to the database being unavailable for a period of time and not to a specific plugin. The cause is described in more details on https://confluence.atlassian.com/display/STASHKB/Random+500+errors+when+running+Stash+-+Database+connection+timeouts

0 votes
Jen Connor August 6, 2014

Thanks Tim. I believe you are correct - I opened a ticket to support to check the error.

0 votes
TimP
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 6, 2014

Hi Jen,

That error likely indicates that the plugin failed to startup again after being upgraded. If the problem is persisting after restarting, I'd recommend contacting support at https://support.atlassian.com, as we'll need version numbers and possibly logs to diagnose what's going wrong.

cheers,

Tim

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events