Jenkins fails when running service start jenkins

Question

I installed jenkins on Centos 7 using the following  sudo wget -O  etc yum repos d jenkins repo http   pkg jenkins io redhat-stable jenkins repo sudo rpm --import http   pkg jenkins io redhat-stable jenkins io key yum install jenkins  as described on the official documentation However when I run  service start jenkins  I get the following error message  Starting jenkins  via systemctl    Job for jenkins service failed because the control process exited with error code  See  quot systemctl status jenkins service quot  and  quot journalctl -xe quot  for details                                                              FAILED   Running systemctl status jenkins service gives me this    jenkins service - LSB  Jenkins Continuous Integration Server    Loaded  loaded   etc rc d init d jenkins     Active  failed  Result  exit-code  since Wed 2016-09-21 16 45 28 BST  3min 59s ago      Docs  man systemd-sysv-generator 8    Process  2818 ExecStart  etc rc d init d jenkins start  code exited  status 1 FAILURE   Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma JavaVMArguments of JavaVMArguments   04  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma JavaVMArguments current JavaVMArgu   92  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma Daemon daemonize Daemon java 106  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma Daemon all Daemon java 88  Sep 21 16 45 28 webstack local caplib jenkins 2818       6 more Sep 21 16 45 28 webstack local caplib systemd 1   jenkins service  control process exited  code exited s   s 1 Sep 21 16 45 28 webstack local caplib systemd 1   Failed to start LSB  Jenkins Continuous Integration Server  Sep 21 16 45 28 webstack local caplib systemd 1   Unit jenkins service entered failed state  Sep 21 16 45 28 webstack local caplib systemd 1   jenkins service failed  Sep 21 16 45 28 webstack local caplib jenkins 2818    FAILED  Hint  Some lines were ellipsized  use -l to show in full   and running journalctl -xe gives me this  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma JavaVMArguments of JavaVMArguments java  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma JavaVMArguments current JavaVMArguments  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma Daemon daemonize Daemon java 106  Sep 21 16 45 28 webstack local caplib jenkins 2818   at com sun akuma Daemon all Daemon java 88  Sep 21 16 45 28 webstack local caplib jenkins 2818       6 more Sep 21 16 45 28 webstack local caplib runuser 2819   pam unix runuser session   session closed for user jenkin Sep 21 16 45 28 webstack local caplib systemd 1   jenkins service  control process exited  code exited status  Sep 21 16 45 28 webstack local caplib systemd 1   Failed to start LSB  Jenkins Continuous Integration Server  -- Subject  Unit jenkins service has failed -- Defined-By  systemd -- Support  http   lists freedesktop org mailman listinfo systemd-devel -- -- Unit jenkins service has failed  -- -- The result is failed  Sep 21 16 45 28 webstack local caplib systemd 1   Unit jenkins service entered failed state  Sep 21 16 45 28 webstack local caplib systemd 1   jenkins service failed  Sep 21 16 45 28 webstack local caplib jenkins 2818    FAILED  Sep 21 16 45 28 webstack local caplib polkitd 1392   Unregistered Authentication Agent for unix-process 2813 8 Sep 21 16 45 28 webstack local caplib dhclient 1390   DHCPREQUEST on eno16777984 to 192 168 15 254 port 67  xi Sep 21 16 45 28 webstack local caplib dhclient 1390   DHCPACK from 192 168 15 254  xid 0x2ab6e6bc  Sep 21 16 45 30 webstack local caplib dhclient 1390   bound to 192 168 15 120 -- renewal in 865 seconds  Sep 21 16 45 36 webstack local caplib systemd 1   Starting Cleanup of Temporary Directories    -- Subject  Unit systemd-tmpfiles-clean service has begun start-up -- Defined-By  systemd -- Support  http   lists freedesktop org mailman listinfo systemd-devel -- -- Unit systemd-tmpfiles-clean service has begun starting up  Sep 21 16 45 36 webstack local caplib systemd 1   Started Cleanup of Temporary Directories  -- Subject  Unit systemd-tmpfiles-clean service has finished start-up -- Defined-By  systemd -- Support  http   lists freedesktop org mailman listinfo systemd-devel -- -- Unit systemd-tmpfiles-clean service has finished starting up  -- -- The start-up result is done   Both of which is really unhelpful  How do I fix this issue

User · Answer

Before you install Jenkins you should install JDK:

apt install openjdk-8-jre

After this install Jenkins:

apt-get install jenkins

And check Jenkins status (should be 'active'):

systemctl status jenkins.service

User · Answer

In my case I were starting jenkins service from root instead of jenkins user  i did   sed -i  s JENKINS USER  jenkins  JENKINS USER  root  g   etc sysconfig jenkins   then   service jenkins restart   all work well

User · Answer

Looks like java version conflicts    Please refer https   medium com lucian-daniliuc upgrading-jenkins-on-ubuntu-14-04-lts-df3e1209f98c

User · Answer

You just need to install Java  It did work after installing Java version 8  using this command    sudo apt install openjdk-8-jre-headless

User · Answer

I had a similar problem on Ubuntu 16 04  Thanks to  Guna I figured out that I had to manually install Java  sudo apt install openjdk-8-jre

User · Answer

I was trying to install it in kubuntu 18 04  and i was already sure that i had java installed  I confirmed by trying     java -version   I got the output like that  java version  1 8 0 91  Java TM  SE Runtime Environment  build 1 8 0 91-b14  Java HotSpot TM  64-Bit Server VM  build 25 91-b14  mixed mode    Since I already know that my java PATH variables are defined in  etc environment file  I added that file to the top of  etc init d jenkins file  source  etc environment   you can even remove the PATH from  etc init d jenkins file  since it s already defined in  etc environment  after that  i restarted my jenkins server and it seemed to start working fine from localhost 8080

User · Answer

I had a similar issue on CentOS 7 while a correct version of Java was installed and java -version gave a nice result   Collecting multiple answers from different SO threads I did the following   Make sure Java is installed  and version is compatible with Jenkins  There re some tricks if saying about CentOS  this is mentioned in official Jenkins tutorial here   If Java is installed and available  when running java -v output should look like this         gt  java -version     openjdk version  1 8 0 161      OpenJDK Runtime Environment  build 1 8 0 161-b14      OpenJDK 64-Bit Server VM  build 25 161-b14  mixed mode    Add a path to Java to your  etc rc d init d jenkins       gt   sudo vim  etc rc d init d jenkins     candidates        etc alternatives java      usr lib jvm java-1 8 0 bin java      usr lib jvm jre-1 8 0 bin java      usr lib jvm java-1 7 0 bin java      usr lib jvm jre-1 7 0 bin java      usr bin java      usr java jdk1 8 0 162 bin java   add your java path here         How to get your  real  path to java distributive which is called when you type smth like java -v Follow this SO thread  If steps above didn t help  try to make sure all permission issues are resolved    If Jenkins fails to run Java  it could be jenkins user doesn t have permissions to run it  then change jenkins to root in config  described here  Try to play with chmod setting 755 permissions to java installation folder   And finally what helped me in result When I did run journalctl -xe as was suggested when I ve tried to sudo service jenkins start  I got similar Java stacktrace   Starting CloudBees Jenkins Enterprise Exception in thread  main  java lang reflect InvocationTargetException at sun reflect NativeMethodAccessorImpl invoke0 Native Method  at sun reflect NativeMethodAccessorImpl invoke NativeMethodAccessorImpl java 62  at sun reflect DelegatingMethodAccessorImpl invoke DelegatingMethodAccessorImpl java 43  at java lang reflect Method invoke Method java 497  at Main  main Main java 140  at Main main Main java 98  Caused by  java lang UnsatisfiedLinkError   tmp jna--1712433994 jna7387046629130767794 tmp   tmp jna--1712433994 jna7387046629130767794 tmp  failed to map segment from shared object  Operation not permitted at java lang ClassLoader NativeLibrary load Native Method  at java lang ClassLoader loadLibrary0 ClassLoader java 1937  at java lang ClassLoader loadLibrary ClassLoader java 1822  at java lang Runtime load0 Runtime java 809  at java lang System load System java 1086  at com sun jna Native loadNativeDispatchLibraryFromClasspath Native java 761  at com sun jna Native loadNativeDispatchLibrary Native java 736  at com sun jna Native  lt clinit gt  Native java 131  at com sun akuma CLibrary  lt clinit gt  CLibrary java 89  at com sun akuma JavaVMArguments resolvePID JavaVMArguments java 128  at com sun akuma JavaVMArguments ofLinux JavaVMArguments java 116  at com sun akuma JavaVMArguments of JavaVMArguments java 104  at com sun akuma JavaVMArguments current JavaVMArguments java 92  at com sun akuma Daemon daemonize Daemon java 106  at com sun akuma Daemon all Daemon java 88      6 more   The problem is that Jenkins tries to launch JNA library from  tmp dir which is marked as noexec by default  so we it could be fixed by creating a temporary directory in a  jenkins path so it could be executed  The full way to do this is described here by CloudBees support  thanks a lot for them   I hope something from this list will help  as well I mostly leave it for me in the future when I ll have to install Jenkins for CentOs again

User · Answer

I had the same issue  and when I checked if Java is installed I realised it s not  so installing Java solved the problem for me   Check for java   java -version   If Java is installed in the system  the command will return the java version otherwise it will show a message like this   The program  java  can be found in the following packages     default-jre    gcj-5-jre-headless    openjdk-8-jre-headless    gcj-4 8-jre-headless    gcj-4 9-jre-headless    openjdk-9-jre-headless   To install java use the following command   sudo apt-get install default-jre

User · Answer

Similar problem on Ubuntu 16 04    Setting up jenkins  2 72      Job for jenkins service failed because the control process exited with error code  See  systemctl status jenkins service  and  journalctl -xe  for details  invoke-rc d  initscript jenkins  action  start  failed    jenkins service - LSB  Start Jenkins at boot time Loaded  loaded   etc init d jenkins  bad  vendor preset  enabled  Active  failed  Result  exit-code  since Tue 2017-08-01 05 39 06 UTC  7ms ago Docs  man systemd-sysv-generator 8  Process  3700 ExecStart  etc init d jenkins start  code exited  status 1 FAILURE   Aug 01 05 39 06 ip-0 systemd 1   Starting LSB  Start Jenkins      Aug 01 05 39 06 ip-0 jenkins 3700   ERROR  No Java executable     Aug 01 05 39 06 ip-0 jenkins 3700   If you actually have java     Aug 01 05 39 06 ip-0 systemd 1   jenkins service  Control pro   1 Aug 01 05 39 06 ip-0 systemd 1   Failed to start LSB  Start J     Aug 01 05 39 06 ip-0 systemd 1   jenkins service  Unit entere     Aug 01 05 39 06 ip-0 systemd 1   jenkins service  Failed with       To fix the issue manually install Java Runtime Environment   JDK version 9   sudo apt install openjdk-9-jre   JDK version 8   sudo apt install openjdk-8-jre   Open Jenkins configuration file    sudo vi  etc init d jenkins   Finally  append path to the new java executable  line 16    PATH  bin  usr bin  sbin  usr sbin  usr lib jvm java-8-openjdk-amd64 bin

User · Answer

sudo vim  etc rc d init d jenkins    candidates     etc alternatives java   usr lib jvm java-1 8 0 bin java   usr lib jvm jre-1 8 0 bin java   usr lib jvm java-1 7 0 bin java   usr lib jvm jre-1 7 0 bin java   usr bin java   usr java jdk1 8 0 162 bin java      add your java path

User · Answer

rm -rf  var log jenkins too big the log

User · Answer

I had below error      Job for jenkins service failed because the control process exited with error code  See  systemctl status jenkins service  and  journalctl -xe  for details    Solution was to revert the NAME to jenkins in the below file  Earlier I have changed it to  NAME ubuntu     sudo vi  etc default jenkins     NAME jenkins   Now restart passed   sudo service jenkins restart sudo systemctl restart jenkins service   Hope that helps

User · Answer

I faced same issue while setting up jenkins  the problem is that java is not installed and hence not available in path   The simplest way is to use scp here to copy jdk binaries to aws ec2 box  script won t work if you make one as they keep on updating download urls Orale  i mean       scp -i C  Users key-pair pem jdk-8u191-linux-x64 tar gz ec2-      user 54 183 220 7       cd  opt   sudo cp  home ec2-user jdk      sudo chmod  x jdk    sudo tar xzf jdk-8u191-linux-x64 tar gz   sudo tar xzf jdk-8u191-linux-x64 tar gz   cd jdk1 8 0 191    sudo alternatives --install  usr bin java java  opt jdk1 8 0 191 bin java 2   sudo alternatives --config java   Here I download tar gz file in loal windows and transferred over scp to AWS ec2-user  default dir  Hope it helps

User · Answer

Still fighting the same error on both ubuntu  ubuntu derivatives and opensuse  This is a great way to bypass and move forward until you can fix the actual issue    Just use the docker image for jenkins from dockerhub   docker pull jenkins jenkins  docker run  -itd -p 8080 8080 --name jenkins container  jenkins  Use the browser to navigate to   localhost 8080 or my pc 8080  To get at the token at the path given on the login screen   docker exec -it jenkins container  bin bash  Then navigate to the token file and copy paste the code into the login screen  You can use the edit copy paste menus in the kde gnome lxde xfce terminals to copy the terminal text  then paste it with ctrl-v   War File  Or use the jenkins war file  For development purposes you can run jenkins as your user  or as jenkins  from the command line or create a short script in  usr local or  opt to start it   Download the jenkins war from the jenkins download page   https   jenkins io download   Then put it somewhere safe    jenkins would be a good place   mkdir   jenkins  cp   Downloads jenkins war   jenkins  Then run   nohup java -jar   jenkins jenkins war     jenkins jenkins log 2  amp 1  To get the initial admin password token  copy the text output of   cat  home my home dir  jenkins secrets initialAdminPassword  and paste that into the box with ctrl-v as your initial admin password   Hope this is detailed enough to get you on your way

User · Answer

For ubuntu 16 04  there is firewall issue  You need to open 8080 port using following command   sudo ufw allow 8080   Detailed steps are given here  https   www digitalocean com community tutorials how-to-install-jenkins-on-ubuntu-16-04

User · Answer

ERROR   Linux   Centos      Job for jenkins service failed because the control process exited with error code  See  systemctl status jenkins service  and  journalctl -xe  for details    Solution    Edit the Jenkins init file by doing  sudo vi  etc init d jenkins  Add your own Java path  for example    opt oracle product java jdk1 8 0 45 bin java  Restart the service   sudo service jenkins start sudo service jenkins status sudo service jenkins stop

User · Answer

In my case  the issue was of unsupported java version Check the file  etc init d jenkins to find out which java versions are supported  To find which java versions are supported  run grep -m 1  quot JAVA ALLOWED VERSIONS quot   etc init d jenkins  The output will be like this your s might be different  JAVA ALLOWED VERSIONS    quot 1 8 quot   quot 11 quot     In my case version 1 8 and 11 are supported  I will be going with version 11  Install the supported version of jre using command For ubuntu debian sudo apt install openjdk-11-jre   For centOS use sudo yum install java-11-openjdk-devel  Find the path to newly installed jre For ubuntu debian path is  usr lib jvm java-11-openjdk-amd64 bin java  You can find the path on centOS under  usr lib jvm  Modify the file  etc init d jenkins At line number 28  replace the JAVA  type -p java   with JAVA   usr lib jvm java-11-openjdk-amd64 bin java  Now run command to reload the systemctl daemon sudo systemctl daemon-reload  Start the jenkins service sudo systemctl start jenkins

User · Answer

Adding on to what has been already answered by Guna Sekaran  Jenkins need the user jenkins to be present in order to run the jenkins as a service   To add user fire  useradd jenkins  as root and fire  passwd jenkins  as root before starting Jenkins as a service

User · Answer

In my case  the port 8080 was taken by some other service  Apache Airflow    So I edit the HTTP port in this file    sudo vi  etc default jenkins   And then started the service and it worked    sudo service jenkins start   I was on Ubuntu 18 04 and installed openjdk-8

User · Answer

100   Solved  I had the same problem today  I checked my server space  df-h   I saw that server is out of space so i check which directory has most size by  sudo du -ch     sort -h   I saw 12 2G     var lib jenkins so i entered this folder and cleared all the logs by  cd  var libs jenkins rm     and restart the jenkins it will work normal   sudo systemctl restart jenkins service

User · Answer

vi  etc init d jenkins   add    usr lib jvm java jre bin java

User · Answer

The easiest possible fix for this issue if it is a AWS linux instance  sudo yum install java-1 8 0 -y   sudo yum remove java-1 7 0-openjdk

[jenkins] Jenkins fails when running "service start jenkins"

Examples related to jenkins