Burn job from Mac failing

Flame Flame Questions
, , ,
1

So here’s a strange one.

Mac Flame
9.3 Burn node
Flame 2025_2_2 / Burn 2025_2_2
Symlinked project from Lucidlink to NAS

[flame@flame-01 projects]$ ls -lag
lrwxrwxrwx 1 flame 0 Nov 12 13:31  XXXXX -> /Volumes/projects/XXXXX

…and Pathing for Lucid and NAS on all machines identical.

Submitting a job from the Mac fails. Errors with:

2025/01/09 19:21:04 ERR [error] 2114525504 bgAdapter.C:384 01/09/25:19:21:04.062 Burn task error: Export path '/Volumes/cloud/projects/XXXXX/' does not exist

I can absolutely reach that path on the burn node in question via a terminal or file browser so I setup a (hail Mary) path translation on the host such that:

/Volumes/cloud/projects/XXXXX/ -> /Volumes/projects/XXXXX/

…and Burn submission still fails with the same error.

I opened a case (which America’s doesn’t seem to be responding to) but I thought I might throw this up here in case one of the folks more experienced then myself has any ideas. I can say that material in other projects without the symlink renders fine.

I can also say that when a Linux Flame can submits the same job, it absolutely renders fine and without error.

Any thoughts?

Support case is 23578405 @fredwarren or @Slabrie

2

We let them the support team investigate the issue and let you know.

1 Like
4

Adding this here as well from diagnostics…

[warn] 2470129664 CoFileIO_MACOSX.cpp:114 01/17/25:12:08:14.489 Unknown file system type 30 [lucidfs]

[warn] 2482860032 CoFileIO_MACOSX.cpp:114 01/17/25:12:08:15.513 Unknown file system type 30 [lucidfs]

[warn] 2487103488 CoFileIO_MACOSX.cpp:114 01/17/25:12:08:16.503 Unknown file system type 30 [lucidfs]

[warn] 2491346944 CoFileIO_MACOSX.cpp:114 01/17/25:12:08:16.686 Unknown file system type 30 [lucidfs]

5

So for anyone that runs up against the same issue:

It’s Lucid.

I switch the user authentication for all flame machines over from SSO via okta to Lucid internal user management, setup daemons for the linux boxes, enabled and restarted and launched Flame on the Linux boxes as well as the Macs.

Burn submissions for Mac happily rendered on the burn node for the timeline, conform and batch.

Next I reassigned all machines to a single BB manager and double checked that all other services were working as expected. Burn, background reactor, caching and background exports all seem to be working on both Mac and the Linux boxes.

I double checked the Lucid install. In the home account of the mounting user there needs to be a an app.json there which should be edited to allow other users to mount the file space…

The details of that can be found here →

https://support-classic.lucidlink.com/hc/en-us/articles/28419147930253-Using-fuse-allow-other-with-the-Lucid-application-Linux

Ours are correct:

[flame@flame-01 ~]$ cat .lucid/app.json 
{
  "updater": {
    "notificationInterval": 86400,
    "askMeLaterIgnoreDuration": 1209600
  },
  "fuseAllowOther": true,
  "filespaces": [
    {
      "user": "XXXXX",
      "filespaceName": "XXXXX",
      "lastLogin": 1737486352,
      "updatedAt": 1737486352,
      "stayConnected": false,
      "filespace": "XXXXX",
      "ssoLoginName": "XXXXX",
      "ssoProvider": "okta"
    }
  ],
  "instances": [
    {
      "filespaceId": "XXXXX",
      "filespaceName": "XXXXX",
      "instance": 501
    }
  ]
}

Likewise our fuse.conf is correct:

[flame@flame-01 ~]$ cat /etc/fuse.conf 
# mount_max = 1000
# user_allow_other
user_allow_other

So one more case for the Lucid support team.

2 Likes
6

This is also a fine way to allow Flame caching of media from Lucid Link. Without this procedure, you cannot cache from Lucid Link.