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: Unable to Connect to i7-debian-buster #2999

Closed
sanssecours opened this issue Sep 22, 2019 · 9 comments
Closed

Jenkins: Unable to Connect to i7-debian-buster #2999

sanssecours opened this issue Sep 22, 2019 · 9 comments

Comments

@sanssecours
Copy link
Member

Description

One of the newer Jenkins problems seem to be connection errors to i7-debian-buster:

ERROR: Issue with creating launcher for agent i7-debian-buster. The agent has not been fully initialized yet
Channel "unknown": Remote call on i7-debian-buster failed. The channel is closing down or has closed down

.

@markus2330
Copy link
Contributor

Maybe it was only a short connection problem? At the moment i7 is executing a build job.

@sanssecours
Copy link
Member Author

Maybe it was only a short connection problem?

That might be the case. However, I still think it makes sense to keep this issue open until we know that it wont happen again (often) in the near future.

@sanssecours
Copy link
Member Author

Jenkins just reported another error on i7-debian-buster that seems to be similar to the one described in this issue:

remote file operation failed

.

@markus2330
Copy link
Contributor

Thank you for reporting! Does restarting the job fix the problem?

@sanssecours
Copy link
Member Author

Does restarting the job fix the problem?

Probably, but the Jenkins build might fail again, because of various other problems. As far as I can tell, the probability that the whole Jenkins build finishes successfully is less than 50%.

@markus2330
Copy link
Contributor

That is really not good. Luckily, Djordje now starts working on it.

@markus2330
Copy link
Contributor

@markus2330
Copy link
Contributor

Is this fixed now? Maybe due to #2984

@sanssecours
Copy link
Member Author

Is this fixed now?

I am not sure. If I remember correctly, I did not see any similar warnings in the last two days though.

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

2 participants