SQL. server not running

hi all - my flames did an auto update overnight! and since then the main machine wont come online. says PostgreSQL server unable to start./ all the others seem to be fine. im getting this….(im pretty sure I didnt have a partition called 2025!) any ideas. how to fix

## Errors/Warnings in application log

[warn] 4108902592 swdb.C:427 08/21/25:11:34:57.920 Mount point for partition 0 (/Volumes/Thunder1/Thunder1-Cache/2025) not found.

[warn] 4108902592 swxSWDBFSAdapter.C:427 08/21/25:11:34:57.922 S+W Database server older than API (2025.2.3 [248]). Some functionalities might be disabled.

[warn] 4108902592 pythonHook.C:152 08/21/25:11:34:59.356 [PYTHON HOOK] ‘customUIAction’ hook have been deprecated. Support for it is not guaranteed in the future. Current used in ‘/opt/Autodesk/presets/2026.1/shotgun/flame_hooks/sg_initialize.py’.

[warn] 4108902592 pythonHook.C:152 08/21/25:11:34:59.357 [PYTHON HOOK] ‘customUIAction’ hook have been deprecated. Support for it is not guaranteed in the future. Current used in ‘/opt/Autodesk/presets/2026.1/shotgun/flame_hooks/python_console.py’.

[warn] 4108902592 backburnerPrefs.C:1193 08/21/25:11:34:59.820 … Fetched storage ID ‘4F6F889E-363C-4F1C-AC54-F4EFD9491A2E-Backburner’ for ‘localhost:0’

[error] 4108902592 swDatabase.cpp:394 08/21/25:11:35:00.191 Thread 0x1f4e8e0c0 failed opening a DBMS connection

[error] 4108902592 swDatabase.cpp:394 08/21/25:11:35:00.191 Thread 0x1f4e8e0c0 failed opening a DBMS connection

[error] 4108902592 swProjectServer.cpp:226 08/21/25:11:35:00.191 Could not connect to DBMS: Couldn’t connect to the database server; make sure it is running

[error] 4108902592 swDatabase.cpp:394 08/21/25:11:35:00.194 Thread 0x1f4e8e0c0 failed opening a DBMS connection

[error] 4108902592 swDatabase.cpp:394 08/21/25:11:35:00.194 Thread 0x1f4e8e0c0 failed opening a DBMS connection

[error] 4108902592 swProjectServer.cpp:226 08/21/25:11:35:00.194 Could not connect to DBMS: Couldn’t connect to the database server; make sure it is running

[warn] 4108902592 colourMgtPolicyOCIO.C:144 08/21/25:11:35:08.321 ColourMgtPolicyOCIO from default: /opt/Autodesk/colour_mgmt/configs/flame_configs/2026.0/aces2.0_config/config.ocio

Screenshot 2025-08-21 at 11.43.33

I noticed that the flame that isnt working doesnt have this user - which all the others do

Since all of your work is archived (assumption) just reinstall flame and create the db again.

Of course, this solution is fucking stupid if it wipes out work that wasn’t backed up (which obviously won’t be the case).

Openclip workflows can mostly survive this kind of system failure.

Some project server workflows might also be more carefully insulated against this kind of system failure, but they bring about their own administrative overhead.

Best course of action is to call support because this is a critical failure and should not happen, especially to your “main” flame.

There may be a reason why it happened and it could possibly have been avoided.

Post what they tell you.

I noticed something dumb from a macOS update recently, (twice actually) the system upgrade wiped out modifications to /etc/auto_master.

Hosts / servers, including storage all got indiscriminately kneecapped.

I’m sure there was a valid reason for helping Mac users avoid their own networks.

Perhaps it’s macOS 47.

Right now I cant even get hold of support. Managed to get past the auto bot to have someone tell me my license is not valid and what product are you enquiring about.

There must be a way to re hook it to the server. As you predicted yesterday’s wasn’t archived as yet!

Whats the trick to get to speak to support?
\

Things used to be different.

You taught me that 30 years ago.

It’s changed from a white glove service to something quite unremarkable.

Wish I could help but I’m on some dumb telephone in a hotel in a telecoms desert.

Someone will help you brother.

who?? where all the things to tweak in terms of what the flame is looking for and where its looking

I’ll be escaping the fiery wastelands of Hollywood this weekend.

Send me a ticket for Monday and I’ll come and help you.

1 Like

hah - might be quicker

1 Like

Might be better

1 Like

well - no luck whatsoever with the support thing. So called XTFX - and James sorted it out. Cheers James

1 Like

Good old James