Open ethancrawford opened 6 days ago
Yes, at on my PC the same error ...
Sonic Pi version: 5.0.0 OS: Windows 10 Version 22H2 CPU: x86_64 spider.log Ignoring rugged-1.7.2 because its extensions are not built. Try: gem pristine rugged --version 1.7.2 Sonic Pi Spider Server booting... The time is 2024-10-22 21:32:49 +0200 Using primary protocol: udp Detecting port numbers... Opening UDP Server to listen to GUI Spider - Pulling in modules... Spider - Starting Runtime Server
Critical: UDP Server Tau Comms ack server for port ["AF_INET", 56749, "127.0.0.1", "127.0.0.1"] had issues receiving from socket Eine vorhandene Verbindung wurde vom Remotehost geschlossen. - recvfrom(2) ["C:/Program Files/Sonic Pi BETA/app/server/ruby/lib/sonicpi/osc/udp_server.rb:88:in
recvfrom'", "C:/Program Files/Sonic Pi BETA/app/server/ruby/lib/sonicpi/osc/udp_server.rb:88:in block in start_listener'", "<internal:kernel>:187:in
loop'", "C:/Program Files/Sonic Pi BETA/app/server/ruby/lib/sonicpi/osc/udp_server.rb:86:in start_listener'", "C:/Program Files/Sonic Pi BETA/app/server/ruby/lib/sonicpi/osc/udp_server.rb:41:in
block in initialize'"]
`
Hi @ethancrawford and @gsegit.
not sure what's going on here. Is there any chance you could clear your ~/.sonic-pi/log
folder out and then try and boot again. I'd really like to see the contents of tau.log
and if there is one: tau_stdouterr.log
. But it's important it's not one from an older boot from a version that worked.
Cleared the top level files from the log folder and tried again.
In case it's helpful at all, the tail end of daemon.log
looks slightly different this time, talking about trying to kill the Erlang process:
[2024-10-23 07:12:10] Process Booter - no need to kill C:\Program Files\Sonic Pi BETA\app\server\beam\tau\_build\prod\rel\tau\erts-15.1\bin\erl.exe with pid and args ["-config", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\sys", "-boot", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\start", "-boot_var", "RELEASE_LIB", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\lib", "-args_file", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\vm.args", "-noshell", "-s", "elixir", "start_cli", "-mode", "embedded", "-extra", "--no-halt"] - already terminated, wait_thr status: #<Process::Waiter:0x000001e81f52c098 dead>, false
[2024-10-23 07:12:10] Process Booter - Unfortunately we don't have a @pid for C:\Program Files\Sonic Pi BETA\app\server\beam\tau\_build\prod\rel\tau\erts-15.1\bin\erl.exe with args ["-config", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\sys", "-boot", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\start", "-boot_var", "RELEASE_LIB", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\lib", "-args_file", "C:\\Program Files\\Sonic Pi BETA\\app\\server\\beam\\tau\\_build\\prod\\rel\\tau\\releases\\0.1.0\\vm.args", "-noshell", "-s", "elixir", "start_cli", "-mode", "embedded", "-extra", "--no-halt"]. wait_thr: #<Process::Waiter:0x000001e81f52c098 dead>
[2024-10-23 07:12:10] Daemon Booter - Over and Out.
Here is tau.log:
07:11:01.696 [info] All systems booting....
07:11:01.696 [info] Initialising MIDI native interface
07:11:01.698 [info] Initialising Link native interface
07:11:01.700 [info] Starting Phoenix server
07:11:01.700 [info] Starting with MIDI server enabled
07:11:01.700 [info] Starting with Link server enabled
Here is tau_stdouterr.log:
prod
One wonders, given the comments in daemon.log no need to kill [... tau ]... - already terminated,
and the fact that there are logs for both tau and tau_stdouterr, if tau is starting but then silently crashing for some reason? [Edit: yes, I can see erl.exe appearing and then then disappearing in Task Manager. Not sure that I'll be able to pin down exactly why it is crashing, but I'll do a bit of investigation and testing just in case. Will post again if I find anything that I think might be useful].
Logs below. This seems similar to the output described at https://github.com/sonic-pi-net/sonic-pi/issues/3207#issuecomment-1241802938 but for me:
tau.log
in the log folderSECRET_KEY_BASE
missing.spider.log
mentions rugged-1.7.2 being ignored.I have noticed that my dev build stopped working also after this with the same tau comms issue - and reverting it to a commit that I know worked the other day (4e6dc0fe0) does not help.
The most recent release version, 4.5.1, works fine.
System Information
spider.log
daemon.log
scsynth.log
gui.log