Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-67570

Jenkins service stopped working after version upgrade to 2.319.1

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Major Major
    • core
    • - jenkins version: 2.319.1
      - java version: openjdk11
      - os: CentOS 7

      A few days ago we upgraded our Jenkins instance from v2.289.1 to v2.319.1.
      We also upgraded all of the installed plugins to their latest version (they are plenty so I will not mention them all here).

      We followed the automatic update process from the Jenkins UI, thus Jenkins restarted after the version upgrade and is up and functional as expected.

      However, it seems that jenkins service stopped working for some reason. We cannot restart - start - stop jenkins by using /etc/rc.d/init.d/jenkins service. This is the error we receive:

      jenkins.service - LSB: Jenkins Automation Server
      Loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
      Active: failed (Result: exit-code) since Wed 2022-01-12 15:10:40 EET; 14s ago
      Docs: man:systemd-sysv-generator(8)
      Process: 16090 ExecStart=/etc/rc.d/init.d/jenkins start (code=exited, status=1/FAILURE)
      Tasks: 220
      Memory: 3.7G
      CGroup: /system.slice/jenkins.service
      └─29835 /etc/alternatives/java -Djava.awt.headless=true -Dorg.jenkinsci.plugins.gitclient.Git.timeOut=120 -Djenkins.scm.impl.subversion.SubversionSCMFileSystem.disable=true -Dsvnkit.http.methods=Basic,Digest,Negotiate,NTLM -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --httpPort=80 --debug=5 --handlerCountMax=100 --handlerCountMaxIdle=20

      Jan 12 15:10:36 jenkins.ourdomain.com systemd[1]: Starting LSB: Jenkins Automation Server...
      Jan 12 15:10:36 jenkins.ourdomain.com runuser[16097]: pam_unix(runuser:session): session opened for user root by (uid=0)
      Jan 12 15:10:40 jenkins.ourdomain.com runuser[16097]: pam_unix(runuser:session): session closed for user root
      Jan 12 15:10:40 jenkins.ourdomain.com jenkins[16090]: Starting Jenkins [FAILED]
      Jan 12 15:10:40 jenkins.ourdomain.com systemd[1]: jenkins.service: control process exited, code=exited status=1
      Jan 12 15:10:40 jenkins.ourdomain.com systemd[1]: Failed to start LSB: Jenkins Automation Server.
      Jan 12 15:10:40 jenkins.ourdomain.com systemd[1]: Unit jenkins.service entered failed state.
      Jan 12 15:10:40 jenkins.ourdomain.com systemd[1]: jenkins.service failed.

      As you can see the error logs are not that informative and do not point us to any directions.
      We have also upgraded our java version on the server from 8 to 11, but nothing changed.

      Java candidates in init.d/jenkins file only point to the installation of openjdk11:

      candidates="
      /usr/lib/jvm/java-11-openjdk/bin/java
      "

      Our JAVA_HOME is: /usr/lib/jvm/java-11-openjdk
      And our PATH is: /usr/lib64/qt-3.3/bin:/root/perl5/bin:/opt/maven/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/usr/lib/jvm/java-11-openjdk/bin

      Could you point us to any direction in order to resolve this error?
      How is it possible that Jenkins is up and running, can be restarted from the URL, etc, but its service throws errors?

      Thank you

            Unassigned Unassigned
            epats Jen P
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: