[JIRA] (JENKINS-45355) Input without permissions or not logged in, shows no message

2020-01-09 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-45355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Input without permissions or not logged in, shows no message   
 

  
 
 
 
 

 
 I've run into something similar to this as well, when not using a submitter list, when users that have Job.READ but not Job.BUILD click the button. (don't think it matters, but this is a specialized job with a security matrix blocking the default inheritance.) Clicking will cause the 'proceed' button to grey / disable, but when the request 500s, no feedback to the user occurs. Weirdly, despite 500-ing, I can't find the error in jenkins's system log, either. Jenkins 2.204.1 and pipeline-input-step 2.11. I can try creating a simple reproducer case if you'd like, but it will be a bit.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183506.1499422981000.5959.1578599400222%40Atlassian.JIRA.


[JIRA] (JENKINS-53858) Deadlock on EC2 resources

2018-11-08 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on EC2 resources   
 

  
 
 
 
 

 
 I put up another PR to hopefully take care of the reentrantlock being null and another NPE I saw.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-53858) Deadlock on EC2 resources

2018-10-16 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53858  
 
 
  Deadlock on EC2 resources   
 

  
 
 
 
 

 
Change By: 
 Mason Donahue  
 
 
Environment: 
 Jenkins v2.144, ubuntu 14.04, ec2-plugin 1.38, 1.39, 1.40-SNAPSHOT (private-160d794a-masondonahue) , 1.40.1  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-53858) Deadlock on EC2 resources

2018-10-08 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on EC2 resources   
 

  
 
 
 
 

 
 We are currently using one cloud, but multiple configurations within that (same AMI, but machine types and labels differ).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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] (JENKINS-53858) Deadlock on EC2 resources

2018-10-04 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on EC2 resources   
 

  
 
 
 
 

 
 And as for the actual objects being held: 

 

Oct 04, 2018 4:34:47 PM jenkins.metrics.api.Metrics$HealthChecker execute
WARNING: Some health checks are reporting as unhealthy: [thread-deadlock : [jenkins.util.Timer [#8] locked on hudson.plugins.ec2.AmazonEC2Cloud@61f05bdb (owned by jenkins.util.Timer [#9]):
   at hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:673)
   at hudson.plugins.ec2.EC2AbstractSlave.stop(EC2AbstractSlave.java:314)
   at hudson.plugins.ec2.EC2AbstractSlave.idleTimeout(EC2AbstractSlave.java:362)
   at hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:126)
   at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:88)
   at hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:46)
   at hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:72)
   at hudson.model.Queue._withLock(Queue.java:1380)
   at hudson.model.Queue.withLock(Queue.java:1257)
   at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:63)
   at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
   at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
   at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
   at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
   at java.lang.Thread.run(Thread.java:748)
, jenkins.util.Timer [#9] locked on java.util.concurrent.locks.ReentrantLock$NonfairSync@731b93cc (owned by jenkins.util.Timer [#8]):
   at sun.misc.Unsafe.park(Native Method)
   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
   at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
   at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
   at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
   at hudson.model.Queue._withLock(Queue.java:1437)
   at hudson.model.Queue.withLock(Queue.java:1300)
   at jenkins.model.Nodes.updateNode(Nodes.java:193)
   at jenkins.model.Jenkins.updateNode(Jenkins.java:2077)
   at hudson.model.Node.save(Node.java:140)
   at hudson.util.PersistedList.onModified(PersistedList.java:173)
   at hudson.util.PersistedList.replaceBy(PersistedList.java:85)
   at hudson.model.Slave.(Slave.java:198)
   at hudson.plugins.ec2.EC2AbstractSlave.(EC2AbstractSlave.java:134)
   at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:49)
   at hudson.plugins.ec2.EC2OndemandSlave.(EC2OndemandSlave.java:42)
   at 

[JIRA] (JENKINS-53858) Deadlock on EC2 resources

2018-10-04 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-53858  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Deadlock on EC2 resources   
 

  
 
 
 
 

 
 Just an update with a stackdump from 1.40.1: 

 

10/4/18 2:34 PM

= Threads on dev-jenkins-master-useast1b-01@172.25.33.234 =

Warning, the following threads are deadlocked : GitHubPushTrigger [#4], jenkins.util.Timer [#2], jenkins.util.Timer [#9]

"GitHubPushTrigger [#4]" prio=5 WAITING
	sun.misc.Unsafe.park(Native Method)
	java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
	java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:209)
	java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:285)
	hudson.model.Queue.schedule2(Queue.java:587)
	jenkins.model.ParameterizedJobMixIn.scheduleBuild2(ParameterizedJobMixIn.java:156)
	jenkins.model.ParameterizedJobMixIn.scheduleBuild(ParameterizedJobMixIn.java:116)
	jenkins.model.ParameterizedJobMixIn.scheduleBuild(ParameterizedJobMixIn.java:105)
	com.cloudbees.jenkins.GitHubPushTrigger$1.run(GitHubPushTrigger.java:143)
	hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:119)
	java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	java.util.concurrent.FutureTask.run(FutureTask.java:266)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	java.lang.Thread.run(Thread.java:748)

"jenkins.util.Timer [#2]" daemon prio=5 BLOCKED
	hudson.plugins.ec2.EC2Cloud.connect(EC2Cloud.java:673)
	hudson.plugins.ec2.EC2AbstractSlave.stop(EC2AbstractSlave.java:314)
	hudson.plugins.ec2.EC2AbstractSlave.idleTimeout(EC2AbstractSlave.java:362)
	hudson.plugins.ec2.EC2RetentionStrategy.internalCheck(EC2RetentionStrategy.java:126)
	hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:88)
	hudson.plugins.ec2.EC2RetentionStrategy.check(EC2RetentionStrategy.java:46)
	hudson.slaves.ComputerRetentionWork$1.run(ComputerRetentionWork.java:72)
	hudson.model.Queue._withLock(Queue.java:1380)
	hudson.model.Queue.withLock(Queue.java:1257)
	hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:63)
	hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
	jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58)
	java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
	java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
	java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
	java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	java.lang.Thread.run(Thread.java:748)

"jenkins.util.Timer [#9]" daemon prio=5 WAITING
	sun.misc.Unsafe.park(Native Method)
	java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
	java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
	

[JIRA] (JENKINS-53858) Deadlock on EC2 resources

2018-10-01 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53858  
 
 
  Deadlock on EC2 resources   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 FABRIZIO MANFREDI  
 
 
Components: 
 ec2-plugin  
 
 
Created: 
 2018-10-01 18:46  
 
 
Environment: 
 Jenkins v2.144, ubuntu 14.04, ec2-plugin 1.38, 1.39, 1.40-SNAPSHOT (private-160d794a-masondonahue)  
 
 
Labels: 
 deadlock  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Mason Donahue  
 

  
 
 
 
 

 
 We seem to be running into an issue about once per day where multiple threads deadlock trying to access and update resources within the EC2 plugin. We have several jobs that add substantial numbers of subjobs (~40) to the build queue, and they thus invoke the Pipeline step `ec2 cloud: 'AWS Cloud', template: 'Micro'` several times to preallocate enough EC2 nodes to run them all (though it looks like this behavior will no longer be necessary in ec2-plugin 1.40). In addition, it seems that manually provisioning a node through the UI or manually deleting a node has a chance of deadlocking if it runs at the same time as the provisioning or unprovisioning process happens.   The following stacktrace shows the three threads running in 1.40-SNAPSHOT (master as of Friday afternoon). 

 

Warning, the following threads are deadlocked : Handling POST /job/Selenium%20Tests/job/PAID-1256%252Fenable-paid-tests/build from 172.26.3.39 : qtp125130493-18700, jenkins.util.Timer [#3], jenkins.util.Timer [#6]

 "jenkins.util.Timer [#3]" daemon 

[JIRA] (JENKINS-52307) BlueOcean: Loading of jobs in top-level raises javascript error

2018-08-03 Thread ma...@sproutsocial.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mason Donahue commented on  JENKINS-52307  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BlueOcean: Loading of jobs in top-level raises _javascript_ error   
 

  
 
 
 
 

 
 Howdy, I was seeing a similar problem with the home page with the latest blueocean release that went away when I deleted the job in question (a maven job), which may show another place where error handling is needed: I'm running 1.7.1 · Core 2.135 · fcec860  · 18th July 2018 01:16 PM, and this is a Jenkins server that has had a lot of history come through it, and maybe wasn't fully consistent   

 

Aug 03, 2018 5:15:45 PM WARNING io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValueAug 03, 2018 5:15:45 PM WARNING io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1 getValueFailed to get "_links" from a io.jenkins.blueocean.service.embedded.rest.AbstractPipelineImpl$1io.jenkins.blueocean.commons.ServiceException$NotFoundException: Run 2014-10-09_20-01-26 not found in organization jenkins and pipeline Brand mention activity monitor at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:72) at io.jenkins.blueocean.service.embedded.rest.RunContainerImpl.get(RunContainerImpl.java:40) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolveRun(LinkResolverImpl.java:63) at io.jenkins.blueocean.service.embedded.LinkResolverImpl.resolve(LinkResolverImpl.java:42) at io.jenkins.blueocean.rest.hal.LinkResolver.resolveLink(LinkResolver.java:32) at io.jenkins.blueocean.service.embedded.rest.AbstractRunImpl.getLinks(AbstractRunImpl.java:360) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72)Caused: java.lang.reflect.InvocationTargetException at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:74) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:167) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:303) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:154) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:148) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:136) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:79) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:70) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at