Re: jenkins issue

[Iván Fernández Calvo]

You do not pass any credentials around the script in the pipeline,So the command “git pull” failed because does not have a way to authenticate. Check the article and the video of my previous message, there is explained how to pass credentials to your script.El 12 oct 2022, a las 8:13, pooja pooja  escribió:this is my deploy.sh file#!/bin/bashssh ubuntu@65.0.256.137 <#cd /home/ubuntu/GJ_DEV/GJ_APIcd  gj/patsudo git pullpm2 restart allpm2 statuspipeline scriptcurrentBuild.displayName = "gj-api-#"+currentBuild.numberpipeline{    agent any     stages{        stage("GITLAB_CHECKOUT"){            steps{                git branch: 'development', credentialsId: 'GITHUB1', url:'https://github.com/gj/pat.git'            }        }        stage("pm2 start"){            steps{                sh 'chmod u+x ./scripts/deploy.sh'                sh './scripts/deploy.sh'            }        }    }can you guys tell me, where the script was wrong,am not able to find the errorOn Tue, Oct 11, 2022 at 10:00 PM Ivan Fernandez Calvo  wrote:one more thing to pass the Git credentials to your script you could check this articleshttps://www.jenkins.io/blog/2021/07/27/git-credentials-binding-phase-1/https://www.youtube.com/watch?v=HSA_mZoADSwEl martes, 11 de octubre de 2022 a las 18:28:26 UTC+2, Ivan Fernandez Calvo escribió:The error is related to something your script is doing, it is not related to Jenkins at all. Try to review the code you are executing and figure out which line is and what is wrong. Googling the error seems related to configuring the git user and git email and the git authentication when you access GitHub using HTTPS URLs. It seems to be an error message from Ruby code. The solution seems to add the authentication to the URL or use an authentication store proper for your environment (I preferer to use gh see https://cli.github.com/manual/gh_auth_setup-git), but I am not sure depends on your script.https://stackoverflow.com/questions/54454853/fatal-could-not-read-username-for-https-github-com-no-such-device-or-addrhttps://stackoverflow.com/questions/69995273/access-organization-repo-on-github-using-personal-access-token-inside-bash-scriphttps://itecnote.com/tecnote/ruby-on-rails-fatal-could-not-read-username-for-https-github-com-no-such-device-or-address/https://github.com/github/hub/issues/1644El martes, 11 de octubre de 2022 a las 13:37:53 UTC+2, pooja...@gmail.com escribió:Hi mark and Mithun,am getting error in jenkins On Tue, Oct 11, 2022 at 9:59 AM pooja pooja  wrote:this is my exact issueOn Mon, Oct 10, 2022 at 7:15 PM Mithun Raj  wrote:1. Update your OS,2. Check if the Git credentials are injected correctly,If running from bastion host or jump box make sure your git hub or enterprise hostnames and IP are updated (ask git admin) in the hosts file under /etc/hosts3. Update—env is the Git global env for gitYou can either set or unset those in your Linux machine it’s your Git ID and pass which you can set as global access. not recommended if you have set it under Jenkins credentials.On Mon, 10 Oct 2022 at 5:49 PM, pooja pooja  wrote:in jenkins am getting below errorNew release '22.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it. fatal: could not read Username for 'https://github.com': No such device or address Use --update-env to update environment variables



-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cec7b2ee-88ba-417d-be66-95d4954dbbfen%40googlegroups.com.




-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANwMLksgv3L6S%2BGdZmXxq0fw8eOCJ_HW-3sbRqpDhnqsB6X71A%40mail.gmail.com.






-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9bed72a1-5419-42fe-ae55-775f0793aa10n%40googlegroups.com.




-- 
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/4MFd7CVFD3U/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 

Re: Multiple Instances on one server with Java 11

[Iván Fernández Calvo]

If you issue is the memory, it is time to check the garbage collector you are 
using, check that you are not using deprecated JVM flags, IIRC the garbage 
collector used by JDK 11 is G1 and should perform better than default JDK8 
defaults.

Regards
Ivan Fernandez Calvo

> El 11 jul 2022, a las 19:48, Matt Wilson  escribió:
> 
> ooo... you may have nailed it there.  I was definitely over  the 75%.  I 
> bumped up my overall system RAM, and then locked in the one site that isn't 
> used too much to a lower value.  Its early, but so far no crashes.  
> Interesting that Java 8 never had an issue with this, but 11 clearly is.
> Hopefully this holds as a solution.  Thanks for the tip!
> 
>> On Monday, July 11, 2022 at 12:40:29 PM UTC-4 kuisat...@gmail.com wrote:
>> If there are three different Apache Tomcat instances running three different 
>> services on Java 11, the only explanation to make one crash that comes to my 
>> mind is the resources of the machine, memory in particular.
>> The recommendation is to not use more than 75% of the memory of the host to 
>> the JVM, in your case you have 3 JVM running so each should not use more 
>> than 25% of the memory of the host, if you use more than that the JVM will 
>> fight for the host resources and one will lose crashing. Check the values on 
>> your `xms` and `xmx` Apache Tomcat parameters.
>> 
>>> El lunes, 11 de julio de 2022 a las 16:40:08 UTC+2, slide escribió:
>>> Is there any crash log in either the apache or jenkins logs? I would look 
>>> for exception dumps in the logs, it might help narrow down where the issue 
>>> is occurring.
>>> 
 On Mon, Jul 11, 2022 at 5:35 AM Matt Wilson  wrote:
 For a few years I've been running multiple (independent) Jenkins instances 
 on one server.  Each server runs under its own apache instance.
 SiteA
 SiteB
 SiteC
 This has worked perfectly fine for a few years with no problems.
 Last week I upgraded all three servers to 2.346.1.  two of the three 
 servers had been updated regularly so this wasn't a huge jump, that third 
 server has a year and a bit behind so it was a bigger jump (siteB).
 All three sites upgraded fine.  
 All three sites got upgraded to Java 11.  That went fine.
 All three sites run independently with no problems.
 When I start all three sites, I have one site that crashes.  The crash 
 seems to be triggered in particular when you access the management page on 
 one particular server.
 so like this
 Site A is fine no matter what
 Site B crashes when site C accesses its manage Jenkins page
 
 I've double checked my settings, I can't find any port conflicts or 
 Jenkins home conflicts.
 I've tried running all three sites on separate Java installs.  Still 
 crashes
 The only thing that seems to stop the crash so far is if I run site C back 
 on Java 8.
 
 Any thoughts on what I could be missing here config wise?
>>> 
 -- 
 You received this message because you are subscribed to the Google Groups 
 "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to jenkinsci-use...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/de1049d2-cbe0-462e-9bce-1f9656ba6018n%40googlegroups.com.
>>> 
>>> 
>>> -- 
>>> Website: http://earl-of-code.com
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/mwvN_V-_C0o/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/ff1e0be4-a93c-48fd-aacd-3df27b92cb97n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/88D2C84D-EA7C-4A0A-B44B-5A374A1865AC%40gmail.com.

Re: Help! I am trying to upgrade from 2.263.1 to 2.303.1

[Iván Fernández Calvo]

RHE6? This is pretty old, I wonder if your Jenkins issue could be related to 
the let’s Encrypt Root CA X3 certificate expiration.

> El 6 oct 2021, a las 0:22, Burns, Daniel  
> escribió:
> 
>  Great, i didn't think there should be an issue, currently we are using RHEL 
> 6, I believe.
> 
> Sent from my Sprint Samsung Galaxy Note10+.
> Get Outlook for Android
> From: jenkinsci-users@googlegroups.com  on 
> behalf of Mark Waite 
> Sent: Tuesday, October 5, 2021 4:49:56 PM
> To: Jenkins Users 
> Subject: Re: Help! I am trying to upgrade from 2.263.1 to 2.303.1
>  
> EXTERNAL EMAIL
>  
> I use Amazon Linux 2 for agents with no issue. I've never heard of a problem 
> that was specific to Amazon Linux 2.
> 
>> On Tue, Oct 5, 2021, 3:23 PM Iván Fernández Calvo  
>> wrote:
>> I do not think so the issue seems related to the upgrade not the OS.
>> 
>> El 5 oct 2021, a las 21:09, Daniel Burns  
>> escribió:
>> 
>> Thank you.  I wanted to at least respond.  This is in DEV so I can 
>> definitely try different things.  Using what you stated, I can mimic PROD 
>> and create a new DEV server with a fresh OS.  I assume there are no issues 
>> with using AWS Amazon Linux 2, instead of RHEL Linux?
>> 
>> Thank you.
>> 
>> On Sunday, October 3, 2021 at 6:13:09 AM UTC-5 kuisat...@gmail.com wrote:
>> It is not clear what it is the current issue you want to resolve, so my 
>> suggestion is to start again the first case you expose.
>> 
>> >On my first try, I thought I had upgraded, but I did not realize that the 
>> >version of WAR file was the same (2.263.1) I upgraded the plugins, then 
>> >realized that it had not been upgraded to 2.303.1, so then I put the new 
>> >WAR file in place.  I was able to log in just fine, but one of the most 
>> >important pipelines I have did not work.  I makes a call out to Gitlab and 
>> >I update Gitlab at the same time.
>> 
>> Before upgrading the production environment try to upgrade the same system 
>> but in another machine:
>> 
>> * In a new machine
>> * Copy the JENKINS_HOME folder to the new server in the same place
>> * Remove the folder JENKINS_HOME/nodes/* (we do not want to use the 
>> production Agents)
>> * Start Jenkins in the new machine 
>> * Upgrade the plugins
>> * Stop Jenkins
>> * Update the war
>> * Start Jenkins
>> * Create a new Agent that fit the requirements of your important pipeline
>> * Test the pipeline
>> 
>> At this point you'd have the same issue you face at the beginning, to try to 
>> troubleshoot it you need to check
>> * Check the Jenkins logs from the start to the execution of the pipeline, we 
>> are looking for exceptions 
>> * Check the console log of the pipeline to see which error is causing the 
>> pipeline to not work
>> * check the logs of the Agent in case we are error there
>> * Check the manage Jenkins and check there is no warning or error at the top 
>> of the page
>> 
>> If you provide the exceptions you found we could help you to point to a 
>> specific fix. 
>> My guess is that you have a problem with a plugin version, it could be that 
>> it conflicts with another, 
>> or your pipeline needs a specific version of a plugin.
>> 
>> El viernes, 1 de octubre de 2021 a las 19:51:26 UTC+2, 
>> daniel...@vistracorp.com escribió:
>> I put a new WAR in place and restart and normally, no issues at all.
>> 
>> I have RedHat 6 running on an AWS EC2.  
>> 
>> On my first try, I thought I had upgraded, but I did not realize that the 
>> version of WAR file was the same (2.263.1) I upgraded the plugins, then 
>> realized that it had not been upgraded to 2.303.1, so then I put the new WAR 
>> file in place.  I was able to log in just fine, but one of the most 
>> important pipelines I have did not work.  I makes a call out to Gitlab and I 
>> update Gitlab at the same time.
>> 
>> I went backwards to snapshots I made of the two servers before I upgraded.  
>> Validated that the pipeline works, then upgraded Gitlab fully tested and the 
>> pipeline worked.  So I narrowed the issue to Jenkins.  I tried the upgrade 
>> again, without updating the plugins first.  This time, I got an error on 
>> login page, If I clicked on Login, it gives me a prompt to put my ID and 
>> password, upon hitting enter it gives me a 403 crumb error.  We use A/D to 
>> validate credentials.
>> 
>> I have tried several times, even trying to go down to the LTS right after 
>> the 2.263 release same issue.  At this point I am assuming I h

Re: Help! I am trying to upgrade from 2.263.1 to 2.303.1

[Iván Fernández Calvo]

I do not think so the issue seems related to the upgrade not the OS.

> El 5 oct 2021, a las 21:09, Daniel Burns  
> escribió:
> 
> Thank you.  I wanted to at least respond.  This is in DEV so I can 
> definitely try different things.  Using what you stated, I can mimic PROD and 
> create a new DEV server with a fresh OS.  I assume there are no issues with 
> using AWS Amazon Linux 2, instead of RHEL Linux?
> 
> Thank you.
> 
>> On Sunday, October 3, 2021 at 6:13:09 AM UTC-5 kuisat...@gmail.com wrote:
>> It is not clear what it is the current issue you want to resolve, so my 
>> suggestion is to start again the first case you expose.
>> 
>> >On my first try, I thought I had upgraded, but I did not realize that the 
>> >version of WAR file was the same (2.263.1) I upgraded the plugins, then 
>> >realized that it had not been upgraded to 2.303.1, so then I put the new 
>> >WAR file in place.  I was able to log in just fine, but one of the most 
>> >important pipelines I have did not work.  I makes a call out to Gitlab and 
>> >I update Gitlab at the same time.
>> 
>> Before upgrading the production environment try to upgrade the same system 
>> but in another machine:
>> 
>> * In a new machine
>> * Copy the JENKINS_HOME folder to the new server in the same place
>> * Remove the folder JENKINS_HOME/nodes/* (we do not want to use the 
>> production Agents)
>> * Start Jenkins in the new machine 
>> * Upgrade the plugins
>> * Stop Jenkins
>> * Update the war
>> * Start Jenkins
>> * Create a new Agent that fit the requirements of your important pipeline
>> * Test the pipeline
>> 
>> At this point you'd have the same issue you face at the beginning, to try to 
>> troubleshoot it you need to check
>> * Check the Jenkins logs from the start to the execution of the pipeline, we 
>> are looking for exceptions 
>> * Check the console log of the pipeline to see which error is causing the 
>> pipeline to not work
>> * check the logs of the Agent in case we are error there
>> * Check the manage Jenkins and check there is no warning or error at the top 
>> of the page
>> 
>> If you provide the exceptions you found we could help you to point to a 
>> specific fix. 
>> My guess is that you have a problem with a plugin version, it could be that 
>> it conflicts with another, 
>> or your pipeline needs a specific version of a plugin.
>> 
>>> El viernes, 1 de octubre de 2021 a las 19:51:26 UTC+2, 
>>> daniel...@vistracorp.com escribió:
>>> I put a new WAR in place and restart and normally, no issues at all.
>>> 
>>> I have RedHat 6 running on an AWS EC2.  
>>> 
>>> On my first try, I thought I had upgraded, but I did not realize that the 
>>> version of WAR file was the same (2.263.1) I upgraded the plugins, then 
>>> realized that it had not been upgraded to 2.303.1, so then I put the new 
>>> WAR file in place.  I was able to log in just fine, but one of the most 
>>> important pipelines I have did not work.  I makes a call out to Gitlab and 
>>> I update Gitlab at the same time.
>>> 
>>> I went backwards to snapshots I made of the two servers before I upgraded.  
>>> Validated that the pipeline works, then upgraded Gitlab fully tested and 
>>> the pipeline worked.  So I narrowed the issue to Jenkins.  I tried the 
>>> upgrade again, without updating the plugins first.  This time, I got an 
>>> error on login page, If I clicked on Login, it gives me a prompt to put my 
>>> ID and password, upon hitting enter it gives me a 403 crumb error.  We use 
>>> A/D to validate credentials.
>>> 
>>> I have tried several times, even trying to go down to the LTS right after 
>>> the 2.263 release same issue.  At this point I am assuming I have a plugin 
>>> problem.
>>> 
>>> I tried to look at the log and even created the logging.properties file but 
>>> I don't see anything glaringly obvious there either.
>>> 
>>> Can someone assist, suggest something?
>>> 
>>> Thank you
>>> Daniel 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/apYDcjRLRCk/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/27ac518f-d42d-4104-b68c-3c05ca1db282n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/BFB1DF60-E6E4-4D74-9C5D-1BD4700F08FD%40gmail.com.

Re: Issue with master-agent communication over ssh

[Iván Fernández Calvo]

gt;>>>>>>>>>>>>>> [12/04/20 15:23:03] [SSH] Copied 1,521,553 bytes.
>>>>>>>>>>>>>>>> Expanded the channel window size to 4MB
>>>>>>>>>>>>>>>> [12/04/20 15:23:03] [SSH] Starting agent process: cd 
>>>>>>>>>>>>>>>> "$JENKINS_SSH_DATA" && java  -jar remoting.jar -workDir 
>>>>>>>>>>>>>>>> $JENKINS_SSH_DATA -jar-cache 
>>>>>>>>>>>>>>>> $JENKINS_SSH_DATA/remoting/jarCache
>>>>>>>>>>>>>>>> Dec 04, 2020 3:23:29 PM 
>>>>>>>>>>>>>>>> org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir
>>>>>>>>>>>>>>>> INFO: Using $JENKINS_SSH_DATA/remoting as a remoting work 
>>>>>>>>>>>>>>>> directory
>>>>>>>>>>>>>>>> Dec 04, 2020 3:23:29 PM 
>>>>>>>>>>>>>>>> org.jenkinsci.remoting.engine.WorkDirManager setupLogging
>>>>>>>>>>>>>>>> INFO: Both error and output logs will be printed to 
>>>>>>>>>>>>>>>> $JENKINS_SSH_DATA/remoting
>>>>>>>>>>>>>>>> <===[JENKINS REMOTING CAPACITY]===>channel started
>>>>>>>>>>>>>>>> Remoting version: 4.5
>>>>>>>>>>>>>>>> This is a Unix agent
>>>>>>>>>>>>>>>> Evacuated stdout
>>>>>>>>>>>>>>>> Agent successfully connected and online
>>>>>>>>>>>>>>>> The Agent is connected, disconnect it before to try to connect 
>>>>>>>>>>>>>>>> it again.
>>>>>>>>>>>>>>>> Dec 04, 2020 3:33:58 PM org.eclipse.jgit.util.FS 
>>>>>>>>>>>>>>>> discoverGitSystemConfig
>>>>>>>>>>>>>>>> WARNING: Exception caught during execution of command '[git, 
>>>>>>>>>>>>>>>> config, --system, --edit]' in '$GIT_PATH/bin', return code 
>>>>>>>>>>>>>>>> '128', error message 'fatal: Invalid path '$GIT_PATH/etc': No 
>>>>>>>>>>>>>>>> such file or directory
>>>>>>>>>>>>>>>> '
>>>>>>>>>>>>>>>> Dec 04, 2020 3:33:58 PM 
>>>>>>>>>>>>>>>> org.eclipse.jgit.util.FS$FileStoreAttributes saveToConfig
>>>>>>>>>>>>>>>> WARNING: locking 
>>>>>>>>>>>>>>>> FileBasedConfig[$JENKINS_PATH/.config/jgit/config] failed 
>>>>>>>>>>>>>>>> after 5 retries
>>>>>>>>>>>>>>>> Dec 04, 2020 3:33:59 PM 
>>>>>>>>>>>>>>>> org.jenkinsci.remoting.util.AnonymousClassWarnings warn
>>>>>>>>>>>>>>>> WARNING: Attempt to (de-)serialize anonymous class 
>>>>>>>>>>>>>>>> com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritTriggerBuildChooser$1;
>>>>>>>>>>>>>>>>  see: 
>>>>>>>>>>>>>>>> https://jenkins.io/redirect/serialization-of-anonymous-classes/
>>>>>>>>>>>>>>>> Dec 04, 2020 3:34:24 PM hudson.remoting.Request$2 run
>>>>>>>>>>>>>>>> WARNING: Failed to send back a reply to the request 
>>>>>>>>>>>>>>>> hudson.remoting.Request$2@493c5a4e
>>>>>>>>>>>>>>>> java.io.IOException: Resource temporarily unavailable
>>>>>>>>>>>>>>>> at java.io.FileOutputStream.writeBytes(Native Method)
>>>>>>>>>>>>>>>> at 
>>>>>>>>>>>>>>>> java.io.FileOutputStream.write(FileOutputStream.java:313)
>>>>>>>>>>>>>>>> at 
>>>>>>>>>>>>>>>> hudson.remoting.StandardOut

Re: Pipeline generic for two Jenkins with two different agent types

[Iván Fernández Calvo]

> El 16 feb 2020, a las 11:15, Georges Moulinier  
> escribió:
> 
> Do you think I could "hide" this syntax " kubernetes { ..." or this "docker { 
> ..." behind a label ?

On both plugins you can configure templates , those templates can be triggered 
by labels so you still can use the agent { label ‘my-label’
} syntax 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6D070AD1-2FA2-4144-904D-81A6755B7B30%40gmail.com.

Re: Frequent "Disconnected computer for node" messages in jenkins logs

[Iván Fernández Calvo]

> El 16 feb 2020, a las 14:15, Vincent Massol  escribió:
> 
> In both cases it"ll be reported as INFO in the logs too. Right?

It seems like, I didn’t noticed that the exception is also a INFO messages, so 
the only difference is the stack trace of the exception, the log level is the 
same.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6A64DDBC-4F5C-405C-838D-9E22A9462EC7%40gmail.com.

Re: remoting issue

[Iván Fernández Calvo]

I dunno if it is your case, but things like VMotion that changes the VM to a 
less loaded rack, energy saving, any kind of power on network, and in general 
every that suspends the VM will break the connection, Jenkins check on agents 
every 4 min, if the agent does not respond on time Jenkins breaks the channel.

> El 18 feb 2019, a las 16:17, Glenn Burkhardt  escribió:
> 
> I have to agree that the Java version is a red herring.
> 
> Our VMs have been more stable in the last few days.  The changes that I think 
> might have had an effect are:
> 
> a)  Increasing the connection timeout to 6
> b) Turning off scatter/gather
> 
> But I also upgraded them all with the most recent Ubuntu updates, including 
> Oracle Java 8.201, and Linux version 4.15.0-45-generic.
> 
> I'll wait a few days, and then try backing out changes to see which makes the 
> problem return.  Thanks.
> 
>> On Tuesday, February 12, 2019 at 2:28:21 AM UTC-5, Ivan Fernandez Calvo 
>> wrote:
>> I think you can discard JVM versions issues and connectivity issues, because 
>> the agent connects and copy the remoting.jar, How much time takes between 
>> the agent connect and the channel is broken? Check you do not have any 
>> configuration  that kill idle connections, also try to assign memory to the 
>> remoting process (-Xmx256m -Xms256m), check those files dmesg, kernel.log, 
>> syslog, and messages of the agent to see if there is some error.
>> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/VbdIfb4ua9A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/0cbe8b8e-cb2c-4f95-9225-8e7ced80ce4a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/C0BE11E8-E103-4BBF-A273-6AF43535E312%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: remoting issue

[Iván Fernández Calvo]

This timeout, it is only for the connection stage, and it includes whole retry  
reconnections, long history, the default value is 210 seconds, less than 30-60 
seconds it is not a good value and only if you have reties to 0. 

I do not know how many agents you spin at the same time, I would try to find 
which number is the limit, I meant, If I spin 50 agent and is stable for some 
hours, I would increase de number until I find the limit

Un Saludo 
Ivan Fernandez Calvo

> El 6 feb 2019, a las 19:01, Glenn Burkhardt  escribió:
> 
> My reading of the code indicates that the timeout value is set by 
> "kexTimeout" in com\trilead\ssh2\Connection.java at line 693.  That appears 
> to be set in SSHLauncher.openConnection():1184.  The value we're using for 
> 'launchTimeoutMillis' should be 15000, assuming that it comes from "Startup 
> Idle" in the slave configuration (we enter '15', since the help says that the 
> units are seconds).  The machine we're using has 64gb of RAM, and 24 cores.  
> It's possible that it's a performance issue, but I doubt it.  I'll try 
> monitoring that a bit...
> 
> Thanks for your response.
> 
>> On Wednesday, February 6, 2019 at 11:14:53 AM UTC-5, Ivan Fernandez Calvo 
>> wrote:
>> >Jenkins and the VMs are all running on the same machine, so network 
>> >activity shouldn't be an issue.
>> 
>> network is not an issue, but performance response, Could it be? it is not a 
>> good idea to run the Jenkins Master and Agents in the same machine, if you 
>> use Docker container and you do not limit the resources used by each 
>> container (memory and CPU), they will fight for resources and some of them 
>> will be killed by docker with a nice OOM.
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/VbdIfb4ua9A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/21922cc3-652d-4fee-b6d6-b90fef7a4bba%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/E0FF82A5-C542-42C1-AA02-75FA9A30DB5B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need Help with SSH Slave Plugin - Unable to Start Node with SSH

[Iván Fernández Calvo]

On the “Known Hosts Key Validation" agents, where you imported the key on the 
jenkins user ssh authorized keys folder or on the etc ssh authorized keys 
folder? On etc does not work.

The other error seems related with the format of the host public key, it 
should’ve something like the following algorithm+base64 key encode

ssh-rsa B3NzaC1yc2EBIwAAAQEAklOUpkDHrfHY17SbrmTIpNLTGK9Tjom/BWDSU 
GPl+nafzlHDTYW7hdI4yZ5ew18JH4JW9jbhUFrviQzM7xlELEVf4h9lFX5QVkbPppSwg0cda3 
Pbv7kOdJ/MTyBlWXFCR+HAo3FXRitBqxiX1nKhXpHAZsMciLq8V6RjsNAQwdsdMFvSlVK/7XA 
t3FaoJoAsncM1Q9x5+3V0Ww68/eIFmb1zuUFljQJKprrX88XypNDvjYNby6vw/Pb0rwert/En 
mZ+AW4OZPnTPI89ZPmVMLuayrD2cE86Z/il8b+gw3r3+1nKatmIkjn2so1d01QraTlMqVSsbx 
NrRFi9wrf+M7Q== test@host


> El 23 abr 2018, a las 16:27, srk  escribió:
> 
> I restarted multiple times. I tried all options available "Known Hosts Key 
> Validation", "Manually Provided key Validation", etc..still get the 
> same/similar errors. I have the below messages in my WebLogic logs for 
> both..The first five are for nodes configured with "Known Hosts Key 
> Validation" while the last one is for "Manually Provided Key validation"... I 
> am able to login at server level using same ssh keys, but when invoking the 
> same using same credentials via Jenkins, it fails. 
> 
> 
> <[04/23/18 
> 10:07:53] SSH Launch of ZZZ on Z.ZZZ.com failed in 26 ms>
> <[04/23/18 
> 10:07:56] SSH Launch of ZZZ on Z.ZZZ.com failed in 2 ms>
> <[04/23/18 
> 10:08:43] SSH Launch of ZZZ on Z.ZZZ.com failed in 3 ms>
> <[04/23/18 
> 10:10:43] SSH Launch of ZZZ on Z.ZZZ.com failed in 3 ms>
> <[04/23/18 
> 10:11:38] SSH Launch of ZZZ on Z.ZZZ.com failed in 35 ms>
>
>   http://abc.xyz.com:1234/jenkins/computer/ZZZ/descriptorByName/hudson.plugins.sshslaves.verifiers.ManuallyProvidedKeyVerificationStrategy/checkKey
> java.lang.reflect.InvocationTargetException
> at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
> Truncated. see log file for complete stacktrace
> Caused By: java.lang.IllegalArgumentException: Key should be 2 parts: 
> algorithm and Base 64 encoded key value.
> at 
> hudson.plugins.sshslaves.verifiers.ManuallyProvidedKeyVerificationStrategy.parseKey(ManuallyProvidedKeyVerificationStrategy.java:98)
> at 
> hudson.plugins.sshslaves.verifiers.ManuallyProvidedKeyVerificationStrategy.access$000(ManuallyProvidedKeyVerificationStrategy.java:52)
> at 
> hudson.plugins.sshslaves.verifiers.ManuallyProvidedKeyVerificationStrategy$ManuallyProvidedKeyVerificationStrategyDescriptor.doCheckKey(ManuallyProvidedKeyVerificationStrategy.java:120)
> at 
> java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
> at 
> org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
> Truncated. see log file for complete stacktrace
> >
> 
>> On Friday, April 20, 2018 at 9:15:04 AM UTC-4, srk wrote:
>> Hi 
>> 
>> I have deployed Jenkins 2.117 war file onto WebLogic 12.2.1.2 as a 
>> webapplication and I am able to login to the application. I want to add 
>> additional nodes (remote servers) and would like to launch them using SSH, I 
>> have ssh key setup configured between the master where the WebLogic hosting 
>> Jenkins is running and remote servers and able to connect via shell. But 
>> when I try to do the same from within the application, I keep getting the 
>> below error message on the console output. I tried searching web and other 
>> support sites, and it seems this was fixed sometime in 2017 in older 
>> releases i.e in SSH Slave Plugin 1.20. I still keep getting the same and I 
>> see the plugin version installed is 1.26 for SSH Slave.
>> 
>> Any help or pointers in right direction is appreciated.
>> 
>> Thanks
>> 
>> Warning: no key algorithms provided; JENKINS-42959 disabled
>> [04/20/18 08:39:05] [SSH] Opening SSH connection to XXX.abc.com:22.
>> ERROR: Unexpected error in launching a slave. This is probably a bug in 
>> Jenkins.
>> java.lang.NoSuchMethodError: 
>> com.trilead.ssh2.Connection.connect(Lcom/trilead/ssh2/ServerHostKeyVerifier;III)Lcom/trilead/ssh2/ConnectionInfo;
>>  at 
>> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1324)
>>  at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:831)
>>  at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:820)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  at 
>>