[
https://issues.jenkins-ci.org/browse/JENKINS-13731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162702#comment-162702
]
bap commented on JENKINS-13731:
-------------------------------
The outputs are not monitored for inactivity, the command completes when the
output and error streams are closed.
The timeout is an overall timeout ie. "if the command does not complete in this
time, then it is probably borked, so disconnect, mark as failure and allow
jenkins to release the executor"
>From the above, it looks like you have configured a 4 minute timeout and the
>yum command did not complete within that window.
Try setting your timeout to 150% or 200% of the time you expect the command to
complete in.
Looking at the above output I would suggest starting with at least 10 minutes,
and see how it goes.
> When using ssh-exec with yum install timeout occurs
> ---------------------------------------------------
>
> Key: JENKINS-13731
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13731
> Project: Jenkins
> Issue Type: Bug
> Components: publish-over-ssh
> Reporter: Sebastian Ruehl
> Assignee: bap
>
> When using a ssh-exec with yum install a timeout occurs.
> It seems that is a problem with the progress bar that won't be displayed
> during the build but after.
> At the end of the build you can see that for each output a line is produced.
> (3/5): package-a- (29%) 26% [=== ] 421 kB/s | 20 MB 02:14 ETA
> (3/5): package-a- (29%) 26% [=== ] 402 kB/s | 20 MB 02:20 ETA
> (3/5): package-a_f- (29%) 26% [=== ] 348 kB/s | 20 MB 02:42 ETA
> SSH: Disconnecting configuration [rpm target] ...
> ERROR: Exception when publishing, exception message [Exec timed out or was
> interrupted after 240.653 ms]
> It seems that these outputs are not recognized during a build which leads to
> a timeout.
> Possible workaround: Turnup timeout
> Caveat: you don't know whenever the build is running or stuck...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
