Flamenco 3.0 Beta 2 - Cached job type is old, job rejected #100735

New Issue

Riccardo Giovanetti · 2022-08-31T20:14:09+02:00

2022-08-31 20:14:09 +02:00

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94

Blender Version
Version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: blender/blender@bcfdb14560

Flamenco Version
flamenco-3.0-beta2-windows-amd64.zip

Short description of error
At job submission I get this error message, and the job is rejected: "Cached job type is old. Refresh the job types and submit again, please"
I don't understand, find, how to "refresh" the job types.

Exact steps for others to reproduce the error
I downloaded the latest Beta 2 version of Flamenco, as well as the related Blender add-on.
As per my previous bug report (#100226) I kept the same folders structure and deleted everything but the test file inside D:\Flamenco\projects;
copied the new beta2 version's files inside D:\Flamenco\software\flamenco;
deleted the worker's configuration files inside C:\Users\Riccardo\AppData\Local\Blender Foundation\Flamenco;
started the Flamenco Manager and successfully configured it to run Blender from D:\Blender_3.2_stable\blender.exe, as well as downloaded the latest add-on for Blender from the link available in the Manager Web interface;
started the Flamenco Worker, successfully finding my laptop as an available worker;
started Blender 3.2.2, installed the latest Flamenco add-on, and opened the test file inside D:\Flamenco\projects.

Clicking on the button to send the job to the Manager I get the following error messages in the Blender Scripts console:
"Cached job type is old. Refresh the job types and submit again, please"

In the Manager console I get this error message:
WRN rejecting submitted job, job type etag does not match error="job type etag does not match: expecting "3120b88aa98c62b463c684ede08ddabe9dd1e764", submitted job has "d58dbf05dd8acdc6dc8c2710a0209a0bade7045c"" name=test type=simple-blender-render

I don't know how to "refresh the job types" and I don't see this option in the Web Interface either. Tried to resend the job as well as to reinstall everything from scratch one more time, as per above description, but I always get the same error and job rejection.

These are the Flamenco Manager configuration files inside D:\Flamenco\software\flamenco:
flamenco-manager.sqlite
flamenco-manager.yaml

These are the Flamenco Worker configuration files inside C:\Users\Riccardo\AppData\Local\Blender Foundation\Flamenco:
flamenco-worker.sqlite
flamenco-worker-credentials.yaml

This is the test file inside D:\Flamenco\projects:
the_cube.blend

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.94 **Blender Version** Version: 3.2.2, branch: master, commit date: 2022-08-02 18:15, hash: `blender/blender@bcfdb14560` **Flamenco Version** flamenco-3.0-beta2-windows-amd64.zip **Short description of error** At job submission I get this error message, and the job is rejected: "Cached job type is old. Refresh the job types and submit again, please" I don't understand, find, how to "refresh" the job types. **Exact steps for others to reproduce the error** I downloaded the latest Beta 2 version of Flamenco, as well as the related Blender add-on. As per my previous bug report (#100226) I kept the same folders structure and deleted everything but the test file inside D:\Flamenco\projects; copied the new beta2 version's files inside D:\Flamenco\software\flamenco; deleted the worker's configuration files inside C:\Users\Riccardo\AppData\Local\Blender Foundation\Flamenco; started the Flamenco Manager and successfully configured it to run Blender from D:\Blender_3.2_stable\blender.exe, as well as downloaded the latest add-on for Blender from the link available in the Manager Web interface; started the Flamenco Worker, successfully finding my laptop as an available worker; started Blender 3.2.2, installed the latest Flamenco add-on, and opened the test file inside D:\Flamenco\projects. Clicking on the button to send the job to the Manager I get the following error messages in the Blender Scripts console: "Cached job type is old. Refresh the job types and submit again, please" In the Manager console I get this error message: WRN rejecting submitted job, job type etag does not match error="job type etag does not match: expecting \"3120b88aa98c62b463c684ede08ddabe9dd1e764\", submitted job has \"d58dbf05dd8acdc6dc8c2710a0209a0bade7045c\"" name=test type=simple-blender-render I don't know how to "refresh the job types" and I don't see this option in the Web Interface either. Tried to resend the job as well as to reinstall everything from scratch one more time, as per above description, but I always get the same error and job rejection. These are the Flamenco Manager configuration files inside D:\Flamenco\software\flamenco: [flamenco-manager.sqlite](https://archive.blender.org/developer/F13441780/flamenco-manager.sqlite) [flamenco-manager.yaml](https://archive.blender.org/developer/F13441782/flamenco-manager.yaml) These are the Flamenco Worker configuration files inside C:\Users\Riccardo\AppData\Local\Blender Foundation\Flamenco: [flamenco-worker.sqlite](https://archive.blender.org/developer/F13441788/flamenco-worker.sqlite) [flamenco-worker-credentials.yaml](https://archive.blender.org/developer/F13441789/flamenco-worker-credentials.yaml) This is the test file inside D:\Flamenco\projects: [the_cube.blend](https://archive.blender.org/developer/F13441795/the_cube.blend)

Riccardo Giovanetti commented

2022-08-31 20:14:09 +02:00

Added subscriber: @Harvester

Dalai Felinto commented

2022-09-01 10:48:38 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2022-09-01 10:48:38 +02:00

The Flamenco Beta 3.0 just came out (yesterday). Can you confirm if the problem persist there? Thanks

Riccardo Giovanetti commented

2022-09-01 11:01:40 +02:00

Hi Dalai,

I downloaded and tested Flamenco 3.0 Beta 2 yesterday. In case, this afternoon (I'm at work now) I can redo from scratch these tests after downloading the current beta, but I presume it is the same as the one I downloaded yesterday. Let me know if I should proceed.

Regards,
Riccardo

Hi Dalai, I downloaded and tested Flamenco 3.0 Beta 2 yesterday. In case, this afternoon (I'm at work now) I can redo from scratch these tests after downloading the current beta, but I presume it is the same as the one I downloaded yesterday. Let me know if I should proceed. Regards, Riccardo

Dalai Felinto commented

2022-09-01 11:07:48 +02:00

Hi Riccardo. If you downloaded the Beta 2 it is indeed the old one. The Beta 3 was released late yesterday.

Riccardo Giovanetti commented

2022-09-01 11:16:19 +02:00

OK, I will retest it and let you know the results.

Sybren A. Stüvel commented

2022-09-01 13:09:40 +02:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2022-09-01 13:09:40 +02:00

This is expected behaviour. The Manager has changed, and because of that the data cached by Blender is outdated. This system prevents you from submitting a job with outdated settings. Just click the 'refresh' button next to the job type select box, and it should work. Be sure to save the file after refreshing.

blender-admin commented

2022-09-01 14:46:22 +02:00

This issue was referenced by 46792ee164

This issue was referenced by 46792ee164bf000204a159c62c429375dcc54678

Riccardo Giovanetti commented

2022-09-01 18:48:02 +02:00

I confirm that Flamenco Beta 3 works as expected. (You can stop reading here, for the purpose of the bug report.)

The only problem I have, at the moment, is related to its naming conventions of the rendered job folders and files, but hopefully this will be made customizable in the future.

In our small production, we need to name each rendered frame/file using a prefix for the shot, needed for proper editing (in DaVinci Resolve) and post-processing. Currently, Flamenco creates a folder with the Job Name (eg. D:\Flamenco\renders\test2) and a subfolder for each render task/instance named with the date and time (eg. D:\Flamenco\renders\test2\2022-09-01_170734), and inside it all files are named just with a frame number of 6 digits (eg. 000001.png). Obviously, the Job Name in Blender can be named with the shot number (eg. D:\Flamenco\renders\s01_01\2022-09-01_170734) but then the created subfolder (\YYYY-MM-DD_time) adds complexity to the path and the files don't have a meaningful name, for our purpose. Hopefully, this might change in the future, allowing customization of paths and/or rendered file naming.

For your information, Flamenco renders also OpenEXR files, which is what we need in production but, obviously, doesn't create a video from them, which anyway we don't need, but it's instead useful when we render animatics of the shots using PNG format. Thank you.

One question. How would you manage to render shots from a production folders structure like the one below, with all data linked inside the shot's .blend files? Currently, it seems to manage only files inside the D:\Flamenco\project folder, which is good for a single Blender file project but not for a real production with linked data as ours. Thank you.

I confirm that Flamenco Beta 3 works as expected. (You can stop reading here, for the purpose of the bug report.) The only problem I have, at the moment, is related to its naming conventions of the rendered job folders and files, but hopefully this will be made customizable in the future. In our small production, we need to name each rendered frame/file using a prefix for the shot, needed for proper editing (in DaVinci Resolve) and post-processing. Currently, Flamenco creates a folder with the Job Name (eg. D:\Flamenco\renders\test2\) and a subfolder for each render task/instance named with the date and time (eg. D:\Flamenco\renders\test2\2022-09-01_170734), and inside it all files are named just with a frame number of 6 digits (eg. 000001.png). Obviously, the Job Name in Blender can be named with the shot number (eg. D:\Flamenco\renders\s01_01\2022-09-01_170734) but then the created subfolder (\YYYY-MM-DD_time) adds complexity to the path and the files don't have a meaningful name, for our purpose. Hopefully, this might change in the future, allowing customization of paths and/or rendered file naming. For your information, Flamenco renders also OpenEXR files, which is what we need in production but, obviously, doesn't create a video from them, which anyway we don't need, but it's instead useful when we render animatics of the shots using PNG format. Thank you. One question. How would you manage to render shots from a production folders structure like the one below, with all data linked inside the shot's .blend files? Currently, it seems to manage only files inside the D:\Flamenco\project folder, which is good for a single Blender file project but not for a real production with linked data as ours. Thank you. ![immagine.png](https://archive.blender.org/developer/F13447273/immagine.png)

Sybren A. Stüvel commented

2022-09-01 19:33:44 +02:00

Changed status from 'Needs Triage' to: 'Resolved'

Sybren A. Stüvel closed this issue

2022-09-01 19:33:44 +02:00

Sybren A. Stüvel self-assigned this 2022-09-01 19:33:44 +02:00

Sybren A. Stüvel commented

2022-09-01 19:33:44 +02:00

In #100735#1411189, @Harvester wrote:
The only problem I have, at the moment, is related to its naming conventions of the rendered job folders and files, but hopefully this will be made customizable in the future.

That's already customisable :)

https://flamenco.blender.org/usage/job-types/ has a little primer on how that's done.

For your information, Flamenco renders also OpenEXR files, which is what we need in production but, obviously, doesn't create a video from them, which anyway we don't need, but it's instead useful when we render animatics of the shots using PNG format. Thank you.

Glad to hear that!

One question. How would you manage to render shots from a production folders structure like the one below, with all data linked inside the shot's .blend files? Currently, it seems to manage only files inside the D:\Flamenco\project folder, which is good for a single Blender file project but not for a real production with linked data as ours. Thank you.

That should work just fine as well with Flamenco. You can read more on the different storage methods on https://flamenco.blender.org/usage/shared-storage/.

If you have more questions, please write me on the #flamenco chat channel; we shouldn't be using this bug report as further discussion forum ;-)

> In #100735#1411189, @Harvester wrote: > The only problem I have, at the moment, is related to its naming conventions of the rendered job folders and files, but hopefully this will be made customizable in the future. That's already customisable :) https://flamenco.blender.org/usage/job-types/ has a little primer on how that's done. > For your information, Flamenco renders also OpenEXR files, which is what we need in production but, obviously, doesn't create a video from them, which anyway we don't need, but it's instead useful when we render animatics of the shots using PNG format. Thank you. Glad to hear that! > One question. How would you manage to render shots from a production folders structure like the one below, with all data linked inside the shot's .blend files? Currently, it seems to manage only files inside the D:\Flamenco\project folder, which is good for a single Blender file project but not for a real production with linked data as ours. Thank you. > > ![immagine.png](https://archive.blender.org/developer/F13447273/immagine.png) That should work just fine as well with Flamenco. You can read more on the different storage methods on https://flamenco.blender.org/usage/shared-storage/. If you have more questions, please write me on [the #flamenco chat channel](https://blender.chat/channel/flamenco); we shouldn't be using this bug report as further discussion forum ;-)

Sybren A. Stüvel commented

2022-09-01 19:35:31 +02:00

PS: I addressed this issue in 46792ee164.

PS: I addressed this issue in 46792ee164.

Riccardo Giovanetti commented

2022-09-01 19:47:51 +02:00

Thank you very much, Dr. Sybren!

Sign in to join this conversation.