[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API
Title: Message Title Michael Vincent commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Folder ownership from CLI/REST API FYI, I had to roll back to 0.11 to work around the createItem() issue. Hopefully it can be resolved soon Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Michael Vincent commented on JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error Based on my analysis so far, I'm certain this is an msys (or Windows?) bug. Jenkins' usage patterns are quite different from a typical developer using git manually and I think that's what's causing issue to show up. Using Jenkins credentials is an interesting idea! I can see how that would enable ssh to work even with a corrupt environment. Running other git commands from a build script might still run into issues with a corrupt environment though. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20750) Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error
Michael Vincent commented on JENKINS-20750 Git plugin 2.0 sometimes fail to fetch (timeouts) with weird error I've run into this as well. It has something to do with concurrent msys processes. I've reported my findings to the msys and msysgit mailing lists. I haven't had time to really dig into it and figure out what's going on. I've done a few things to try and work around the issue: Minimized concurrent jobs on each node. Matrix jobs in particular tend to cause more issues. Replaced all shell scripts in jobs with Python scripts. Windows batch scripts were also an option, but Windows batch scripting is absolutely terrible. Jobs often need to run additional git commands to properly clean the repository, deal with deleted submodules, etc. I run all of these through the following Python function that checks for a corrupt environment and aborts instead of just hanging. def print_exec_corrupt_check(args): """Prints a command to be executed and then executes it """ cmdline = " ".join(args) print "" print "Exec:", cmdline print sys.stdout.flush() # Add an environment check before the command cmdline = r'if [ ! -r "$HOME" ]; then echo "Corrupt environment detected, aborting..."; exit 1; fi; ' + cmdline subprocess.check_call([r'C:\Program Files (x86)\Git\bin\bash.exe', r'-c', cmdline], bufsize=-1) print sys.stdout.flush() Possible future workarounds: Split matrix jobs out into individual jobs using the DSL plugin. Switch Jenkins to jgit. If jgit isn't mature enough yet, then maybe try Dulwich/Gittle. Fix the issue in msys. 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/groups/opt_out.
[JIRA] [managed-scripts] (JENKINS-18496) Exception caused by quotes in the shebang line of shell scripts
Michael Vincent created JENKINS-18496 Exception caused by quotes in the shebang line of shell scripts Issue Type: Bug Assignee: domi Components: managed-scripts Created: 25/Jun/13 10:30 PM Description: Exception: executing script 'Post-SCM-git-submodule-update-and-clean' [Job] $ "C:\Program Files (x86)\Git\bin\bash.exe" -e C:\Users\HANDSE~1\AppData\Local\Temp\build_step_template2413741568138346591.sh FATAL: Caught exception while loading script 'Post-SCM-git-submodule-update-and-clean' java.lang.IllegalArgumentException: Executable name has embedded quote, split the arguments at java.lang.ProcessImpl.isQuoted(Unknown Source) at java.lang.ProcessImpl.getExecutablePath(Unknown Source) at java.lang.ProcessImpl.init(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) at java.lang.ProcessBuilder.start(Unknown Source) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:763) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:988) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:955) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Build step 'Execute managed script' marked build as failure Contents of the managed script: #!"C:\Program Files (x86)\Git\bin\bash.exe" -e git fetch origin git submodule update --recursive --init git clean -ffdx git submodule foreach --recursive 'git clean -ffdx; git reset --hard' Java 7u21 has changed the way quotes are handled by Runtime.exec() on Windows: http://www.oracle.com/technetwork/java/javase/7u21-relnotes-1932873.html#jruntime Downgrading the slaves to Java 7u17 fixed the problem. I suppose I could have used PROGRA~2 instead of the quotes, but that's pretty ugly. I've placed this issue in the managed-scripts component because I haven't experienced the same issue with regular "Execute Shell" build steps. Environment: Jenkins LTS 1.509.1 Master on Linux, slaves on Windows 7 Slaves running JRE 7u21 Managed script plugin 1.1 Using bash from msysgit 1.8.0 Project: Jenkins Labels: exception windows Priority: Minor Reporter: Michael Vincent 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/groups/opt_out.
