-
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
PNG frames were not sent to S3 bucket #8
Comments
Difficult to say. You'd have to look at the log files to see if the brenda-node script running the EC2 instances had trouble pushing the PNG files to S3. James |
That's the other issue I'm having, blenda-tool gives an error when I try to use it. |
James, I've provision a new EC2 instance using the ami-018c9568, which is Ubuntu 14.04. brenda-tool works as it should. I've done a new test to render 10 frames of a blender project. When I execute the s2cmd ls s3://test_bucket_name the bucket is empty. After looking at the log I get this ------- ec2-54-85-95-9.compute-1.amazonaws.com Blender quit The .blender file is not being seen as a blend file |
James, I found the issue. The blenda file was for version 2.7 I had the make it 2.6x compatible after that it worked. The problem now is that of the 500+ frames only 1 frame is being rendered. |
James, I figured out the issue as to why a single frame is being rendered. The frame-template file was wrong. All the renders were overwriting each other. |
I've completed a job, once the job was done and I checked the project_bucket (not the actual name of the s3 bucket) the PNG frame were not there. The Ec2 instances were already terminate by the DONE=shutdown parameter in ~/.brenda.conf file. I'm re-running the job and I have commented the parameter so that I can have a look at the EC2 log files.
Is it possible I have done something wrong during the setup of the job which would result in this issue?
The text was updated successfully, but these errors were encountered: