Closed heiderich closed 6 years ago
Looks like a problem parsing the JSON response from the snapserver, have seen this before, just not when opening the config.
Updating to build 377 now and will test afterwards
Just updated and installed plugin, I'm getting all kinds of errors (expected ones, since my config is not okay), but no reboot:
Mar 13 20:12:44 volumioboss volumio[812]: info: ## populating UI...
Mar 13 20:12:44 volumioboss volumio[812]: info: 1/7 server settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 2/7 client settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 3/7 MPD settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 4/7 asound settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 5/7 spotify settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 6/7 template settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: 7/7 environment settings loaded
Mar 13 20:12:44 volumioboss volumio[812]: info: Populated config screen.
Mar 13 20:12:45 volumioboss snapclient[3050]: Exception in Controller::worker(): connect: Connection refused
Mar 13 20:12:45 volumioboss snapclient[3050]: Error in socket shutdown: Transport endpoint is not connected
Mar 13 20:12:46 volumioboss snapclient[3050]: Exception in Controller::worker(): connect: Connection refused
Mar 13 20:12:46 volumioboss snapclient[3050]: Error in socket shutdown: Transport endpoint is not connected
Update, when configured correctly I'm getting the following (EOF error is because there has been no playback yet):
Mar 13 20:14:26 volumioboss volumio[812]: info: [{"prettyName":"Kodi Krypton","name":"kodi","category":"miscellanea","version":"2.2.11","icon":"fa fa-tv","enabled":false,"active":false},{"prettyName":"SnapCast","name":"snapcast","category":"miscellanea","version":"2.2.2","icon":"fa fa-podcast","enabled":true,"active":true}]
Mar 13 20:14:30 volumioboss volumio[812]: info: CoreCommandRouter::getUIConfigOnPlugin
Mar 13 20:14:30 volumioboss volumio[812]: info: Loaded the previous config.
Mar 13 20:14:30 volumioboss volumio[812]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , getDevices
Mar 13 20:14:30 volumioboss snapserver[4113]: ControlServer::NewConnection: ::ffff:127.0.0.1
Mar 13 20:14:30 volumioboss volumio[812]: info: ## populating UI...
Mar 13 20:14:30 volumioboss volumio[812]: info: 1/7 server settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 2/7 client settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 3/7 MPD settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 4/7 asound settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 5/7 spotify settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 6/7 template settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: 7/7 environment settings loaded
Mar 13 20:14:30 volumioboss volumio[812]: info: Populated config screen.
Mar 13 20:14:30 volumioboss snapserver[4113]: Exception in ControlSession::reader(): read_until: End of file
Mar 13 20:14:39 volumioboss volumio[812]: info: CALLMETHOD: miscellanea snapcast updateSnapServer [object Object]
Mar 13 20:14:39 volumioboss volumio[812]: info: CoreCommandRouter::executeOnPlugin: snapcast , updateSnapServer
Mar 13 20:14:39 volumioboss volumio[812]: info: Successfully updated snapserver configuration
Running on "System version: 2.377 Release: Tue Mar 13 17:56:48 CET 2018"
I was mistaken. The box does not reboot, but the volumio service restarts.
Could you help to debug this?
I can't reproduce... can you update to 377 please?
Correction: 378 has been released.
With version 2.378 this problems does not occur anymore.
Awesome! :)
I think Volumio solved it by using the crash reports.
I installed this plugin on volumio 2.376. When entering the settings page of the snapcast plugin, volumio seems to initiate a reboot and I cannot change anything anymore. Is this a known problem?
The output of
sudo journalctl -f
is: