I keep getting configuration updates

Help and Support
1

I am running the autostart plugin. Every time volumio boots up. It plays just as it should then 30 seconds later it quits playing and says configuration updated, system restarted.
Why??? So f#$%king frustrating.
This happens on more than one device as i have 4 of them

2

I guess autostart plugin starts too early, before the boot process end…

3

Hi @jocoman ,

Please experience with the time setting in de settings. I have mine set to 60000.

1 Like
4

ok, that worked , thanks

5

I’m still getting this constantly. I’ve reformatted and reinstalled multiple times. How do I change this setting to see if that will resolve my issue? Thanks in advance.

6

it’s just a setting in the auto-start plugin

7

In addition to the continuous ‘Configuration Update’ loop, when I go to Plugins it tells me I have to be signed into My Volumio. I go to my account and it shows me signed in with Premium account and it shows MyVolumio activated on my device. This is happening on the latest version of Volumio on a Raspberry Pi 4 with HifiBerry DAC2 Pro connected via Ethernet cable. I just sent a log report, so hopefully you can tell me what I can do to get this running. This issue has been going on for a while. Thanks in advance.

8

Please paste the link to the log here, otherwise we have no clue which log is what.
Please got to myvolumio and delete your device and reboot.

9

Sorry about that. Here you go.

http://logs.volumio.org/volumio/FRKRwEf.html

1 Like
10

You have a network error, hence the continuous reboot.
Please try to boot with a cabled connection and check your DNS.
You can set the DNS in volumio.
use
8.8.8.8
8.8.4.4

image
image1156×356 48.2 KB 

Jan 23 04:38 : client: [0] opened from local
Jan 23 04:38 : exception: No such directory
Jan 23 04:38 : client: [1] opened from local
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : client: [0] opened from local
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : client: [0] opened from local
Jan 23 04:39 : exception: No such directory
Jan 23 04:39 : client: [1] opened from local
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : client: [0] opened from local
Jan 23 04:39 : exception: No such directory
Jan 23 04:39 : client: [1] opened from local
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : client: [0] opened from local
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf
Jan 23 04:39 : zeroconf: No global port, disabling zeroconf




Jan 23 21:23:13 volumio volumio[32351]: |||||||||||||||||||||||| WARNING: FATAL ERROR |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Jan 23 21:23:13 volumio volumio[32351]: Error: getaddrinfo -3007
Jan 23 21:23:13 volumio volumio[32351]:     at errnoException (/volumio/node_modules/mdns/lib/resolver_sequence_tasks.js:199:11)
Jan 23 21:23:13 volumio volumio[32351]:     at getaddrinfo_complete (/volumio/node_modules/mdns/lib/resolver_sequence_tasks.js:112:10)
Jan 23 21:23:13 volumio volumio[32351]:     at GetAddrInfoReqWrap.oncomplete (/volumio/node_modules/mdns/lib/resolver_sequence_tasks.js:120:9) {
Jan 23 21:23:13 volumio volumio[32351]:   code: -3007,
Jan 23 21:23:13 volumio volumio[32351]:   errno: -3007,
Jan 23 21:23:13 volumio volumio[32351]:   syscall: 'getaddrinfo'
Jan 23 21:23:13 volumio volumio[32351]: }
Jan 23 21:23:13 volumio volumio[32351]: |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
11

Enabling the Custom DNS server seems to have fixed the issue. I really appreciate your help.