[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Title: Message Title dogfood commented on JENKINS-24453 Re: Jenkins server got blue screen to death Integrated in jenkins_main_trunk #4292 JENKINS-24453 [ZD-20503] Incorporated a newer version of winp. (Revision 21fb398bfa7068f6f72154763bdbb09baddf313d) Result = UNSTABLE ogondza : 21fb398bfa7068f6f72154763bdbb09baddf313d Files : core/pom.xml Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon commented on JENKINS-24453 Jenkins server got blue screen to death Code changed in jenkins User: Kohsuke Kawaguchi Path: core/pom.xml http://jenkins-ci.org/commit/jenkins/21fb398bfa7068f6f72154763bdbb09baddf313d Log: JENKINS-24453ZD-20503 Incorporated a newer version of winp. This version checks the critical flag of the process, as killing such a process results in BSoD. (cherry picked from commit 040b7d4047b324f17c0971f2511f954eb173fa23) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/b105627b7357^...21fb398bfa70 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Michael Vincent
commented on JENKINS-24453
Jenkins server got blue screen to death
We've been running into this issue since at least March 2013. One out of our 5 nodes seems to blue screen every few days. I always figured it was something in Java or driver issue since I didn't think it was possible for a userspace program to crash the whole machine, so I just worked around it.
We're currently running Jenkins LTS 1.565.2 on a Linux master with Windows 7 64-bit slaves.
I have a complete crash dump (8.3 GB) from a BSOD today. Here's it's bugcheck analysis. I'm not familiar enough with Windows internals to really dig much deeper, but let me know if I can help debug further.
Kernel Complete Dump File: Full address space is available
Symbol search path is: srv*D:\MSSymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18229.amd64fre.win7sp1_gdr.130801-1533
Machine Name:
Kernel base = 0xf800`03049000 PsLoadedModuleList = 0xf800`0328c6d0
Debug session time: Thu Sep 25 13:58:37.568 2014 (UTC - 5:00)
System Uptime: 2 days 1:04:26.686
Loading Kernel Symbols
...
Loading User Symbols
...
Loading unloaded module list
Unable to enumerate user-mode unloaded modules, NTSTATUS 0xC147
***
* *
*Bugcheck Analysis*
* *
***
Use !analyze -v to get detailed debugging information.
BugCheck F4, {3, fa800aa49060, fa800aa49340, f800033c50d0}
*** ERROR: Symbol file could not be found. Defaulted to export symbols for winp.x64.FEF9CB80B43534DCA303AC36686258E8.dll -
Probably caused by : _
Followup: MachineOwner
-
2: kd !analyze -v
***
* *
*Bugcheck Analysis*
* *
***
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0003, Process
Arg2: fa800aa49060, Terminating object
Arg3: fa800aa49340, Process image file name
Arg4: f800033c50d0, Explanatory message (ascii)
Debugging Details:
--
PROCESS_OBJECT: fa800aa49060
IMAGE_NAME: _
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: _
FAULTING_MODULE:
PROCESS_NAME: java.exe
BUGCHECK_STR: 0xF4_java.exe
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from f8000344cd92 to f800030beb80
STACK_TEXT:
f880`072b89c8 f800`0344cd92 : `00f4 `0003 fa80`0aa49060 fa80`0aa49340 : nt!KeBugCheckEx
f880`072b89d0 f800`033f91db : ` fa80`10987b50 fa80`0aa49060 fa80`0a3ccb30 : nt!PspCatchCriticalBreak+0x92
f880`072b8a10 f800`03378ec4 : ` `0001 fa80`0aa49060 `0008 : nt! ?? ::NNGAKEGL::`string'+0x17476
f880`072b8a60 f800`030bde13 : fa80`0aa49060 ` fa80`10987b50 ` : nt!NtTerminateProcess+0xf4
f880`072b8ae0 `770c157a : 07fe`fd35402f ` ` `12c2ec30 : nt!KiSystemServiceCopyEnd+0x13
`12c2e998 07fe`fd35402f : ` ` `12c2ec30 `0ab0 : ntdll!NtTerminateProcess+0xa
`12c2e9a0 07fe`fa3c193c : `075c `0001 ` `075c :
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon commented on JENKINS-24453 Jenkins server got blue screen to death Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html http://jenkins-ci.org/commit/jenkins/d000cd65a7b0152334532bc7abd148095d5cee09 Log: FIXED JENKINS-24453 The actual fix is made in 040b7d4047b324f17c0971f2511f954eb173fa23 through winp. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
SCM/JIRA link daemon resolved JENKINS-24453 as Fixed Jenkins server got blue screen to death Change By: SCM/JIRA link daemon (23/Sep/14 8:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Kohsuke Kawaguchi commented on JENKINS-24453 Jenkins server got blue screen to death csrss.exe wouldn't have the right environment variables, so it should never match the killing criteria. In 1.583 we made a change to winp so that at least it won't terminate a critical process, but we'll likely still have to figure out why that process was selected as a target of killing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
dogfood commented on JENKINS-24453 Jenkins server got blue screen to death Integrated in jenkins_main_trunk #3700 FIXED JENKINS-24453 (Revision d000cd65a7b0152334532bc7abd148095d5cee09) Result = SUCCESS kohsuke : d000cd65a7b0152334532bc7abd148095d5cee09 Files : changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death This issue is not seen after upgrade jenkins to 1.565.1. But we are seeing download issue on 1.565.1. See https://issues.jenkins-ci.org/browse/JENKINS-23868?focusedCommentId=211163#comment-211163 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Still see this issue on Jenkins ver. 1.532.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Could you please let me know how to run a normal user(not administrator)run jenkins? I followed the guide but it failed: http://technet.microsoft.com/en-us/library/cc787533%28v=WS.10%29.aspx Currently this crash issue happens more than once a day... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death I took a look at the windows dump file, the blue screen is caused by java.exe which called jenkins. GetPointerFromAddress: unable to read from f800018be000 PROCESS fa804b96db30 SessionId: none Cid: 053cPeb: 7fd5000 ParentCid: 04f8 DirBase: 82c93e000 ObjectTable: f8a001823860 HandleCount: Data Not Accessible Image: java.exe VadRoot fa804bdb6680 Vads 972 Clone 0 Private 744164. Modified 258616. Locked 58. DeviceMap f8a0019d4cc0 Token f8a001c0da30 ReadMemory error: Cannot get nt!KeMaximumIncrement value. f780: Unable to get shared data ElapsedTime 00:00:00.000 UserTime 00:00:00.000 KernelTime00:00:00.000 QuotaPoolUsagePagedPool 0 QuotaPoolUsageNonPagedPool 0 Working Set Sizes (now,min,max) (746794, 50, 345) (2987176KB, 200KB, 1380KB) PeakWorkingSetSize747257 VirtualSize 20052 Mb PeakVirtualSize 20075 Mb PageFaultCount1577231 MemoryPriorityBACKGROUND BasePriority 8 CommitCharge 1015778 Error in reading nt!_ETHREAD @ fa804b971a30 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death No we did almost all of the tasks on slave jobs and the only job on master does not even run when this issue happen and does not have progress killing related command. I believe this might problably related to the last two LFS version. We plan to do a downgrade to 1.532.3 next Monday(we stayed on this version for months and didn't see this issue) to check this issue will be gone or not. Currently even if I delete this dll, it will be generated again automatically. And I don't find a hint which job might trigger it yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Oleg Nenashev commented on JENKINS-24453 Jenkins server got blue screen to death @sharon Does that mean the latest 1.556.1 still has this issue? Most probably, the answer is yes. BTW, I cannot find any similar issues in Jenkins JIRA, hence I suppose that the issue does not appear on every Windows installation. Probably, it is somehow related to your system configurations or jobs running on the master node (they have Administrator privileges as well) Is it OK if I remove winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll from the WEB-INF/lib folder? No. You'll just corrupt the Jenkins installation with the unpredictable further behavior This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia created JENKINS-24453 Jenkins server got blue screen to death Issue Type: Bug Assignee: Unassigned Components: core Created: 27/Aug/14 1:43 AM Description: Jenkins Server get blue screen to death crash about twice a day. After sending the dump to microsoft, it turns out there The Java related binary D:\Jenkins_CI\war\WEB-INF\lib\winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll has called to Terminate the csrss.exe and csrss.exe is a critical process since it was called to Terminate this process the machine Bug Checked. What is CSRSS.EXE? This is the user-mode portion of the Win32 subsystem (with Win32.sys being the kernel-mode portion). Csrss stands for client/server run-time subsystem and is an essential subsystem that must be running at all times. Csrss is responsible for console windows, creating and/or deleting threads, and some parts of the 16-bit virtual MS-DOS environment Due Date: 27/Aug/14 12:00 AM Environment: Windows Server 2008 R2; VMware; Project: Jenkins Labels: jenkins winp Priority: Major Reporter: sharon xia This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death System Properties Name ↓ Value awt.toolkit sun.awt.windows.WToolkit executable-war D:\Jenkins_CI\jenkins.war file.encoding Cp1252 file.encoding.pkg sun.io file.separator \ hudson.diyChunking true hudson.lifecycle hudson.lifecycle.WindowsServiceLifecycle java.awt.graphicsenv sun.awt.Win32GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.awt.windows.WPrinterJob java.class.path D:\Jenkins_CI\jenkins.war java.class.version 51.0 java.endorsed.dirs C:\Program Files\Java\jre7\lib\endorsed java.ext.dirs C:\Program Files\Java\jre7\lib\ext;C:\Windows\Sun\Java\lib\ext java.home C:\Program Files\Java\jre7 java.io.tmpdir C:\Users\ADMINI~1\AppData\Local\Temp\ java.library.path C:\Program Files\Java\jre7\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin;C:\Python27;C:\Program Files (x86)\Git\bin;. java.runtime.name Java(TM) SE Runtime Environment java.runtime.version 1.7.0_60-b19 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_60 java.vm.info mixed mode java.vm.name Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.60-b09 javamelody.analytics-id UA-1335263-7 javamelody.gzip-compression-disabled true javamelody.http-transform-pattern /\d+/|/site/.|avadoc/.|/ws/.|obertura/.|estReport/.|iolations/file/.|/user/.|/static/\w/ javamelody.no-database true javamelody.storage-directory /D:\Jenkins_CI\monitoring javamelody.system-actions-enabled true line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Windows Server 2008 R2 os.version 6.1 path.separator ; pid 1340 sun.arch.data.model 64 sun.awt.enableExtraMouseButtons true sun.boot.class.path C:\Program Files\Java\jre7\lib\resources.jar;C:\Program Files\Java\jre7\lib\rt.jar;C:\Program Files\Java\jre7\lib\sunrsasign.jar;C:\Program Files\Java\jre7\lib\jsse.jar;C:\Program Files\Java\jre7\lib\jce.jar;C:\Program Files\Java\jre7\lib\charsets.jar;C:\Program Files\Java\jre7\lib\jfr.jar;C:\Program Files\Java\jre7\classes sun.boot.library.path C:\Program Files\Java\jre7\bin sun.cpu.endian little sun.cpu.isalist amd64 sun.desktop windows sun.io.unicode.encoding UnicodeLittle sun.java.command D:\Jenkins_CI\jenkins.war --httpPort=8080 --httpsPort=443 --httpsKeyStore=D:\Jenkins_CI\jre\bin\jenkins.jks --httpsKeyStorePassword=** sun.java.launcher SUN_STANDARD sun.jnu.encoding Cp1252 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level Service Pack 1 svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false svnkit.symlinks false user.country US user.dir D:\Jenkins_CI user.home C:\Users\Administrator user.language en user.name Administrator user.script user.timezone America/New_York user.variant Environment Variables Name ↓ Value ALLUSERSPROFILE C:\ProgramData APPDATA C:\Users\Administrator\AppData\Roaming BASE D:\Jenkins_CI CommonProgramFiles C:\Program Files\Common Files CommonProgramFiles(x86) C:\Program Files (x86)\Common Files CommonProgramW6432 C:\Program Files\Common Files COMPUTERNAME WIN2K8-R2-0 ComSpec C:\Windows\system32\cmd.exe FP_NO_HOST_CHECK NO JAVA_HOME C:\Program Files (x86)\Java\jre7\bin JENKINS_HOME D:\Jenkins_CI LOCALAPPDATA C:\Users\Administrator\AppData\Local NUMBER_OF_PROCESSORS 12 OS Windows_NT Path C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Java\jre7\bin;C:\Python27;C:\Program Files (x86)\Git\bin PATHEXT .COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC PROCESSOR_ARCHITECTURE AMD64 PROCESSOR_IDENTIFIER Intel64 Family 6 Model 44 Stepping 2, GenuineIntel PROCESSOR_LEVEL 6 PROCESSOR_REVISION 2c02 ProgramData C:\ProgramData ProgramFiles C:\Program Files ProgramFiles(x86) C:\Program Files (x86) ProgramW6432 C:\Program Files PSModulePath C:\Windows\system32\WindowsPowerShell\v1.0\Modules\ PUBLIC C:\Users\Public SystemDrive C: SystemRoot C:\Windows TEMP
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Daniel Beck commented on JENKINS-24453 Jenkins server got blue screen to death Please specify your Jenkins version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Daniel Beck commented on JENKINS-24453 Jenkins server got blue screen to death Also, it helps if you're not running Jenkins as Local System or a similarly privileged user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Jenkins Version: Jenkins ver. 1.554.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Actually we are running Jenkins as Local System account "Administrator", does it matter? Will this trigger this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Do you mean if we do not run it as Local System then we can get more debugging information or it will trigger this issue? For now I have to move the winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll out of the WEN-INF/lib folder, however I am not sure what plugin or what function of jenkins will rely on it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Daniel Beck commented on JENKINS-24453 Jenkins server got blue screen to death If you run Jenkins as an unprivileged user it doesn't get to kill csrss, so yes, that should be a workaround. winp is used as a process killer, usually however only for processes that are started in your builds. This is designed as regular "clean up" after a build finishes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death However when I installed the newest LTS version of jenkins it does not have this dll in it. Do you know which plugin/version might use it? Does it work if I upgrade my jenkins to the latest one 1.556.1? Also, By default the jenkins will run as Local System and we didn't have this issue before for several years. Why it turns out only recently? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
Daniel Beck commented on JENKINS-24453 Jenkins server got blue screen to death winp is used by Jenkins core, only indirectly by plugins. There have been a few changes to winp/process killing recently. As I don't use Windows I cannot say for sure what the current status is, generally, killing processes has always been a bit brittle/prone to error. In this case, the fix for JENKINS-22685 comes to mind as a potential candidate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24453) Jenkins server got blue screen to death
sharon xia commented on JENKINS-24453 Jenkins server got blue screen to death Does that mean the latest 1.556.1 still has this issue? Is it OK if I remove winp.x64.35A3F35D2ED629A6CEC5B41DD1D280C3.dll from the WEB-INF/lib folder? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
