[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-16 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Issue Type: 
 Improvement Bug  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.8500.1571210400360%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-16 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 I did a lot of manual tests and the problem is always when support-core isn't yet installed. The problem isn't directly in advisor Ryan Campbell Otherwise we will have to see with Allan BURDAJEWICZ if we can isolate/fix the issue in support-core. The only thing I could try to do at the advisor level is to catch this error and ask to the administrator to restart the instance. For now the user is seeing this generic error in the Advisor config panel:    And this warning monitor (note to myself: they should be unified ...)  Note, that as soon the support-core is installed but the instance not restarted the logs are polluted with these errors   

 
Oct 16, 2019 8:49:05 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed
java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2
	at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450)
	at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47)
	at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402)
	at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80)
	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)

Oct 16, 2019 8:49:08 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@2656884b failed
java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2
	at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450)
	at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47)
	at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402)
	at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80)
	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.la

[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-16 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier stopped work on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.8497.1571209982133%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-16 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Attachment: 
 Screenshot 2019-10-16 09.00.42.png  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.8494.1571209320747%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-16 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Attachment: 
 Screenshot 2019-10-16 08.57.20.png  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.8490.1571209200250%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-15 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Component/s: 
 support-core-plugin  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.8488.1571208180308%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-14 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 As seen above and with Allan BURDAJEWICZ tests, the problem is perhaps in support-core and not in advisor ( JENKINS-59775 )   
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.7018.1571056020103%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-11 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 Allan BURDAJEWICZ could we discuss about this ?  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.6101.1570812960053%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 In fact doing 3/ with the current master code and not the patched one works too  Should I conclude that to install a plugin without restarting the master the best strategy is to upload it manually instead of installing it from the UC?  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3908.1570632780088%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 Pierre Beitz also found something similar done by Stephen Connolly a year ago: https://github.com/jenkinsci/metrics-plugin/blame/bb4a572004bb708136a57d2d359a930c934786b1/src/main/java/jenkins/metrics/impl/JenkinsMetricProviderImpl.java#L708-L721 https://issues.jenkins-ci.org/browse/JENKINS-28983 https://issues.jenkins-ci.org/browse/JENKINS-52072 But my tests are with 2.138 thus we should have the required fix in core And strangely I find ~ no plugin using @Extension(dynamicLoadable = YesNoMaybe.YES)   
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3898.1570631580065%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 3/ Jenkins 2.138.4 installed from scratch with suggested plugins. *I upload from the UI a patched version of the plugin* with all extensions and marked as loadable dynamically and it works. I can trigger an upload from the console. No issue. https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/50 But is it a test which is relevant compared to installations 1/ and 2/ done from the UC ?  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3893.1570630680218%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier edited a comment on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 More tests:1/ Jenkins 2.138.4 installed from scratch with suggested plugins.  *"  Install without Restart "*  adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing:{noformat}Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Started Bundle UploadOct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logErrorSEVERE: ERROR: Could not save support bundlejava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logSEVERE: ERROR: Unable to generate support bundleOct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Finished Bundle Upload. 8 msOct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) 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)Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecu

[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 2/ Jenkins 2.138.4 installed from scratch with suggested plugins. "Download now and install after restart" but adds Variant, Metrics and Support core plugins but all of them are "Downloaded Successfully. Will be activated during the next boot". We cannot use any of them before the next restart  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3867.1570626540089%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier edited a comment on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 More tests:1/ Jenkins 2.138.4 installed from scratch with suggested plugins. Install without Restart adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing:{noformat}Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Started Bundle UploadOct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logErrorSEVERE: ERROR: Could not save support bundlejava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96) at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71) at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101) at java.lang.Thread.run(Thread.java:748)Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logSEVERE: ERROR: Unable to generate support bundleOct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 runINFO: Finished Bundle Upload. 8 msOct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) 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)Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask runSEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failedjava.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2 at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450) at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47) at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402) at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorServic

[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-09 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 More tests: 1/ Jenkins 2.138.4 installed from scratch with suggested plugins. Install without Restart adds Variant, Metrics and Support core plugins. Going in Manage Jenkins allows to configure the plugin. Trying to trigger it using the Groovy Console is failing: 

 
Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Started Bundle Upload
Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload logError
SEVERE: ERROR: Could not save support bundle
java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2
	at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450)
	at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47)
	at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402)
	at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:291)
	at com.cloudbees.jenkins.plugins.advisor.BundleUpload.generateBundle(BundleUpload.java:96)
	at com.cloudbees.jenkins.plugins.advisor.BundleUpload.execute(BundleUpload.java:71)
	at hudson.model.AsyncPeriodicWork$1.run(AsyncPeriodicWork.java:101)
	at java.lang.Thread.run(Thread.java:748)

Oct 09, 2019 2:51:33 PM com.cloudbees.jenkins.plugins.advisor.BundleUpload log
SEVERE: ERROR: Unable to generate support bundle
Oct 09, 2019 2:51:33 PM hudson.model.AsyncPeriodicWork$1 run
INFO: Finished Bundle Upload. 8 ms
Oct 09, 2019 2:51:34 PM hudson.triggers.SafeTimerTask run
SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failed
java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2
	at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450)
	at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47)
	at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402)
	at com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker.doRun(SlowRequestChecker.java:80)
	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)

Oct 09, 2019 2:51:37 PM hudson.triggers.SafeTimerTask run
SEVERE: Timer task com.cloudbees.jenkins.support.slowrequest.SlowRequestChecker@63dd7a2 failed
java.lang.IllegalStateException: Expected 1 instance of com.cloudbees.jenkins.support.filter.ContentFilters but got 2
	at hudson.ExtensionList.lookupSingleton(ExtensionList.java:450)
	at com.cloudbees.jenkins.support.filter.ContentFilters.get(ContentFilters.java:47)
	at com.cloudbees.jenkins.support.SupportPlugin.getContentFilter(SupportPlugin.java:402)
	at com.cloudbees.jenkins.support.slowrequest.Slo

[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-08 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier started work on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3583.1570570860087%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-08 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier commented on  JENKINS-59696  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
 I took a clean 2.138.4, installed the plugin with `Install without restart` and the plugin isn't in the Manage Jenkins page I have the warning `Changes will take effect when you restart Jenkins`  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3575.1570569000447%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-08 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Change By: 
 Arnaud Héritier  
 
 
Priority: 
 Minor Major  
 

  
 
 
 
 

 
 
 

 
 
 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.202395.1570521598000.3176.1570521660313%40Atlassian.JIRA.


[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated

2019-10-08 Thread aherit...@apache.org (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arnaud Héritier created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59696  
 
 
  Jenkins Health Advisor requires to restart the instance to be activated   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Arnaud Héritier  
 
 
Components: 
 cloudbees-jenkins-advisor-plugin  
 
 
Created: 
 2019-10-08 07:59  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Arnaud Héritier  
 

  
 
 
 
 

 
 Right now the plugin requires to have the master restarted otherwise (often?) it doesn't start to send bundles. We want to verify if we could fix this issue (it's painful to have to restart an instance to install a plugin)   I suppose the issue could come from the instanciation/activation of the AsyncPeriodicWork task https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/advisor/BundleUpload.java Is there any good practices to follow ? Any sample of such AsyncPeriodicWork extensions which aren't requiring to restart the master ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment