-
Notifications
You must be signed in to change notification settings - Fork 67
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
Getting Bad HTTP Status Code error from some Instances #4
Comments
I was able to re-run a similar job without this error. Seems as though I was trying to use subfolders in my buckets. The tutorial does specifically prescribe against this, but since the S3 console let me add subfolders, I thought it would be okay. Turns out you need to use a separate bucket for source and output areas, and no subfolders. Lesson learned! It would be nice in the future to somehow support sub folders, especially if you want to further automate the render job launching process, but it's not biggie right now. |
I am getting the same problem now (-5, 'PC_ERR_HTTP : bad HTTP status code') on all machines and I haven't messed with a sub-folders. Can anyone show me direction what could I check to find where have I mistaken. Thanks. |
I solved the problem by a installing on a client: so some of those was making trouble probably. |
I had this same error. Turns out I had my project file name misspelled in .brenda.conf... |
I saw this error as well, and it was because I accidentally pushed the .blend file to s3 instead of the .tar.gz |
* Switch to open() from file() * Add fixed AMI * Get test script working
I'm getting this error from some of the instances but not all of them:
Probably my settings, but I'm having trouble figuring it out.
Any ideas?
The text was updated successfully, but these errors were encountered: