Not able to create jenkins agent in K8s cluster

Using Jenkins
1

Hi Team,
I am unable to create jenkins agent in k8s cluster. I am able to connect cluster (test connection is sucessfull) but not able to see the pod in cluster level.

Kubernetes pluginVersion3952.v88e3b_0cf300b_
Jenkins version : 2.401.1
k8s version : 1.23.15
rancher version : 2.6.9

In jenkins dashboard i can see pod name jenkins-3456 (launching and suspended )

I could find below logs in Jenkins master. Can som one please assist me to fix this issue.

####################
2023-07-01 13:09:18
2023-07-01 07:39:17.997+0000 [id=322596] WARNING o.c.j.p.k.KubernetesLauncher#launch: Kubernetes returned unhandled HTTP code -1 null
2023-07-01 13:09:18
2023-07-01 07:39:17.997+0000 [id=322596] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: jenkinsarjun-q1f09, template=PodTemplate{id=‘eead99eb-616a-400f-a4f7-803597e52b45’, name=‘jenkinsarjun’, label=‘jnlpslave’, containers=[ContainerTemplate{name=‘jnlp’, image=‘bcr-d01.inside.XXXX.cloud/ti3fe/jenkins-agent:latest’, workingDir=‘/home/jenkins’, command=‘’, args=‘’, resourceRequestCpu=‘’, resourceRequestMemory=‘’, resourceRequestEphemeralStorage=‘’, resourceLimitCpu=‘’, resourceLimitMemory=‘’, resourceLimitEphemeralStorage=‘’, envVars=[KeyValueEnvVar [getValue()=https://rb-jmaas.xxxxxxxx.com/Ram-dev:8080, getKey()=JENKINS_URL]], livenessProbe=ContainerLivenessProbe{execArgs=‘’, timeoutSeconds=0, initialDelaySeconds=0, failureThreshold=0, periodSeconds=0, successThreshold=0}}]}
2023-07-01 13:09:18
java.net.SocketTimeoutException: timeout
2023-07-01 13:09:18
at okhttp3.internal.http2.Http2Stream$StreamTimeout.newTimeoutException(Http2Stream.kt:675)
2023-07-01 13:09:18
at okhttp3.internal.http2.Http2Stream$StreamTimeout.exitAndThrowIfTimedOut(Http2Stream.kt:684)
2023-07-01 13:09:18
at okhttp3.internal.http2.Http2Stream.takeHeaders(Http2Stream.kt:143)
2023-07-01 13:09:18
at okhttp3.internal.http2.Http2ExchangeCodec.readResponseHeaders(Http2ExchangeCodec.kt:97)
2023-07-01 13:09:18
at okhttp3.internal.connection.Exchange.readResponseHeaders(Exchange.kt:110)
2023-07-01 13:09:18
at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.kt:93)
2023-07-01 13:09:18
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2023-07-01 13:09:18
at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.kt:34)
2023-07-01 13:09:18
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2023-07-01 13:09:18
at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.kt:95)
2023-07-01 13:09:18
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2023-07-01 13:09:18
at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.kt:83)
2023-07-01 13:09:18
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2023-07-01 13:09:18
at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.kt:76)
2023-07-01 13:09:18
at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.kt:109)
2023-07-01 13:09:18
at okhttp3.internal.connection.RealCall.getResponseWithInterceptorChain$okhttp(RealCall.kt:201)
2023-07-01 13:09:18
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:517)
2023-07-01 13:09:18
Caused: java.io.IOException: timeout
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.waitForResult(OperationSupport.java:535)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handleResponse(OperationSupport.java:558)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.OperationSupport.handleCreate(OperationSupport.java:349)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.handleCreate(BaseOperation.java:711)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.BaseOperation.handleCreate(BaseOperation.java:93)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:42)
2023-07-01 13:09:18
Caused: io.fabric8.kubernetes.client.KubernetesClientException: An error has occurred.
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:129)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.KubernetesClientException.launderThrowable(KubernetesClientException.java:122)
2023-07-01 13:09:18
at io.fabric8.kubernetes.client.dsl.internal.CreateOnlyResourceOperation.create(CreateOnlyResourceOperation.java:44)
2023-07-01 13:09:18
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:133)
2023-07-01 13:09:18
at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:298)
2023-07-01 13:09:18
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
2023-07-01 13:09:18
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
2023-07-01 13:09:18
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
2023-07-01 13:09:18
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2023-07-01 13:09:18
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2023-07-01 13:09:18
at java.base/java.lang.Thread.run(Thread.java:829)
2023-07-01 13:09:18
2023-07-01 07:39:17.998+0000 [id=322596] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent jenkinsarjun-q1f09
2023-07-01 13:09:18
2023-07-01 07:39:18.070+0000 [id=322596] WARNING o.c.j.p.k.KubernetesSlave#_terminate: Agent pod jenkinsarjun-q1f09 was not deleted due to retention policy Default.
2023-07-01 13:09:18
2023-07-01 07:39:18.070+0000 [id=322596] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer jenkinsarjun-q1f09

2

Hey,

I am not sure but tour problem seems that you agente doesnt reply to the máster. Can you send how you created the agent? The yaml file o the params into cloud Page of jenkins

3

Hi Rumberomelo,
Thanks for the reply

  1. In jenkins the connnection is established with kubernetes cluster. its show “Connected to Kubernetes v1.23.10”.
  2. Updated Jenkins URL and tunnel
  3. Updated pod teamplate with ns and labels. updated "only build job with label expression matching this node "
  4. added env variables.

while builing the job in jenkins it shows " (pending—All nodes of label ‘jnlpslave’ are offline)"

Currently i could see the jnlp pod is getting created in k8 cluster, but pod is terminating quickly with out completing the job.

I could see below logs in Jenkins master.

“023-07-07 23:53:33
2023-07-07 18:23:32.934+0000 [id=914153] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: jenkinsarjun-2hs5r, template=PodTemplate{id=‘eead99eb-616a-400f-a4f7-803597e52b45’, name=‘jenkinsarjun’, namespace=‘healthcheck’, label=‘jnlpslave’, containers=[ContainerTemplate{name=‘jnlp’, image=‘bcr-XXXXX/tidfe/inbound-agent_new’, workingDir=‘/home/jenkins’, command=‘’, args=‘’, resourceRequestCpu=‘100m’, resourceRequestMemory=‘100Mi’, resourceRequestEphemeralStorage=‘’, resourceLimitCpu=‘800m’, resourceLimitMemory=‘1000Mi’, resourceLimitEphemeralStorage=‘’, envVars=[KeyValueEnvVar [getValue()=xxxxx.com, getKey()=JENKINS_URL]], livenessProbe=ContainerLivenessProbe{execArgs=‘’, timeoutSeconds=0, initialDelaySeconds=0, failureThreshold=0, periodSeconds=0, successThreshold=0}}]}
2023-07-07 23:53:33
java.lang.IllegalStateException: Node was deleted, computer is null
2023-07-07 23:53:33
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:187)
2023-07-07 23:53:33
at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:298)
2023-07-07 23:53:33
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
2023-07-07 23:53:33
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
2023-07-07 23:53:33
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
2023-07-07 23:53:33
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2023-07-07 23:53:33
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2023-07-07 23:53:33
at java.base/java.lang.Thread.run(Thread.java:829)
2023-07-07 23:53:33
2023-07-07 18:23:32.934+0000 [id=914153] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent jenkinsarjun-2hs5r
2023-07-07 23:53:33
2023-07-07 18:23:32.959+0000 [id=914153] SEVERE o.c.j.p.k.KubernetesSlave#_terminate: Computer for agent is null: jenkinsarjun-2hs5r
2023-07-07 23:53:33
2023-07-07 18:23:32.959+0000 [id=914153] INFO hudson.slaves.AbstractCloudSlave#terminate: FATAL: Computer for agent is null: jenkinsarjun-2hs5r”

“Note : previosly I didnt added memory and cpu req /limit values after adding resources the pod getting created in k8 cluster ,but it is terminating quickly, no pod logs avialable”

4

Hello

How I can see the error have changed. That IS a good Signal. The error

All nodes of label ‘jnlpslave’ are offline

Can means that the namespace doent have enough quota to provide resources to the pod.

You can check it with the commnad

Kubectl describe [namespace name]

I hope this Will be the problem

Regrards

5

Hi rumberomelo,

Thanks for your precious time. Still the pod is getting terminated.is this a proxy issue.I have updated the resource quotas in namespace ., please find the ns yaml. This time i pasted jenkns Dashboard logs and also the agent pod logs

apiVersion: v1
kind: Namespace
metadata:
annotations:
cattle.io/status: >-
{“Conditions”:[{“Type”:“ResourceQuotaInit”,“Status”:“True”,“Message”:“”,“LastUpdateTime”:“2023-07-08T18:11:11Z”},{“Type”:“InitialRolesPopulated”,“Status”:“True”,“Message”:“”,“LastUpdateTime”:“2023-07-08T18:11:11Z”}]}
field.cattle.io/containerDefaultResourceLimit: >-
{“limitsCpu”:“500m”,“limitsMemory”:“600Mi”,“requestsCpu”:“400m”,“requestsMemory”:“500Mi”}
field.cattle.io/projectId: c-lfm9r:p-ttp7l
lifecycle.cattle.io/create.namespace-auth: ‘true’
creationTimestamp: ‘2023-07-08T18:11:10Z’
finalizers:
- controller.cattle.io/namespace-auth
labels:
field.cattle.io/projectId: p-ttp7l
kubernetes.io/metadata.name: healthcheck
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
.: {}
f:field.cattle.io/containerDefaultResourceLimit: {}
f:field.cattle.io/projectId: {}
f:labels:
.: {}
f:field.cattle.io/projectId: {}
f:kubernetes.io/metadata.name: {}
manager: agent
operation: Update
time: ‘2023-07-08T18:11:10Z’
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:metadata:
f:annotations:
f:cattle.io/status: {}
f:lifecycle.cattle.io/create.namespace-auth: {}
f:finalizers:
.: {}
v:“controller.cattle.io/namespace-auth”: {}
manager: rancher
operation: Update
time: ‘2023-07-08T18:11:10Z’
name: healthcheck
resourceVersion: ‘179095929’
uid: d9c1cbda-65d1-4a3a-9435-4ba84a2b149c
spec:
finalizers:
- kubernetes
status:
phase: Active
###############################

in Jenkins dashboard the pods logs is showing as below error.

HTTP ERROR 404 Not Found

URI: /Radium-dev/computer/jenkinsarjun-c0b4z/podLog
STATUS: 404
MESSAGE: Not Found
SERVLET: Stapler

Powered by Jetty:// 10.0.13
################################################
After adding again resource quotas i am getting same error like in Jenkins Dashborad logs

2023-07-09 00:27:57
2023-07-08 18:57:57.536+0000 [id=34] INFO hudson.slaves.NodeProvisioner#update: jenkinsarjun-qj7r9 provisioning successfully completed. We have now 5 computer(s)
2023-07-09 00:27:58
2023-07-08 18:57:58.600+0000 [id=1011448] INFO o.c.j.p.k.KubernetesLauncher#launch: Created Pod: app-int healthcheck/jenkinsarjun-qj7r9
2023-07-09 00:28:00
2023-07-08 18:58:00.091+0000 [id=1011448] INFO o.c.j.p.k.KubernetesLauncher#launch: Pod is running: app-int healthcheck/jenkinsarjun-qj7r9
2023-07-09 00:28:07
2023-07-08 18:58:07.493+0000 [id=914096] INFO o.c.j.p.k.p.r.Reaper$TerminateAgentOnContainerTerminated#lambda$onEvent$1: healthcheck/jenkinsarjun-qj7r9 Container jnlp was just terminated, so removing the corresponding Jenkins agent
2023-07-09 00:28:07
2023-07-08 18:58:07.516+0000 [id=914096] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent jenkinsarjun-qj7r9
2023-07-09 00:28:07
2023-07-08 18:58:07.561+0000 [id=914096] INFO o.c.j.p.k.KubernetesSlave#deleteSlavePod: Terminated Kubernetes instance for agent healthcheck/jenkinsarjun-qj7r9
2023-07-09 00:28:07
2023-07-08 18:58:07.561+0000 [id=914096] INFO o.c.j.p.k.KubernetesSlave#_terminate: Disconnected computer jenkinsarjun-qj7r9
2023-07-09 00:28:08
2023-07-08 18:58:08.301+0000 [id=1011448] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: jenkinsarjun-qj7r9, template=PodTemplate{id=‘eead99eb-616a-400f-a4f7-803597e52b45’, name=‘jenkinsarjun’, namespace=‘healthcheck’, label=‘jnlpslave’, containers=[ContainerTemplate{name=‘jnlp’, image=‘bcr-de01.XXXXX/tid3fe/jenkinsagent:latest-jdk11’, workingDir=‘/home/jenkins’, command=‘’, args=‘’, resourceRequestCpu=‘100m’, resourceRequestMemory=‘100Mi’, resourceRequestEphemeralStorage=‘’, resourceLimitCpu=‘200m’, resourceLimitMemory=‘200Mi’, resourceLimitEphemeralStorage=‘’, envVars=[KeyValueEnvVar [getValue()=https://rb-XXXXXadium-dev:8080, getKey()=JENKINS_URL]], livenessProbe=ContainerLivenessProbe{execArgs=‘’, timeoutSeconds=0, initialDelaySeconds=0, failureThreshold=0, periodSeconds=0, successThreshold=0}}]}
2023-07-09 00:28:08
java.lang.IllegalStateException: Node was deleted, computer is null
2023-07-09 00:28:08
at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:187)
2023-07-09 00:28:08
at hudson.slaves.SlaveComputer.lambda$_connect$0(SlaveComputer.java:298)
2023-07-09 00:28:08
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
2023-07-09 00:28:08
at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:80)
2023-07-09 00:28:08
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
2023-07-09 00:28:08
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
2023-07-09 00:28:08
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
2023-07-09 00:28:08
at java.base/java.lang.Thread.run(Thread.java:829)
2023-07-09 00:28:08
2023-07-08 18:58:08.301+0000 [id=1011448] INFO o.c.j.p.k.KubernetesSlave#_terminate: Terminating Kubernetes instance for agent jenkinsarjun-qj7r9
2023-07-09 00:28:08
2023-07-08 18:58:08.324+0000 [id=1011448] SEVERE o.c.j.p.k.KubernetesSlave#_terminate: Computer for agent is null: jenkinsarjun-qj7r9
2023-07-09 00:28:08
2023-07-08 18:58:08.324+0000 [id=1011448] INFO hudson.slaves.AbstractCloudSlave#terminate: FATAL: Computer for agent is null: jenkinsarjun-qj7r9

########################### ############ #################

Jenkins agent Pod Logs in Kubernetes cluster :

Jul 08, 2023 7:05:01 PM hudson.remoting.jnlp.Main createEngine

Sun, Jul 9 2023 12:35:01 amINFO: Setting up agent: jenkinsarjun-9p9w9

Sun, Jul 9 2023 12:35:02 amJul 08, 2023 7:05:02 PM hudson.remoting.Engine startEngine

Sun, Jul 9 2023 12:35:02 amINFO: Using Remoting version: 3107.v665000b_51092

Sun, Jul 9 2023 12:35:02 amJul 08, 2023 7:05:02 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

Sun, Jul 9 2023 12:35:02 amINFO: Using /home/jenkins/remoting as a remoting work directory

Sun, Jul 9 2023 12:35:02 amJul 08, 2023 7:05:02 PM org.jenkinsci.remoting.engine.WorkDirManager setupLogging

Sun, Jul 9 2023 12:35:02 amINFO: Both error and output logs will be printed to /home/jenkins/remoting

Sun, Jul 9 2023 12:35:03 amJul 08, 2023 7:05:03 PM hudson.remoting.jnlp.Main$CuiListener status

Sun, Jul 9 2023 12:35:03 amINFO: Locating server among [https://rb-jmaaXXXXX.com/Radium-dev:8080/]

Sun, Jul 9 2023 12:35:06 amJul 08, 2023 7:05:06 PM hudson.remoting.jnlp.Main$CuiListener error

Sun, Jul 9 2023 12:35:06 amSEVERE: Failed to connect to https://jj-XXXXXcom/Raium-dev:8080/tcpSlveAgentListener/: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Sun, Jul 9 2023 12:35:06 amjava.io.IOException: Failed to connect to https://jj/XXX/Raium-dev:8080/tcpSlaveAgentListener/: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Sun, Jul 9 2023 12:35:06 am at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:216)

Sun, Jul 9 2023 12:35:06 am at hudson.remoting.Engine.innerRun(Engine.java:755)

Sun, Jul 9 2023 12:35:06 am at hudson.remoting.Engine.run(Engine.java:543)

Sun, Jul 9 2023 12:35:06 amCaused by: javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.Alert.createSSLException(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.TransportContext.fatal(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.checkServerCerts(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.onConsumeCertificate(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.CertificateMessage$T13CertificateConsumer.consume(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLHandshake.consume(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.HandshakeContext.dispatch(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.TransportContext.dispatch(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLTransport.decode(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLSocketImpl.decode(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLSocketImpl.readHandshakeRecord(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.SSLSocketImpl.startHandshake(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.net.www.protocol.https.HttpsURLConnectionImpl.connect(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:213)

Sun, Jul 9 2023 12:35:06 am … 2 more

Sun, Jul 9 2023 12:35:06 amCaused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.validator.PKIXValidator.doBuild(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.validator.PKIXValidator.engineValidate(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.validator.Validator.validate(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.X509TrustManagerImpl.validate(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.X509TrustManagerImpl.checkTrusted(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(Unknown Source)

Sun, Jul 9 2023 12:35:06 am … 18 more

Sun, Jul 9 2023 12:35:06 amCaused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.provider.certpath.SunCertPathBuilder.build(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/sun.security.provider.certpath.SunCertPathBuilder.engineBuild(Unknown Source)

Sun, Jul 9 2023 12:35:06 am at java.base/java.security.cert.CertPathBuilder.build(Unknown Source)

Sun, Jul 9 2023 12:35:06 am … 24 more

Regards
Arjun

6

Hi,
The problem now seems the ssl validation. You have to get the certificate on https://jj and save into cacerts of the agent java virtual machine.

You can use OpenSSL app to get the certificate and the keytool app to save It into cacerts. There are a lot of examples in the web.

Try It and Tello me the results.
Bye

7

Please did you find solution ? i have same issue