Flamenco Manager does not report the storage location correctly when mapping to a bare drive path #104237
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#104237
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?
System Information
Operating System(s): Windows 10 22H2, Ubuntu 22.04.02 LTS
Flamenco Version
Is Broken: 3.2
Worked OK: 3.1
Short description of error
When using Flamenco 3.2, Linux machines that have tasks sent to them will be given the file path using backslashes instead of forward slashes, resulting in a failure.
Exact steps for others to reproduce the error
In Flamenco 3.1, the variables below in flamenco-manager.yaml would work properly, resulting in the following log:
However, when using the same variables in Flamenco 3.2, the following log appears:
On Windows machines this error doesn't appear and Flamenco 3.2 works normally. For context, I didn't use Shaman in either 3.1 or 3.2.
Please include steps to reproduce this. I'm fairly sure that it's relevant which OS the Manager is running on, and same for the Workers. This, however, is not specified in the report.
Sorry about that, the manager is running on Windows 10, two other workers (one of them being the network storage) are also running on W10 without issue, but the one having problems is on Ubutnu.
Reproducing it (at least on my end) is pretty straightforward:
When using the same computers and configuration on Flamenco 3.1, both Windows and Ubuntu machines were able to run through all the tasks normally. However, I was also using Blender 3.4 and 3.5 previously. I can test Flamenco 3.2 with those versions to see if Blender is actually the cause when I have some time.
Thanks for the detailed info. This certainly looks like a bug to me.
Yup, that was a bug. Thanks again for the report!
Flamenco Manager uses backslashes instead of forward slashes for file paths when assigning a job to Linux workers.to Flamenco Manager does not report the storage location correctly when mapping to a bare drive pathI am a first time user, so I may well just be doing the install wrong. I have a similar setup to NovaXP, but on slightly different hardware/APIs.
A Windows 10 computer acts both as my flamenco-manager as well as the host for my file sharing service (the root is C:\blends). I am using an OS X Catalina computer as my flamenco-worker, with the shared directory at /Volumes/blends . Both are connected through their respective OS-proprietary SMB services. Both are running the most recent version of Flamenco (3.2) and Blender (3.6.1).
During manager setup on Windows, I set the shared storage location to my shared directory, C:\blends (note, unlike NovaXP, my blender folder is the only thing exposed on the network).
With setup finished, I append the following to flamenco-manager.yaml :
I only have one worker (on Catalina named myComputer.local, with username myUser), so i just launch flamenco-worker from /Users/myUser/Downloads folder. C:\blends is networked to /Volumes/blends .
I entered my manager's IP into the manager's Blender add-ons prompt as instructed, as well as routing it to C:\blends . With worker running on Catalina, Echo Sleep Test ran flawlessly, and there are no errors on startup of either the manager or worker processes.
I have a test project located at C:\blends\test with savefile test.blend, featuring 5 frames of default cube.
For Simple Blender Render, I set render to PNG with Render Output Root as C:\blends\renders ('relative path' disabled). Submitting to Flamenco, the log outputs:
Of course, the issue is the construction/parsing of the path '/Users/myUser/C:\blends\test\test.flamenco.blend', but I am unsure whether it is a replication of NovaXP's bug, or if I'm botching the yaml file somehow or mac user groups need to change for my setup. Apologies if it is the latter.
Given that the fix hasn't been released yet, what are you installing? Did you build the fixed Flamenco yourself?
Ah yes, that version still has the bug, so there is no use in re-testing with that particular one. You'll either have to wait for Flamenco 3.3 to be released, build it yourself, or grab the special SIGGRAPH 2023 build. Be aware that the latter is an alpha release, i.e. is not feature-complete and may have bugs.
@dr.sybren I think I may be experiencing this same issue in my setup as well. Can you please confirm whether there is an immediate solution in my case or if I need to wait until 3.3 as well?
Flamenco 3.2 manager is installed on a Win10 machine with Shaman enabled. The local worker works great. We tried to add a second worker on a different machine (Win 11) but it keeps giving an error: "Unable to read file "F:\jobs\test\test09-14.blend" Invalid Argument" and it soft-fails the job.
The same drive is mapped to F:\ on both systems. The drive itself is an SMB share hosted by the same computer that is running the Flamenco Manager
I have also tried a different computer with a brand new Windows 10 install and it gets the same issue. I have made sure symlinks are enabled on all relevant machines. I spent several hours on this today and haven't been able to get anywhere with it. What is your suggestion?
Thanks
The immediate solution would be to grab the sources and build Flamenco yourself. This is documented at https://flamenco.blender.org/development/getting-started/
Symlinks are still notoriously difficult for Windows machines. I would recommend running Linux, at least for the Manager and the Workers, or turning off the Shaman system.