sonic-pi
sonic-pi copied to clipboard
sonic-pi-net
Critical Error! Could not boot Sonic Pi Server
On a school network, students (but not me with admin rights) are getting the following error. Was hoping to use Sonic Pi with 300 students...any ideas??
Sonic Pi Boot Error Report
System Information
- Sonic Pi version: 3.2.0
- OS: Windows 10 Version 1909
GUI Log
C:\Users\15ristirzakerl\.sonic-pi\log\gui.log
[GUI] - Welcome to the Sonic Pi GUI
[GUI] - ===========================
[GUI] -
[GUI] - {693e2da5-4de9-45ba-891a-b886eeb15241}
[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 : 51237 : 51237
[GUI] - Port entry server-send-to-gui : 51237 : 51237
[GUI] - Port entry scsynth : 51238 : 51238
[GUI] - Port entry scsynth-send : 51238 : 51238
[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 51237
[GUI] - port: 51237 [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 51238
[GUI] - port: 51238 [OK]
[GUI] - Server send to GUI port 51237
[GUI] - port: 51237 [OK]
[GUI] - GUI send to server port 51235
[GUI] - port: 51235 [OK]
[GUI] - Scsynth send port 51238
[GUI] - port: 51238 [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: 11276
[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] - wait for sync
[GUI] - waiting for Sonic Pi Server to boot...
[GUI] - starting UDP OSC Server on port 51237...
[GUI] - UDP OSC Server ready and listening.............................................................
[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
GUI] - Aborting. Sorry about this.
Server Errors
C:\Users\15ristirzakerl\.sonic-pi\log\server-errors.log
Failed to load the fast_osc c-extension, falling back to pure Ruby version
Overriding fast_osc c-extension FastOsc::decode_single_message, falling back to pure Ruby version
C:/Program Files/Sonic Pi/app/server/ruby/vendor/sys-proctable-1.1.3/lib/windows/sys/proctable.rb:97: warning: constant ::Fixnum is deprecated
Server Output
C:\Users\15ristirzakerl\.sonic-pi\log\server-output.log
Sonic Pi server booting...
This is version 3.2.0 running on Ruby 2.7.0.
The time is 2021-03-10 13:36:04 +0000
Using primary protocol: udp
Detecting port numbers...
Listen port: 51235
- OK
Scsynth port: 51238
- OK
Scsynth send port: 51238
- 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
Scsynth Output
C:\Users\15ristirzakerl\.sonic-pi\log\scsynth.log
Process Log
C:\Users\15ristirzakerl\.sonic-pi\log\processes.log
Hi @MrsHWilliams,
so sorry you're having issues. We'll do our best to get you up and running. One thing I can see is that you're using an outdated version of Sonic Pi. Would it be possible to upgrade to v3.3.1 and see if that improves matters for you?
We have completely overhauled the building and booting systems in the recently released v4 of Sonic Pi:
https://github.com/sonic-pi-net/sonic-pi/releases
Please give that a try and feel free to create a new issue if you're still having problems.
Great! First day of hols today but will install and test it in September. We did have to abandon using It in the end as we couldn’t get it working. 🤞🏻
Helen
Sent from my iPhone
On 20 Jul 2022, at 9:35 am, Sam Aaron @.***> wrote:
— Reply to this email directly, view it on GitHubhttps://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fsonic%2dpi%2dnet%2fsonic%2dpi%2fissues%2f2724%23event%2d7027185283&umid=320d2112-c9b9-4da8-801e-262e3ff89337&auth=6e25a8fdf2f22007a2f31f290f8246de01927921-461cc5aacd44c7a4fa8defcd979ebf6ea61213e1, or unsubscribehttps://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fARGPMCQ7MAXMB7XYWNCAXQTVU624BANCNFSM4Y6DOGCQ&umid=320d2112-c9b9-4da8-801e-262e3ff89337&auth=6e25a8fdf2f22007a2f31f290f8246de01927921-f7aa29864f04221c3283534de44fd04b6e2cf9ae. You are receiving this because you were mentioned.Message ID: @.***>
Hi Sam
They have tried but currently it is still not opening for non admin users. I have copied Maxime in.
@.***
From: Sam Aaron @.> Sent: 20 July 2022 09:35 To: sonic-pi-net/sonic-pi @.> Cc: Mrs H Williams @.>; Mention @.> Subject: [External] Re: [sonic-pi-net/sonic-pi] Critical Error! Could not boot Sonic Pi Server (#2724)
We have completely overhauled the building and booting systems in the recently released v4 of Sonic Pi:
https://github.com/sonic-pi-net/sonic-pi/releaseshttps://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fsonic%2dpi%2dnet%2fsonic%2dpi%2freleases&umid=72b638e6-9e4d-4464-8997-34432494a7b4&auth=6e25a8fdf2f22007a2f31f290f8246de01927921-b25da850dbf5152f9bebc4587352f8c7d310b02e
Please give that a try and feel free to create a new issue if you're still having problems.
— Reply to this email directly, view it on GitHubhttps://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fsonic%2dpi%2dnet%2fsonic%2dpi%2fissues%2f2724%23issuecomment%2d1189989533&umid=72b638e6-9e4d-4464-8997-34432494a7b4&auth=6e25a8fdf2f22007a2f31f290f8246de01927921-c29c9e9a791fd679cf012dcf34510779eefdc76b, or unsubscribehttps://smex-ctp.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fARGPMCQ7MAXMB7XYWNCAXQTVU624BANCNFSM4Y6DOGCQ&umid=72b638e6-9e4d-4464-8997-34432494a7b4&auth=6e25a8fdf2f22007a2f31f290f8246de01927921-18097e57575e13e02020b2f1caacd348fc469c56. You are receiving this because you were mentioned.Message ID: @.@.>>
Oh that’s a real shame.
Would it be possible to share a copy of the logs in the .sonic-pi\log directory found in the users home directory?
Also, could you find out if either of the environment variables HOMEDRIVE or HOMEPATH are set and if so what their values are?
@MrsHWilliams - just to let you know that I just released v4.2 of Sonic Pi which contains fixes for a school that couldn't get Sonic Pi working for non-admin users. Their IT person was really helpful in figuring out the problem and testing a fix. I'm wondering/hoping that it was the same issue you faced and whether v4.2 will be a fix for you too:
https://github.com/sonic-pi-net/sonic-pi/releases/tag/v4.2.0