Re: remoting issue

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

Re: remoting issue

Okay going by the logs now, here are some of the possible things that you can look into: 1. jdk versions consistent across the master and slaves 2. https://issues.jenkins-ci.org/plugins/servlet/mobile#issue/JENKINS-30561 3.

Re: remoting issue

I've attached the two logs. I did make a change after seeing 'Failed to ack the stream' to turn off scatter/gather. But I think that's a bit of a "hail mary". On Monday, February 11, 2019 at 10:16:05 AM UTC-5, Ivan Fernandez Calvo wrote: > > It could be tons of things, Probably, if you go

Help with using the scripts int he vars directory of shared libraries

I'm writing share libraries by following Extending with Shared Libraries , and I have a simple example working. I now have created a script in the vars directory called debugger.groovy, that has a class definition, like this class

Re: Does the SSH Agents plugin support FIPS 140-2?

Try with an ed25519 private key. Some online docs suggest that ed25519 is FIPS-140-2 approved. On Mon, Feb 11, 2019, 12:13 PM Dunnigan (US), Terrence J < terrence.j.dunni...@boeing.com wrote: > Hi all, > > > > Does the SSH Slaves plugin support FIPS 140-2 ( >

Does the SSH Agents plugin support FIPS 140-2?

Hi all, Does the SSH Slaves plugin support FIPS 140-2 (https://en.wikipedia.org/wiki/FIPS_140-2) ? In my case I have a Windows VM running Jenkins trying to connect to a RHEL7 VM with FIPs enabled. I'm getting SSH authentication errors, and the RHEL logs suggest that the Jenkins SSH Slaves

Re: remoting issue

This thing caught my eye: Feb 11, 2019 8:15:03 AM hudson.remoting.ProxyOutputStream$Chunk$1 run WARNING: Failed to *ack *the stream That indicates a TCP issue over there. Try this [root@ip-172-31-2-59 ec2-user]# ethtool -K eth0 sg off Actual changes: scatter-gather: off tx-scatter-gather:

Re: remoting issue

It could be tons of things, Probably, if you go to the node log (JENKINS_URL/computer/NODE_NAME/log) we could see if the agent connect or not, then if the communication is broken before/after connection and in which point. El miércoles, 6 de febrero de 2019, 16:39:17 (UTC+1), Glenn Burkhardt

Re: remoting issue

I see now that the value for "kexTimeout" should be the 210 value you reference. BTW, we are using only 5 agents. I found reports of a similar problem with connection timeouts here: https://github.com/jenkinsci/ec2-fleet-plugin/issues/41 and as an experiment, followed the recommendation

Re: How to prevent concurrent execution of jobs on the same node, but allow a few parallel steps execution?

I started to play with the lockable resources plugin. I'd like to prevent parallel execution of my pipeline (multibranch pipeline) on the same Jenkins slave, so I tried to use "$NODE_NAME" as lockable resource, like this: pipeline { agent { label 'slave-parallel' } options { lock

Re: Jenkins is running as a docker image in a kubernetes cluster and won't come up due to plugin version incompatibility

The docker image uses the file 'plugins.txt' to select the plugin versions to use. You can modify the plugins.txt file to change the versions of plugins used in the docker image. On Mon, Feb 11, 2019 at 6:37 AM आलोक कुमार wrote: > We are running Jenkins as a docker image in a kubernetes

How to integrate Jenkins with Google LDAP service

Hello, Does anyone has successes in such kind of integration? Because Google LDAP service requires certificate authentication I can't point Jenkins directly to the ldaps://ldap.google.com. I have tried to use stunnel but without success. Jenkins: 2.150.2 LDAP plugin: 1.20 Jenkins settings

Jenkins is running as a docker image in a kubernetes cluster and won't come up due to plugin version incompatibility

We are running Jenkins as a docker image in a kubernetes cluster. However it does not come up any more because of some plugin version incompatibility. How can we upgrade the plugins, or disable them to bring up Jenkins? Note that because Jenkins is not up, we cannot upgrade / disable

Re: Need help understanding this NotSerializableException

I tried to reproduce this in a standalone pipeline, but the below code worked fine. The only difference between the failing code and the below test code is that the BOM class is defined inside a var file with a getter that creates an instance: class BOM { private List order = ['a', 'b',