Upgrading Digital Ocean Cloud Plugin - First run always fails
Locked
Upgrading Digital Ocean Cloud Plugin - First run always fails
 
|
Re: Upgrading Digital Ocean Cloud Plugin - First run always fails
|
|
Re: Upgrading Digital Ocean Cloud Plugin - First run always fails
|
|
Re: Upgrading Digital Ocean Cloud Plugin - First run always fails
|
|
Okay managed to do a bunch of permutations. 2.60.3 works just fine on both first and second freestyle job 2.263.4 fails on first job, but will succeed on the second if the agent is still running 2.263.4 works fine on first and second with pipeline
UserRequest.getClassLoader(callable) where callable is Launcher$RemoteLauncher$KillTask returns a WebAppClassLoader. Is that possibly why its trying to load ServletError? I've been trying to attach a debugger and track this down more but Its well outside my java knowledge. How can I get a debugger inside of a
MasterToSlaveCallable, specifically https://github.com/jenkinsci/jenkins/blob/8c6327f4c6777d135e374e3d507ba9c20820bfc6/core/src/main/java/hudson/Launcher.java#L1164 I've tried attaching it to the hpi:run process, and the agent/remoting.jar process. I think the remoting process is the way to do it, but I can't figure out how to get a breakpoint inside of killtask  On Thu, Feb 11, 2021 at 8:11 PM Gavin Mogan <[hidden email]> wrote:
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DuvJTqzQ86UhUY6yNCgZz7C-hNg9_-O4VTKPP2OgOv0%2BWQ%40mail.gmail.com. |
Re: Upgrading Digital Ocean Cloud Plugin - First run always fails
|
|
The patch is merged, but before I cut a release, I'd like to address the freestyle issue. Is anyone available to pair with me to diagnose this? Or can I get someone credit to look into it? On Sat, Feb 13, 2021 at 7:10 PM Gavin Mogan <[hidden email]> wrote:
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DusTywAs19iLx1ZrBtAuZVvdEEFRk8P5QKgKRmXbpmKeFw%40mail.gmail.com. |
Re: Upgrading Digital Ocean Cloud Plugin - First run always fails
|
|
I've had a bit of a look at this, I patched the plugin to enable logging via workDir, unfortunately it didn't give much more than what's in the log for the freestyle build. (https://gist.github.com/timja/4b28f173d5d2925c82781109dce57362) I had a look through these slides from Oleg https://speakerdeck.com/onenashev/day-of-jenkins-2017-dealing-with-agent-connectivity-issues?slide=66 But it didn't help any more than say enable logging FTR I've got a very similar error in the slack plugin on freestyle builds when uploading a file from the agent. Anyone got any tips for debugging this? Specific logs to enable and how to enable them? The agent is started here: I patched it to be: + String launchString = "java " + jvmOpts + " -jar /tmp/agent.jar -workDir /root/.jenkins/remotingWorkDir"; Thanks Tim On Wed, 24 Feb 2021 at 21:23, 'Gavin Mogan' via Jenkins Developers <[hidden email]> wrote:
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BidSCOCNEv%3Dw0uUv3GSjGK-%3D7uZeHhmQiLPo1iO%3Dcwgr9g%40mail.gmail.com. |
| Free forum by Nabble | Edit this page |