Resolve Studio 19.1.3 hangs on startup from command line

When I try to start Resolve Studio (testing mostly on a Mac, but the same thing seems to be happening on Linux) from the command line, the splash screen hangs at the "Checking Licenses" step and eventually becomes unresponsive. The app starts fine via Spotlight/Applications, but I need to start via the command line because the goal is to run with -nogui for headless scripting purposes.

The final lines in the log file are

0x16dff7000 | Main | ERROR | 2025-02-04 16:53:39,438 | Unable to open listener socket for external communication
0x1f3540840 | UI.GLContext | INFO | 2025-02-04 16:53:39,442 | Creating shared OpenGL context for this thread (1 total).
0x1f3540840 | UI.GLContext | INFO | 2025-02-04 16:53:39,495 | Initialized OpenGL 2.1 (requested 2.0) on device 'Apple Apple M4 Max'
0x1f3540840 | Main | INFO | 2025-02-04 16:53:39,495 | Show splash screen message: Checking Licenses

so my guess was that it's trying to reach the license server differently when started via the command line, but I went back and looked again, and the "Unable to open listener socket" line is also present for a successful startup, so I'm out of ideas. I haven't been able to find any relevant forum posts so far; has anyone else run into this issue?

[Dwaine Maggart]

Having a full Resolve diagnostics log could be helpful. Launch normally and open a new project or load a project, just so you can access the Resolve Help menu and select "Create Diagnostics Log on Desktop" to generate the log file. Then put it on a file sharing site and provide a link to the file here. Or you can attach it if it's less than 1MB in size.

Thanks for the quick reply—I was going to post an update when this post got approved, but you beat me to it.

I actually managed to solve this myself not too long after I gave in and made a forum post. I use pyenv on both my systems for managing Python environments, and its Python shim was symlinked to /usr/local/bin/python3 on both systems. Launching via commandline was going through my user shell, Resolve was looking for Python in /usr/local/bin, and the shim was causing a hang somewhere. Launching via the OS was using the system Python in /Library/whatever. Once I removed the symlink, the commandline launch (headless or not) started working. I now have a different problem on Linux, but that's a separate topic; I might make a new post about that tomorrow if I can't figure it out.

Out of curiosity, would a system log from a normal startup have helped diagnose that? I only happened to catch it because I noticed a bunch of spare bash processes from the failed startups hanging around doing some kind of busy wait and found that they had the pyenv shim open.

[Dwaine Maggart]

Resolve keeps a rolling copy of the last 5 good logs and last 5 crash logs, in the LogArchive folder.

When you generate a Resolve diagnostics log, all those are included.

So it may have had a clue about the Python issue.