-
Notifications
You must be signed in to change notification settings - Fork 289
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
buildbox-artifact hanging #32
Comments
Does running the |
Nothing particularly useful. We don't suppress the output on our builds. I've run it manually and replicated the resultant hang. I copied the buildbox env settings from a running build, and also set the AWS env variables.
It's hasn't returned to the shell after that last file. Note the "Failed to read file ... is a directory" errors are expected and normal. |
So it just gets stuck after that? |
Yep. I let it sit for about 10 minutes then had to CTRL-C it. |
What happens as a test, if you remove the "upload the s3" part, and upload to BB. Does that change anything? (Sorry about the hassle) |
Also try a "--debug" on the command to get more info. |
As an aside, and it might be a different issue, but we're getting a lot of stuck builds at the moment. Given the issues with artifacts, I simply disabled them for the time being yesterday so we could get our builds going. However I am now finding that buildbox-agent simply stops responding, on both servers, usually within about 10-15 mins of each other (worth noting our build time is about 15 mins). I downgraded one of the systems to 0.1 for comparison, but both are still seeing the same symptoms. I'm now running both in a console with --debug, we'll see what comes out of that. One particularly annoying part of this is that sometimes the agent is telling the buildbox server that it's picked up a build, but then never reports that it's even started the first part of the build. This results in the buildbox server never giving the ci box another job, even after restarting the agent. The only way I can track these down (short of stopping every queued build and re-queueing them) is by looking at the agent status and seeing what build it thinks it's running, then re-queueing that one. |
@keithpitt will do. Oddly enough it's been quite stable now that I'm running it manually (not as a service) and with debug on. |
I haven't seen the hanging issue again while running the agent in the foreground with debug enabled. I've just updated to the latest beta (beta8) and re-enabled artifacts, I'll see how it goes. |
I am using beta8 on three systems at the moment, running in a terminal with --debug. 2 of the 3 agents have frozen, are no longer polling, and stopped putting any information into the debug terminal. One froze at 12:43:08, the other at 12:19:30. |
@sj26 has just made some tweaks to how artifacts are handled. When you get some time, can you upgrade to https://github.com/buildboxhq/buildbox-agent/releases/tag/v0.2-beta.10 |
Since beta9 and beta10 it's been fairly stable, I haven't seen the buildbox process hang and artifacts haven't hung for a while now. |
I'm going to close this. Hopefully it doesn't come back :) |
This initially seemed similar to #30 however I am not seeing any certificate errors, and I've also upgraded to the version listed in this issue (0.2-beta.3) but I am still seeing the issue.
Basically it seems that artifacts are uploaded to S3 (Amazon) correctly but the process never finishes, and builds will hang forever on this step. Running an strace against the process doesn't yield anything particularly useful, other than it looping through some kind of wait state.
The text was updated successfully, but these errors were encountered: