Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-77817

Problem with Docker Image of Jira Software v10.0.0-EAP04

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.0.0
    • 10.0.0
    • Jira 10.0 EAP
    • None

      Issue Summary

      Problem with Docker image: atlassian/jira-software:10.0.0-EAP04 available in Docker hub. Container starts with Error and Jira instance is not up.

      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      1. Run Jira container by following below steps
        docker pull atlassian/jira-software:10.0.0-EAP04       //Pull Image
        
        docker volume create --name jiraVolumev10  
        docker run -v jiraVolumev10:/var/atlassian/application-data/jira --name="jirav10" -d -p 9090:8080 atlassian/jira-software:10.0.0-EAP04
        
      2. Container is UP

      Expected Results

      Jira should be accessible from URL: http://localhost:9090 (Database Set-up configuration page should show up)

      Actual Results

      URL: http://localhost:9090 Errors out with HTTP 404

      docker exec -it jirav10 tail -f /opt/atlassian/jira/logs/catalina.2024-06-17.log

      17-Jun-2024 14:24:36.742 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=/opt/atlassian/jira/temp
      17-Jun-2024 14:24:36.746 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The Apache Tomcat Native library which allows using OpenSSL was not found on the java.library.path: [/usr/java/packages/lib:/usr/lib64:/lib64:/lib:/usr/lib]
      17-Jun-2024 14:24:37.446 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8080"]
      17-Jun-2024 14:24:37.478 INFO [main] org.apache.catalina.startup.Catalina.load Server initialization in [1179] milliseconds
      17-Jun-2024 14:24:37.588 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
      17-Jun-2024 14:24:37.589 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.89]
      17-Jun-2024 14:24:42.450 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
      17-Jun-2024 14:24:42.467 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [] startup failed due to previous errors
      17-Jun-2024 14:24:42.573 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]
      17-Jun-2024 14:24:42.601 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [5122] milliseconds
      

      docker logs jirav10

      17-Jun-2024 13:09:01.416 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match [Server/Service/Connector] failed to set property [proxyPort] to []
      17-Jun-2024 13:09:01.622 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version name:   Apache Tomcat/9.0.89
      17-Jun-2024 13:09:01.624 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server built:          May 3 2024 20:22:11 UTC
      17-Jun-2024 13:09:01.624 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.89.0
      17-Jun-2024 13:09:01.625 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name:               Linux
      17-Jun-2024 13:09:01.625 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version:            6.6.12-linuxkit
      17-Jun-2024 13:09:01.625 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Architecture:          amd64
      17-Jun-2024 13:09:01.625 INFO [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home:             /opt/java/openjdk
      ...
      ...
      17-Jun-2024 14:24:37.589 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Apache Tomcat/9.0.89]
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error processing element JiraHomeAppender ([Appenders: null]): CLASS_NOT_FOUND
      ERROR StatusConsoleListener Error proc
      ...
      ...
      

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

              98b38e34cfc4 Raphaël Biland
              072fabfd41a3 Shreekesh Mohan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: