#7960 java.net.SocketTimeoutException: sent ping but didn't receive pong within 1000ms (after 1 successful ping/pongs)
Closed: Fixed 5 years ago by pingou. Opened 5 years ago by bgoncalv.

During execution of some builds we see this error happening, it also seems in some cases it causes to build to fail.

It is related to https://pagure.io/fedora-ci/general/issue/54

It looks like that setting ping interval fixes the issue: https://issues.jenkins-ci.org/browse/JENKINS-53532?focusedCommentId=367502&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-367502


Add:

  -Dkubernetes.websocket.ping.interval=10000  -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=86400 

I'm guessing this needs set in centos-ci? @bstinson or @siddharthvipul1 can you take a look?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Assignee (was: Needs Review)

5 years ago

@kevin I spoke to Brian and confirmed, there is nothing really much for us to do. These are separate Jenkins Masters with all the access to project members. They can do it themselves :)
I remember answering this yesterday on IRC (to @bgoncalv )

@bgoncalv Were you able to confirm this with project members?

@siddharthvipul1, @astepano will try to deploy the application with this settings.

Let's close this for now then and we can re-open if the problem persist :)

Metadata Update from @pingou:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

Log in to comment on this ticket.

Metadata
Attachments 2