Stash does not start the new version after update

I just updated our Stash from 3.6.1 to 3.9.1.

Installation works fine.

But, after stopping 3.6 and starting 3.9, i caanot access 3.9 via Browser or git-command; the startup tells me, everything is alright.

root@stash:~# /opt/atlassian/stash/3.9.1/bin/
To run Stash in the foreground, start the server with -fg
Starting Atlassian Stash as dedicated user atlstash
No directory, logging in with HOME=/
-su: line 0: cd: /root: Permission denied
Stash is being run with a umask that contains potentially unsafe settings.
The following issues were found with the mask "u=rwx,g=rwx,o=rx" (0002):
 - access is allowed to 'others'. It is recommended that 'others' be denied
   all access for security reasons.
 - write access is allowed to 'group'. It is recommend that 'group' be
   denied write access. Read access to a restricted group is recommended
   to allow access to the logs.
The recommended umask for Stash is "u=,g=w,o=rwx" (0027) and can be
configured in
Using STASH_HOME:      /home/stash_home
Using CATALINA_BASE:   /opt/atlassian/stash/3.9.1
Using CATALINA_HOME:   /opt/atlassian/stash/3.9.1
Using CATALINA_TMPDIR: /opt/atlassian/stash/3.9.1/temp
Using JRE_HOME:        /usr/lib/jvm/java-7-oracle
Using CLASSPATH:       /opt/atlassian/stash/3.9.1/bin/stash-bootstrap.jar:/opt/atlassian/stash/3.9.1/bin/bootstrap.jar:/opt/atlassian/stash/3.9.1/bin/tomcat-juli.jar
Using CATALINA_PID:    /opt/atlassian/stash/3.9.1/work/
Existing PID file found during start.
Removing/clearing stale PID file.
Tomcat started.
Success! You can now use Stash at the following address:
If you cannot access Stash at the above location within 3 minutes, or encounter any other issues starting or stopping Atlassian Stash, please see the troubleshooting guide at:

But: I still can start the old 3.6.1 Stash - so we can work on, BUT: I still want to work with the newer version, so please help.


3 answers

1 accepted

0 votes
Accepted answer

I fixed it mysqlf, there was the "server.xml" missing in the "conf" directory.

yes that is moved to the home directory from 3.8 onwards

I put it in the /conf, not in home ... where in home does it belong exactly?

<home>/shared/ is the new location. Atlassian changed so that we need not to update server.xml for future upgrade. Please refer to upgrade guide.

Validate home directory and install directory have same owner and permission. It looks permission issue to me.

Are you installing using root? or do you have separate ID to run Stash?


Starting Atlassian Stash as dedicated user atlstash
No directory, logging in with HOME=/
-su:line 0: cd: /root: Permission denied



Home Directory is correct. First, i started as root (like always, even after previous updates it works like this). Only this time, i got some trouble starting up. Switching user to atlstash does not work either.

You might need to change user and group as "atlstash"

Switch to atlastah and then start Stash. Let me know if this fix.



Hi Anurag,

stopped the 3.6 stash, switchedto user "atlstash" and started 3.9 stash, console as above (i read it as all okay) and i still cannot access git or stash sad

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,924 views 7 10
Read article

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