Cannot start after the upgrade, the installer used is upgraded to 7.13.0
Asked by cruise:

????

??./atlassian-confluence-7.13.0-x64.bin

Cannot start after upgrading

confluence.service - LSB: Atlassian Confluence  
Loaded: loaded (/etc/init.d/confluence; generated)  
Active: failed (Result: exit-code) since Wed 2021-09-29 03:19:54 UTC; 17min ago  
Docs: man:systemd-sysv-generator(8)  
Process: 27654 ExecStart=/etc/init.d/confluence start (code=exited, status=1/FAILURE)

Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: ---------------------------------------------------------------------------  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: Existing PID file found during start.  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: Tomcat appears to still be running with PID 26719. Start aborted.  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: If the following process is not a Tomcat process, remove the PID file and try again:  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: UID PID PPID C STIME TTY TIME CMD  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: conflue+ 26719 1 5 03:01 ? 00:00:56 /opt/atlassian/confluence/jre//bin/java -Djava.util.logging.config.file=/opt/  
Sep 29 03:19:54 ip-172-31-42-222 runuser\[27671\]: pam_unix(runuser:session): session closed for user confluence1  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: confluence.service: Control process exited, code=exited status=1  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: confluence.service: Failed with result 'exit-code'.  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: Failed to start LSB: Atlassian Confluence.

Also tried manual start

```
 sudo /opt/atlassian/confluence/bin/start-confluence.sh -fg
```

systemctl status confluence.service

confluence.service - LSB: Atlassian Confluence  
Loaded: loaded (/etc/init.d/confluence; generated)  
Active: failed (Result: exit-code) since Wed 2021-09-29 03:19:54 UTC; 1h 12min ago  
Docs: man:systemd-sysv-generator(8)  
Process: 27654 ExecStart=/etc/init.d/confluence start (code=exited, status=1/FAILURE)

Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: ---------------------------------------------------------------------------  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: Existing PID file found during start.  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: Tomcat appears to still be running with PID 26719. Start aborted.  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: If the following process is not a Tomcat process, remove the PID file and try again:  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: UID PID PPID C STIME TTY TIME CMD  
Sep 29 03:19:54 ip-172-31-42-222 confluence\[27654\]: conflue+ 26719 1 5 03:01 ? 00:00:56 /opt/atlassian/confluence/jre//bin/java -Djava.util.logging.config.file=/opt/  
Sep 29 03:19:54 ip-172-31-42-222 runuser\[27671\]: pam_unix(runuser:session): session closed for user confluence1  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: confluence.service: Control process exited, code=exited status=1  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: confluence.service: Failed with result 'exit-code'.  
Sep 29 03:19:54 ip-172-31-42-222 systemd\[1\]: Failed to start LSB: Atlassian Confluence.


Answers:
author: Benjamin
body: Hi [@cruise](/t5/user/viewprofilepage/user-id/4577174) ,

Looking at the log. There seems to be a PID issue. Have you tried restarting the server completely to start fresh and then start the confluence server?

-Ben

comments: author: cruise
body: How to start the service completely?


author: Benjamin
body: You can tried to run the stop script first and then run the start script again. Otherwise just restart the whole server.


author: cruise
body: Useless


author: cruise
body: executing using dedicated user: confluence1  
If you encounter issues starting up Confluence, please see the Installation guide at <http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide>

Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out  
---------------------------------------------------------------------------  
Using Java: /opt/atlassian/confluence/jre//bin/java  
2021-09-29 05:08:11,262 INFO \[main\] \[atlassian.confluence.bootstrap.SynchronyProxyWatchdog\] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required  
---------------------------------------------------------------------------  
Using CATALINA_BASE: /opt/atlassian/confluence  
Using CATALINA_HOME: /opt/atlassian/confluence  
Using CATALINA_TMPDIR: /opt/atlassian/confluence/temp  
Using JRE_HOME: /opt/atlassian/confluence/jre/  
Using CLASSPATH: /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar  
Using CATALINA_OPTS: -Datlassian.plugins.startup.options='-fg' -Dorg.apache.tomcat.websocket.DEFAULT_BUFFER_SIZE=32768 -Dconfluence.context.path= -Djava.locale.providers=JRE,SPI,CLDR -Dsynchrony.enable.xhr.fallback=true -Datlassian.plugins.enable.wait=300 -Djava.awt.headless=true -Xloggc:/opt/atlassian/confluence/logs/gc-2021-09-29_05-08-11.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -Xlog:gc+age=debug:file=/opt/atlassian/confluence/logs/gc-2021-09-29_05-08-11.log::filecount=5,filesize=2M -XX:G1ReservePercent=20 -XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent -XX:+PrintGCDateStamps -XX:+IgnoreUnrecognizedVMOptions -XX:ReservedCodeCacheSize=256m -Xms1024m -Xmx1024m  
Using CATALINA_PID: /opt/atlassian/confluence/work/catalina.pid  
NOTE: Picked up JDK_JAVA_OPTIONS: --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.io=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED  
\[0.000s\]\[warning\]\[gc\] -Xloggc is deprecated. Will use -Xlog:gc:/opt/atlassian/confluence/logs/gc-2021-09-29_05-08-11.log instead.  
29-Sep-2021 05:08:11.754 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:11.881 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Connector\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:11.912 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:11.919 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:11.985 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:12.022 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
29-Sep-2021 05:08:12.454 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]  
29-Sep-2021 05:08:12.485 SEVERE \[main\] org.apache.catalina.util.LifecycleBase.handleSubClassException Failed to initialize component \[Connector\[HTTP/1.1-8090\]\]  
org.apache.catalina.LifecycleException: Protocol handler initialization failed  
at org.apache.catalina.connector.Connector.initInternal(Connector.java:1048)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.core.StandardService.initInternal(StandardService.java:556)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:1045)  
at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:136)  
at org.apache.catalina.startup.Catalina.load(Catalina.java:724)  
at org.apache.catalina.startup.Catalina.load(Catalina.java:746)  
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)  
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)  
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)  
at java.base/java.lang.reflect.Method.invoke(Unknown Source)  
at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:302)  
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:472)  
Caused by: java.net.BindException: Address already in use  
at java.base/sun.nio.ch.Net.bind0(Native Method)  
at java.base/sun.nio.ch.Net.bind(Unknown Source)  
at java.base/sun.nio.ch.Net.bind(Unknown Source)  
at java.base/sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)  
at org.apache.tomcat.util.net.NioEndpoint.initServerSocket(NioEndpoint.java:300)  
at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:253)  
at org.apache.tomcat.util.net.AbstractEndpoint.bindWithCleanup(AbstractEndpoint.java:1204)  
at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:1217)  
at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:603)  
at org.apache.coyote.http11.AbstractHttp11Protocol.init(AbstractHttp11Protocol.java:80)  
at org.apache.catalina.connector.Connector.initInternal(Connector.java:1045)  
... 13 more  
29-Sep-2021 05:08:12.490 INFO \[main\] org.apache.catalina.startup.Catalina.load Server initialization in \[856\] milliseconds  
29-Sep-2021 05:08:12.497 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]


Tags: confluence-server

server