Project: Error writing to database

[MagicMtn]

On 1 of 3 flames I am no longer able to open the projects properly.

The system will hang on the step “volumemgt : Initializing” and eventually give the Error Message: Project: Error writing to database

I am able to eventually get the projects open and had our flame artist export the archives he needs.

If we try to switch projects from within flame we receive a different error message:

Locked Project Database lock held by: Unknown 15051, on: flame3hostname. Retry?

So far we have tried just about every troubleshooting step we know:

• Rebuilding stone wire database from mirror
• Removing all .Ref* files from /opt/Autodesk/clip/Stonefs
• Removed all lock files from /opt/Autodesk/user/username/tmp/

If we try to to open the project of flame 1 (the problem machine) using another working flame we get the following error:

It sounds to me like our database is some how locked and thats why we cant write to it.
Any ideas whats going on, how to resolve this?

update: mac os 12.7.6 flame 2023.3

[philm]

@MagicMtn - I don’t have an answer but I’m curious if your setup is Linux or macOS?

[ytf]

It helps to have a version number with questions like these.

[allklier]

I assume rebooted as well?

That 15051 is most likely referencing a process id, or less likely a user id.

If you rebooted this may no longer apply. If you didn’t, I’d try

ps aux | fgrep 15051

and see if that exists and if so if you can kill it.

[philm]

@MagicMtn - are all flame versions at the same level?
Have there been any pre-release versions installed on flame 1?

[ytf]

I think the last version certified to run on an imac pro was the 2021 series. Anything newer than that might give you troubles.

[MagicMtn]

@ytf

It helps to have a version number with questions like these.

Flame version 2023.3 on mac os 12.7.6
its worth noting flame 3 recently had 24.2.2 installed perhaps thats part of the issue?

[MagicMtn]

all of them are on flame 2023.3 mac os 12.7.6

flame 3 recently had 2024.2.2 installed on it.

[MagicMtn]

funny enough the imac pro is not the system giving us problems but it is the system flame 1 thinks the database is locked to i guess.

[cristhiancordoba]

Pretty basic pretty obvious but, is your sw partition writable or read-only?

[MagicMtn]

@philm

- I don’t have an answer but I’m curious if your setup is Linux or macOS?

Mac OS

[MagicMtn]

yes

[cristhiancordoba]

Have you tried by sw_restart? Also check this in System Preferences on Mac and Confidentiality / Full Access to disk.
You have to allow : Flame / sw_dbd / sw_serverd / ifffsWiretapServer / Wiretapgateway.

[ytf]

Checking to see if Flame had Full Disk Access was my next guess as well

[MagicMtn]

@allklier

I assume rebooted as well?

That 15051 is most likely referencing a process id, or less likely a user id.

If you rebooted this may no longer apply. If you didn’t, I’d try

ps aux | fgrep 15051

and see if that exists and if so if you can kill it.

Thank you for your response i ran that command on both flame 1 and flame 3 with the following results:

not entirely sure what I am looking at or what command i would run next

kill -95587?
or
kill -72285?

[MagicMtn]

I should have included that but we checked this as well.

[MagicMtn]

@cristhiancordoba

Have you tried by sw_restart? Also check this in System Preferences on Mac and Confidentiality / Full Access to disk.
You have to allow : Flame / sw_dbd / sw_serverd / ifffsWiretapServer / Wiretapgateway.

What do you mean.

I have checked to make sure I am allowing all those things, and I am…is swrestart a command I can run to reinitiate that process?

[MagicMtn]

@allklier

I assume rebooted as well?

That 15051 is most likely referencing a process id, or less likely a user id.

If you rebooted this may no longer apply. If you didn’t, I’d try

ps aux | fgrep 15051

and see if that exists and if so if you can kill it.

we have rebooted mutiple times on both machines

[allklier]

@MagicMtn

…Thank you for your response i ran that command on both flame 1 and flame 3 with the following results:not entirely sure what I am looking at or what command i would run nextkill -95587?orkill -72285?

That command also finds itself. So there was no process running with that pid.

No solution there.

[MagicMtn]

@cristhiancordoba

Have you tried by sw_restart? Also check this in System Preferences on Mac and Confidentiality / Full Access to disk.
You have to allow : Flame / sw_dbd / sw_serverd / ifffsWiretapServer / Wiretapgateway.

we have restarted stone+wire from the service monitor mutiple times as well… is this the same thing as running the sw_restart command?