[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick created an issue Jenkins / JENKINS-42180 JS errors and 403s prevent configuring project properly Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Feb/19 8:00 PM Environment: Jenkins 2.46 on Ubuntu 16.04.2 LTS, affects all browsers tested on OSX Labels: configuration project Priority: Blocker Reporter: rherrick I'm trying to configure a multiproject Gradle build on Jenkins 2.46. Anything that requires adding a panel is failing. For example, adding additional behaviors in SCM section fails, so I can't specify advanced submodules behaviors. I also can't add build or post-build actions. When I first load the configure page for the project, I get these errors (i.e. I'm not doing anything, just opening the project): configure:1 This page includes a password or credit card input in a non-secure context. A warning will be added to the URL bar in Chrome 56 (Jan 2017). For more information, see https://goo.gl/zmWq3m. hudson-behavior.js:417 Uncaught TypeError: Cannot read property 'firstChild' of undefined at registerValidator (/static/b7508750/scripts/hudson-behavior.js:417:66) at Array.forEach (native) at /static/b7508750/scripts/behavior.js:111:30 at Array.forEach (native) at /static/b7508750/scripts/behavior.js:107:27 at Array.forEach (native) at Object.applySubtree (/static/b7508750/scripts/behavior.js:93:17)
[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly No, I'm using the same URL that's set in Configure System. I am using nginx in front of Jenkins running as a stand-alone application (i.e. not as a war in Tomcat), but I don't have the broken reverse proxy message. I just updated to 2.47, cleared my cookies and cache, and am still seeing the problem. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly I can get things working again properly if I turn "Prevent Cross Site Request Forgery exploits" OFF on the "Configure Global Security" page. If I turn it on, the only option I have for "Crumb Algorithm" is "Default Crumb Issuer". So I select that and then it doesn't matter if I have "Enable proxy compatibility" checked or not, I see the same failure. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly In the nginx access logs, I see the following when I reload a project page: 172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/a4338d24-8ef6-4b36-a45e-dba6f4b8139f/render HTTP/1.1" 403 305 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806" 172.1.54.116 - - [21/Feb/2017:19:42:07 -0500] "POST /$stapler/bound/ab8ee004-37cc-4e2b-8d49-3802040cdf60/render HTTP/1.1" 403 304 "/job/XNAT%20S3/configure" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 OPR/43.0.2442.806" Those are the only 403s I see on the page load, everything else is 200. There are no entries in the nginx error.log. In the jenkins.log, I get these messages: Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a. Will check remaining parameters for a valid one... Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /$stapler/bound/d29a127d-6455-4b93-80b3-653dc55aeaa7/render. Returning 403. Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: Found invalid crumb ebd8053576b9c79716223a4d305f753a, ebd8053576b9c79716223a4d305f753a. Will check remaining parameters for a valid one... Feb 21, 2017 7:46:52 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /$stapler/bound/8ff58aec-9694-4c5f-b3a3-4906160a9176/render. Returning 403. I can capture the full HTTP request/response cycle with Charles if that'd be helpful. Add Comment
[JIRA] (JENKINS-42180) JS errors and 403s prevent configuring project properly
Title: Message Title rherrick commented on JENKINS-42180 Re: JS errors and 403s prevent configuring project properly Yes, if you can give me some pointers on where to look. I've poked through it a bit and can see the crumb token getting added to the request headers but I'm not sure to look to see it being doubled up. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-24869) POM_VERSION is not resetted
Title: Message Title rherrick commented on JENKINS-24869 Re: POM_VERSION is not resetted I'm still getting this issue on Jenkins v2.51 with Maven integration plugin v2.15.1. This makes the integration plugin almost useless. I'm trying to tie the RELEASE_VERSION setting to the Maven version property (pretty reasonable) and imagine my surprise when the new release has the last version. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-24869) POM_VERSION is not resetted
Title: Message Title rherrick edited a comment on JENKINS-24869 Re: POM_VERSION is not resetted I'm still getting this issue on Jenkins v2.51 with Maven integration plugin v2.15.1. This makes the integration plugin almost useless. I'm trying to tie the RELEASE_VERSION setting to the Maven version property (pretty reasonable) and imagine my surprise when the new release has the last version. It looks to me like the problem is that it's setting the POM properties _before_ pulling from VCS. I re-ran my release build and this time got the updated version. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick created an issue Jenkins / JENKINS-49538 Release plugin doesn't appear at all Issue Type: Bug Assignee: Oleg Nenashev Attachments: Screen Shot 2018-02-13 at 11.45.47 AM.png, Screen Shot 2018-02-13 at 11.50.04 AM.png Components: release-plugin Created: 2018-02-13 17:57 Environment: CentOS 7.4.1708, Jenkins ver. 2.106, Release plugin v2.10 Priority: Major Reporter: rherrick We've had the release plugin working on our Jenkins installation for quite a while and used the lastSuccessfulReleaseBuild permalink as a way to publish our downloads. A couple weeks ago this just stopped working. I'm not sure if it was the upgrade to v2.10 or not, although that happened in close proximity time-wise to when the problem started occurring. When I started looking into it, I realized that nothing from the release plugin was working: we don't have the lastSuccessfulReleaseBuild permalink, the Release option is no longer available in pop-ups, and previous release builds are no longer marked as release builds (although they are still marked as "keep forever"). I included a screen shot of one of our projects where you can see the lack of lastSuccessfulReleaseBuild permalink as well as a build marked "keep forever" that was our previous 1.7.4.1 release. I've tried removing the release plugin and reinstalling it with no change. I've removed it, completely deleted it from the plugins folder (release.jpi, release.hpi.pinned and the release folder), and reinstalled it. No change. There are no errors relating to the release plugin in the jenkins.log that I can se
[JIRA] (JENKINS-49538) Release plugin doesn't appear at all
Title: Message Title rherrick updated an issue Jenkins / JENKINS-49538 Release plugin doesn't appear at all Change By: rherrick Attachment: health-checker.log Attachment: jenkins.log Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick commented on JENKINS-49538 Re: Release plugin doesn't appear at all Oleg Nenashev No, nothing other than a couple of innocuous warnings. I've attached the contents of jenkins.log and health-checker.log recorded from start-up. The words "error", "warn", and "release" don't appear in any files in the ~jenkins/logs folder at all. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-49538) Release plugin doesn't appear at all
Title: Message Title rherrick closed an issue as Not A Defect It turns out the problem was a rogue Puppet configuration that was configured to "restore" our Jenkins job configurations. Unfortunately it was "restoring" to a configuration that didn't have "Configure release build" turned on. So every time I'd work on the job configuration, Puppet would overwrite all my work. Sorry for the false alarm Jenkins / JENKINS-49538 Release plugin doesn't appear at all Change By: rherrick Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5548.1558372860565%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5558.1558373880261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5579.1558373944205%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5565.1558373941277%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick updated an issue Jenkins / JENKINS-57244 java.io.NotSerializableException: The calling thread Thread has no associated channel Change By: rherrick Attachment: jenkins.log.gz 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199007.1556619184000.5572.1558373942099%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57244) java.io.NotSerializableException: The calling thread Thread has no associated channel
Title: Message Title rherrick commented on JENKINS-57244 Re: java.io.NotSerializableException: The calling thread Thread has no associated channel This issue is absolutely killing our build server. It's appearing in many different contexts, including getting build configurations, viewing jobs, running executors, routine maintenance tasks like fingerprint cleanup, etc. There have been 4,707 occurrences in just the last three hours: jenkins.log is 32MB (attached compressed jenkins.log.gz). Jenkins is at 2.178. I keep upgrading hoping that this will be fixed but clearly it's not. If there's a single plugin causing the problem, I'd be happy to uninstall it but, as I noted, it's happening for lots of different operations. The biggest problem is that it's blocking the credentials store functionality, so projects that already have credentials configured have a warning "Cannot find any credentials with id ". The only options available in the credentials drop-down list are "current" and "none". If I set the credentials to "none" and save the configuration, then the only option available is "none". At some point the following message is logged: 2019-05-20 14:36:05.974+ [id=10] WARNING hudson.FilePath#_getChannelForSerialization: A FilePath object is being serialized when it should not be, indicating a bug in a plugin. See https://jenkins.io/redirect/filepath-serialization for details. java.io.NotSerializableException: The calling thread Thread[Handling GET /credentials/store/system/domain/_/credential// from __ : __ CredentialsStoreAction/CredentialsWrapper/index.jelly,5,main] has no associated channel. The current object null is interface org.jenkinsci.remoting.SerializableOnlyOverRemoting, but it is likely being serialized/deserialized without the channel I've got builds limping along now after dealing with weird conflicts from the authorize project plugin that may or may not be related to this issue, but I would really like a fix to this both so we can configure credentials on projects without having to edit config.xml files and to declutter the log files so that we can see any other issues that may occur. Add Comment This message was sent by Atlassi
