Correct, obviously not related to Virtual Box.
Will be investigated.
I am a superstar subscriber that sometimes uses mConnect when doing Qobuz and the interface is not working well. Some times you get an error message and sometimes it plays but only one song.
Please excuse my ignorance, but how would I submit a log per the instructions that would allow you to diagnose the error. Or is this out of scope?
Thanks
3 Likes
As a Superstar subscriber you are entitled to official dedicated support contact techsupport at volumio dot org 
Would you share some system logs please?
Preferable from a fresh reboot, with minimal steps to reproduce the problem
1 Like
3.129 Hangs at start up if you disable wireless.
Device: RPI4 2GB
Version: 2021-10-29-pi-volumiobuster-3.129
Debug log link:http://logs.volumio.org/volumiobuster/ZeQ6otF.html
I posted further up that 3.129 would not play for ~2mins ( cant link to a single post???)
But after further investigation its due to disabling wifi in the options.
easy to reproduce.
Connected by ethernet.
fresh install or factory reset of 3.129.
go through initial setup
find a web radio station that plays ok.
reboot, as soon as the UI reappears click play and it will play… like it should.
now disable wireless, and reboot
try and play your web radio station, it doesent . It will hang for approx 120 seconds. before pressing play works.
NAS drives will not show either during this time.
re enabling wireless does not sort this out, only way to fix is a factory reset. This wasnt an issue in 3.114.
1 Like
Same Here. Disabling WIFI creates problems.
Volume 3,129
Thank you Volumio people!
Is it possible that the sound is much better than version 2.x?
I enjoy the great sound, it’s fantastic!
The system works much more reliably, even after many days of operation.
I mainly use Qobuz and internet radio. But sometimes my FLACs too.
RPI 2/3, Allo BOSS DAC, Allo Nirvana
Thanks very much!
Device: Raspberry Pi A+
Version: 3.129 (2021-10-29-pi-volumiobuster-3.129)
Issue: Unable to connect using wifi hotspot.
Debug log link:
Bit of a challenge for me to get the logs. I’m attempting to run on a Pi A+ (2014 - https://www.raspberrypi.com/products/raspberry-pi-1-model-a-plus/) using a Wifi dongle. This is currently also broken in Volumio 2, which used to work before. Was hoping Volumio 3 would’ve corrected the issue. Tried with a couple different dongles.
v3.129 on RPi4 is generally working well for me (USB hard disk library and radio sources). Only issue I have encountered is with Shairport. Either it refuses to connect in the Mac’s Sound preferences panel or it connects but there is no sound (MacOS 12.0.1)
Another quirk is that my album count has gone up by around 300 albums since upgrading from 2.x
system: Raspberry Pi 3B+
dac: IQaudio
software: volumio 3.129
In response to your earlier question, I played a few DSD songs yesterday without issue.
Just now, after running for over two days, I played a flac 44.1/16 song and then switched over to Web Radio. /usr/bin/node processing usage started to increase to where it was staying above 100%. The web interface kept getting increasingly slower. /usr/bin/node memory consumption is at 54% and climbing. I will let the Web Radio run overnight and then stage the mpd.log and a journalctl dump for you.
Would comparing timelines between the two files help? Would any other files help?
1 Like
Please send log as soon as it happens, using either the /dev page or the method described here:
Thanks Rost! This makes us really happy!
Re the sound: many things has changed (new kernel, updated drivers, new mpd, new alsa pipeline) so its hard to say if this might have contributed to a better sound…
Crash when browsing genres happened to me again with version 3.129. This time I managed to capture the fatal error (ReferenceError: albumartist is not defined) :
Nov 06 10:10:04 music volumio[536]: info: CorePlayQueue::getTrack 6
Nov 06 10:10:04 music volumio[536]: verbose: STATE SERVICE {"status":"play","position":0,"seek":0,"duration":404,"samplerate":"44.1 kHz","bitdepth":"16 bit",
Nov 06 10:10:04 music volumio[536]: verbose: CURRENT POSITION 6
Nov 06 10:10:04 music volumio[536]: info: CoreStateMachine::syncState stateService play
Nov 06 10:10:04 music volumio[536]: info: CoreStateMachine::syncState currentStatus play
Nov 06 10:10:04 music volumio[536]: info: Received an update from plugin. extracting info from payload
Nov 06 10:10:04 music volumio[536]: info: CoreStateMachine::pushState
Nov 06 10:10:04 music volumio[536]: info: CoreCommandRouter::volumioPushState
Nov 06 10:10:04 music volumio[536]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Nov 06 10:10:04 music volumio[536]: info: CoreStateMachine::pushState
Nov 06 10:10:04 music volumio[536]: info: CoreCommandRouter::volumioPushState
Nov 06 10:10:04 music volumio[536]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Nov 06 10:10:04 music volumio[536]: info: ------------------------------ 4191ms
Nov 06 10:10:04 music volumio[536]: info: ------------------------------ 4194ms
Nov 06 10:10:08 music volumio[536]: Upnp client error: Error: This socket has been ended by the other party
Nov 06 10:10:08 music volumio[536]: Upnp client error: Error: This socket has been ended by the other party
Nov 06 10:10:22 music volumio[536]: info: CoreCommandRouter::executeOnPlugin: mpd , handleBrowseUri
Nov 06 10:10:22 music volumio[536]: info: CURURI: genres://
Nov 06 10:10:23 music volumio[536]: An internal error occurred while serving an albumart. Details: Error: ENOENT: no such file or directory, stat '/volumio/app/plugins/misce
Nov 06 10:10:26 music volumio[536]: info: CoreCommandRouter::executeOnPlugin: mpd , handleBrowseUri
Nov 06 10:10:26 music volumio[536]: info: CURURI: genres://Alt.%20Rock
Nov 06 10:10:26 music volumio[536]: |||||||||||||||||||||||| WARNING: FATAL ERROR |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Nov 06 10:10:26 music volumio[536]: ReferenceError: albumartist is not defined
Nov 06 10:10:26 music volumio[536]: at /volumio/app/plugins/music_service/mpd/index.js:3618:31
Nov 06 10:10:26 music volumio[536]: at MpdClient.handleMessage (/volumio/app/plugins/music_service/mpd/lib/mpd.js:77:3)
Nov 06 10:10:26 music volumio[536]: at MpdClient.receive (/volumio/app/plugins/music_service/mpd/lib/mpd.js:68:12)
Nov 06 10:10:26 music volumio[536]: at Socket.<anonymous> (/volumio/app/plugins/music_service/mpd/lib/mpd.js:43:12)
Nov 06 10:10:26 music volumio[536]: at Socket.emit (events.js:315:20)
Nov 06 10:10:26 music volumio[536]: at addChunk (internal/streams/readable.js:309:12)
Nov 06 10:10:26 music volumio[536]: at readableAddChunk (internal/streams/readable.js:280:11)
Nov 06 10:10:26 music volumio[536]: at Socket.Readable.push (internal/streams/readable.js:223:10)
Nov 06 10:10:26 music volumio[536]: at Pipe.onStreamRead (internal/stream_base_commons.js:188:23)
Nov 06 10:10:26 music volumio[536]: |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Nov 06 10:10:26 music sudo[26839]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl --since=2021-11-06 10:09
Nov 06 10:10:26 music sudo[26839]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 06 10:10:26 music sudo[26839]: pam_unix(sudo:session): session closed for user root
Nov 06 10:10:33 music volumio-remote-updater[408]: [2021-11-06 10:10:33] [error] handle_read_frame error: websocketpp.transport:7 (End of File)
Nov 06 10:10:33 music volumio-remote-updater[408]: [2021-11-06 10:10:33] [disconnect] Disconnect close local:[1006,End of File] remote:[1006]
Nov 06 10:10:33 music systemd[1]: volumio.service: Main process exited, code=exited, status=1/FAILURE
Nov 06 10:10:33 music systemd[1]: media-Shared.mount: Succeeded.
Nov 06 10:10:38 music volumio-remote-updater[408]: [2021-11-06 10:10:38] [info] asio async_connect error: system:111 (Connection refused)
Nov 06 10:10:38 music volumio-remote-updater[408]: [2021-11-06 10:10:38] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected)
Nov 06 10:10:38 music volumio-remote-updater[408]: [2021-11-06 10:10:38] [error] handle_connect error: Underlying Transport Error
Nov 06 10:10:39 music systemd[1]: volumio.service: Failed with result 'exit-code'.
Hifiberry Digi Pro+
Any idea when the support for this car might be fixed ?
Thanks !
Hi,
Volumio 3.129 running from an external USB drive on a x86 PC. The internal HDD labelled ihdd is not mounted. I spotted this in the log:
Nov 06 15:45:41 volumiopc volumio[770]: info: Mounting Device ihdd
Nov 06 15:45:41 volumiopc sudo[1027]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/mount /dev/sda1 /mnt/INTERNAL/ -o noatime
Nov 06 15:45:41 volumiopc sudo[1027]: pam_unix(sudo:session): session opened for user root by (uid=0)
Nov 06 15:45:41 volumiopc kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Nov 06 15:45:41 volumiopc sudo[1027]: pam_unix(sudo:session): session closed for user root
Nov 06 15:45:41 volumiopc volumio[770]: error: Failed to mount ihdd: ReferenceError: checkLabelForInternalDiskToBeMounted is not defined
Did I do anything wrong? Shall I configure the HDD differently?
Here follows the log:
http://logs.volumio.org/volumiobuster/R7MBn4I.html
Cheers 
The web interface is firmly hung this morning after running 2 days and 16 hours. “/usr/bin/node /volumnio/index.js” is using 58.1% memory and 100.00% cpu capacity. Your log-submit script ran successfully.
volumio@stereo:~$ node /volumio/logsubmit.js
{“status”:“OK”,“link”:“http://logs.volumio.org/volumiobuster/m0kWY4U.html”}
No, sorry. It’s a bug on our side. Thanks for reporting!
Thanks! Super useful!
I see that you are using pandora plugin.
Do you mind uninstalling it and report back if the situation improves? If you still have crashes after 2 days?
I am also experiencing the same sluggishness/hang after many hours of use (or following day), with the “node” process taking 100% CPU, and I am not using pandora plugin. Mostly Tidal playing.
Also fighting with USB DAC reconnect after a power cycle of the DAC (had the same issue with volumio 2, btw). It “re-discovers” the DAC only after I unplug and replug it, and only after a couple of minutes. Otherwise, USB audio doesn’t even show up in the output devices list.
On the good side, the sound quality is excellent!
Had a quick look at the logs, and also at the code for volumiodiscovery…
There might be some issues with multiple socket instances being created.
Also there is a sequence of pushState → saveDeviceInfo that keeps repeating, even without track changes.
Other than that, saveDeviceInfo could be an expensive function to call as often as the logs show…
Take for example here:
In fact there are many places that do the same getPlugin call for system_controller just to get the uuid config value. Isn’t this overkill, especially when there is a separate API exposed to get a plugins’s config value.
My Js knowledge is just enough to make me dangerous, so if someone more knowledgeable in the Js object model confirm is passing around Object instances can trip up the garbage collector?
I can’t get this HAT to work either, is there a known issue? Thanks
1 Like