infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Takamori (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16609) jenkins node timeouts
Date Mon, 04 Jun 2018 17:12:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500537#comment-16500537
] 

Daniel Takamori commented on INFRA-16609:
-----------------------------------------

There was a bunch of hung processes so I disconnected the node and nuked all the old junk
on it.  Should be all better now.

> jenkins node timeouts
> ---------------------
>
>                 Key: INFRA-16609
>                 URL: https://issues.apache.org/jira/browse/INFRA-16609
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Jenkins
>         Environment: node H27
>            Reporter: Dan Kirkwood
>            Priority: Major
>
> I'm seeing network timeouts on node H27.   Here is one example: https://builds.apache.org/view/S-Z/view/TrafficControl/job/incubator-trafficcontrol-PR/1748/console
> <pre>
> + ./bin/docker-compose -p jenkins-incubator-trafficcontrol-PR-1748 -f infrastructure/docker/build/docker-compose.yml
up --build
> An HTTP request took too long to complete. Retry with --verbose to obtain debug information.
> If you encounter this issue regularly because of slow network conditions, consider setting
COMPOSE_HTTP_TIMEOUT to a higher value (current value: 120).
> </pre>



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message