Please help, I screwed up my jira 7.2.6 instance and cannot restart it

[Deleted user]

I have a home installation of Jira Software 7.2.6 running on an Ubuntu VM.

As I reworked my network, I changed the servername of my jira server and something apparently happened to the jira instance. I relized it first when it failed to startup on boot after a reboot. I had previously (2016) configured it to.

When local on the server trying "localhost:8080" to reach the installation, I get an error "localhost:8080/JiraLockedError","Jira has no permission to either create or write to subdirectory /plugins/.bundled-plugins of jira.home /var/atlassian..."


Googling around I found this: "https://community.atlassian.com/t5/Jira-questions/JiraLockedError-with-quot-JIRA-Startup-Failed-quot-error/qaq-p/423809"

but following that and having removed the offending dot plugin folders, Jira fails to start. What I cannot figure out is why the permissions suddenly has changed, and what they are supposed to be. I certainly did not fiddle with those. Unfortunately I did not document the installation well enough... There could well be other errors lurking in the shadows. The data I have in the database is valuable to me but not exactly vital, so would be very happy if (come to worst) the database can be saved somehow.

I want to get a Service Desk install instead, but Atlassian won't accept PayPal for non-cloud instances, so I am stuck with this old one.

Please help.

[Timothy · Accepted solution]

If you've cleared up the folder and Jira still fails to start, back up your log folder and clear them out (both catalina.out and atlassian-jira.log). Once you have done that, (re)start Jira again and look into the logs.

[Deleted user]

Thanks! After clearing the logs, they indicated some address was already in use, and the catalina.2018-09-02.log looked ok, so I tried a "localhost:8080" again, and this time it worked! Thing is alive!

Turns out, the problems I was seeing, was all because I had forgot to add the port 8080 when addressing it in my browser. Thinking it was not started (resolution is crappy and keyboard is another story, missing pipe), I tried to start it, thus crashing things and filling my logs.

But, shouldn't the .pid file trigger a warning if trying to start a second instance?

[Deleted user]

Ouch, spoke too soon.

My login won't work. I use a password manager so I know what it should accept. Is there any chance of resetting? I already tried the reset link on loginpage, but I haven't configured a smtp server for jira to use...

[Timothy (Goldfinger Holdings)]

Try the:

* https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html

[Deleted user]

Thank you! I stumbled upon that earlier and has just now completed the password recovery. Not entirely simple since my copy-paste don't work (have to fix all these small annoyances), but finally made it.

double checked and now I'm let in as I'd expect in my own Jira.

Time to document this experience for future needs

Thanks!