Ray-daemon not starting automatically

[4oo4]

I'm on Debian Trixie, I tried both the distro packaged version of raysession (0.14.4-3) as well as the latest 0.17.1 and following the manual, I can get raysession to open, and create a new JACK configuration memory session, but then from that point I'm not able to add any applications or executable. I verified that I have all the runtime dependencies, and had JACK running via qjackctl prior to starting raysession.

When I run it with --dbg all, it tells me Impossible to connect to JACK dbus and Sandbox: CanCreateUserNamespace() clone() failure: EPERM

raysession --dbg all

[ray-daemon]
URL : osc.udp://192.168.101.192:16187/
      osc.udp://oplx:16187/
ROOT: /home/user/Ray Sessions
GUI connected at osc.udp://oplx:17503/
Unable to find theme 
WARNING:patchbay.patchcanvas.patchcanvas - theme '' has not been found,use 'Yellow Boards' instead.
Attempting to open /home/user/Ray Sessions/test

[ray-daemon load.sh script]
Impossible to connect to JACK dbus

[ray-daemon]
Done
[2] Sandbox: CanCreateUserNamespace() clone() failure: EPERM
Bye Bye...

[4oo4]

I think I found the issue, so because I'm using the Hydrogen appimage, I need this sysctl setting:

kernel.unprivileged_userns_clone=1

https://forums.kicksecure.com/t/unprivileged-user-namespaces-kernel-unprivileged-userns-clone-can-not-run-flatpak-apps-appimages-after-kicksecure-update/592/7

That resolves that error message, however now I encounter another issue where it appears that ray-daemon isn't starting automatically.

raysession --dbg all

[ray-daemon]
URL : osc.udp://192.168.101.192:16187/
      osc.udp://oplx:16187/
ROOT: /home/user/Ray Sessions
GUI connected at osc.udp://oplx:19612/
Unable to find theme 
WARNING:patchbay.patchcanvas.patchcanvas - theme '' has not been found,use 'Yellow Boards' instead.
Attempting to open /home/user/Ray Sessions/test
Commanding smart clients to switch
Telling all clients that session is loaded...
Loaded
Done
ERROR:jackpatch.jack_engine_remote - Failed to get ports and connections from patchbay_daemon, will quit.

Per this, when I start ray-daemon separately and start raysession with --daemon-port, then it works as expected. What's the best way to make sure that ray-daemon starts automatically at the same time as raysession and passes the daemon port?

#264

[Houston4444]

Hi, so, the first bug seems to be resolved.

now I encounter another issue where it appears that ray-daemon isn't starting automatically.

with this log, I can say that ray-daemon is started automatically when raysession is launched, and still running at the end of prompt. The problem comes with ray-jackpatch (the client which saves and restore JACK connections).

when starting raysession, is the patchbay OK ? can you see all ports you can list with jack_lsp ?

You can try to edit the session file (when session is not open of course) and remove internal="true" in the jackpatch attributes. Then, open the session and see what happens, it could be different.

Note that raysession --dbg all will not print any particular information, "all" is not implemented. you could type raysession --dbg ray_daemon to have something more pertinent. You could not know that, it is not documented yet.