Howdy folks. I’m running Rocky 9.5 on all my machines. I’ve got one main workstation with local storage and three burn nodes connected to that. Curiously even with all these fresh installs, I’m only able to send renders to the burns via Flame 2025.2. 2026 is installed and detected on the other machines, but the jobs just crash out and get stuck waiting at 0% in Backburner monitor.
I don’t urgently need to move to 2026 or anything, but I was curious if anyone else had run into any quirks migrating and how if so how they’d solved them.
are you rendering soft-imported footage to file sequences?
check you rmountpoints.
if you are using legacy managed media that has been upgraded to a 2026 media cache directory, make sure that your 2026 media can be accessed by your burn nodes.
from your description it would appear to be mountpoints.
Will put whatever solution I figure out here for posterity so folks can find it easily down the road. Based on the discord convos I just need to be using NFS instead of SMB to mount my local disks as a NAS. I have to step away from the machine today but will report back when I get to futzing with it tomorrow!
I know you said that it works for you in v2025 - i had an issue getting 2025 to run that sounds similar to what you are seeing here. Ive not yet got round to v2026.
When installing burn - everything looked ok with the installer and node shows up as ready/idle in BBM. but when given a job it just hangs. It turned out to be with the installer - specifically VirtualGL not installing correctly. One clue to this would be to see if the vglusers group was succesfully made. if not, try manully installing virtualGL (dnf install -e 1 -d 1 -y VirtualGL --nobest) and then re-installing burn.
just a thought..