Jenkins active (exited)

loaded: loaded (/etc/rc.d/init.d/jenkins; bad; vendor preset: disabled)
ufw status: active (exited)
jenkins: unrecognized service
failed to start lsb: start jenkins at boot time ubuntu
networking service active (exited)
status active exited linux
linux server active exited
squid active (exited)

For some reason Jenkins stops working all the time and I have to restart jenkins service to make it work again. Every time this happens service is "active (exited)" but there is nothing in the logs. I use Ubuntu 16.04.

root@laran:~# service jenkins status
    ● jenkins.service - LSB: Start Jenkins at boot time
       Loaded: loaded (/etc/init.d/jenkins; bad; vendor preset: enabled)
       Active: active (exited) since Sun 2017-03-05 06:09:46 EST; 6min ago
         Docs: man:systemd-sysv-generator(8)
      Process: 25459 ExecStop=/etc/init.d/jenkins stop (code=exited, status=0/SUCCESS)
      Process: 25477 ExecStart=/etc/init.d/jenkins start (code=exited, status=0/SUCCESS)

Jenkins status active(exited) coming after the installation of Jenkins , $service jenkins start $systemctl status Jenkins. And the output coming is like. Jenkins status active(exited). I don't know why it is exiting. The service jenkins status shows Active: active (exited) although the service is up and running. I checked and confirmed that the jenkins jvm process was running (with jps command which displays list of running java processes).

Setting permissions for files and folders under /var/lib/jenkins worked for me:

vim /etc/sysconfig/jenkins  
# make sure that $JENKINS_USER="jenkins"

chown -R jenkins:jenkins /var/lib/jenkins
chown -R jenkins:jenkins /var/cache/jenkins
chown -R jenkins:jenkins /var/log/jenkins
systemctl restart jenkins 

Jenkins service is not able to start up · Issue #23 · konstruktoid , Hi, After the OS is harden and reboot. my Jenkins service never able to (/etc/init​.d/jenkins; bad; vendor preset: enabled) Active: failed (Result: QA systemd[1]: jenkins.service: Control process exited, code=exited status=7 For Jenkins to work with Nginx, you will need to update the Jenkins configuration so that the Jenkins server listens only on the localhost interface rather than on all interfaces (0.0.0.0). If Jenkins listens on all interfaces, it’s potentially accessible on its original, unencrypted port ( 8080 ).

Have You Updated Your Jenkins?

if So, read this...

In my case, it was a Jenkins update which changed the configuration. My custom jenkins port (9090) was changed (defaulted to 8080 after update). I was not able to open the jenkins dashboard on 9090 port. So I tried with the mentioned suggestions. I checked the service status and journalctl logs which I found absolutely misleading. The service jenkins status shows Active: active (exited) although the service is up and running.

I checked and confirmed that the jenkins jvm process was running (with jps command which displays list of running java processes).

So before you bang your head on figuring out what went wrong, just check if the jenkins update has changed any configuration and whether the jenkins process is already running in the background on some other port.

Starting, stopping, and restarting Jenkins on Ubuntu, d/jenkins; bad; vendor preset: enabled) Active: active (exited) since Wed Get Learning Continuous Integration with Jenkins - Second Edition now with O'Reilly​  In this tutorial, we will show you how to install Jenkins on an Ubuntu 18.04 machine using the Jenkins Debian package repository. Jenkins is an open-source automation server that offers an easy way to set up a continuous integration and continuous delivery (CI/CD) pipeline.

What does status "active (exited)" mean for a SystemD service , It seems you are running a system with systemd yet you are using sysV commands. Did you create a sysV init script or a systemd unit file? State active (​exited)  I just installed the latest deb-package on my ubuntu host. When starting jenkins nothing happens. No logfile under /var/log/jenkins. When debugging, I realized, that when running the classical init script, some weird systemd interceptor magic happens, which results in systemd trying to run jenkins.

[JENKINS-29965] Debian Package, Ubuntu 15.04 and systemd , service - LSB: Start Jenkins at boot time Loaded: loaded (/etc/init.d/jenkins) Active​: active (exited) since Sat 2015-08-15 01:53:02 CEST; 47min  Jenkins is an open source automation server intended to automate repetitive technical tasks involved in the continuous integration and delivery of software. Continuous Integration is a development practice that requires developers to integrate code into a shared repository at regular intervals.

Jenkins active (exited), For some reason Jenkins stops working all the time and I have to restart jenkins service to make it work again. Every time this happens service is “active (exited)”​ 

Comments
  • Have you checked the jenkins logs at /var/log/jenkins?
  • @JonS I did, but there is nothing unusual. Last log is "INFO: Jenkins is fully up and running" unless there are some logs related to jobs that were executed before Jenkins stopped working.
  • Could you check (or post) the output of journalctl -xu jenkins please?
  • @AlexO Mar 05 07:42:15 laran jenkins[26708]: jenkins: fatal: client (pid 26709) killed by signal 9, exiting
  • @AlexO VPS I use only has 512MB of RAM, so maybe that's the cause?
  • Doing this helped me. Just to take notice: I was in a server with a user named "jenkins" that was previously created. Not sure if having created this user was the cause of the problem...