Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Jenkins leaves behind connections in ESTABLISHED state

Description

Throughout the last days I noticed several times when a slave got non-responsive and after rebooting it never recovered until being removed/re-added to Jenkins.

Further investigation on el7-vm06.phx.ovirt.org revealed that on Jenkins the connection is still marked as "ESTABLISHED" hours after the slave crashed and rebooted:

tcp6 0 0 66.187.230.92:33374 66.187.230.77:22 ESTABLISHED 14625/java

Due to this new SSH connections are not opened and Jenkins can't reconnect to the slave.
I didn't see this behavior before, maybe it is related to the latest security upgrade of jenkins.

Activity

Show:

Former user January 20, 2017 at 11:57 AM

Didn't see this issue after upgrading Jenkins. Closing for now, will re-open if it happens again

Former user December 8, 2016 at 1:35 PM

Will monitor after core is updated to 2.x ( )

Eyal Edri December 8, 2016 at 12:51 PM

see if this is still relevant.

Fixed

Details

Assignee

Reporter

Blocked By

Priority

Parent

Created September 13, 2016 at 8:46 AM
Updated January 30, 2017 at 9:25 AM
Resolved January 20, 2017 at 11:57 AM