Rebooted my Ec2 instances nd all server apps not reachable. Linux boots but cannot access apps.

[Serial Founder]

Hello I have set up new Ec2 instances running Jira, Confluence and Jira Service Desk installs on AWS EC2 respsectvely. After adding a url in the proxyname position in their respective server.xml files, I rebooted my EC2 instances.

Since the instances have come back, I cannot access any of the applications or any of the servers.

I have tried to run the 

$ sudo /etc/init.d/jira start

command, however (at least for Jira) it remains unreachable.

Please help!

[Nic Brough -Adaptavist-]

Ok, it looks like you started the service as root once, which will clobber files all over the installation.

Stop Jira and Confluence if they are running and use "chown -R <user>" on both the systems installation and data directories (the users are probably something like jira and conf)

[Serial Founder]

ah...I will try that. Thanks.

[Serial Founder]

Nic - thank you very much. Now that I know this issue, I was able to resolve all other instances. Moving forward, I will only perform commands as the native user. This should reduce any issues.

[planeverapp]

What did you do to fixed it? I tried changing server.xml file to incorporate ssl. It doesnt work. So I changed it back, and then this happened to me.

[Serial Founder]

My issue was caused by the fact that the user 'confluence' must be the owner own of all files associated with the install. In order for me to access the server.xml file, I had to change the owner of a few folders including the server.xml file. After I made those changes, I didn't change the owner back to 'confluence' and the rebooted confluence from the CL.

Normally I would have impersonated the 'confluence' user, but I was accessing the files via FTP and editing them in a mac app, instead of using the command line to edit the files.

@Nic Brough (Adaptavist)'s suggestion essentially updated the owner of ALL files / folders that may have been changed do to my modification misstep.

It solved the issue!

[Serial Founder]

When I dig deeper to inspect the error here is what I found...

● confluence.service - LSB: Start/stop Atlassian Confluence standalone server

   Loaded: loaded (/etc/init.d/confluence; bad; vendor preset: enabled)

   Active: failed (Result: exit-code) since Sat 2018-09-29 13:30:18 UTC; 1min 22s ago

     Docs: man:systemd-sysv-generator(8)

  Process: 1577 ExecStart=/etc/init.d/confluence start (code=exited, status=2)

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: If you encounter issues starting up Confluence Standalone, please see the Installation guide at http://confluence.

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: Existing PID file found during start.

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: Removing/clearing stale PID file.

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: touch: cannot touch '/opt/atlassian/confluence/logs/catalina.out': Permission denied

Sep 29 13:30:18 ip-172-31-8-48 confluence[1577]: /opt/atlassian/confluence/bin/catalina.sh: 464: /opt/atlassian/confluence/bin/catalina.sh: cannot create /opt/atla

Sep 29 13:30:18 ip-172-31-8-48 systemd[1]: confluence.service: Control process exited, code=exited status=2

Sep 29 13:30:18 ip-172-31-8-48 systemd[1]: Failed to start LSB: Start/stop Atlassian Confluence standalone server.

Sep 29 13:30:18 ip-172-31-8-48 systemd[1]: confluence.service: Unit entered failed state.

Sep 29 13:30:18 ip-172-31-8-48 systemd[1]: confluence.service: Failed with result 'exit-code'.

[Serial Founder]

After reboot, log not updated.

I tried to access confluence at the appropriate URL and ...

Service Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

---

Apache Server at confluence.btbxapps.com Port 80

[Serial Founder]

Going back to the server to try to force start, here is what I get.

ubuntu@ip-172-31-8-48:~$ sudo /etc/init.d/confluence start

[....] Starting confluence (via systemctl): confluence.serviceJob for confluence.service failed because the control process exited with error code. See "systemctl status confluence.service" and "journalctl -xe" for details.

failed!

[Serial Founder]

I went back and reviewed the logs for all products and the results are the same.

Unable to read Server.xml

Example: 

-rw-r----- 1 root root 1503 Sep 29 00:06 /opt/atlassian/confluence/conf/server.xml

During my configuration process, I did change ownership from root to me and forgot to change it back. However, I just reversed the ownership rebooted the server and the results are still the same.

Here is a snapshot from the log- file

-------------------------------------

29-Sep-2018 01:55:45.114 WARNING [main] org.apache.catalina.startup.Catalina.load Unable to load server configuration from [/opt/atlassian/confluence/conf/server.xml]
29-Sep-2018 01:55:45.140 WARNING [main] org.apache.catalina.startup.Catalina.load Permissions incorrect, read permission is not allowed on the file.
29-Sep-2018 01:55:45.140 SEVERE [main] org.apache.catalina.startup.Catalina.start Cannot start server. Server instance is not configured.
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
29-Sep-2018 12:56:31.453 WARNING [main] org.apache.catalina.startup.Catalina.load Unable to load server configuration from [/opt/atlassian/confluence/conf/server.xml]
29-Sep-2018 12:56:31.482 WARNING [main] org.apache.catalina.startup.Catalina.load Permissions incorrect, read permission is not allowed on the file.
29-Sep-2018 12:56:31.482 SEVERE [main] org.apache.catalina.startup.Catalina.start Cannot start server. Server instance is not configured.

[Nic Brough -Adaptavist-]

Are Confluence and Jira running after starting them?  What do their logs say?