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/start-stash.sh To run Stash in the foreground, start the server with start-stash.sh -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 setenv.sh ------------------------------------------------------------------------------- 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/catalina.pid Existing PID file found during start. Removing/clearing stale PID file. Tomcat started. Success! You can now use Stash at the following address: http://localhost:7990/ 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: https://confluence.atlassian.com/display/STASHKB/Troubleshooting+Installation root@stash:~#
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.
Thanks.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I put it in the /conf, not in home ... where in home does it belong exactly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
<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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You might need to change user and group as "atlstash
"
Switch to atlastah and then start Stash. Let me know if this fix.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.