[JIRA] (JENKINS-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Sam Van Oort thanks - back up and running 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Sam Van Oort commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Simon Watts This is a known and now-fixed issue, resolved in the latest workflow-cps releases and verified to resolve the issue. Two strategies to get a stable system to apply the update: if you shutdown your Jenkins and go into the FlowExecutionList.xml you will find a list of builds there and can hunt down and delete the builds – this will prevent them resuming upon restart. You'll want to update plugins ASAP though in case new builds get triggered. Alternately, since you were pretty much up to date otherwise, you should be able to grab the latest workflow-cps plugin and drop it in /plugins/ (replacing the existing one). No new dependencies were added in the last 2 releases. 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Sam Van Oort closed an issue as Duplicate Jenkins / JENKINS-51241 Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts edited a comment on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. We just restarted the Jenkins service. I managed to get into the web front end briefly, but it then hung again (so about 10 minutes since restart, and only a couple of minutes on the gui).Possible that there is an on-going job which regenerates the deadlock when the service restarts? Is there a way to stop jobs without access to the web or REST? I would like to abort the jobs listed in connection with the deadlock.Also to note: Plugins were all up-to-date as of *4 May 2018* at 10:40 hrs (UTC+1) .I note that there have been updates to pipeline plugins since that time, but if I cannot access the GUI or REST it is going to be hard to update them... 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts edited a comment on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. We just restarted the Jenkins service. I managed to get into the web front end briefly, but it then hung again (so about 10 minutes since restart, and only a couple of minutes on the gui).Possible that there is an on-going job which regenerates the deadlock when the service restarts? Is there a way to stop jobs without access to the web or REST? I would like to abort the jobs listed in connection with the deadlock. Also to note: Plugins were all up-to-date as of *4 May 2018* at 10:40 hrs.I note that there have been updates to pipeline plugins since that time, but if I cannot access the GUI or REST it is going to be hard to update them... 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. We just restarted the Jenkins service. I managed to get into the web front end briefly, but it then hung again (so about 10 minutes since restart, and only a couple of minutes on the gui). Possible that there is an on-going job which regenerates the deadlock when the service restarts? Is there a way to stop jobs without access to the web or REST? I would like to abort the jobs listed in connection with the deadlock. 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Oleg Nenashev commented on JENKINS-51241 Re: Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. According to stacktraces it looks like a Pipeline issue. CC Sam Van Oort Andrew Bayer 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-51241 Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Change By: Oleg Nenashev Component/s: pipeline Component/s: core 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-51241) Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2.
Title: Message Title Simon Watts created an issue Jenkins / JENKINS-51241 Jenkins web interface - deadlock since u/g to 2.107.2 from 2.89.2. Issue Type: Improvement Assignee: Unassigned Attachments: jenkins-jheap.txt, jenkins-jinfo.txt, jenkins-jstack.txt Components: core Created: 2018-05-10 09:39 Environment: Jenkins 2.107.2 Red Hat Enterprise Linux Server release 6.6 (Santiago) x86_64 java version "1.8.0_51" Java(TM) SE Runtime Environment (build 1.8.0_51-b31) Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode) Priority: Critical Reporter: Simon Watts Since upgrading our Jenkins master from 2.89.2 to 2.107.2 (LTS) we have experienced the web interface becoming non-responsive (including jenkins-cli). Restarting the service clears the issue, but it keeps reappearing. SCM triggered builds appear to be continuing in the background. We did not experience this with the previous release. The stack trace reports a deadlock. Attached are the output from jinfo, jmap (heap), and jstack: jstack -l jmap -heap jinfo
