Flamenco: Failed: command exited abnormally with code 11 #103673
Labels
No Label
Good First Issue
Priority
High
Priority
Low
Priority
Normal
Status
Archived
Status
Confirmed
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Job Type
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: studio/flamenco#103673
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I'm not sure where to report this case around Flamenco.
blender.crash.txt
Similar for Blender 3.2 - flamenco-3.1-windows-amd64.zip
The blender file was just a cube standard in test.blend file
Added subscriber: @ManBlender
it be nice to download old version https://flamenco.blender.org/downloads/
Please update the task description with steps to reproduce this issue. If it cannot be reproduced with standard Blender but requires a specific Blender add-on, then it's considerably harder to figure out what's going wrong.
That's a good idea. Until that's there, you can edit the URL of the packages to download other versions -- just change
3.2
to3.1
or3.0
.I have the same issue when I set up a multi platform farm:
They all start correctly and all see the correct share and files.
1 flying and 1 static, with moving parts.
I can share the files if really needed, they are combined somewhat around 115MB
Renderings are correct.
I hope this can help for this bug / problem. If I find a sollution myself, I update this message.
I added 3 loggings, one containing this error, 2 others contained other errors.
@BlackElkX thanks for the details on the setup and crash logs.
There is a discussion about "exit 11" in Flamenco chat here: https://blender.chat/channel/flamenco?msg=QEmqpZMJbQCb8h9Rp
The short of it is that this is a Blender exit code and not related to Flamenco. Flamenco spawns Blender with the .blend project file, with some parameters. It simply waits until Blender is done assuming if non-error exit code it was successful. If Blender signals it was not successful, Flamenco will simple reschedule the task again a number of attempts.
The OP mention Blender 3.2 on one machine. You list Blender 3.6 and various different machines.
The crash looks similar and looks to be a NULL pointer exception.
Do you get the same exception or crash just running Blender manually on a machine... with these parameters?
I can't think how Flamenco could influence this type of crash unless related to how Flamenco launches sub-processes (ie: Blender) when it has some work to do. It is more likely memory corruption or a bug in Blender.
If this crash doesn't happen by running Blender manually but only happens when a project is rendered using Flamenco that would be a very useful data point.
Let us know if this only happens when using Flamenco. If yes, then please provide more configuration on how Flamenco is provisioned in your farm. The specific project files would be very useful too to see if someone else on different hardware can reproduce the same crash.
@BlackElkX - a quick search on Blender and there are four open issues with specifically in the title but none look like this exactly type of null pointer exception (all zeros memory address).
You can see them using this query:
https://projects.blender.org/blender/blender/issues?type=all&state=open&labels=&milestone=0&project=0&assignee=0&poster=0&q=EXCEPTION_ACCESS_VIOLATION
I just noticed, two of your crash logs have multiple EXCEPTION_ACCESS_VIOLATIONs as well as the null pointer one.
Eg:
These happen near the start of the Blender run. I dont know how but these bug reports include a crash attachment that includes a stack trace which would be very helpful. Example of this type of log can be found in blender/blender#109903 at https://projects.blender.org/attachments/51027c56-71bc-4748-9210-d11c159cf852. (Note this may not be the exact same root cause... just an example of a blender crash log vs a Flamenco crash log).
This Blender crash file (not Flamenco) would be very helpful. Flamenco is only logging the output of Blender logs and not the crash log itself. On Windows, you would want to find a file .crash.txt. (https://docs.blender.org/manual/en/latest/troubleshooting/crash.html#windows)
This issue can be more observed around nvidia, etc. and in relation to GPU.
In normal mode eg. Blender or other 3d app is focused to run with GPU processor as priority and default, etc.
https://pureinfotech.com/set-default-gpu-apps-windows-11/
https://www.youtube.com/watch?v=hlyFjjJGaow
But when command line running flamenco or blender instance this setup can be omitted and render process if advanced (big project) failed. Then.. if small project working, that is more predicted whats going on.. if new sub-process.
I not solved this problem.
This is the main question to answer now. Just run this command in a terminal and see what happens. Just make sure all text ends up on the same line.
For @ManBlender to run:
For @BlackElkX to run:
I did some extra checks: Added a very recent asus rog laptop with 2060: works after I installed the flamenco plugin.
I did updates of windows for all windows machines: no change
I run the manager in a docker container on the linux i9 machine. Worker does not work either direct or in docker on same machine.
The AMD machine is still giving same errors: I check in Blender.
The Linux machine (both docker and direct): I cannot install the plugin, it has no X11 interface. I will try another machine to configure and copy the plugins and settings to this machine.
Status: 3 of 6 working: 1 iMac and 2 Win11
To be continued...
What 'plugin' is that? Do you mean the Blender add-on?
This is why I'm puzzled about the word "plugin". If this is about the Flamenco add-on for Blender, this is only necessary for submitting jobs to Flamenco. It does not need to be installed on the Workers.
If there's no info about what doesn't work, there's little I can do to help. As a general recommendation: avoid complicating your setup until you have things working. Containerising things in Docker adds complexity and I issues with such setups are off topic for this tracker. If you want to run things in Docker that's of course fine, but issues there cannot be handled as issues with Flamenco.
Closing due to inactivity of the reporter.