You have PM 
I have the same issue. Just after login with my premium Account it starts a loop updating the configuration in about every 15s.
“Configuration update
Player successfully restarted”
Update:
I turned off all Sources (UPNP Renderer, Shairport-Sync, DLNA Browser). Everything works fine, until i log in with my Premium Account. Just after that, the Looping begins. Tested on both Versions 3.179 and 3.165. As described in Volumio 3 issues: hints and solutions I went back to 3.165. Same Issue. The Log is from 3.165.
Link to the Logfile: http://logs.volumio.org/volumio/imqT6SI.html
Update 2:
tail -f /var/log/mpd.log show repeating:
Jan 13 22:15 : zeroconf: No global port, disabling zeroconf
Jan 13 22:15 : client: [0] opened from local
Jan 13 22:15 : exception: No such directory
Jan 13 22:15 : client: [1] opened from local
Jan 13 22:15 : zeroconf: No global port, disabling zeroconf
Jan 13 22:15 : client: [0] opened from local
Jan 13 22:15 : client: [1] opened from local
Jan 13 22:15 : client: [2] opened from local
Jan 13 22:15 : client: [3] opened from local
Jan 13 22:15 : client: [4] opened from local
Jan 13 22:15 : client: [5] opened from local
Jan 13 22:15 : client: [6] opened from local
Jan 13 22:15 : client: [7] opened from local
Jan 13 22:15 : client: [8] opened from local
Jan 13 22:15 : client: [9] opened from local
Jan 13 22:15 : client: [10] opened from local
Jan 13 22:15 : client: [11] opened from local
Jan 13 22:15 : client: [12] opened from local
Jan 13 22:15 : client: [13] opened from local
Jan 13 22:15 : client: [14] opened from local
Jan 13 22:15 : client: [15] opened from local
Jan 13 22:15 : client: [16] opened from local
Jan 13 22:15 : client: [11] closed
Jan 13 22:15 : client: [10] closed
Jan 13 22:15 : client: [16] closed
Jan 13 22:15 : client: [15] closed
Jan 13 22:15 : client: [14] closed
Jan 13 22:15 : client: [13] closed
Jan 13 22:15 : client: [12] closed
Jan 13 22:15 : client: [9] closed
Jan 13 22:15 : client: [8] closed
Jan 13 22:15 : client: [7] closed
Jan 13 22:15 : client: [6] closed
Jan 13 22:15 : client: [5] closed
Jan 13 22:15 : client: [4] closed
Jan 13 22:15 : client: [3] closed
Jan 13 22:15 : client: [2] closed
Jan 13 22:15 : client: [1] closed
Jan 13 22:15 : client: [0] closed
Jan 13 22:16 : zeroconf: No global port, disabling zeroconf
Jan 13 22:16 : client: [0] opened from local
Jan 13 22:16 : exception: No such directory
Jan 13 22:16 : client: [1] opened from local
Jan 13 22:16 : zeroconf: No global port, disabling zeroconf
Jan 13 22:16 : client: [0] opened from local
Jan 13 22:16 : client: [1] opened from local
Jan 13 22:16 : client: [2] opened from local
Jan 13 22:16 : client: [3] opened from local
Jan 13 22:16 : client: [4] opened from local
Jan 13 22:16 : client: [5] opened from local
Jan 13 22:16 : client: [6] opened from local
Jan 13 22:16 : client: [7] opened from local
Jan 13 22:16 : client: [8] opened from local
Jan 13 22:16 : client: [9] opened from local
Jan 13 22:16 : client: [10] opened from local
Jan 13 22:16 : client: [11] opened from local
Jan 13 22:16 : client: [12] opened from local
Jan 13 22:16 : client: [13] opened from local
Jan 13 22:16 : client: [14] opened from local
Jan 13 22:16 : client: [15] opened from local
Jan 13 22:16 : client: [16] opened from local
Jan 13 22:16 : client: [15] closed
Jan 13 22:16 : client: [14] closed
Jan 13 22:16 : client: [13] closed
Jan 13 22:16 : client: [12] closed
Jan 13 22:16 : client: [11] closed
Jan 13 22:16 : client: [10] closed
Jan 13 22:16 : client: [16] closed
Jan 13 22:16 : client: [9] closed
Jan 13 22:16 : client: [8] closed
Jan 13 22:16 : client: [7] closed
Jan 13 22:16 : client: [6] closed
Jan 13 22:16 : client: [5] closed
Jan 13 22:16 : client: [4] closed
Jan 13 22:16 : client: [3] closed
Jan 13 22:16 : client: [2] closed
Jan 13 22:16 : client: [1] closed
Jan 13 22:16 : client: [0] closed
Jan 13 22:16 : zeroconf: No global port, disabling zeroconf
Jan 13 22:16 : client: [0] opened from local
Jan 13 22:16 : exception: No such directory
Jan 13 22:16 : client: [1] opened from local
And the link to your system log file is …?
as soon as I set “Activate MyVolumio On Devices” enabled to “off”, the looping stops and Volumio works as expected. When I set to “on”, the looping starts again.
btw, there’s a topic with the same issue, better to merge and continue there.
Anyone got a fix for this?
@deadlyrick Looks like it was solved at the end of this discussion.
If you’re not happy trying the beta release, you can wait for the next stable update, which must be coming soon.
Hello, I installed version 3.378 few days ago and since then Volumio constantly restart.
I’ve already tried:
- reset to factory setting
- re- flush from scratch SD card
- disabled DNLA, UPNP etc…
All on Raspberry PI 4 model B 2GB
Many thanks for any suggestion?
Did you flash with Balena? if so take a fresh card and flash with win32diskimager or raspberry pi imager
Yes, I used Balena.
I’ll give a try to win32diskimager or raspberry pi imager and let you know…
Will prob. solve the issue. Multiple reports have been filed with Balena.
Today I flashed with win32diskimager but I have the same issue. Volumio starts every few minuts…
try to connect the rPi to a screen and see if you get errors during boot.
Is this a brand new rPi or an older one?
So still no fix for this? My player is currently bricked by this loop. The original system was flashed over a year ago and then updated ota since then.
I’m using a Rpi3 with an Allo boss dac. Should I try a new SD card and do a fresh install? My configuration is pretty basic without much customization so it wouldn’t be too bad. I would be flashing from MacOS, so any particular writer to use to minimize problems?
Please flash V3.396. That should have solved this issue,
https://updates.volumio.org/pi/volumio/3.396/Volumio-3.396-2022-12-04-pi.zip
1 Like
I am experiencing this problem(1/13/2023). Pi4, latest version of volumio. I have tried every recommendation on this thread. Has this been solved somewhere? If I let Volumio run long enough it eventual seems to solve itself but the constant resets interferes with the configuration sequence of the touch screen.
Experiencing this same issue on my Raspberry Pi 3. The Device goes into a continuous loop every 12 seconds or so, reloading services / configuration the second I sign into myVolumio & enable the device. This is happening with V3.396. This configuration has worked greatly for the past 5+ months without an issue until now
Please don’t adding the same comment to different topics.
Please add a custom DNS within Volumio.
Use:
8.8.8.8
8.8.4.4
Unfortunately that didn’t do it. What’s happening is the Volumio services keep restarting randomly on their own and the device drops a ton of packets at random when it happens.
Here’s the log: http://logs.volumio.org/volumio/z6htIzN.html
The second I sign into Tidal Premium, the network randomly drops on the Pi resulting in streaming to be unplayable and the UI is unusable as well. This is on a Raspberry Pi 3. I do not get packet loss when I flash Raspbian & install a Spotify streamer.
Update @Wheaten
Like I said, the network drops when the UI completely goes out.
This starts the second I sign into my Volumio subscription.
The second I flash Volumio, connect to it’s WiFi, then connect it to my WiFi, the network packets are rock solid stable until I sign into my Volumio subscription.
I have a constant ping of ping 192.168.1.6 -t going. That log was captured while the issue was actively happening, which is why those network drops are there.
Per here: Wifi connection unstable - Page 3 - Raspberry Pi Forums I’m going to disable the WiFi Power Saver and see if that helps.