I recently updated jenkins, I believe by accident actually, by running yum 
update on my linux EC2 instance. Since I did this, if the user defined in 
/etc/sysconfig/jenkins is "root", jenkins launches fine. If I try to keep 
user="jenkins" though, as it was before the update, the service doesn't 
start. When I ask for the service status I get "Jenkins dead but PID file 
exists." The log file doesn't give much information because there are no 
exceptions. When I try to run the war file manually from the command line I 
have the same symptoms, and it just says "killed" when it dies off.

My searching around for solutions to this issue seems to point to it being 
a directory ownership problem. I have updated the ownership to 
jenkins:jenkins recursively on /var/lib/jenkins (my jenkins home) 
/var/cache/jenkins and /var/log/jenkins but I am still running in to this 
issue. I am wondering if it's possible there is a permission somewhere that 
I am missing, possibly something related to the version of Jenkins I now 
have installed.

I am running jenkins version 2.179 and I have java 1.8.0_201 installed

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/40c66d63-e70a-4a2c-bf78-12baa424d3a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to