Unless someone comes up with better advice, I would suggest you remove/disable the Active Directory plugin and try if it still crashes.
-- Sami Michael Fowler <[email protected]> kirjoitti 28.2.2013 kello 18.21: > So It crashed again last night. No one was logged into the server and no jobs > were running. Any idea what happened? From the err.log > > Feb 27, 2013 6:56:21 PM winstone.Logger logInternal > WARNING: Untrapped Error in Servlet > java.lang.NullPointerException > at > hudson.plugins.active_directory.ActiveDirectoryAuthenticationProvider.retrieveUser(ActiveDirectoryAuthenticationProvider.java:88) > at > org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:119) > at > org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:195) > at > org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:45) > at > org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:138) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) > at > hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) > at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) > at > org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) > at > hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) > at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) > at > winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) > at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) > at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > > > > stdout: > # > # A fatal error has been detected by the Java Runtime Environment: > # > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77cae3be, pid=4648, > tid=2960 > # > # JRE version: 6.0_41-b02 > # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode, sharing > windows-x86 ) > # Problematic frame: > # C [ntdll.dll+0x2e3be] > # > # An error report file with more information is saved as: > # C:\Windows\system32\hs_err_pid4648.log > # > # If you would like to submit a bug report, please visit: > # http://java.sun.com/webapps/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > > [error occurred during error reporting , id 0xc0000005] > > > On Tue, Feb 19, 2013 at 10:07 AM, Michael Fowler <[email protected]> > wrote: > Thanks James, > I've added that to the config, we'll see what happens next time it crashes. > -Michael > > > On Tue, Feb 19, 2013 at 4:38 AM, teilo <[email protected]> wrote: > Presumably the service account under which Jenkins is running does not have > write permissions in the system32 folder. > > You may want to add > “-XX:ErrorFile=c:\some\path\where\jenkins\can\write\hs_err_.log” to your > Jenkins JVM startup options so that in the event of a crash the log can be > found. > > It may be caused by a fault in the JDK - and you may want to submit a bug > report to Oracle with this log file. > > /James > > > On Monday, 18 February 2013 19:47:50 UTC, MDKF wrote: > Hi Stuart, > Thanks for the link. It has happened while viewing the console output, but > we don't have any slave machines, just two executors on the master. But as in > the bug report we don't have .log files either. > > > On Mon, Feb 18, 2013 at 2:40 PM, Stuart Whelan > <[email protected]> wrote: > Could it be related to this: > > "Jenkins master node crashes often when viewing console logs of builds on > slaves" > > https://issues.jenkins-ci.org/browse/JENKINS-16528 > > It happens to me maybe half a dozen times a day. > > It is causing us huge problems, I am about to rebuild our jenkins master with > a clean os to see if that fixes it. > > > On Mon, Feb 18, 2013 at 11:44 AM, MDKF <[email protected]> wrote: > > > > Hi all, > > Jenkins keeps crashing randomly. There seems to be no particular trigger. > > Any idea whats happening? > > > > Heres my log: > > > > > > Running from: C:\Program Files (x86)\Jenkins\jenkins.war > > webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") > > Jenkins home directory: C:\Program Files (x86)\Jenkins found at: > > EnvVars.masterEnvVars.get("JENKINS_HOME") > > Running from: C:\Program Files (x86)\Jenkins\jenkins.war > > webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") > > Jenkins home directory: D:\Jenkins_Home found at: > > EnvVars.masterEnvVars.get("JENKINS_HOME") > > return code: 0 > > stderr: > > stdout: The command completed successfully. > > > > Running from: C:\Program Files (x86)\Jenkins\jenkins.war > > webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") > > Jenkins home directory: D:\Jenkins_Home found at: > > EnvVars.masterEnvVars.get("JENKINS_HOME") > > return code: 0 > > stderr: > > stdout: The command completed successfully. > > > > # > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x018d1a23, pid=1516, > > tid=3204 > > # > > # JRE version: 6.0_39-b04 > > # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode, sharing > > windows-x86 ) > > # Problematic frame: > > # J > > org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z > > # > > # An error report file with more information is saved as: > > # C:\Windows\system32\hs_err_pid1516.log > > # > > # If you would like to submit a bug report, please visit: > > # http://java.sun.com/webapps/bugreport/crash.jsp > > # > > Running from: C:\Program Files (x86)\Jenkins\jenkins.war > > webroot: EnvVars.masterEnvVars.get("JENKINS_HOME") > > Jenkins home directory: D:\Jenkins_Home found at: > > EnvVars.masterEnvVars.get("JENKINS_HOME") > > return code: 2 > > stderr: System error 85 has occurred. > > The local device name is already in use. > > > > stdout: > > # > > # A fatal error has been detected by the Java Runtime Environment: > > # > > # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x0154dd23, pid=4728, > > tid=4012 > > # > > # JRE version: 6.0_39-b04 > > # Java VM: Java HotSpot(TM) Client VM (20.14-b01 mixed mode, sharing > > windows-x86 ) > > # Problematic frame: > > # J > > org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z > > # > > # An error report file with more information is saved as: > > # C:\Windows\system32\hs_err_pid4728.log > > # > > # If you would like to submit a bug report, please visit: > > # http://java.sun.com/webapps/bugreport/crash.jsp > > # > > > > > > -- > > 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]. > > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > > -- > 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]. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > 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]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
