I'm a little surprised at that message. When I stop the Jenkins process with "kill" (which defaults to sending SIGTERM), I think it reports killing a process named "java", not a process named "jenkins". Is it possible that you have another program named jenkins which is being started (and killed) instead of "java -jar jenkins.war"? Mark Waite
>________________________________ > From: Richard Mortimer <ri...@oldelvet.org.uk> >To: Domen Kožar <do...@dev.si> >Cc: jenkinsci-users@googlegroups.com >Sent: Friday, February 24, 2012 11:26 AM >Subject: Re: Jenkins (JVM) crashes after few minutes after start > > >On 24/02/2012 16:54, Domen Kožar wrote: >> That's the issue, java just exists, no stacktrace, even if ran in >> non-daemon mode. >> >From you serverfault page it shows syslog output of > >"Jan 31 17:50:02 cherry jenkins: jenkins: fatal: client (pid 16189) >killed by signal 15, exiting" > >That says that jenkins received signal 15 (SIGTERM in most universes). >Now it is possible that jenkins sent itself that but unlikely. > >Can you check for cron jobs that might be sending signals. If there is >nothing obvious you might want to look at the timing of jenkins >terminating. That might give some pattern to allow you to identify a >specific job killing things. > >Richard > > >> On Fri, Feb 24, 2012 at 5:51 PM, Didier Durand <durand.did...@gmail.com >> <mailto:durand.did...@gmail.com>> wrote: >> >> Hi, >> >> Do you have the Java stack trace of the crash? >> >> regards >> >> didier >> >> On Feb 24, 4:04 pm, Domen Kožar <do...@dev.si <mailto:do...@dev.si>> >> wrote: >> > I have been fighting with this one for a month, would be really >> > pleased if someone can give tips or request more data: >> > >> > >> >>Crosspost:http://serverfault.com/questions/355516/jenkins-jvm-crashes-after-few... >> >> > > >
