Dear All,
We have Jira 6.3.3 and Confluence 5.5.3 running on the same Linux machine.
A week ago, both Jira and Confluence have started to have problems in working.
We have rebooted the machine but we have not reached to any solution.
The linux machine version is Debian 7.6 .
1-) First if you start Jira as a service from as below;
/etc/init.d# ./jira start
2-) Here is the output of the JIRA log file ;
tail -f /opt/atlassian/jira/logs/catalina.out
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384m; support was removed in 8.0
May 08, 2019 11:19:32 AM org.apache.catalina.core.AprLifecycleListener init
INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib
May 08, 2019 11:19:33 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8080"]
May 08, 2019 11:19:33 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1181 ms
May 08, 2019 11:19:33 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
May 08, 2019 11:19:33 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.47
It stops as above and does not go further .......
3-) First if you start Confluence as a service from as below;
/etc/init.d# ./confluence start
4-) Here is the output of the CONFLUENCE log file ;
tail -f /opt/atlassian/confluence/logs/catalina.out
May 08, 2019 11:47:26 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'minProcessors' to '5' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'maxProcessors' to '75' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'useURIValidationHack' to 'false' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.
May 08, 2019 11:47:26 AM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.
It stops as above and does not go further .......
5-) After restarting the JIRA and CONFLUENCE as a service, the LISTEN PORT status are as below;
The below status is when everthing has been working smoothly.
The below picture is from old times when both Confluence (8090 port) and Jira (8080 port) have been working smoothly.
3-) Here below are the setenv.sh memory settings for JIRA.
JVM_MINIMUM_MEMORY="384m"
JVM_MAXIMUM_MEMORY="768m"
JIRA_MAX_PERM_SIZE=384m
4-) Here below are the setenv.sh memory settings for CONFLUENCE.
JAVA_OPTS="-Xms256m -Xmx512m -XX:MaxPermSize=256m $JAVA_OPTS -Djava.awt.headless=true "
Is there any suggestion for the solution ?
Regards.
@Nuri Gürsel Yarkın I think your problem looks like the once here, please check resolution here
https://community.atlassian.com/t5/Confluence-questions/Confluence-isn-t-starting/qaq-p/1074529
best regards,
Moses
Dear Moses,
Thanks for the reply ...
It definetly helped us more than we have expected.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.