Re: SAML Configuration

[Ivan Fernandez Calvo]

I have made a PR that disables the Auth Request on HTTP-POST binding when 
the encryption settings are not set, the same behavior HTTP-REDIRECT 
binding, when the PR build finishes, you would have a version of the plugin 
with the patch here 
https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fsaml-plugin/detail/PR-71/1/artifacts

El jueves, 29 de agosto de 2019, 21:31:03 (UTC+2), Ivan Fernandez Calvo 
escribió:
>
> modify the JENKINS_HOME/saml-sp-metadata.xml  does not work, I am 
> reviewing it because maybe there is a way to implement it by extending a 
> class.
>

-- 
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/c6f43035-51f1-4a49-af35-2dfe5b13064f%40googlegroups.com.

Re: Generate API Token does not display token to user.

[Philip Mason]

>
> Hi Mark,


No proxy involved at any level ...  Standard Chrome browser.

But I've just discovered there's a potential problem writing to the user 
config files.

 hudson.model.User.save  is hitting NPEs in the Cloudbees example token 
generation script, as well as occasionally when I re-login to a old session 
like this:

java.lang.NullPointerException
at hudson.Util.fileToPath(Util.java:1501)
at 
hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145)
at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92)
at hudson.model.User.putUserFolderIfAbsent(User.java:806)
at hudson.model.User.constructUserConfigFile(User.java:802)
at hudson.model.User.save(User.java:796)
at 
jenkins.security.LastGrantedAuthoritiesProperty.update(LastGrantedAuthoritiesProperty.java:81)
at 
jenkins.security.LastGrantedAuthoritiesProperty$SecurityListenerImpl.loggedIn(LastGrantedAuthoritiesProperty.java:112)
at 
jenkins.security.SecurityListener.fireLoggedIn(SecurityListener.java:129)
at 
hudson.security.AuthenticationProcessingFilter2.onSuccessfulAuthentication(AuthenticationProcessingFilter2.java:106)
at 
org.acegisecurity.ui.AbstractProcessingFilter.successfulAuthentication(AbstractProcessingFilter.java:486)
at 
org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:266)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at 
hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:90)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610)
at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:540)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1701)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at 
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1345)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at 
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:480)
at 
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1668)
at 
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at 
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1247)
at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:502)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:370)
at 
org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:267)
at 
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:305)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103)
at 
org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:427)
at 
org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:321)
at 
org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:159)
at 

Re: Generate API Token does not display token to user.

[Mark Waite]

That is quite unexpected.  I just used Jenkins 2.176.3 with Google Chrome
and confirmed that a token is generated as expected.  In my case, I am
connecting to Jenkins over SSL from the public internet, with the SSL
certificate handled by LetsEncrypt and the reverse proxy by nginx.

Can you describe the ways that your configuration is different from mine?

Are you running a reverse proxy?
Are you running a different web browser?
Are you running through a web proxy?
Are you running some software that might be filtering or blocking a portion
of the HTTP traffic from Jenkins?



On Thu, Aug 29, 2019 at 3:22 PM Philip Mason  wrote:

> Hi Jenkins folks. Running LTS 2.176.3.
>
> I find that "Add New Token" in the user configuration page isn't working.
>
> "Generate" button creates token, but it is never displayed to the user.
> Have to refresh the page to see that the token was created.
>
> The Script Console suggestion from Cloudbees to generate a token for a
> user throws an NPE at user.save().
>
> - - - Philip
>
> --
> 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/77cca0af-1244-4193-94fe-7e87d9de9a98%40googlegroups.com
> 
> .
>


-- 
Thanks!
Mark Waite

-- 
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/CAO49JtGHpe5cQYSYExqDgEnZQqQkPjv0pZ9j4ZfJbOEidMDvvQ%40mail.gmail.com.

Re: SAML Configuration

[Ivan Fernandez Calvo]

modify the JENKINS_HOME/saml-sp-metadata.xml  does not work, I am reviewing 
it because maybe there is a way to implement it by extending a class.

-- 
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/354cd5d6-d932-4427-9eab-ff26ccb7faa2%40googlegroups.com.

Generate API Token does not display token to user.

[Philip Mason]

Hi Jenkins folks. Running LTS 2.176.3. 

I find that "Add New Token" in the user configuration page isn't working. 

"Generate" button creates token, but it is never displayed to the user. 
Have to refresh the page to see that the token was created.

The Script Console suggestion from Cloudbees to generate a token for a user 
throws an NPE at user.save().

- - - Philip

-- 
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/77cca0af-1244-4193-94fe-7e87d9de9a98%40googlegroups.com.

Re: SAML Configuration

[Ivan Fernandez Calvo]

Hi,

It is not possible to disable signed on HTTP-POST, I've found some 
difficulties to make it on pac4j library (
https://issues.jenkins-ci.org/browse/JENKINS-47966), there is a workaround 
the IIRC works that it is to modify the JENKINS_HOME/saml-sp-metadata.xml 
file manually to disable it, you have to edit the SPSSODescriptor section 
to something like this "", the inconvenience of that it is 
that every time you modify the security configuration this file would 
change and you will lose your changes.



https://github.com/jenkinsci/saml-plugin/blob/master/doc/CONFIGURE.md


   - Disable Signature Redirect Binding Auth Request - Disable signature of 
   the Redirect Binding Auth Request 
   (urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect), It is not possible to 
   disable the signature in HTTP-POST binding.

-- 
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/8ca7b6e4-5867-42d2-b4f0-415a434f300e%40googlegroups.com.

Re: unable to launch remoting agent on slaves

[Ivan Fernandez Calvo]

SSH-slaves plugin does not recommend to use the same user on the same host for 
several agent connections because it would share the remoting and the java 
cache folders 
https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/TROUBLESHOOTING.md#overall-recommendations
 it would never was recommended. In your case you share home folder on a remote 
filesystem, that it is mostly the same. Also the use of a remote filesystem for 
the working folder would impact in the performance of any job that you run on 
those agents, it would be a bottleneck, it has to support all the IO operations 
of all your simultaneous running jobs, and those remoting filesystem use to not 
perform as fast as an hard disk.

-- 
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/7f979d8e-09b6-42e6-b65d-0ead14be906c%40googlegroups.com.

HTML Publisher for S3?

[Basil Crow]

Hi all,

I generate HTML code coverage reports with JaCoCo and make them available 
via the Jenkins UI with the HTML Publisher Plugin, much as is described 
here:

https://www.cloudbees.com/blog/publishing-html-reports-pipeline

The trouble is that these reports contain thousands of tiny HTML files, 
which get saved to my build directory. This makes deleting old builds a 
very slow operation, since the master has to delete thousands of tiny files.

I could just zip the results and publish the result as an artifact, but 
that wouldn't be as convenient for users. Users would then need to download 
and extract the archive, as opposed to (more conveniently) being able to 
browse the coverage report in the Jenkins UI with a few clicks.

Ideally I'd be able to publish the HTML files in S3 and have a link on the 
sidebar to the (S3-hosted) coverage results. Then I could set the artifacts 
to expire in S3 based on a sensible expiration policy, and I wouldn't have 
to worry about thousands of tiny files cluttering my build directories.

Does anyone have any ideas about how best to accomplish this?

Thanks,
Basil

-- 
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/27d27eb3-2e4e-4b4e-b425-11613d47e7e9%40googlegroups.com.

Jenkins Docker Master Multiarch

[Slide]

Thanks to the major work of other people, Jenkins is now providing
multiarch docker master images for arm64 (aarch64), arm (armv7), s390x and
ppc64le alongside the existing amd64 images.

They are currently being published to an evaluation org on dockerhub until
there is enough positive feedback to merge them into the main jenkins
organization. If you have one of these architectures that you have been
wanting to run a Jenkins docker master image on, please check them out and
provide feedback via JIRA.

https://hub.docker.com/r/jenkins4eval/jenkins/tags

Thanks!

Alex

-- 
Website: http://earl-of-code.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/CAPiUgVdF%3DLpYyX5R6E%2BCEWmqN1yB21UZP56_5G1nw3F5yCaw4g%40mail.gmail.com.

Re: Windows slave error

[Anetta van der Walt]

Also had to alow it on the master. So problem is now fixed.

On Thu, Aug 29, 2019 at 12:42 PM Anetta van der Walt 
wrote:

> Hey Emilo,
>
> Thanks for your response.
> I opened the port
>
> [image: Port.PNG]
> but still no luck
>
> [image: error.PNG]
> Any suggestions?
>
> Regards
> Anetta
>
> On Thursday, August 29, 2019 at 10:44:20 AM UTC+2, Emilio Escobar Reyero
> wrote:
>>
>> Hi,
>>
>> It seems that you cannot reach 10.17.23.30 (port:39677) from the slave
>> host. You need to check that before. Also seems to be a random port
>> (configured in the master at Manage Jenkins / Configure Global Security).
>> You probably prefer to use a fixed one (choosing one port like 5) and
>> opening it in your firewalls.
>>
>> Regards.
>>
>> On Thu, Aug 29, 2019 at 10:07 AM Anetta van der Walt 
>> wrote:
>>
>>> Good day
>>>
>>>
>>>
>>> I am trying to setup a windows slave, but keep getting this error
>>>
>>> [image: slave.png]
>>>
>>>
>>>
>>>
>>>
>>> I tried to solve it by setting “TCP port for inbound agents” to a
>>> specific port, but that is not helping.
>>>
>>> Any suggestions?
>>>
>>>
>>>
>>>
>>>
>>> Regards
>>>
>>> Anetta
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/c19448de-c6a6-4c0d-a69d-ff1c918d5ae9%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>>
>> Emilio Escobar
>> Software Engineer
>>
>> CloudBees, Inc.
>>
>> [image: CloudBees-Logo.png] 
>>
>>
>> E: eescoba...@cloudbees.com
>> Skype: escoem
>>
> --
> 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/d33847c8-f990-483a-bedf-b5a40f7af523%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/CADUMJYuxMGd4usb1F3NhVw8LweJKmPrb6B640ra%2BUzC7kLU_PA%40mail.gmail.com.

Re: Windows slave error

[Anetta van der Walt]

Hey Emilo,

Thanks for your response.
I opened the port

[image: Port.PNG]
but still no luck

[image: error.PNG]
Any suggestions?

Regards
Anetta

On Thursday, August 29, 2019 at 10:44:20 AM UTC+2, Emilio Escobar Reyero 
wrote:
>
> Hi,
>
> It seems that you cannot reach 10.17.23.30 (port:39677) from the slave 
> host. You need to check that before. Also seems to be a random port 
> (configured in the master at Manage Jenkins / Configure Global Security). 
> You probably prefer to use a fixed one (choosing one port like 5) and 
> opening it in your firewalls.
>
> Regards.
>
> On Thu, Aug 29, 2019 at 10:07 AM Anetta van der Walt  > wrote:
>
>> Good day
>>
>>  
>>
>> I am trying to setup a windows slave, but keep getting this error
>>
>> [image: slave.png]
>>
>>  
>>
>>  
>>
>> I tried to solve it by setting “TCP port for inbound agents” to a 
>> specific port, but that is not helping.
>>
>> Any suggestions?
>>
>>  
>>
>>  
>>
>> Regards
>>
>> Anetta
>>
>> -- 
>> 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 jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/c19448de-c6a6-4c0d-a69d-ff1c918d5ae9%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
>
> Emilio Escobar
> Software Engineer
>
> CloudBees, Inc.
>
> [image: CloudBees-Logo.png] 
>
>
> E: eescoba...@cloudbees.com 
> Skype: escoem
>

-- 
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/d33847c8-f990-483a-bedf-b5a40f7af523%40googlegroups.com.

Delay agent execution for auto-updates at boot

[James Green]

I finally used Packer to build an AMI based on Amazon Linux 2 to act as as
agent. Yesterday, the builds began failing with a Java stack trace.

Turns out the EC2 instance starts, and in parallel the Jenkins agent begins
and an auto-upgrade of openjdk kicked off. Further instructions failed.
Rebuild the AMI and the new agent worked a treat.

Is there a way of avoiding this problem by preventing Jenkins from
launching the agent until the boot steps are complete? I cannot be the
first to encounter this issue :-)

Thanks,

James

-- 
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/CAMH6%2BazGdqPwmrt3U%3Ds7xgXA0v%3DoF3ygv8nxv5DGkMJCc1rCCg%40mail.gmail.com.

Re: Windows slave error

[Emilio Escobar Reyero]

Hi,

It seems that you cannot reach 10.17.23.30 (port:39677) from the slave
host. You need to check that before. Also seems to be a random port
(configured in the master at Manage Jenkins / Configure Global Security).
You probably prefer to use a fixed one (choosing one port like 5) and
opening it in your firewalls.

Regards.

On Thu, Aug 29, 2019 at 10:07 AM Anetta van der Walt 
wrote:

> Good day
>
>
>
> I am trying to setup a windows slave, but keep getting this error
>
> [image: slave.png]
>
>
>
>
>
> I tried to solve it by setting “TCP port for inbound agents” to a specific
> port, but that is not helping.
>
> Any suggestions?
>
>
>
>
>
> Regards
>
> Anetta
>
> --
> 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/c19448de-c6a6-4c0d-a69d-ff1c918d5ae9%40googlegroups.com
> 
> .
>


-- 

Emilio Escobar
Software Engineer

CloudBees, Inc.

[image: CloudBees-Logo.png] 


E: eescobarrey...@cloudbees.com
Skype: escoem

-- 
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/CAEVizn%2BmqqRojAR19%3DCA2pHTve6U1MoEf07ZsDMQigyF-VS8uQ%40mail.gmail.com.

Windows slave error

[Anetta van der Walt]

Good day

 

I am trying to setup a windows slave, but keep getting this error

[image: slave.png]

 

 

I tried to solve it by setting “TCP port for inbound agents” to a specific 
port, but that is not helping.

Any suggestions?

 

 

Regards

Anetta

-- 
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/c19448de-c6a6-4c0d-a69d-ff1c918d5ae9%40googlegroups.com.

Re: unable to launch remoting agent on slaves

[Seth Galitzer]

I found a solution to this shortly after posting my question. It seems 
jenkins uses a cache directory in the SSH users homedir for caching of 
jars when the agent runs. All of my slaves use the same SSH account to 
launch the agent. That account authenticates using LDAP and has a 
homedir on a central fileserver that all the slave nodes connect to. So 
when the first connection is established, it seems to be locking the 
cache dir, blocking subsequent use of it.


This appears to be new behavior, as we have been using this setup for 
years without trouble. The solution was to set -Duser.home= 
in the JVM Options in advanced configuration for the node. Since 
 is always on the local disk of the slave node, there 
should be no further file locking problems.


It would have saved me some pain if the error logging had been more 
descriptive to identify this problem. "I/O error" or "null" was not 
super useful in debugging this. And since we haven't had problems in the 
past, it didn't occur to me that this might be an issue. Regardless, it 
seems to be resolved now and hopefully this post will help somebody in 
the future.


Seth

On 8/28/19 11:34 AM, Seth Galitzer wrote:
For the last two weeks, I cannot launch the remoting agent on linux 
slaves. Server version is 2.191, running on Debian 9.9 (stretch), 
installed from jenkins.io repo. Slaves are Ubuntu 18.04 (bionic), with 
openjdk-8 installed. Eventually, one slave will start, but none of the 
rest will. Between reboots or restarts of the jenkins server, the slave 
that successfully connects is different each time. There are 22 linux 
slaves total. Working directory is on local disk for each slave. SSH 
user is from LDAP.


Can somebody help me figure out what is blocking the start of the agents?

Thanks.
Seth

Sample server log:
2019-08-28 16:11:35.107+ 
[id=740]SEVEREhudson.slaves.ChannelPinger#install: Failed to set up a 
ping for linux64-santos13-minion

java.io.IOException: Closing all channels
at com.trilead.ssh2.channel.Channel.setReasonClosed(Channel.java:333)
at 
com.trilead.ssh2.channel.ChannelManager.closeChannel(ChannelManager.java:289)
at 
com.trilead.ssh2.channel.ChannelManager.closeAllChannels(ChannelManager.java:269)

at com.trilead.ssh2.Connection.close(Connection.java:536)
at com.trilead.ssh2.Connection.close(Connection.java:530)
at 
hudson.plugins.sshslaves.SSHLauncher.cleanupConnection(SSHLauncher.java:511)

at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:484)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
at 
jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at 
jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)

Caused: java.io.IOException: SSH channel is closed
at 
com.trilead.ssh2.channel.ChannelManager.ioException(ChannelManager.java:1540)

at com.trilead.ssh2.channel.ChannelManager.sendData(ChannelManager.java:373)
at 
com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:63)
at 
com.trilead.ssh2.channel.ChannelOutputStream.write(ChannelOutputStream.java:68)
at 
hudson.remoting.ChunkedOutputStream.sendFrame(ChunkedOutputStream.java:89)
at 
hudson.remoting.ChunkedOutputStream.sendBreak(ChunkedOutputStream.java:62)
at 
hudson.remoting.ChunkedCommandTransport.writeBlock(ChunkedCommandTransport.java:46)
at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.write(AbstractSynchronousByteArrayCommandTransport.java:46)

at hudson.remoting.Channel.send(Channel.java:721)
at hudson.remoting.Request.call(Request.java:213)
at hudson.remoting.Channel.call(Channel.java:954)
at hudson.slaves.ChannelPinger.install(ChannelPinger.java:115)
at hudson.slaves.ChannelPinger.preOnline(ChannelPinger.java:98)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:667)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:435)
at hudson.plugins.sshslaves.SSHLauncher.startAgent(SSHLauncher.java:607)
at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:113)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:441)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:406)
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:748)
2019-08-28 16:11:35.107+ 
[id=846]INFOh.r.SynchronousCommandTransport$ReaderThread#run: I/O error 
in channel linux64-santos14-minion

java.io.EOFException
at 
java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681)
at 
java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156)

at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)
at java.io.ObjectInputStream.(ObjectInputStream.java:358)
at