Remote logging Kubernetes agents dying due to channel closed exception

6 views
Skip to first unread message

Andrew Feller

unread,
Apr 25, 2019, 2:34:08 PM4/25/19
to jenkins...@googlegroups.com
We've been trying to troubleshoot OpenShift-support Jenkins Kubernetes agents terminating due to closed channel exceptions and reaching for straws here.  We're considering enabling remote logging as a last ditch effort to debug what is going on within the JNLP container, however I'm not sure how configuring -workDir should take into account ephemeral Kubernetes pods for agents.

Any help would be appreciated!
--

BandwidthMaroon.png


Andy Feller    Sr DevOps Engineer

900 Main Campus Drive, Suite 500, Raleigh, NC 27606



e: afe...@bandwidth.com

Carlos Sanchez

unread,
Apr 25, 2019, 3:45:07 PM4/25/19
to Jenkins Users
you should look into the networking layer in your kubernetes cluster, it may be aggressively closing connections

--
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/CAAg6KNENkQCCMSP4%2BOp99rxbcyGeSSjUA4-Fv_o8i1N4gsiJWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages