"Server boot error"
circuit-lab opened this issue · comments
Received this error on a fresh install of Sonic Pi on xUbuntu (still getting the same error after system reboot and continued attempts to start Sonic Pi):
Sonic Pi Boot Error Report
System Information
- Sonic Pi version: 3.2.2
- OS: Ubuntu 22.04.3 LTS
GUI Log
/home/circuit/.sonic-pi/log/gui.log
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -
[GUI] - {ad3bf7ee-155b-47d6-811e-8a5cbbb906af}
[GUI] - Discovering port numbers...
[GUI] - Port entry server-listen-to-gui : 51235 : 51235
[GUI] - Port entry gui-send-to-server : 51235 : 51235
[GUI] - Port entry gui-listen-to-server : 51236 : 51236
[GUI] - Port entry server-send-to-gui : 51236 : 51236
[GUI] - Port entry scsynth : 51237 : 51237
[GUI] - Port entry scsynth-send : 51237 : 51237
[GUI] - Port entry osc-midi-out : 51239 : 51239
[GUI] - Port entry osc-midi-in : 51240 : 51240
[GUI] - Port entry server-osc-cues : 4560 : 4560
[GUI] - Port entry erlang-router : 51241 : 51241
[GUI] - Port entry websocket : 51242 : 51242
[GUI] - Detecting port numbers...
[GUI] - GUI listen to server port 51236
[GUI] - port: 51236 [OK]
[GUI] - Server listen to gui port 51235
[GUI] - port: 51235 [OK]
[GUI] - Server incoming OSC cues port 4560
[GUI] - port: 4560 [OK]
[GUI] - Scsynth port 51237
[GUI] - port: 51237 [OK]
[GUI] - Server send to GUI port 51236
[GUI] - port: 51236 [OK]
[GUI] - GUI send to server port 51235
[GUI] - port: 51235 [OK]
[GUI] - Scsynth send port 51237
[GUI] - port: 51237 [OK]
[GUI] - Erlang router port 51241
[GUI] - port: 51241 [OK]
[GUI] - OSC MIDI out port 51239
[GUI] - port: 51239 [OK]
[GUI] - OSC MIDI in port 51240
[GUI] - port: 51240 [OK]
[GUI] - Websocket port 51242
[GUI] - port: 51242 [OK]
[GUI] - All ports OK
[GUI] - launching Sonic Pi Runtime Server:
[GUI] - Ruby server pid registered: 1328
[GUI] - hiding main window
[GUI] - initialising toolbar icons
[GUI] - setting up window structure
[GUI] - restoring scope states
[GUI] - creating status bar
[GUI] - creating info panel
[GUI] - creating shortcuts
[GUI] - creating tool bar
[GUI] - initialising documentation window
[GUI] - starting UDP OSC Server on port 51236...
[GUI] - UDP OSC Server ready and listening
[GUI] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
............................................................
[GUI] - Critical error! Could not boot Sonic Pi Server.
[GUI] - stopping UDP OSC Server...
[GUI] - Critical Error. Unable to connect to server..
[GUI] - UDP OSC Server no longer listening
Server Errors
/home/circuit/.sonic-pi/log/server-errors.log
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
JackTemporaryException : now quits...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
Cannot create RT messagebuffer thread: Operation not permitted (1)
Retrying messagebuffer thread without RT scheduling
Messagebuffer not realtime; consider enabling RT scheduling for user
no message buffer overruns
ALSA: Cannot open PCM device alsa_pcm for playback. Falling back to capture-only mode
JackTemporaryException : now quits...
Cannot initialize driver
JackServer::Open failed with -1
Failed to open server
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
Cannot connect to server socket err = No such file or directory
Cannot connect to server request channel
jack server is not running or cannot be started
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
JackShmReadWritePtr::~JackShmReadWritePtr - Init not done for -1, skipping unlock
terminate called without an active exception
Server Output
/home/circuit/.sonic-pi/log/server-output.log
Sonic Pi server booting...
This is version 3.2.0 running on Ruby 3.0.2.
The time is 2023-12-22 17:46:04 -0500
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
- OK
Scsynth port: 51237
- OK
Scsynth send port: 51237
- OK
OSC cues port: 4560
- OK
Erlang port: 51241
- OK
OSC MIDI out port: 51239
- OK
OSC MIDI in port: 51240
- OK
Websocket port: 51242
- OK
Opening UDP Server to listen to GUI on port: 51235
Starting Server Runtime
Booting server...
Booting Sonic Pi
----------------
Booting on Linux
Jackd not running on system. Starting...
jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|2048|3|44100|0|0|nomon|swmeter|-|32bit
Released audio card Audio0
audio_reservation_finish
Started [1343] [-] jackd [-] /tmp/sonic-pi-pids/1343
Boot - Starting the SuperCollider server...
Boot - scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1
Started [1353] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/1353
Scsynth Output
/home/circuit/.sonic-pi/log/scsynth.log
# Starting SuperCollider 2023-12-22 17:46:05
Found 0 LADSPA plugins
jackdmp 1.9.20
Copyright 2001-2005 Paul Davis and others.
Copyright 2004-2016 Grame.
Copyright 2016-2021 Filipe Coelho.
jackdmp comes with ABSOLUTELY NO WARRANTY
This is free software, and you are welcome to redistribute it
under certain conditions; see the file COPYING for details
JACK server starting in realtime mode with priority 10
self-connect-mode is "Don't restrict self connect requests"
audio_reservation_init
Acquire audio card Audio0
creating alsa driver ... hw:0|hw:0|1024|2|48000|0|0|nomon|swmeter|-|32bit
Released audio card Audio0
audio_reservation_finish
could not initialize audio.
Process Log
/home/circuit/.sonic-pi/log/processes.log
No pids store found here: /tmp/sonic-pi-pids
Exiting
Creating pids store: /tmp/sonic-pi-pids
Started [1328] [-] /usr/bin/ruby -E utf-8 /usr/lib/sonic-pi/app/server/ruby/bin/sonic-pi-server.rb -u 51235 51236 51237 51237 4560 51241 51239 51240 51242 [-] /tmp/sonic-pi-pids/1328
Started [1343] [-] jackd [-] /tmp/sonic-pi-pids/1343
Started [1353] [-] scsynth -u 51237 -m 131072 -a 1024 -D 0 -R 0 -l 1 -i 16 -o 16 -b 4096 -B 127.0.0.1 [-] /tmp/sonic-pi-pids/1353
see my comment here