Re: Unable to Launch Node

2022-03-30 Thread Ivan Fernandez Calvo 
I do not really have too much data to know what exactly is going on, which 
version of the SSH build Agents and the trilead-api plugins are you using? 
Are you using the latest versions? Do the issue happen only in that agent? 
Which SSH server do you use and what version? Do you have any kind of 
transfer limit on that agent? my theory is that the sftp read operation 
fail because something cut it.

El miércoles, 30 de marzo de 2022 a las 21:50:52 UTC+2, eric@gmail.com 
escribió:

> Just did it again on me.  Deleting the file again to fix it but would be 
> great if I could fix it.  Any advise?
>
> On Friday, March 18, 2022 at 11:17:56 AM UTC-6 kuisat...@gmail.com wrote:
>
>> The SSH Build Agents plugin make an sftp or scp (if one fail try the 
>> other) with the user configured in the Jenkins Agent to copy a file in the 
>> "Remote root directory" folder configured in the Agent config, nothing 
>> special, if the user configured in the Agent can make scp/sftp to copy a 
>> file in that folder it should not fail. 
>>
>> The point where the Agent fails to copy the file is interesting, it 
>> checks the value of the read bytes and fails if is <0 or >32768, I will 
>> bet the value is `-1` and it is related to read the remoting.jar from the 
>> Agent to check the md5, for some reason is returning an EOF
>>
>>
>> https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/SFTPv3Client.java#L1231
>>
>> https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L706
>> El viernes, 18 de marzo de 2022 a las 16:10:56 UTC+1, eric@gmail.com 
>> escribió:
>>
>>> Hmmm, I deleted the remoting.jar file and was able to restart Jenkins 
>>> and the node came up.  Wonder if this is going to happen every we patch and 
>>> boot this machine?
>>>
>>> On Friday, March 18, 2022 at 8:43:55 AM UTC-6 eric@gmail.com wrote:
>>>
 Hi!  I have a node that is unable to launch.  On the log it shows:

 [03/18/22 09:39:01] [SSH] Copying latest remoting.jar... 
 java.io.IOException: Could not copy remoting.jar into 
 '/home/myuser/checkout' on agent at 
 hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:715) at 
 hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:112) at 
 hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:455) at 
 hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422) at 
 java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:750) Caused by: 
 java.lang.IllegalArgumentException: invalid len argument at 
 com.trilead.ssh2.SFTPv3Client.read(SFTPv3Client.java:1232) at 
 com.trilead.ssh2.jenkins.SFTPClient$SFTPInputStream.read(SFTPClient.java:172)
  
 at 
 com.google.common.io.ByteStreams.toByteArrayInternal(ByteStreams.java:184) 
 at com.google.common.io.ByteStreams.toByteArray(ByteStreams.java:224) at 
 hudson.plugins.sshslaves.SSHLauncher.readInputStreamIntoByteArrayAndClose(SSHLauncher.java:773)
  
 at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:684) 
 ... 7 more

 I've set my perms on the checkout dir to 777, so it's not that it 
 doesn't have permission to write over the current remoting.jar that lives 
 there. Anyone have any clues or further trouble shooting advise? 
 Running Jenkins 2.232.1 on RHEL 7.9.

 Thanks - Eric 

>>>

-- 
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/9a5d39af-9f6d-4881-a0de-7d00c0dfff64n%40googlegroups.com.

Re: Why jenkins doesn't assign jobs to an agent with more resources

2022-03-30 Thread John Patrick 
Hi,
Some basic questions;
- what Jenkins version?
- has it ever work for you?
- you mention 8-9 dockers per agent, is that being controlled using "Number
of executors" being set for each agent?

John



On Sun, 27 Mar 2022 at 09:30, chencho m-a  wrote:

> Hi all,
>
> I have a cluster with 20 agents, all of them are able to run 8-9 dockers.
> In my understanding after installing "least load" plugin, it should take
> agent1-docker1 and then, agent2-docker1 but why i am seeing is that it is
> using agent1-docker1, agent1-docker2. So I have a node overloaded and 19
> more doing nothing.
>
> Any clue?
>
> --
> 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/49b2c7f4-139a-4c18-b03d-f2900dcc8717n%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/CAH9u10k%3D%2B5C%3DEDMxXDhFDjh5z6pbEpP3bceYmDWaS5AKqt%2BjmA%40mail.gmail.com.

Re: Unable to Launch Node

2022-03-30 Thread eric....@gmail.com 
Just did it again on me.  Deleting the file again to fix it but would be 
great if I could fix it.  Any advise?

On Friday, March 18, 2022 at 11:17:56 AM UTC-6 kuisat...@gmail.com wrote:

> The SSH Build Agents plugin make an sftp or scp (if one fail try the 
> other) with the user configured in the Jenkins Agent to copy a file in the 
> "Remote root directory" folder configured in the Agent config, nothing 
> special, if the user configured in the Agent can make scp/sftp to copy a 
> file in that folder it should not fail. 
>
> The point where the Agent fails to copy the file is interesting, it checks 
> the value of the read bytes and fails if is <0 or >32768, I will bet the 
> value is `-1` and it is related to read the remoting.jar from the Agent to 
> check the md5, for some reason is returning an EOF
>
>
> https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/SFTPv3Client.java#L1231
>
> https://github.com/jenkinsci/ssh-slaves-plugin/blob/main/src/main/java/hudson/plugins/sshslaves/SSHLauncher.java#L706
> El viernes, 18 de marzo de 2022 a las 16:10:56 UTC+1, eric@gmail.com 
> escribió:
>
>> Hmmm, I deleted the remoting.jar file and was able to restart Jenkins and 
>> the node came up.  Wonder if this is going to happen every we patch and 
>> boot this machine?
>>
>> On Friday, March 18, 2022 at 8:43:55 AM UTC-6 eric@gmail.com wrote:
>>
>>> Hi!  I have a node that is unable to launch.  On the log it shows:
>>>
>>> [03/18/22 09:39:01] [SSH] Copying latest remoting.jar... 
>>> java.io.IOException: Could not copy remoting.jar into 
>>> '/home/myuser/checkout' on agent at 
>>> hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:715) at 
>>> hudson.plugins.sshslaves.SSHLauncher.access$300(SSHLauncher.java:112) at 
>>> hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:455) at 
>>> hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422) at 
>>> java.util.concurrent.FutureTask.run(FutureTask.java:266) 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:750) Caused by: 
>>> java.lang.IllegalArgumentException: invalid len argument at 
>>> com.trilead.ssh2.SFTPv3Client.read(SFTPv3Client.java:1232) at 
>>> com.trilead.ssh2.jenkins.SFTPClient$SFTPInputStream.read(SFTPClient.java:172)
>>>  
>>> at 
>>> com.google.common.io.ByteStreams.toByteArrayInternal(ByteStreams.java:184) 
>>> at com.google.common.io.ByteStreams.toByteArray(ByteStreams.java:224) at 
>>> hudson.plugins.sshslaves.SSHLauncher.readInputStreamIntoByteArrayAndClose(SSHLauncher.java:773)
>>>  
>>> at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:684) 
>>> ... 7 more
>>>
>>> I've set my perms on the checkout dir to 777, so it's not that it 
>>> doesn't have permission to write over the current remoting.jar that lives 
>>> there. Anyone have any clues or further trouble shooting advise? 
>>> Running Jenkins 2.232.1 on RHEL 7.9.
>>>
>>> Thanks - Eric 
>>>
>>

-- 
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/b182927d-e91d-4353-834a-6ed573288a1bn%40googlegroups.com.