Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-13731] When using ssh-exec with yum install timeout occurs #217

Closed
jira-importer opened this issue May 10, 2012 · 1 comment
Closed

Comments

@jira-importer
Copy link
Collaborator

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...


Originally reported by sruehl, imported from: When using ssh-exec with yum install timeout occurs
  • assignee: bap
  • status: Closed
  • priority: Major
  • resolution: Not A Defect
  • resolved: 2012-05-12T21:42:13+10:00
  • imported: 2022/01/10
@jira-importer
Copy link
Collaborator Author

bap:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant