Before I raise a support ticket, would like to roughly know what does the following log message means:
Caused by: com.atlassian.stash.internal.home.HomeLockDeniedException: The Stash home directory 'C:\Stash\StashHome' is already locked by another running instance of Stash.
Please stop the other instance of Stash and restart this instance.
If you are absolutely certain that no other instance of Stash is running, please remove the lock file 'C:\Stash\StashHome\.lock' and restart this instance.
The error message pretty much says it all.
So we create that lock file when Stash starts, and remove it again when it shutsdown (cleanly). Either there is actually another Stash running, or previously Stash wasn't shutdown properly (ie kill -9).
If you know for a fact that Stash isn't running you're almost certianly safe to delete the file and start Stash again. I would also generally recommend taking a full backup of the home directory and database just in case. If you have any concerns, or in any case, please feel free to raise a support ticket with your logs attached.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot