Re: Jenkins not starting

2020-05-12 Thread Mai Waly
This is a duplicate issue, already a post open. On Tuesday, May 12, 2020 at 5:45:33 AM UTC+2, Mai Waly wrote: > > Hi All, > > > > Please advise what happen as Jenkins is no longer starting and showing > error, there is no gui any more. > > > ay 10, 2020 7:48:13 AM hudson.util.BootFailure

Jenkins not starting

2020-05-11 Thread Mai Waly
Hi All, Please advise what happen as Jenkins is no longer starting and showing error, there is no gui any more. ay 10, 2020 7:48:13 AM hudson.util.BootFailure publish SEVERE: Failed to initialize Jenkins hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException:

Re: Jenkins not starting and killing Tomcat on Solaris VM

2017-01-05 Thread Andrew
Julien No, no fix, no update. Ended up retaining on physical kit. :-( On Wednesday, August 5, 2015 at 8:51:37 PM UTC+10, Julien Verger wrote: > > Hello Andrew, > > did you hav any update since this post? I've a same problem to solve. > > Regards > -- You received this message because you are

Re: Jenkins not starting and killing Tomcat on Solaris VM

2015-08-05 Thread Julien Verger
Hello Andrew, did you hav any update since this post? I've a same problem to solve. Regards -- 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

Jenkins not starting and killing Tomcat on Solaris VM

2015-02-04 Thread Andrew
environment, and the line stat(/dev/zfs, ...) in the non working environment is replaced by ioctl(9, ZFS_IOC_POOL_CONFIGS, 0xA152ABF8) = 0 in the working. I have tried starting TC without Jenkins and then deploying Jenkins - effectively the same outcome - everything dies. Directory structure

Re: How debug Jenkins not starting? ( jenkins dead but pid file exists )

2014-07-06 Thread Lokesh Agrawal
Change JENKINS_AJP_PORT Change it from JENKINS_AJP_PORT=8009 OR whatever value to JENKINS_AJP_PORT=-1 It will work for sure. Regards, Lokesh Agrawal On Wednesday, February 20, 2013 3:57:30 PM UTC+5:30, Jan Collijs wrote: I had the same problem, it seems this was related to the version of