Tue Aug 2 13:52:38 UTC 2022 Description="'Spotify OAuth Error'" # cat /proc/version --------------- Linux version 5.10.92-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1514 SMP Mon Jan 17 17:36:39 GMT 2022 # cat /etc/os-release --------------- PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" VOLUMIO_BUILD_VERSION="1f061e035f7cb2799b32d3520aa8e55cd07df6f9" VOLUMIO_FE_VERSION="9971a09df9c3edfdedf2ecf438999be8aba9db68" VOLUMIO_FE3_VERSION="3974def988c7b2392ddc85f9b8cb4692d5e8fda9" VOLUMIO_BE_VERSION="b3c53a818b9b3d0e5c13c9d346c4d613c4ca426f" VOLUMIO_ARCH="arm" VOLUMIO_VARIANT="volumio" VOLUMIO_TEST="FALSE" VOLUMIO_BUILD_DATE="Mon 11 Jul 2022 04:03:33 PM CEST" VOLUMIO_VERSION="3.324" VOLUMIO_HARDWARE="pi" VOLUMIO_DEVICENAME="Raspberry Pi" VOLUMIO_HASH="5b2f59e6e90e57f326ca25c7ca839d52" # ifconfig --------------- eth0: flags=4163 mtu 1500 inet 192.168.1.242 netmask 255.255.255.0 broadcast 192.168.1.255 ether b8:27:eb:07:d9:c2 txqueuelen 1000 (Ethernet) RX packets 2399 bytes 683108 (667.0 KiB) RX errors 0 dropped 1 overruns 0 frame 0 TX packets 1775 bytes 250968 (245.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 1392 bytes 146132 (142.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1392 bytes 146132 (142.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163 mtu 1500 inet 192.168.211.1 netmask 255.255.255.0 broadcast 192.168.211.255 ether b8:27:eb:52:8c:97 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 70 bytes 14932 (14.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 # sudo iwconfig --------------- lo no wireless extensions. eth0 no wireless extensions. wlan0 IEEE 802.11 Mode:Master Tx-Power=31 dBm Retry short limit:7 RTS thr:off Fragment thr:off Power Management:off # aplay -l --------------- **** List of PLAYBACK Hardware Devices **** card 0: b1 [bcm2835 HDMI 1], device 0: bcm2835 HDMI 1 [bcm2835 HDMI 1] Subdevices: 4/4 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 card 1: Headphones [bcm2835 Headphones], device 0: bcm2835 Headphones [bcm2835 Headphones] Subdevices: 4/4 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 card 2: sndrpihifiberry [snd_rpi_hifiberry_dacplus], device 0: HiFiBerry DAC+ HiFi pcm512x-hifi-0 [HiFiBerry DAC+ HiFi pcm512x-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 # ps -ef --------------- UID PID PPID C STIME TTY TIME CMD root 1 0 1 13:43 ? 00:00:09 /sbin/init root 2 0 0 13:43 ? 00:00:00 [kthreadd] root 3 2 0 13:43 ? 00:00:00 [rcu_gp] root 4 2 0 13:43 ? 00:00:00 [rcu_par_gp] root 7 2 0 13:43 ? 00:00:00 [kworker/u8:0-brcmf_wq/mmc1:0001:1] root 8 2 0 13:43 ? 00:00:00 [mm_percpu_wq] root 9 2 0 13:43 ? 00:00:00 [rcu_tasks_rude_] root 10 2 0 13:43 ? 00:00:00 [rcu_tasks_trace] root 11 2 0 13:43 ? 00:00:00 [ksoftirqd/0] root 12 2 0 13:43 ? 00:00:00 [rcu_sched] root 13 2 0 13:43 ? 00:00:00 [migration/0] root 14 2 0 13:43 ? 00:00:00 [cpuhp/0] root 15 2 0 13:43 ? 00:00:00 [cpuhp/1] root 16 2 0 13:43 ? 00:00:00 [migration/1] root 17 2 0 13:43 ? 00:00:00 [ksoftirqd/1] root 19 2 0 13:43 ? 00:00:00 [kworker/1:0H-kblockd] root 20 2 0 13:43 ? 00:00:00 [cpuhp/2] root 21 2 0 13:43 ? 00:00:00 [migration/2] root 22 2 0 13:43 ? 00:00:00 [ksoftirqd/2] root 25 2 0 13:43 ? 00:00:00 [cpuhp/3] root 26 2 0 13:43 ? 00:00:00 [migration/3] root 27 2 0 13:43 ? 00:00:00 [ksoftirqd/3] root 30 2 0 13:43 ? 00:00:00 [kdevtmpfs] root 31 2 0 13:43 ? 00:00:00 [netns] root 32 2 0 13:43 ? 00:00:00 [kworker/0:1-events] root 33 2 0 13:43 ? 00:00:00 [kworker/1:1-events_power_efficient] root 34 2 0 13:43 ? 00:00:00 [kauditd] root 35 2 0 13:43 ? 00:00:00 [kworker/0:2-events] root 36 2 0 13:43 ? 00:00:00 [khungtaskd] root 37 2 0 13:43 ? 00:00:00 [oom_reaper] root 38 2 0 13:43 ? 00:00:00 [writeback] root 39 2 0 13:43 ? 00:00:00 [kcompactd0] root 57 2 0 13:43 ? 00:00:00 [kblockd] root 58 2 0 13:43 ? 00:00:00 [blkcg_punt_bio] root 59 2 0 13:43 ? 00:00:00 [watchdogd] root 60 2 0 13:43 ? 00:00:00 [kworker/2:1-mm_percpu_wq] root 62 2 0 13:43 ? 00:00:00 [rpciod] root 64 2 0 13:43 ? 00:00:00 [xprtiod] root 65 2 0 13:43 ? 00:00:00 [kswapd0] root 66 2 0 13:43 ? 00:00:00 [nfsiod] root 67 2 0 13:43 ? 00:00:00 [kworker/3:1-mm_percpu_wq] root 68 2 0 13:43 ? 00:00:00 [kworker/1:2-events_power_efficient] root 69 2 0 13:43 ? 00:00:00 [iscsi_eh] root 70 2 0 13:43 ? 00:00:00 [iscsi_destroy] root 71 2 0 13:43 ? 00:00:00 [dwc_otg] root 73 2 0 13:43 ? 00:00:00 [DWC Notificatio] root 74 2 0 13:43 ? 00:00:00 [kworker/3:3-mm_percpu_wq] root 75 2 0 13:43 ? 00:00:00 [vchiq-slot/0] root 76 2 0 13:43 ? 00:00:00 [vchiq-recy/0] root 77 2 0 13:43 ? 00:00:00 [vchiq-sync/0] root 78 2 0 13:43 ? 00:00:00 [zswap-shrink] root 90 2 0 13:43 ? 00:00:00 [mmc_complete] root 91 2 0 13:43 ? 00:00:00 [kworker/3:1H-kblockd] root 92 2 0 13:43 ? 00:00:00 [kworker/0:1H-kblockd] root 112 2 0 13:43 ? 00:00:00 [kworker/2:1H-kblockd] root 113 2 0 13:43 ? 00:00:00 [kworker/2:2H-kblockd] root 117 2 0 13:43 ? 00:00:00 [kworker/0:2H-kblockd] root 118 2 0 13:43 ? 00:00:00 [jbd2/mmcblk0p2-] root 119 2 0 13:43 ? 00:00:00 [ext4-rsv-conver] root 123 2 0 13:43 ? 00:00:00 [irq/199-usb-001] root 129 2 0 13:43 ? 00:00:01 [loop0] root 155 2 0 13:43 ? 00:00:00 [kworker/3:2H-kblockd] root 156 2 0 13:43 ? 00:00:00 [jbd2/mmcblk0p3-] root 157 2 0 13:43 ? 00:00:00 [ext4-rsv-conver] root 165 2 0 13:43 ? 00:00:00 [kworker/1:2H-kblockd] root 166 2 0 13:43 ? 00:00:00 [ipv6_addrconf] root 185 1 0 13:43 ? 00:00:01 /lib/systemd/systemd-journald root 213 1 0 13:43 ? 00:00:01 /lib/systemd/systemd-udevd root 239 2 0 13:43 ? 00:00:00 [vchiq-keep/0] root 241 2 0 13:43 ? 00:00:00 [SMIO] root 273 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 274 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 275 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 276 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 277 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 278 2 0 13:43 ? 00:00:00 [mmal-vchiq] root 300 2 0 13:43 ? 00:00:00 [kworker/2:3-mm_percpu_wq] root 317 2 0 13:43 ? 00:00:00 [cfg80211] root 330 2 0 13:43 ? 00:00:00 [brcmf_wq/mmc1:0] root 335 2 0 13:43 ? 00:00:00 [brcmf_wdog/mmc1] _rpc 428 1 0 13:43 ? 00:00:00 /sbin/rpcbind -f -w root 432 1 0 13:43 ? 00:00:02 /usr/sbin/haveged --Foreground --verbose=1 -w 1024 root 442 2 0 13:43 ? 00:00:00 [kworker/u8:3-events_unbound] nobody 448 1 0 13:43 ? 00:00:00 /usr/sbin/thd --triggers /etc/triggerhappy/triggers.d/ --socket /run/thd.socket --user nobody --deviceglob /dev/input/event* avahi 449 1 0 13:43 ? 00:00:00 avahi-daemon: running [volumiopi3.local] root 451 1 0 13:43 ? 00:00:00 /usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon volumio 456 1 0 13:43 ? 00:00:00 /usr/local/bin/volumio-remote-updater message+ 460 1 0 13:43 ? 00:00:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only root 467 1 0 13:43 ? 00:00:00 /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant root 472 1 0 13:43 ? 00:00:00 /lib/systemd/systemd-logind avahi 520 449 0 13:43 ? 00:00:00 avahi-daemon: chroot helper root 618 1 0 13:43 ? 00:00:00 /usr/sbin/nmbd --foreground --no-process-group root 627 1 0 13:43 tty1 00:00:00 /sbin/agetty -o -p -- \u --noclear tty1 linux root 630 1 0 13:43 ? 00:00:00 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d10 -w -I ntp 641 1 0 13:43 ? 00:00:00 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 103:103 root 645 1 0 13:43 ? 00:00:00 /usr/sbin/sshd -D root 651 618 0 13:43 ? 00:00:00 /usr/sbin/nmbd --foreground --no-process-group root 709 2 0 13:43 ? 00:00:00 [kworker/u9:1-hci0] root 710 1 0 13:43 ? 00:00:00 /usr/bin/hciattach /dev/serial1 bcm43xx 3000000 flow - b8:27:eb:ad:73:68 root 713 2 0 13:43 ? 00:00:00 [kworker/u9:2-hci0] root 717 1 0 13:43 ? 00:00:00 /sbin/dhcpcd eth0 root 744 1 0 13:43 ? 00:00:00 /usr/lib/bluetooth/bluetoothd --noplugin=sap root 765 1 0 13:43 ? 00:00:00 /usr/sbin/winbindd --foreground --no-process-group root 775 1 0 13:43 ? 00:00:00 /usr/sbin/hostapd -B -P /run/hostapd.pid -B /etc/hostapd/hostapd.conf dnsmasq 777 1 0 13:43 ? 00:00:00 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service volumio 782 1 3 13:43 ? 00:00:17 /usr/bin/node /volumio/index.js root 793 765 0 13:43 ? 00:00:00 winbindd: domain child [VOLUMIOPI3] root 795 1 0 13:43 ? 00:00:00 /usr/sbin/smbd --foreground --no-process-group root 802 795 0 13:43 ? 00:00:00 /usr/sbin/smbd --foreground --no-process-group root 803 795 0 13:43 ? 00:00:00 /usr/sbin/smbd --foreground --no-process-group root 804 765 0 13:43 ? 00:00:00 winbindd: idmap child root 805 765 0 13:43 ? 00:00:00 winbindd: domain child [BUILTIN] root 806 795 0 13:43 ? 00:00:00 /usr/sbin/smbd --foreground --no-process-group volumio 853 782 0 13:43 ? 00:00:00 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart volumio 860 853 0 13:43 ? 00:00:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart volumio 861 853 0 13:43 ? 00:00:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart volumio 862 853 0 13:43 ? 00:00:01 /usr/bin/node /volumio/app/plugins/miscellanea/albumart/serverStartup.js 3001 /data/albumart mpd 941 1 0 13:43 ? 00:00:01 /usr/bin/mpd --no-daemon shairpo+ 968 1 0 13:43 ? 00:00:00 /usr/bin/shairport-sync --configfile=/tmp/shairport-sync.conf volumio 984 1 0 13:43 ? 00:00:00 /usr/bin/upmpdcli -c /tmp/upmpdcli.conf volumio 1007 1 0 13:44 ? 00:00:00 /bin/streaming-daemon volumio 1059 1 0 13:44 ? 00:00:00 /bin/bash /usr/lib/startconnect.sh volumio 1060 1059 0 13:44 ? 00:00:00 ./usr/bin/vollibrespot -c /tmp/volspotify.toml - volumio 1067 782 0 13:45 ? 00:00:00 /bin/journalctl --output cat -f root 1076 2 0 13:48 ? 00:00:00 [kworker/2:0-mm_percpu_wq] root 1077 2 0 13:48 ? 00:00:00 [kworker/0:0-events] root 1080 2 0 13:49 ? 00:00:00 [kworker/3:0-events_freezable] volumio 1090 782 0 13:52 ? 00:00:00 /bin/sh -c /usr/bin/node /volumio/logsubmit.js 'Spotify OAuth Error' volumio 1091 1090 0 13:52 ? 00:00:00 /usr/bin/node /volumio/logsubmit.js Spotify OAuth Error volumio 1111 1091 0 13:52 ? 00:00:00 /bin/sh -c ps -ef >>/tmp/logondemand 2>&1 volumio 1112 1111 0 13:52 ? 00:00:00 ps -ef # df -h --------------- Filesystem Size Used Avail Use% Mounted on /dev/mmcblk0p2 2.5G 425M 1.9G 19% /imgpart /dev/loop0 364M 364M 0 100% /static overlay 56G 43M 53G 1% / devtmpfs 445M 0 445M 0% /dev tmpfs 484M 0 484M 0% /dev/shm tmpfs 484M 9.0M 475M 2% /run tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 484M 0 484M 0% /sys/fs/cgroup tmpfs 484M 0 484M 0% /var/spool/cups tmpfs 20M 28K 20M 1% /var/log tmpfs 484M 52K 484M 1% /tmp tmpfs 484M 0 484M 0% /var/spool/cups/tmp /dev/mmcblk0p1 92M 54M 38M 59% /boot # mount --------------- /dev/mmcblk0p2 on /imgpart type ext4 (rw,relatime) /dev/loop0 on /static type squashfs (ro,relatime) overlay on / type overlay (rw,relatime,lowerdir=/mnt/static,upperdir=/mnt/ext/dyn,workdir=/mnt/ext/work) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,relatime) devtmpfs on /dev type devtmpfs (rw,nosuid,size=455212k,nr_inodes=113803,mode=755) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=46,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) tmpfs on /var/spool/cups type tmpfs (rw,noatime,mode=755) tmpfs on /var/log type tmpfs (rw,nodev,relatime,size=20480k,mode=777,uid=1000,gid=4) tmpfs on /tmp type tmpfs (rw,noatime,mode=755) tmpfs on /var/spool/cups/tmp type tmpfs (rw,noatime,mode=755) /dev/mmcblk0p1 on /boot type vfat (rw,nosuid,nodev,noexec,relatime,fmask=0111,dmask=0000,allow_utime=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro,user) # netstat -natp --------------- (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:5000 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:49149 0.0.0.0:* LISTEN 984/upmpdcli tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 984/upmpdcli tcp 0 0 192.168.1.242:43108 104.199.65.124:443 ESTABLISHED 1060/./usr/bin/voll tcp 0 0 127.0.0.1:36334 127.0.0.1:3000 ESTABLISHED 456/volumio-remote- tcp 0 0 127.0.0.1:49838 127.0.0.1:6599 ESTABLISHED 984/upmpdcli tcp 0 0 127.0.0.1:36310 127.0.0.1:3000 ESTABLISHED 782/node tcp 0 0 127.0.0.1:36314 127.0.0.1:3000 ESTABLISHED 782/node tcp 0 0 127.0.0.1:49834 127.0.0.1:6599 ESTABLISHED 984/upmpdcli tcp 0 0 127.0.0.1:37618 127.0.0.1:6600 ESTABLISHED 782/node tcp 0 0 192.168.1.242:52184 34.120.160.131:443 ESTABLISHED 782/node tcp6 0 0 :::6599 :::* LISTEN 782/node tcp6 0 0 :::5000 :::* LISTEN - tcp6 0 0 :::6600 :::* LISTEN - tcp6 0 0 :::139 :::* LISTEN - tcp6 0 0 :::111 :::* LISTEN - tcp6 0 0 :::53 :::* LISTEN - tcp6 0 0 :::22 :::* LISTEN - tcp6 0 0 :::3000 :::* LISTEN 782/node tcp6 0 0 :::3001 :::* LISTEN 853/node tcp6 0 0 :::3005 :::* LISTEN 782/node tcp6 0 0 :::445 :::* LISTEN - tcp6 0 0 :::7777 :::* LISTEN 1007/streaming-daem tcp6 0 0 192.168.1.242:3000 192.168.1.140:50719 ESTABLISHED 782/node tcp6 0 0 127.0.0.1:3000 127.0.0.1:36310 ESTABLISHED 782/node tcp6 0 0 127.0.0.1:6599 127.0.0.1:49838 ESTABLISHED 782/node tcp6 0 0 127.0.0.1:3000 127.0.0.1:36334 ESTABLISHED 782/node tcp6 0 0 192.168.1.242:3000 192.168.1.140:50718 ESTABLISHED 782/node tcp6 0 0 127.0.0.1:3000 127.0.0.1:36314 ESTABLISHED 782/node tcp6 0 0 127.0.0.1:6600 127.0.0.1:37618 ESTABLISHED - tcp6 0 0 127.0.0.1:6599 127.0.0.1:49834 ESTABLISHED 782/node # cat /etc/asound.conf --------------- pcm.!default { type empty slave.pcm "volumio" } pcm.volumio { type empty slave.pcm "volumioOutput" } # There is always a plug before the hardware to be safe pcm.volumioOutput { type plug slave.pcm "volumioHw" } pcm.volumioHw { type hw card "sndrpihifiberry" } # cat /var/log/mpd.log --------------- Aug 02 13:43 : zeroconf: No global port, disabling zeroconf Aug 02 13:43 : zeroconf: No global port, disabling zeroconf Aug 02 13:43 : client: [0] opened from local Aug 02 13:43 : exception: No such directory Aug 02 13:43 : client: [1] opened from local Aug 02 13:43 : zeroconf: No global port, disabling zeroconf Aug 02 13:43 : client: [0] opened from local Aug 02 13:43 : client: [1] opened from 127.0.0.1:37614 Aug 02 13:43 : client: [2] opened from 127.0.0.1:37618 Aug 02 13:43 : exception: Failed to read mixer for 'alsa': no such mixer control: PCM Aug 02 13:44 : client: [1] closed # volumio plugin list --------------- This command will list installed plugins on your device ----------------------- Installed Plugins: [ { prettyName: 'Spotify', name: 'spop', category: 'music_service', version: '3.0.3', icon: 'fa-spotify', isManuallyInstalled: false, enabled: true, active: true } ] ------------------------------------------ # cat /data/configuration/plugins.json --------------- { "music_service": { "airplay_emulation": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "inputs": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "mpd": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "webradio": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "example_plugin": { "enabled": { "type": "boolean", "value": false }, "status": { "type": "string", "value": "STOPPED" } }, "last_100": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "upnp_browser": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "streaming_services": { "status": { "type": "string", "value": "STARTING" } }, "spop": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } } }, "audio_interface": { "outputs": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "upnp": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "alsa_controller": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } } }, "miscellanea": { "alarm-clock": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "albumart": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "appearance": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "wizard": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "my_music": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } } }, "user_interface": { "websocket": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "mpdemulation": { "enabled": { "type": "boolean", "value": false }, "status": { "type": "string", "value": "STARTED" } }, "rest_api": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } } }, "system_controller": { "updater_comm": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "network": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "networkfs": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "services": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "system": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "i2s_dacs": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "volumiodiscovery": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "volumio_command_line_client": { "enabled": { "type": "boolean", "value": true }, "status": { "type": "string", "value": "STARTED" } }, "my_volumio": { "status": { "type": "string", "value": "STARTED" } } } } # cat /etc/mpd.conf --------------- # Volumio MPD Configuration File # Files and directories ####################################################### music_directory "/var/lib/mpd/music" playlist_directory "/var/lib/mpd/playlists" db_file "/var/lib/mpd/tag_cache" log_file "/var/log/mpd.log" #pid_file "/var/run/mpd/pid" #state_file "/var/lib/mpd/state" #sticker_file "/var/lib/mpd/sticker.sql" ############################################################################### # General music daemon options ################################################ user "mpd" group "audio" bind_to_address "any" #port "6600" #log_level "default" #save_absolute_paths_in_playlists "no" #metadata_to_use "artist,album,title,track,name,genre,date,composer,performer,disc" auto_update "no" #auto_update_depth "3" ############################################################################### # Symbolic link behavior ###################################################### follow_outside_symlinks "yes" follow_inside_symlinks "yes" ############################################################################### # Input ####################################################################### # input { plugin "curl" # proxy "proxy.isp.com:8080" # proxy_user "user" # proxy_password "password" } ############################################################################### # Decoder ################################################################ decoder { plugin "faad" enabled "no" } ############################################################################### # Audio Output ################################################################ resampler { plugin "soxr" quality "high" threads "1" } audio_output { type "alsa" name "alsa" device "volumio" dop "no" } audio_output { type "fifo" enabled "no" name "multiroom" path "/tmp/snapfifo" format "44100:16:2" } #replaygain "album" #replaygain_preamp "0" volume_normalization "no" ############################################################################### # MPD Internal Buffering ###################################################### audio_buffer_size "2048" ############################################################################### # Resource Limitations ######################################################## #connection_timeout "60" max_connections "20" max_playlist_length "81920" max_command_list_size "81920" max_output_buffer_size "81920" ############################################################################### # Character Encoding ########################################################## filesystem_charset "UTF-8" ############################################################################### # volumio endpointstest --------------- TESTING REMOTE ENDPOINTS https://google.com, 562 ms: OK https://www.googleapis.com, 282 ms: OK https://securetoken.googleapis.com, 324 ms: OK https://myvolumio.firebaseio.com, 428 ms: OK https://functions.volumio.cloud, 906 ms: OK https://oauth-performer.dfs.volumio.org, 280 ms: OK https://browsing-performer.dfs.volumio.org, 369 ms: OK http://cddb.volumio.org, 736 ms: OK https://functions.volumio.cloud, 882 ms: OK http://pushupdates.volumio.org, 247 ms: OK http://plugins.volumio.org, 1410 ms: OK https://database.volumio.cloud, 620 ms: OK https://radio-directory.firebaseapp.com, 348 ms: OK ---------- REMOTE ENDPOINTS TEST OK, all Endpoints are reachable ---------- # sudo journalctl -p 7 --------------- -- Logs begin at Thu 2019-02-14 10:11:59 UTC, end at Tue 2022-08-02 13:52:44 UTC. -- Feb 14 10:11:59 volumiopi3 kernel: Booting Linux on physical CPU 0x0 Feb 14 10:11:59 volumiopi3 kernel: Linux version 5.10.92-v7+ (dom@buildbot) (arm-linux-gnueabihf-gcc-8 (Ubuntu/Linaro 8.4.0-3ubuntu1) 8.4.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #1514 SMP Mon Jan 17 17:36:39 GMT 2022 Feb 14 10:11:59 volumiopi3 kernel: CPU: ARMv7 Processor [410fd034] revision 4 (ARMv7), cr=10c5383d Feb 14 10:11:59 volumiopi3 kernel: CPU: div instructions available: patching division code Feb 14 10:11:59 volumiopi3 kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Feb 14 10:11:59 volumiopi3 kernel: OF: fdt: Machine model: Raspberry Pi 3 Model B Plus Rev 1.3 Feb 14 10:11:59 volumiopi3 kernel: random: fast init done Feb 14 10:11:59 volumiopi3 kernel: Memory policy: Data cache writealloc Feb 14 10:11:59 volumiopi3 kernel: Reserved memory: created CMA memory pool at 0x3a000000, size 64 MiB Feb 14 10:11:59 volumiopi3 kernel: OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool Feb 14 10:11:59 volumiopi3 kernel: Zone ranges: Feb 14 10:11:59 volumiopi3 kernel: DMA [mem 0x0000000000000000-0x000000003dffffff] Feb 14 10:11:59 volumiopi3 kernel: Normal empty Feb 14 10:11:59 volumiopi3 kernel: Movable zone start for each node Feb 14 10:11:59 volumiopi3 kernel: Early memory node ranges Feb 14 10:11:59 volumiopi3 kernel: node 0: [mem 0x0000000000000000-0x000000003dffffff] Feb 14 10:11:59 volumiopi3 kernel: Initmem setup node 0 [mem 0x0000000000000000-0x000000003dffffff] Feb 14 10:11:59 volumiopi3 kernel: On node 0 totalpages: 253952 Feb 14 10:11:59 volumiopi3 kernel: DMA zone: 2232 pages used for memmap Feb 14 10:11:59 volumiopi3 kernel: DMA zone: 0 pages reserved Feb 14 10:11:59 volumiopi3 kernel: DMA zone: 253952 pages, LIFO batch:63 Feb 14 10:11:59 volumiopi3 kernel: percpu: Embedded 20 pages/cpu s50828 r8192 d22900 u81920 Feb 14 10:11:59 volumiopi3 kernel: pcpu-alloc: s50828 r8192 d22900 u81920 alloc=20*4096 Feb 14 10:11:59 volumiopi3 kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 Feb 14 10:11:59 volumiopi3 kernel: Built 1 zonelists, mobility grouping on. Total pages: 251720 Feb 14 10:11:59 volumiopi3 kernel: Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=640 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 splash plymouth.ignore-serial-consoles dwc_otg.fiq_enable=1 dwc_otg.fiq_fsm_enable=1 dwc_otg.fiq_fsm_mask=0xF dwc_otg.nak_holdoff=1 quiet console=ttyS0,115200 console=tty1 imgpart=/dev/mmcblk0p2 imgfile=/volumio_current.sqsh rootwait bootdelay=5 elevator=noop logo.nologo vt.global_cursor_default=0 net.ifnames=0 snd-bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 loglevel=0 Feb 14 10:11:59 volumiopi3 kernel: Kernel parameter elevator= does not have any effect anymore. Please use sysfs to set IO scheduler for individual devices. Feb 14 10:11:59 volumiopi3 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: mem auto-init: stack:off, heap alloc:off, heap free:off Feb 14 10:11:59 volumiopi3 kernel: Memory: 910424K/1015808K available (10240K kernel code, 1312K rwdata, 2952K rodata, 1024K init, 862K bss, 39848K reserved, 65536K cma-reserved) Feb 14 10:11:59 volumiopi3 kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 Feb 14 10:11:59 volumiopi3 kernel: ftrace: allocating 32087 entries in 95 pages Feb 14 10:11:59 volumiopi3 kernel: ftrace: allocated 95 pages with 6 groups Feb 14 10:11:59 volumiopi3 kernel: rcu: Hierarchical RCU implementation. Feb 14 10:11:59 volumiopi3 kernel: Rude variant of Tasks RCU enabled. Feb 14 10:11:59 volumiopi3 kernel: Tracing variant of Tasks RCU enabled. Feb 14 10:11:59 volumiopi3 kernel: rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies. Feb 14 10:11:59 volumiopi3 kernel: NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16 Feb 14 10:11:59 volumiopi3 kernel: random: get_random_bytes called from start_kernel+0x3ac/0x580 with crng_init=1 Feb 14 10:11:59 volumiopi3 kernel: arch_timer: cp15 timer(s) running at 19.20MHz (phys). Feb 14 10:11:59 volumiopi3 kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns Feb 14 10:11:59 volumiopi3 kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns Feb 14 10:11:59 volumiopi3 kernel: Switching to timer-based delay loop, resolution 52ns Feb 14 10:11:59 volumiopi3 kernel: Console: colour dummy device 80x30 Feb 14 10:11:59 volumiopi3 kernel: printk: console [tty1] enabled Feb 14 10:11:59 volumiopi3 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000) Feb 14 10:11:59 volumiopi3 kernel: pid_max: default: 32768 minimum: 301 Feb 14 10:11:59 volumiopi3 kernel: LSM: Security Framework initializing Feb 14 10:11:59 volumiopi3 kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: cgroup: Disabling memory control group subsystem Feb 14 10:11:59 volumiopi3 kernel: CPU: Testing write buffer coherency: ok Feb 14 10:11:59 volumiopi3 kernel: CPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Feb 14 10:11:59 volumiopi3 kernel: Setting up static identity map for 0x100000 - 0x10003c Feb 14 10:11:59 volumiopi3 kernel: rcu: Hierarchical SRCU implementation. Feb 14 10:11:59 volumiopi3 kernel: smp: Bringing up secondary CPUs ... Feb 14 10:11:59 volumiopi3 kernel: CPU1: thread -1, cpu 1, socket 0, mpidr 80000001 Feb 14 10:11:59 volumiopi3 kernel: CPU2: thread -1, cpu 2, socket 0, mpidr 80000002 Feb 14 10:11:59 volumiopi3 kernel: CPU3: thread -1, cpu 3, socket 0, mpidr 80000003 Feb 14 10:11:59 volumiopi3 kernel: smp: Brought up 1 node, 4 CPUs Feb 14 10:11:59 volumiopi3 kernel: SMP: Total of 4 processors activated (153.60 BogoMIPS). Feb 14 10:11:59 volumiopi3 kernel: CPU: All CPU(s) started in HYP mode. Feb 14 10:11:59 volumiopi3 kernel: CPU: Virtualization extensions available. Feb 14 10:11:59 volumiopi3 kernel: devtmpfs: initialized Feb 14 10:11:59 volumiopi3 kernel: VFP support v0.3: implementor 41 architecture 3 part 40 variant 3 rev 4 Feb 14 10:11:59 volumiopi3 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns Feb 14 10:11:59 volumiopi3 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: pinctrl core: initialized pinctrl subsystem Feb 14 10:11:59 volumiopi3 kernel: NET: Registered protocol family 16 Feb 14 10:11:59 volumiopi3 kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations Feb 14 10:11:59 volumiopi3 kernel: audit: initializing netlink subsys (disabled) Feb 14 10:11:59 volumiopi3 kernel: thermal_sys: Registered thermal governor 'step_wise' Feb 14 10:11:59 volumiopi3 kernel: audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1 Feb 14 10:11:59 volumiopi3 kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers. Feb 14 10:11:59 volumiopi3 kernel: hw-breakpoint: maximum watchpoint size is 8 bytes. Feb 14 10:11:59 volumiopi3 kernel: Serial: AMBA PL011 UART driver Feb 14 10:11:59 volumiopi3 kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled Feb 14 10:11:59 volumiopi3 kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2022-01-20T13:58:22, variant start Feb 14 10:11:59 volumiopi3 kernel: raspberrypi-firmware soc:firmware: Firmware hash is bd88f66f8952d34e4e0613a85c7a6d3da49e13e2 Feb 14 10:11:59 volumiopi3 kernel: Kprobes globally optimized Feb 14 10:11:59 volumiopi3 kernel: bcm2835-dma 3f007000.dma: DMA legacy API manager, dmachans=0x1 Feb 14 10:11:59 volumiopi3 kernel: SCSI subsystem initialized Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver usbfs Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver hub Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new device driver usb Feb 14 10:11:59 volumiopi3 kernel: clocksource: Switched to clocksource arch_sys_counter Feb 14 10:11:59 volumiopi3 kernel: VFS: Disk quotas dquot_6.6.0 Feb 14 10:11:59 volumiopi3 kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Feb 14 10:11:59 volumiopi3 kernel: FS-Cache: Loaded Feb 14 10:11:59 volumiopi3 kernel: CacheFiles: Loaded Feb 14 10:11:59 volumiopi3 kernel: NET: Registered protocol family 2 Feb 14 10:11:59 volumiopi3 kernel: IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: TCP: Hash tables configured (established 8192 bind 8192) Feb 14 10:11:59 volumiopi3 kernel: UDP hash table entries: 512 (order: 2, 16384 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear) Feb 14 10:11:59 volumiopi3 kernel: NET: Registered protocol family 1 Feb 14 10:11:59 volumiopi3 kernel: RPC: Registered named UNIX socket transport module. Feb 14 10:11:59 volumiopi3 kernel: RPC: Registered udp transport module. Feb 14 10:11:59 volumiopi3 kernel: RPC: Registered tcp transport module. Feb 14 10:11:59 volumiopi3 kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Feb 14 10:11:59 volumiopi3 kernel: Trying to unpack rootfs image as initramfs... Feb 14 10:11:59 volumiopi3 kernel: Freeing initrd memory: 13028K Feb 14 10:11:59 volumiopi3 kernel: hw perfevents: enabled with armv7_cortex_a7 PMU driver, 7 counters available Feb 14 10:11:59 volumiopi3 kernel: Initialise system trusted keyrings Feb 14 10:11:59 volumiopi3 kernel: workingset: timestamp_bits=14 max_order=18 bucket_order=4 Feb 14 10:11:59 volumiopi3 kernel: zbud: loaded Feb 14 10:11:59 volumiopi3 kernel: FS-Cache: Netfs 'nfs' registered for caching Feb 14 10:11:59 volumiopi3 kernel: NFS: Registering the id_resolver key type Feb 14 10:11:59 volumiopi3 kernel: Key type id_resolver registered Feb 14 10:11:59 volumiopi3 kernel: Key type id_legacy registered Feb 14 10:11:59 volumiopi3 kernel: nfs4filelayout_init: NFSv4 File Layout Driver Registering... Feb 14 10:11:59 volumiopi3 kernel: nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering... Feb 14 10:11:59 volumiopi3 kernel: Key type asymmetric registered Feb 14 10:11:59 volumiopi3 kernel: Asymmetric key parser 'x509' registered Feb 14 10:11:59 volumiopi3 kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) Feb 14 10:11:59 volumiopi3 kernel: io scheduler mq-deadline registered Feb 14 10:11:59 volumiopi3 kernel: io scheduler kyber registered Feb 14 10:11:59 volumiopi3 kernel: bcm2708_fb soc:fb: FB found 1 display(s) Feb 14 10:11:59 volumiopi3 kernel: Console: switching to colour frame buffer device 80x30 Feb 14 10:11:59 volumiopi3 kernel: bcm2708_fb soc:fb: Registered framebuffer for display 0, size 640x480 Feb 14 10:11:59 volumiopi3 kernel: bcm2835-rng 3f104000.rng: hwrng registered Feb 14 10:11:59 volumiopi3 kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB) Feb 14 10:11:59 volumiopi3 kernel: gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000 Feb 14 10:11:59 volumiopi3 kernel: brd: module loaded Feb 14 10:11:59 volumiopi3 kernel: loop: module loaded Feb 14 10:11:59 volumiopi3 kernel: Loading iSCSI transport class v2.0-870. Feb 14 10:11:59 volumiopi3 kernel: libphy: Fixed MDIO Bus: probed Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver lan78xx Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver smsc95xx Feb 14 10:11:59 volumiopi3 kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus) Feb 14 10:11:59 volumiopi3 kernel: Core Release: 2.80a Feb 14 10:11:59 volumiopi3 kernel: Setting default values for core params Feb 14 10:11:59 volumiopi3 kernel: Finished setting default values for core params Feb 14 10:11:59 volumiopi3 kernel: Using Buffer DMA mode Feb 14 10:11:59 volumiopi3 kernel: Periodic Transfer Interrupt Enhancement - disabled Feb 14 10:11:59 volumiopi3 kernel: Multiprocessor Interrupt Enhancement - disabled Feb 14 10:11:59 volumiopi3 kernel: OTG VER PARAM: 0, OTG VER FLAG: 0 Feb 14 10:11:59 volumiopi3 kernel: Dedicated Tx FIFOs mode Feb 14 10:11:59 volumiopi3 kernel: Feb 14 10:11:59 volumiopi3 kernel: WARN::dwc_otg_hcd_init:1074: FIQ DMA bounce buffers: virt = ba114000 dma = 0xfa114000 len=9024 Feb 14 10:11:59 volumiopi3 kernel: FIQ FSM acceleration enabled for : Non-periodic Split Transactions Periodic Split Transactions High-Speed Isochronous Endpoints Interrupt/Control Split Transaction hack enabled Feb 14 10:11:59 volumiopi3 kernel: dwc_otg: Microframe scheduler enabled Feb 14 10:11:59 volumiopi3 kernel: Feb 14 10:11:59 volumiopi3 kernel: WARN::hcd_init_fiq:457: FIQ on core 1 Feb 14 10:11:59 volumiopi3 kernel: Feb 14 10:11:59 volumiopi3 kernel: WARN::hcd_init_fiq:458: FIQ ASM at 807cc05c length 36 Feb 14 10:11:59 volumiopi3 kernel: Feb 14 10:11:59 volumiopi3 kernel: WARN::hcd_init_fiq:497: MPHI regs_base at be810000 Feb 14 10:11:59 volumiopi3 kernel: dwc_otg 3f980000.usb: DWC OTG Controller Feb 14 10:11:59 volumiopi3 kernel: dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1 Feb 14 10:11:59 volumiopi3 kernel: dwc_otg 3f980000.usb: irq 89, io mem 0x00000000 Feb 14 10:11:59 volumiopi3 kernel: Init: Port Power? op_state=1 Feb 14 10:11:59 volumiopi3 kernel: Init: Power Port (0) Feb 14 10:11:59 volumiopi3 kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.10 Feb 14 10:11:59 volumiopi3 kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 Feb 14 10:11:59 volumiopi3 kernel: usb usb1: Product: DWC OTG Controller Feb 14 10:11:59 volumiopi3 kernel: usb usb1: Manufacturer: Linux 5.10.92-v7+ dwc_otg_hcd Feb 14 10:11:59 volumiopi3 kernel: usb usb1: SerialNumber: 3f980000.usb Feb 14 10:11:59 volumiopi3 kernel: hub 1-0:1.0: USB hub found Feb 14 10:11:59 volumiopi3 kernel: hub 1-0:1.0: 1 port detected Feb 14 10:11:59 volumiopi3 kernel: dwc_otg: FIQ enabled Feb 14 10:11:59 volumiopi3 kernel: dwc_otg: NAK holdoff enabled Feb 14 10:11:59 volumiopi3 kernel: dwc_otg: FIQ split-transaction FSM enabled Feb 14 10:11:59 volumiopi3 kernel: Module dwc_common_port init Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver usb-storage Feb 14 10:11:59 volumiopi3 kernel: mousedev: PS/2 mouse device common for all mice Feb 14 10:11:59 volumiopi3 kernel: bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer Feb 14 10:11:59 volumiopi3 kernel: sdhci: Secure Digital Host Controller Interface driver Feb 14 10:11:59 volumiopi3 kernel: sdhci: Copyright(c) Pierre Ossman Feb 14 10:11:59 volumiopi3 kernel: mmc-bcm2835 3f300000.mmcnr: could not get clk, deferring probe Feb 14 10:11:59 volumiopi3 kernel: sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe Feb 14 10:11:59 volumiopi3 kernel: sdhci-pltfm: SDHCI platform and OF driver helper Feb 14 10:11:59 volumiopi3 kernel: ledtrig-cpu: registered to indicate activity on CPUs Feb 14 10:11:59 volumiopi3 kernel: hid: raw HID events driver (C) Jiri Kosina Feb 14 10:11:59 volumiopi3 kernel: usbcore: registered new interface driver usbhid Feb 14 10:11:59 volumiopi3 kernel: usbhid: USB HID core driver Feb 14 10:11:59 volumiopi3 kernel: Initializing XFRM netlink socket Feb 14 10:11:59 volumiopi3 kernel: NET: Registered protocol family 17 Feb 14 10:11:59 volumiopi3 kernel: Key type dns_resolver registered Feb 14 10:11:59 volumiopi3 kernel: Registering SWP/SWPB emulation handler Feb 14 10:11:59 volumiopi3 kernel: registered taskstats version 1 Feb 14 10:11:59 volumiopi3 kernel: Loading compiled-in X.509 certificates Feb 14 10:11:59 volumiopi3 kernel: Key type ._fscrypt registered Feb 14 10:11:59 volumiopi3 kernel: Key type .fscrypt registered Feb 14 10:11:59 volumiopi3 kernel: Key type fscrypt-provisioning registered Feb 14 10:11:59 volumiopi3 kernel: uart-pl011 3f201000.serial: cts_event_workaround enabled Feb 14 10:11:59 volumiopi3 kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 114, base_baud = 0) is a PL011 rev2 Feb 14 10:11:59 volumiopi3 kernel: bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver Feb 14 10:11:59 volumiopi3 kernel: mmc-bcm2835 3f300000.mmcnr: mmc_debug:0 mmc_debug2:0 Feb 14 10:11:59 volumiopi3 kernel: mmc-bcm2835 3f300000.mmcnr: DMA channel allocated Feb 14 10:11:59 volumiopi3 kernel: sdhost: log_buf @ (ptrval) (fa113000) Feb 14 10:11:59 volumiopi3 kernel: mmc1: queuing unknown CIS tuple 0x80 (2 bytes) Feb 14 10:11:59 volumiopi3 kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Feb 14 10:11:59 volumiopi3 kernel: mmc1: queuing unknown CIS tuple 0x80 (3 bytes) Feb 14 10:11:59 volumiopi3 kernel: mmc1: queuing unknown CIS tuple 0x80 (7 bytes) Feb 14 10:11:59 volumiopi3 kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1) Feb 14 10:11:59 volumiopi3 kernel: of_cfs_init Feb 14 10:11:59 volumiopi3 kernel: of_cfs_init: OK Feb 14 10:11:59 volumiopi3 kernel: Indeed it is in host mode hprt0 = 00021501 Feb 14 10:11:59 volumiopi3 kernel: Freeing unused kernel memory: 1024K Feb 14 10:11:59 volumiopi3 kernel: Run /init as init process Feb 14 10:11:59 volumiopi3 kernel: with arguments: Feb 14 10:11:59 volumiopi3 kernel: /init Feb 14 10:11:59 volumiopi3 kernel: splash Feb 14 10:11:59 volumiopi3 kernel: with environment: Feb 14 10:11:59 volumiopi3 kernel: HOME=/ Feb 14 10:11:59 volumiopi3 kernel: TERM=linux Feb 14 10:11:59 volumiopi3 kernel: imgpart=/dev/mmcblk0p2 Feb 14 10:11:59 volumiopi3 kernel: imgfile=/volumio_current.sqsh Feb 14 10:11:59 volumiopi3 kernel: bootdelay=5 Feb 14 10:11:59 volumiopi3 kernel: mmc0: host does not support reading read-only switch, assuming write-enable Feb 14 10:11:59 volumiopi3 kernel: mmc1: new high speed SDIO card at address 0001 Feb 14 10:11:59 volumiopi3 kernel: mmc0: new high speed SDXC card at address aaaa Feb 14 10:11:59 volumiopi3 kernel: mmcblk0: mmc0:aaaa SR64G 59.5 GiB Feb 14 10:11:59 volumiopi3 kernel: mmcblk0: p1 p2 p3 Feb 14 10:11:59 volumiopi3 kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg Feb 14 10:11:59 volumiopi3 kernel: Indeed it is in host mode hprt0 = 00001101 Feb 14 10:11:59 volumiopi3 initramfs: Booting Volumio for BCM2835 Feb 14 10:11:59 volumiopi3 initramfs: This script mounts rootfs RO with an overlay RW layer. Feb 14 10:11:59 volumiopi3 kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher Feb 14 10:11:59 volumiopi3 initramfs: IMGPART=/dev/mmcblk0p2 Feb 14 10:11:59 volumiopi3 initramfs: IMGFILE=/volumio_current.sqsh Feb 14 10:11:59 volumiopi3 initramfs: Boot delay (except first time) will be 5 seconds Feb 14 10:11:59 volumiopi3 initramfs: /dev/mmcblk0p2: Feb 14 10:11:59 volumiopi3 kernel: usb 1-1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3 Feb 14 10:11:59 volumiopi3 kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Feb 14 10:11:59 volumiopi3 kernel: hub 1-1:1.0: USB hub found Feb 14 10:11:59 volumiopi3 kernel: hub 1-1:1.0: 4 ports detected Feb 14 10:11:59 volumiopi3 kernel: EXT4-fs (mmcblk0p2): recovery complete Feb 14 10:11:59 volumiopi3 kernel: EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) Feb 14 10:11:59 volumiopi3 initramfs: Doing a 5 second delay here to give kernel load a headstart Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1: new high-speed USB device number 3 using dwc_otg Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1: New USB device found, idVendor=0424, idProduct=2514, bcdDevice= b.b3 Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Feb 14 10:11:59 volumiopi3 kernel: hub 1-1.1:1.0: USB hub found Feb 14 10:11:59 volumiopi3 kernel: hub 1-1.1:1.0: 3 ports detected Feb 14 10:11:59 volumiopi3 kernel: dwc_otg_handle_wakeup_detected_intr lxstate = 2 Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1.1: new high-speed USB device number 4 using dwc_otg Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1.1: New USB device found, idVendor=0424, idProduct=7800, bcdDevice= 3.00 Feb 14 10:11:59 volumiopi3 kernel: usb 1-1.1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Feb 14 10:11:59 volumiopi3 kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): No External EEPROM. Setting MAC Speed Feb 14 10:11:59 volumiopi3 kernel: libphy: lan78xx-mdiobus: probed Feb 14 10:11:59 volumiopi3 kernel: lan78xx 1-1.1.1:1.0 (unnamed net_device) (uninitialized): int urb period 64 Feb 14 10:11:59 volumiopi3 initramfs: Checking for USB updates Feb 14 10:11:59 volumiopi3 initramfs: No USB device detected (when incorrect, try adding 'bootdelay=5' to your boot cmdline) Feb 14 10:11:59 volumiopi3 kernel: EXT4-fs (mmcblk0p3): recovery complete Feb 14 10:11:59 volumiopi3 kernel: EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null) Feb 14 10:11:59 volumiopi3 initramfs: With Option: Feb 14 10:11:59 volumiopi3 initramfs: VOLUMIO_VERSION="3.324" Feb 14 10:11:59 volumiopi3 initramfs: Finish initramfs, continue booting Volumio Feb 14 10:11:59 volumiopi3 systemd[1]: System time before build time, advancing clock. Feb 14 10:11:59 volumiopi3 kernel: NET: Registered protocol family 10 Feb 14 10:11:59 volumiopi3 kernel: Segment Routing with IPv6 Feb 14 10:11:59 volumiopi3 systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) Feb 14 10:11:59 volumiopi3 systemd[1]: Detected architecture arm. Feb 14 10:11:59 volumiopi3 systemd[1]: Set hostname to . Feb 14 10:11:59 volumiopi3 systemd[1]: /lib/systemd/system/winbind.service:8: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/winbindd.pid → /run/samba/winbindd.pid; please update the unit file accordingly. Feb 14 10:11:59 volumiopi3 kernel: random: systemd: uninitialized urandom read (16 bytes read) Feb 14 10:11:59 volumiopi3 kernel: random: systemd: uninitialized urandom read (16 bytes read) Feb 14 10:11:59 volumiopi3 kernel: random: systemd: uninitialized urandom read (16 bytes read) Feb 14 10:11:59 volumiopi3 systemd[1]: Listening on udev Control Socket. Feb 14 10:11:59 volumiopi3 systemd[1]: Listening on Journal Audit Socket. Feb 14 10:11:59 volumiopi3 systemd[1]: Listening on Journal Socket (/dev/log). Feb 14 10:11:59 volumiopi3 systemd[1]: Created slice system-systemd\x2dfsck.slice. Feb 14 10:11:59 volumiopi3 systemd[1]: Listening on fsck to fsckd communication Socket. Feb 14 10:11:59 volumiopi3 systemd[1]: Listening on RPCbind Server Activation Socket. Feb 14 10:11:59 volumiopi3 kernel: i2c /dev entries driver Feb 14 10:11:59 volumiopi3 systemd-journald[185]: Journal started Feb 14 10:11:59 volumiopi3 systemd-journald[185]: Runtime journal (/run/log/journal/26288ad12cf0817baa21aee262cc2d39) is 3.7M, max 30.0M, 26.2M free. Feb 14 10:11:59 volumiopi3 systemd-modules-load[189]: Inserted module 'i2c_dev' Feb 14 10:11:59 volumiopi3 systemd[1]: Mounted POSIX Message Queue File System. Feb 14 10:11:59 volumiopi3 systemd[1]: Mounted Kernel Debug File System. Feb 14 10:11:59 volumiopi3 systemd[1]: Mounted RPC Pipe File System. Feb 14 10:11:59 volumiopi3 systemd[1]: Started Remount Root and Kernel File Systems. Feb 14 10:11:59 volumiopi3 systemd[1]: Mounted Kernel Configuration File System. Aug 02 13:43:05 volumiopi3 fake-hwclock[191]: Tue Aug 2 13:43:05 UTC 2022 Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Create System Users... Aug 02 13:43:05 volumiopi3 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Load/Save Random Seed... Aug 02 13:43:05 volumiopi3 systemd[1]: Started Restore / save the current clock. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Apply Kernel Variables. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Load/Save Random Seed. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Create System Users. Aug 02 13:43:05 volumiopi3 systemd[1]: dynamicswap.service: Succeeded. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Create Static Device Nodes in /dev... Aug 02 13:43:05 volumiopi3 systemd[1]: Started Create Static Device Nodes in /dev. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting udev Kernel Device Manager... Aug 02 13:43:05 volumiopi3 systemd[1]: Reached target Local File Systems (Pre). Aug 02 13:43:05 volumiopi3 systemd[1]: Mounting /var/spool/cups... Aug 02 13:43:05 volumiopi3 systemd[1]: var-log.mount: Directory /var/log to mount over is not empty, mounting anyway. Aug 02 13:43:05 volumiopi3 systemd[1]: Mounting /var/log... Aug 02 13:43:05 volumiopi3 systemd[1]: tmp.mount: Directory /tmp to mount over is not empty, mounting anyway. Aug 02 13:43:05 volumiopi3 systemd[1]: Mounting /tmp... Aug 02 13:43:05 volumiopi3 systemd[1]: Started udev Coldplug all Devices. Aug 02 13:43:05 volumiopi3 systemd[1]: Mounted /var/spool/cups. Aug 02 13:43:05 volumiopi3 systemd[1]: Mounted /var/log. Aug 02 13:43:05 volumiopi3 systemd[1]: Mounted /tmp. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Flush Journal to Persistent Storage... Aug 02 13:43:05 volumiopi3 systemd[1]: Mounting /var/spool/cups/tmp... Aug 02 13:43:05 volumiopi3 systemd-udevd[213]: Network interface NamePolicy= disabled on kernel command line, ignoring. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Helper to synchronize boot up for ifupdown... Aug 02 13:43:05 volumiopi3 systemd[1]: Mounted /var/spool/cups/tmp. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Helper to synchronize boot up for ifupdown. Aug 02 13:43:05 volumiopi3 systemd-journald[185]: Runtime journal (/run/log/journal/26288ad12cf0817baa21aee262cc2d39) is 7.5M, max 30.0M, 22.5M free. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Flush Journal to Persistent Storage. Aug 02 13:43:05 volumiopi3 systemd[1]: Started udev Kernel Device Manager. Aug 02 13:43:05 volumiopi3 systemd[1]: Starting Show Plymouth Boot Screen... Aug 02 13:43:05 volumiopi3 systemd[1]: Received SIGRTMIN+20 from PID 233 (plymouthd). Aug 02 13:43:05 volumiopi3 systemd[1]: Started Show Plymouth Boot Screen. Aug 02 13:43:05 volumiopi3 systemd[1]: Started Forward Password Requests to Plymouth Directory Watch. Aug 02 13:43:05 volumiopi3 systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 02 13:43:05 volumiopi3 systemd[1]: Reached target Local Encrypted Volumes. Aug 02 13:43:05 volumiopi3 systemd[1]: Reached target Paths. Aug 02 13:43:05 volumiopi3 kernel: vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:05 volumiopi3 kernel: bcm2835_vc_sm_cma_probe: Videocore shared memory driver Aug 02 13:43:05 volumiopi3 kernel: [vc_sm_connected_init]: start Aug 02 13:43:05 volumiopi3 kernel: [vc_sm_connected_init]: installed successfully Aug 02 13:43:05 volumiopi3 kernel: mc: Linux media interface: v0.10 Aug 02 13:43:06 volumiopi3 kernel: snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835_audio bcm2835_audio: card created with 4 channels Aug 02 13:43:06 volumiopi3 kernel: bcm2835_audio bcm2835_audio: card created with 4 channels Aug 02 13:43:06 volumiopi3 kernel: videodev: Linux video capture interface: v2.00 Aug 02 13:43:06 volumiopi3 kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video10 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 decode Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video11 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 encode Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video20 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video12 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 isp Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video21 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video22 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video23 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register output node 0 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 1 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 2 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Register capture node 3 with media controller Aug 02 13:43:06 volumiopi3 kernel: bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp Aug 02 13:43:06 volumiopi3 kernel: bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Device registered as /dev/video18 Aug 02 13:43:06 volumiopi3 kernel: bcm2835-codec bcm2835-codec: Loaded V4L2 image_fx Aug 02 13:43:06 volumiopi3 systemd[1]: Found device /dev/mmcblk0p1. Aug 02 13:43:06 volumiopi3 systemd-udevd[224]: Using default interface naming scheme 'v240'. Aug 02 13:43:07 volumiopi3 kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database Aug 02 13:43:07 volumiopi3 systemd-udevd[224]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Aug 02 13:43:07 volumiopi3 systemd-udevd[229]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Aug 02 13:43:07 volumiopi3 kernel: cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Aug 02 13:43:07 volumiopi3 kernel: brcmfmac: F1 signature read @0x18000000=0x15264345 Aug 02 13:43:07 volumiopi3 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Aug 02 13:43:07 volumiopi3 kernel: usbcore: registered new interface driver brcmfmac Aug 02 13:43:08 volumiopi3 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Aug 02 13:43:08 volumiopi3 kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Aug 02 13:43:08 volumiopi3 kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e Aug 02 13:43:08 volumiopi3 kernel: random: crng init done Aug 02 13:43:08 volumiopi3 kernel: random: 7 urandom warning(s) missed due to ratelimiting Aug 02 13:43:08 volumiopi3 systemd-udevd[230]: Using default interface naming scheme 'v240'. Aug 02 13:43:08 volumiopi3 systemd-udevd[230]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in 7800 being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in FUSE Control File System being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in Huge Pages File System being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 02 13:43:09 volumiopi3 systemd[1]: Starting File System Check on /dev/mmcblk0p1... Aug 02 13:43:09 volumiopi3 systemd[1]: Starting Load/Save RF Kill Switch Status... Aug 02 13:43:09 volumiopi3 systemd[1]: Started File System Check Daemon to report status. Aug 02 13:43:09 volumiopi3 systemd[1]: Found device /sys/subsystem/net/devices/wlan0. Aug 02 13:43:09 volumiopi3 systemd[1]: Started Load/Save RF Kill Switch Status. Aug 02 13:43:09 volumiopi3 systemd-fsck[368]: fsck.fat 4.1 (2017-01-24) Aug 02 13:43:09 volumiopi3 systemd-fsck[368]: /dev/mmcblk0p1: 297 files, 27487/46774 clusters Aug 02 13:43:09 volumiopi3 systemd[1]: Started File System Check on /dev/mmcblk0p1. Aug 02 13:43:09 volumiopi3 systemd[1]: Mounting /boot... Aug 02 13:43:10 volumiopi3 systemd[1]: Mounted /boot. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target Local File Systems. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Raise network interfaces... Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Started ifup for eth0. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Preprocess NFS configuration... Aug 02 13:43:10 volumiopi3 systemd[1]: Started ifup for wlan0. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Tell Plymouth To Write Out Runtime Data... Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Create Volatile Files and Directories... Aug 02 13:43:10 volumiopi3 systemd[1]: plymouth-read-write.service: Succeeded. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Tell Plymouth To Write Out Runtime Data. Aug 02 13:43:10 volumiopi3 systemd[1]: Received SIGRTMIN+20 from PID 233 (plymouthd). Aug 02 13:43:10 volumiopi3 systemd[1]: nfs-config.service: Succeeded. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Preprocess NFS configuration. Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in RPC security service for NFS server being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in RPC security service for NFS client and server being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target NFS client services. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Create Volatile Files and Directories. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Update UTMP about System Boot/Shutdown... Aug 02 13:43:10 volumiopi3 systemd[1]: Starting RPC bind portmap service... Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in Network Time Synchronization being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Entropy daemon using the HAVEGE algorithm. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Update UTMP about System Boot/Shutdown. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target System Initialization. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Daily apt download activities. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Daily apt upgrade and clean activities. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Daily Cleanup of Temporary Directories. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target Timers. Aug 02 13:43:10 volumiopi3 systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket. Aug 02 13:43:10 volumiopi3 systemd[1]: Listening on triggerhappy.socket. Aug 02 13:43:10 volumiopi3 systemd[1]: Listening on mpd.socket. Aug 02 13:43:10 volumiopi3 systemd[1]: Listening on D-Bus System Message Bus Socket. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target Sockets. Aug 02 13:43:10 volumiopi3 systemd[1]: Reached target Basic System. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting triggerhappy global hotkey daemon... Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Avahi mDNS/DNS-SD Stack... Aug 02 13:43:10 volumiopi3 systemd[1]: Started Volumio Iptables Module. Aug 02 13:43:10 volumiopi3 systemd[1]: Started Manage Sound Card State (restore and store). Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Save/Restore Sound Card State... Aug 02 13:43:10 volumiopi3 alsactl[451]: alsactl 1.1.8 daemon started Aug 02 13:43:10 volumiopi3 thd[448]: Unable to parse trigger line: Aug 02 13:43:10 volumiopi3 thd[448]: Unable to parse trigger line: KEY_MIN_INTERESTING 1 /usr/local/bin/volumio volume toggle Aug 02 13:43:10 volumiopi3 thd[448]: Unable to parse trigger line: Aug 02 13:43:10 volumiopi3 systemd[1]: Started UPnP Renderer front-end to MPD. Aug 02 13:43:10 volumiopi3 kernel: 8021q: 802.1Q VLAN Support v1.8 Aug 02 13:43:10 volumiopi3 systemd[1]: Started volumio-remote-updater.service. Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in Copy user wpa_supplicant.conf being skipped. Aug 02 13:43:10 volumiopi3 kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled Aug 02 13:43:10 volumiopi3 systemd[1]: Started D-Bus System Message Bus. Aug 02 13:43:10 volumiopi3 thd[448]: Found socket passed from systemd Aug 02 13:43:10 volumiopi3 systemd[1]: Starting WPA supplicant... Aug 02 13:43:10 volumiopi3 systemd[1]: Starting dhcpcd on all interfaces... Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in Volumio SSH enabler being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Login Service... Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Configure Bluetooth Modems connected by UART... Aug 02 13:43:10 volumiopi3 systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped. Aug 02 13:43:10 volumiopi3 systemd[1]: Starting Wireless Services... Aug 02 13:43:10 volumiopi3 systemd[1]: Started triggerhappy global hotkey daemon. Aug 02 13:43:11 volumiopi3 dhcpcd[471]: Not running dhcpcd because /etc/network/interfaces Aug 02 13:43:11 volumiopi3 dhcpcd[471]: defines some interfaces that will use a Aug 02 13:43:11 volumiopi3 dhcpcd[471]: DHCP client or static address Aug 02 13:43:11 volumiopi3 kernel: uart-pl011 3f201000.serial: no DMA platform data Aug 02 13:43:11 volumiopi3 systemd-logind[472]: New seat seat0. Aug 02 13:43:11 volumiopi3 avahi-daemon[449]: Found user 'avahi' (UID 110) and group 'avahi' (GID 113). Aug 02 13:43:11 volumiopi3 avahi-daemon[449]: Successfully dropped root privileges. Aug 02 13:43:11 volumiopi3 avahi-daemon[449]: avahi-daemon 0.7 starting up. Aug 02 13:43:11 volumiopi3 kernel: lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped Aug 02 13:43:11 volumiopi3 sh[376]: eth0: waiting for carrier Aug 02 13:43:11 volumiopi3 dhcpcd[424]: eth0: waiting for carrier Aug 02 13:43:11 volumiopi3 kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Aug 02 13:43:11 volumiopi3 sh[376]: eth0: carrier acquired Aug 02 13:43:11 volumiopi3 dhcpcd[424]: eth0: carrier acquired Aug 02 13:43:12 volumiopi3 sh[376]: DUID 00:01:00:01:2a:5e:eb:66:b8:27:eb:07:d9:c2 Aug 02 13:43:12 volumiopi3 sh[376]: eth0: IAID eb:07:d9:c2 Aug 02 13:43:12 volumiopi3 dhcpcd[424]: DUID 00:01:00:01:2a:5e:eb:66:b8:27:eb:07:d9:c2 Aug 02 13:43:12 volumiopi3 dhcpcd[424]: eth0: IAID eb:07:d9:c2 Aug 02 13:43:12 volumiopi3 sh[376]: eth0: adding address fe80::9876:6d6e:3354:3e50 Aug 02 13:43:12 volumiopi3 sh[376]: ipv6_addaddr1: Permission denied Aug 02 13:43:12 volumiopi3 dhcpcd[424]: eth0: adding address fe80::9876:6d6e:3354:3e50 Aug 02 13:43:12 volumiopi3 dhcpcd[424]: ipv6_addaddr1: Permission denied Aug 02 13:43:12 volumiopi3 dbus-daemon[460]: [system] Successfully activated service 'org.freedesktop.systemd1' Aug 02 13:43:12 volumiopi3 systemd[1]: Started Login Service. Aug 02 13:43:12 volumiopi3 systemd[1]: Started RPC bind portmap service. Aug 02 13:43:12 volumiopi3 systemd[1]: Started Save/Restore Sound Card State. Aug 02 13:43:12 volumiopi3 systemd[1]: dhcpcd.service: Control process exited, code=exited, status=6/NOTCONFIGURED Aug 02 13:43:12 volumiopi3 systemd[1]: dhcpcd.service: Failed with result 'exit-code'. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Successfully called chroot(). Aug 02 13:43:12 volumiopi3 systemd[1]: Failed to start dhcpcd on all interfaces. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Successfully dropped remaining capabilities. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Loading service file /services/volumio.service. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Network interface enumeration completed. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Server startup complete. Host name is volumiopi3.local. Local service cookie is 1159842951. Aug 02 13:43:12 volumiopi3 avahi-daemon[449]: Service "VolumioPi3" (/services/volumio.service) successfully established. Aug 02 13:43:12 volumiopi3 systemd[1]: Started Avahi mDNS/DNS-SD Stack. Aug 02 13:43:12 volumiopi3 sh[380]: wlan0=wlan0 Aug 02 13:43:12 volumiopi3 systemd[1]: Reached target Sound Card. Aug 02 13:43:12 volumiopi3 systemd[1]: Reached target Remote File Systems (Pre). Aug 02 13:43:12 volumiopi3 systemd[1]: Reached target Remote File Systems. Aug 02 13:43:12 volumiopi3 systemd[1]: Starting LSB: Load kernel modules needed to enable cpufreq scaling... Aug 02 13:43:12 volumiopi3 systemd[1]: Reached target RPC Port Mapper. Aug 02 13:43:12 volumiopi3 sh[376]: eth0: soliciting a DHCP lease Aug 02 13:43:12 volumiopi3 dhcpcd[424]: eth0: soliciting a DHCP lease Aug 02 13:43:12 volumiopi3 systemd[1]: Started Raise network interfaces. Aug 02 13:43:12 volumiopi3 sh[376]: eth0: soliciting an IPv6 router Aug 02 13:43:12 volumiopi3 dhcpcd[424]: eth0: soliciting an IPv6 router Aug 02 13:43:13 volumiopi3 loadcpufreq[540]: Loading cpufreq kernel modules...done (none). Aug 02 13:43:13 volumiopi3 systemd[1]: Started LSB: Load kernel modules needed to enable cpufreq scaling. Aug 02 13:43:13 volumiopi3 systemd[1]: Starting LSB: set CPUFreq kernel parameters... Aug 02 13:43:13 volumiopi3 sh[376]: eth0: offered 192.168.1.242 from 192.168.1.1 Aug 02 13:43:13 volumiopi3 dhcpcd[424]: eth0: offered 192.168.1.242 from 192.168.1.1 Aug 02 13:43:13 volumiopi3 cpufrequtils[582]: CPUFreq Utilities: Setting performance CPUFreq governor...CPU0...CPU1...CPU2...CPU3...done. Aug 02 13:43:13 volumiopi3 systemd[1]: Started LSB: set CPUFreq kernel parameters. Aug 02 13:43:13 volumiopi3 haveged[432]: haveged: ver: 1.9.1; arch: generic; vend: ; build: (gcc 8.2.0 CTV); collect: 128K Aug 02 13:43:13 volumiopi3 haveged[432]: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 11/40; sz: 14768/63488 Aug 02 13:43:13 volumiopi3 haveged[432]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 8.00062 Aug 02 13:43:13 volumiopi3 haveged[432]: haveged: fills: 0, generated: 0 Aug 02 13:43:13 volumiopi3 systemd[1]: iptables.service: Succeeded. Aug 02 13:43:13 volumiopi3 sh[376]: eth0: probing address 192.168.1.242/24 Aug 02 13:43:13 volumiopi3 dhcpcd[424]: eth0: probing address 192.168.1.242/24 Aug 02 13:43:13 volumiopi3 systemd[1]: Started WPA supplicant. Aug 02 13:43:13 volumiopi3 systemd[1]: Reached target Network. Aug 02 13:43:13 volumiopi3 wpa_supplicant[467]: Successfully initialized wpa_supplicant Aug 02 13:43:13 volumiopi3 systemd[1]: Reached target Network is Online. Aug 02 13:43:13 volumiopi3 systemd[1]: Started Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:13 volumiopi3 systemd[1]: Starting LSB: Brings up/down network automatically... Aug 02 13:43:13 volumiopi3 systemd[1]: Starting Samba NMB Daemon... Aug 02 13:43:13 volumiopi3 systemd[1]: Starting Network Time Service... Aug 02 13:43:13 volumiopi3 systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped. Aug 02 13:43:13 volumiopi3 systemd[1]: Starting OpenBSD Secure Shell server... Aug 02 13:43:13 volumiopi3 systemd[1]: Starting /etc/rc.local Compatibility... Aug 02 13:43:13 volumiopi3 systemd[1]: Starting Permit User Sessions... Aug 02 13:43:14 volumiopi3 systemd[1]: Starting Music Player Daemon... Aug 02 13:43:14 volumiopi3 systemd[1]: Started /etc/rc.local Compatibility. Aug 02 13:43:14 volumiopi3 systemd[1]: Started Permit User Sessions. Aug 02 13:43:14 volumiopi3 systemd[1]: Starting Terminate Plymouth Boot Screen... Aug 02 13:43:14 volumiopi3 systemd[1]: Starting Hold until boot process finishes up... Aug 02 13:43:14 volumiopi3 systemd[1]: Received SIGRTMIN+21 from PID 233 (plymouthd). Aug 02 13:43:14 volumiopi3 systemd[1]: plymouth-quit.service: Succeeded. Aug 02 13:43:14 volumiopi3 systemd[1]: Started Terminate Plymouth Boot Screen. Aug 02 13:43:14 volumiopi3 systemd[1]: plymouth-start.service: Succeeded. Aug 02 13:43:14 volumiopi3 systemd[1]: plymouth-quit-wait.service: Succeeded. Aug 02 13:43:14 volumiopi3 systemd[1]: Started Hold until boot process finishes up. Aug 02 13:43:14 volumiopi3 systemd[1]: Received SIGRTMIN+21 from PID 233 (n/a). Aug 02 13:43:14 volumiopi3 systemd[1]: Started Getty on tty1. Aug 02 13:43:14 volumiopi3 systemd[1]: Reached target Login Prompts. Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: ifplugd 0.28 initializing. Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: Using interface eth0/B8:27:EB:07:D9:C2 with driver (version: 5.10.92-v7+) Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: Using detection mode: SIOCETHTOOL Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: Initialization complete, link beat detected. Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: Executing '/etc/ifplugd/ifplugd.action eth0 up'. Aug 02 13:43:14 volumiopi3 ifplugd(eth0)[630]: client: ifup: waiting for lock on /run/network/ifstate.eth0 Aug 02 13:43:14 volumiopi3 ntpd[607]: ntpd 4.2.8p12@1.3728-o (1): Starting Aug 02 13:43:14 volumiopi3 systemd[1]: Started Network Time Service. Aug 02 13:43:14 volumiopi3 ntpd[607]: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 103:103 Aug 02 13:43:14 volumiopi3 ntpd[641]: proto: precision = 0.573 usec (-21) Aug 02 13:43:14 volumiopi3 ntpd[641]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): good hash signature Aug 02 13:43:14 volumiopi3 ntpd[641]: leapsecond file ('/usr/share/zoneinfo/leap-seconds.list'): loaded, expire=2022-12-28T00:00:00Z last=2017-01-01T00:00:00Z ofs=37 Aug 02 13:43:14 volumiopi3 ntpd[641]: Listen and drop on 0 v6wildcard [::]:123 Aug 02 13:43:14 volumiopi3 ntpd[641]: Listen and drop on 1 v4wildcard 0.0.0.0:123 Aug 02 13:43:14 volumiopi3 ntpd[641]: Listen normally on 2 lo 127.0.0.1:123 Aug 02 13:43:14 volumiopi3 ntpd[641]: Listening on routing socket on fd #19 for interface updates Aug 02 13:43:14 volumiopi3 ntpd[641]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 02 13:43:14 volumiopi3 ntpd[641]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 02 13:43:14 volumiopi3 volumio-remote-updater[456]: Error: No active session Aug 02 13:43:14 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:14] [info] asio async_connect error: system:111 (Connection refused) Aug 02 13:43:14 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:14] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected) Aug 02 13:43:14 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:14] [error] handle_connect error: Underlying Transport Error Aug 02 13:43:14 volumiopi3 systemd[1]: systemd-rfkill.service: Succeeded. Aug 02 13:43:14 volumiopi3 volumio[455]: Could not open config: /tmp/upmpdcli.conf Aug 02 13:43:14 volumiopi3 systemd[1]: upmpdcli.service: Main process exited, code=exited, status=1/FAILURE Aug 02 13:43:14 volumiopi3 systemd[1]: upmpdcli.service: Failed with result 'exit-code'. Aug 02 13:43:15 volumiopi3 sshd[645]: Server listening on 0.0.0.0 port 22. Aug 02 13:43:15 volumiopi3 sshd[645]: Server listening on :: port 22. Aug 02 13:43:15 volumiopi3 systemd[1]: Started OpenBSD Secure Shell server. Aug 02 13:43:15 volumiopi3 ntpd[641]: error resolving pool 0.debian.pool.ntp.org: System error (-11) Aug 02 13:43:16 volumiopi3 ntpd[641]: error resolving pool 1.debian.pool.ntp.org: System error (-11) Aug 02 13:43:16 volumiopi3 nmbd[618]: [2022/08/02 13:43:16.511868, 0] ../source3/nmbd/asyncdns.c:158(start_async_dns) Aug 02 13:43:16 volumiopi3 nmbd[618]: started asyncdns process 651 Aug 02 13:43:16 volumiopi3 nmbd[618]: [2022/08/02 13:43:16.514642, 0] ../lib/util/become_daemon.c:149(daemon_status) Aug 02 13:43:16 volumiopi3 nmbd[618]: daemon_status: STATUS=daemon 'nmbd' : No local IPv4 non-loopback interfaces available, waiting for interface ... Aug 02 13:43:16 volumiopi3 nmbd[618]: [2022/08/02 13:43:16.514861, 0] ../source3/nmbd/nmbd_subnetdb.c:254(create_subnets) Aug 02 13:43:16 volumiopi3 nmbd[618]: NOTE: NetBIOS name resolution is not supported for Internet Protocol Version 6 (IPv6). Aug 02 13:43:17 volumiopi3 wireless.js[477]: Cleaning previous... Aug 02 13:43:17 volumiopi3 ntpd[641]: error resolving pool 2.debian.pool.ntp.org: System error (-11) Aug 02 13:43:17 volumiopi3 sudo[660]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Aug 02 13:43:17 volumiopi3 sudo[660]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:17 volumiopi3 sudo[660]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:17 volumiopi3 sudo[662]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Aug 02 13:43:17 volumiopi3 sudo[662]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:18 volumiopi3 sudo[662]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:18 volumiopi3 mpd[640]: Aug 02 13:43 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg Aug 02 13:43:18 volumiopi3 mpd[640]: Aug 02 13:43 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured Aug 02 13:43:18 volumiopi3 mpd[640]: Aug 02 13:43 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured Aug 02 13:43:18 volumiopi3 systemd[1]: Started Music Player Daemon. Aug 02 13:43:18 volumiopi3 wireless.js[477]: Stopped aP Aug 02 13:43:18 volumiopi3 sudo[671]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Aug 02 13:43:18 volumiopi3 sudo[671]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:18 volumiopi3 sudo[671]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:18 volumiopi3 kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled Aug 02 13:43:18 volumiopi3 sudo[673]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iw reg get Aug 02 13:43:18 volumiopi3 sudo[673]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:18 volumiopi3 sudo[673]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:18 volumiopi3 sudo[680]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 up Aug 02 13:43:18 volumiopi3 sudo[680]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:18 volumiopi3 sudo[680]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:18 volumiopi3 sudo[682]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iw wlan0 scan Aug 02 13:43:18 volumiopi3 sudo[682]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:18 volumiopi3 ntpd[641]: error resolving pool 3.debian.pool.ntp.org: System error (-11) Aug 02 13:43:18 volumiopi3 sh[376]: eth0: leased 192.168.1.242 for 86400 seconds Aug 02 13:43:18 volumiopi3 dhcpcd[424]: eth0: leased 192.168.1.242 for 86400 seconds Aug 02 13:43:18 volumiopi3 sh[376]: eth0: adding route to 192.168.1.0/24 Aug 02 13:43:18 volumiopi3 sh[376]: eth0: adding default route via 192.168.1.1 Aug 02 13:43:18 volumiopi3 dhcpcd[424]: eth0: adding route to 192.168.1.0/24 Aug 02 13:43:18 volumiopi3 dhcpcd[424]: eth0: adding default route via 192.168.1.1 Aug 02 13:43:18 volumiopi3 avahi-daemon[449]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.242. Aug 02 13:43:18 volumiopi3 avahi-daemon[449]: New relevant interface eth0.IPv4 for mDNS. Aug 02 13:43:18 volumiopi3 avahi-daemon[449]: Registering new address record for 192.168.1.242 on eth0.IPv4. Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: Core ver 2.22 Aug 02 13:43:18 volumiopi3 kernel: NET: Registered protocol family 31 Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI device and connection manager initialized Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI socket layer initialized Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: L2CAP socket layer initialized Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: SCO socket layer initialized Aug 02 13:43:18 volumiopi3 btuart[475]: bcm43xx_init Aug 02 13:43:18 volumiopi3 btuart[475]: Flash firmware /lib/firmware/brcm/BCM4345C0.hcd Aug 02 13:43:18 volumiopi3 btuart[475]: Set BDADDR UART: b8:27:eb:ad:73:68 Aug 02 13:43:18 volumiopi3 btuart[475]: Set Controller UART speed to 3000000 bit/s Aug 02 13:43:18 volumiopi3 btuart[475]: Device setup complete Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI UART driver ver 2.3 Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI UART protocol H4 registered Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI UART protocol Three-wire (H5) registered Aug 02 13:43:18 volumiopi3 kernel: Bluetooth: HCI UART protocol Broadcom registered Aug 02 13:43:18 volumiopi3 systemd[1]: Starting Load/Save RF Kill Switch Status... Aug 02 13:43:18 volumiopi3 systemd[1]: Started Configure Bluetooth Modems connected by UART. Aug 02 13:43:18 volumiopi3 sh[376]: forked to background, child pid 717 Aug 02 13:43:18 volumiopi3 dhcpcd[424]: forked to background, child pid 717 Aug 02 13:43:18 volumiopi3 systemd[1]: Started Load/Save RF Kill Switch Status. Aug 02 13:43:18 volumiopi3 systemd[1]: Created slice system-bthelper.slice. Aug 02 13:43:18 volumiopi3 systemd[1]: Starting Raspberry Pi bluetooth helper... Aug 02 13:43:19 volumiopi3 bthelper[718]: Raspberry Pi BDADDR already set Aug 02 13:43:19 volumiopi3 systemd[1]: Started Raspberry Pi bluetooth helper. Aug 02 13:43:19 volumiopi3 systemd[1]: Starting Bluetooth service... Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Bluetooth daemon 5.50 Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Unknown key AutoConnectTimeout for group General in /etc/bluetooth/main.conf Aug 02 13:43:19 volumiopi3 systemd[1]: Started Bluetooth service. Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Starting SDP server Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Excluding (cli) sap Aug 02 13:43:19 volumiopi3 systemd[1]: Reached target Bluetooth. Aug 02 13:43:19 volumiopi3 ifplugd(eth0)[630]: client: ifup: interface eth0 already configured Aug 02 13:43:19 volumiopi3 sh[376]: eth0=eth0 Aug 02 13:43:19 volumiopi3 kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 Aug 02 13:43:19 volumiopi3 kernel: Bluetooth: BNEP filters: protocol multicast Aug 02 13:43:19 volumiopi3 kernel: Bluetooth: BNEP socket layer initialized Aug 02 13:43:19 volumiopi3 dbus-daemon[460]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.5' (uid=0 pid=744 comm="/usr/lib/bluetooth/bluetoothd --noplugin=sap ") Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Bluetooth management interface 1.18 initialized Aug 02 13:43:19 volumiopi3 systemd[1]: Starting Hostname Service... Aug 02 13:43:19 volumiopi3 ifplugd(eth0)[630]: Program executed successfully. Aug 02 13:43:19 volumiopi3 ifplugd[604]: Network Interface Plugging Daemon...start eth0...done. Aug 02 13:43:19 volumiopi3 systemd[1]: Started LSB: Brings up/down network automatically. Aug 02 13:43:19 volumiopi3 bluetoothd[744]: Failed to set privacy: Rejected (0x0b) Aug 02 13:43:19 volumiopi3 dbus-daemon[460]: [system] Successfully activated service 'org.freedesktop.hostname1' Aug 02 13:43:19 volumiopi3 systemd[1]: Started Hostname Service. Aug 02 13:43:19 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:19] [info] asio async_connect error: system:111 (Connection refused) Aug 02 13:43:19 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:19] [info] Error getting remote endpoint: system:107 (Transport endpoint is not connected) Aug 02 13:43:19 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:19] [error] handle_connect error: Underlying Transport Error Aug 02 13:43:20 volumiopi3 ntpd[641]: Listen normally on 3 eth0 192.168.1.242:123 Aug 02 13:43:20 volumiopi3 ntpd[641]: new interface(s) found: waking up resolver Aug 02 13:43:21 volumiopi3 sudo[682]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:21 volumiopi3 sudo[759]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ip addr flush dev wlan0 Aug 02 13:43:21 volumiopi3 sudo[759]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:21 volumiopi3 sudo[759]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:21 volumiopi3 sudo[761]: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 down Aug 02 13:43:21 volumiopi3 sudo[761]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:21 volumiopi3 sudo[761]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:21 volumiopi3 nmbd[618]: [2022/08/02 13:43:21.822068, 0] ../lib/util/become_daemon.c:138(daemon_ready) Aug 02 13:43:21 volumiopi3 systemd[1]: Started Samba NMB Daemon. Aug 02 13:43:21 volumiopi3 nmbd[618]: daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections Aug 02 13:43:21 volumiopi3 systemd[1]: Starting Samba Winbind Daemon... Aug 02 13:43:21 volumiopi3 avahi-daemon[449]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.211.1. Aug 02 13:43:21 volumiopi3 avahi-daemon[449]: New relevant interface wlan0.IPv4 for mDNS. Aug 02 13:43:21 volumiopi3 avahi-daemon[449]: Registering new address record for 192.168.211.1 on wlan0.IPv4. Aug 02 13:43:21 volumiopi3 kernel: brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled Aug 02 13:43:21 volumiopi3 nmbd[618]: [2022/08/02 13:43:21.846938, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) Aug 02 13:43:21 volumiopi3 nmbd[618]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.242 for name WORKGROUP<1d>. Aug 02 13:43:21 volumiopi3 nmbd[618]: This response was from IP 192.168.1.193, reporting an IP address of 192.168.1.193. Aug 02 13:43:21 volumiopi3 systemd[1]: Starting Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator... Aug 02 13:43:21 volumiopi3 systemd[1]: Starting dnsmasq - A lightweight DHCP and caching DNS server... Aug 02 13:43:21 volumiopi3 dnsmasq[770]: dnsmasq: syntax check OK. Aug 02 13:43:21 volumiopi3 hostapd[769]: Configuration file: /etc/hostapd/hostapd.conf Aug 02 13:43:21 volumiopi3 hostapd[769]: wlan0: Could not connect to kernel driver Aug 02 13:43:21 volumiopi3 hostapd[769]: Using interface wlan0 with hwaddr b8:27:eb:52:8c:97 and ssid "Volumio-1BF19" Aug 02 13:43:22 volumiopi3 hostapd[769]: wlan0: interface state UNINITIALIZED->ENABLED Aug 02 13:43:22 volumiopi3 hostapd[769]: wlan0: AP-ENABLED Aug 02 13:43:22 volumiopi3 systemd[1]: Started Advanced IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator. Aug 02 13:43:22 volumiopi3 dnsmasq[777]: started, version 2.80 cachesize 150 Aug 02 13:43:22 volumiopi3 dnsmasq[777]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack ipset auth DNSSEC loop-detect inotify dumpfile Aug 02 13:43:22 volumiopi3 dnsmasq-dhcp[777]: DHCP, IP range 192.168.211.100 -- 192.168.211.200, lease time 1d Aug 02 13:43:22 volumiopi3 dnsmasq[777]: reading /etc/resolv.conf Aug 02 13:43:22 volumiopi3 dnsmasq[777]: using nameserver 192.168.1.1#53 Aug 02 13:43:22 volumiopi3 dnsmasq[777]: using nameserver 208.67.222.222#53 Aug 02 13:43:22 volumiopi3 dnsmasq[777]: using nameserver 208.67.220.220#53 Aug 02 13:43:22 volumiopi3 dnsmasq[777]: read /etc/hosts - 2 addresses Aug 02 13:43:22 volumiopi3 systemd[1]: wireless.service: Succeeded. Aug 02 13:43:22 volumiopi3 systemd[1]: Started Wireless Services. Aug 02 13:43:22 volumiopi3 systemd[1]: Started Volumio Backend Module. Aug 02 13:43:22 volumiopi3 systemd[1]: Started Volumio Streaming Daemon. Aug 02 13:43:22 volumiopi3 systemd[1]: Started dnsmasq - A lightweight DHCP and caching DNS server. Aug 02 13:43:22 volumiopi3 systemd[1]: Reached target Host and Network Name Lookups. Aug 02 13:43:22 volumiopi3 winbindd[765]: [2022/08/02 13:43:22.233856, 0] ../source3/winbindd/winbindd_cache.c:3160(initialize_winbindd_cache) Aug 02 13:43:22 volumiopi3 winbindd[765]: initialize_winbindd_cache: clearing cache and re-creating with version number 2 Aug 02 13:43:22 volumiopi3 winbindd[765]: [2022/08/02 13:43:22.284938, 0] ../lib/util/become_daemon.c:138(daemon_ready) Aug 02 13:43:22 volumiopi3 systemd[1]: Started Samba Winbind Daemon. Aug 02 13:43:22 volumiopi3 winbindd[765]: daemon_ready: STATUS=daemon 'winbindd' finished starting up and ready to serve connections Aug 02 13:43:22 volumiopi3 systemd[1]: Starting Samba SMB Daemon... Aug 02 13:43:22 volumiopi3 volumio-streaming-daemon[783]: ############################ Aug 02 13:43:22 volumiopi3 volumio-streaming-daemon[783]: # Volumio Streaming Daemon # Aug 02 13:43:22 volumiopi3 volumio-streaming-daemon[783]: # Running on port 7777 # Aug 02 13:43:22 volumiopi3 volumio-streaming-daemon[783]: ############################ Aug 02 13:43:22 volumiopi3 volumio-streaming-daemon[783]: Environment: production Aug 02 13:43:23 volumiopi3 smbd[795]: [2022/08/02 13:43:23.050824, 0] ../lib/util/become_daemon.c:138(daemon_ready) Aug 02 13:43:23 volumiopi3 systemd[1]: Started Samba SMB Daemon. Aug 02 13:43:23 volumiopi3 smbd[795]: daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections Aug 02 13:43:23 volumiopi3 systemd[1]: Reached target Multi-User System. Aug 02 13:43:23 volumiopi3 systemd[1]: Reached target Graphical Interface. Aug 02 13:43:23 volumiopi3 systemd[1]: Starting Update UTMP about System Runlevel Changes... Aug 02 13:43:23 volumiopi3 systemd[1]: systemd-update-utmp-runlevel.service: Succeeded. Aug 02 13:43:23 volumiopi3 systemd[1]: Started Update UTMP about System Runlevel Changes. Aug 02 13:43:23 volumiopi3 systemd[1]: Startup finished in 11.474s (kernel) + 20.074s (userspace) = 31.549s. Aug 02 13:43:23 volumiopi3 ntpd[641]: Listen normally on 4 wlan0 192.168.211.1:123 Aug 02 13:43:23 volumiopi3 ntpd[641]: new interface(s) found: waking up resolver Aug 02 13:43:23 volumiopi3 systemd[1]: systemd-rfkill.service: Succeeded. Aug 02 13:43:24 volumiopi3 bthelper[718]: Changing power off succeeded Aug 02 13:43:24 volumiopi3 bthelper[718]: [CHG] Controller B8:27:EB:AD:73:68 Class: 0x0000041c Aug 02 13:43:24 volumiopi3 bthelper[718]: Changing power on succeeded Aug 02 13:43:25 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:25 volumiopi3 volumio[782]: info: ----- Volumio3 ---- Aug 02 13:43:25 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:25 volumiopi3 volumio[782]: info: ----- System startup ---- Aug 02 13:43:25 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:25 volumiopi3 kernel: cam1-reg: disabling Aug 02 13:43:25 volumiopi3 kernel: cam-dummy-reg: disabling Aug 02 13:43:26 volumiopi3 volumio[782]: info: MYVOLUMIO Environment detected Aug 02 13:43:26 volumiopi3 volumio[782]: info: Plugin folders cleanup Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning into folder /volumio/app/plugins/ Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category audio_interface Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category miscellanea Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category music_service Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category plugins.json Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category system_controller Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category user_interface Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning into folder /data/plugins/ Aug 02 13:43:26 volumiopi3 volumio[782]: info: Scanning category music_service Aug 02 13:43:26 volumiopi3 volumio[782]: info: Plugin folders cleanup completed Aug 02 13:43:26 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:26 volumiopi3 volumio[782]: info: ----- Core plugins startup ---- Aug 02 13:43:26 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:26 volumiopi3 volumio[782]: info: Loading plugins from folder /volumio/app/plugins/ Aug 02 13:43:26 volumiopi3 volumio[782]: info: Adding plugin upnp to MyMusic Plugins Aug 02 13:43:26 volumiopi3 volumio[782]: info: Adding plugin airplay_emulation to MyMusic Plugins Aug 02 13:43:26 volumiopi3 volumio[782]: info: Adding plugin upnp_browser to MyMusic Plugins Aug 02 13:43:26 volumiopi3 volumio[782]: info: Loading plugins from folder /data/plugins/ Aug 02 13:43:26 volumiopi3 volumio[782]: info: Loading plugin "system"... Aug 02 13:43:26 volumiopi3 volumio[782]: info: Loading plugin "appearance"... Aug 02 13:43:27 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:27] [connect] Successful connection Aug 02 13:43:27 volumiopi3 volumio[782]: info: Loading plugin "network"... Aug 02 13:43:27 volumiopi3 volumio[782]: info: Refreshing Cached IP Addresses Aug 02 13:43:27 volumiopi3 sudo[827]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Aug 02 13:43:27 volumiopi3 sudo[827]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:27 volumiopi3 sudo[827]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:27 volumiopi3 volumio[782]: info: Loading plugin "services"... Aug 02 13:43:27 volumiopi3 sudo[829]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Aug 02 13:43:27 volumiopi3 sudo[829]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:27 volumiopi3 volumio[782]: info: Loading plugin "alsa_controller"... Aug 02 13:43:27 volumiopi3 sudo[829]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:27 volumiopi3 sudo[832]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwlist wlan0 scan Aug 02 13:43:27 volumiopi3 sudo[832]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:27 volumiopi3 volumio[782]: info: Loading plugin "wizard"... Aug 02 13:43:27 volumiopi3 volumio[782]: info: Loading plugin "volumio_command_line_client"... Aug 02 13:43:28 volumiopi3 volumio[782]: info: Loading plugin "upnp"... Aug 02 13:43:28 volumiopi3 volumio[782]: info: [1659447808012] Starting Upmpd Daemon Aug 02 13:43:28 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Aug 02 13:43:28 volumiopi3 volumio[782]: info: Loading plugin "my_music"... Aug 02 13:43:28 volumiopi3 volumio[782]: info: Loading plugin "mpd"... Aug 02 13:43:28 volumiopi3 volumio[782]: info: Creating MPD Configuration file Aug 02 13:43:28 volumiopi3 volumio[782]: info: Loading plugin "upnp_browser"... Aug 02 13:43:28 volumiopi3 sudo[840]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /etc/mpd.conf Aug 02 13:43:28 volumiopi3 sudo[840]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:28 volumiopi3 sudo[840]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:28 volumiopi3 sudo[842]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart mpd.service Aug 02 13:43:28 volumiopi3 sudo[842]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:28 volumiopi3 systemd[1]: Stopping Music Player Daemon... Aug 02 13:43:28 volumiopi3 systemd[1]: mpd.service: Succeeded. Aug 02 13:43:28 volumiopi3 systemd[1]: Stopped Music Player Daemon. Aug 02 13:43:28 volumiopi3 systemd[1]: Starting Music Player Daemon... Aug 02 13:43:29 volumiopi3 volumio[782]: info: Loading plugin "networkfs"... Aug 02 13:43:29 volumiopi3 volumio[782]: info: Starting Udev Watcher for removable devices Aug 02 13:43:29 volumiopi3 volumio[782]: info: Ignoring mount for partition: boot Aug 02 13:43:29 volumiopi3 volumio[782]: info: Ignoring mount for partition: volumio Aug 02 13:43:29 volumiopi3 volumio[782]: info: Ignoring mount for partition: volumio_data Aug 02 13:43:29 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Aug 02 13:43:29 volumiopi3 volumio[782]: info: Loading plugin "alarm-clock"... Aug 02 13:43:30 volumiopi3 mpd[847]: Aug 02 13:43 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg Aug 02 13:43:30 volumiopi3 mpd[847]: Aug 02 13:43 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured Aug 02 13:43:30 volumiopi3 mpd[847]: Aug 02 13:43 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured Aug 02 13:43:30 volumiopi3 systemd[1]: Started Music Player Daemon. Aug 02 13:43:30 volumiopi3 sudo[842]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "airplay_emulation"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Starting Shairport Sync Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "last_100"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "webradio"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "i2s_dacs"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "volumiodiscovery"... Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** Please fix your application to use the native API of Avahi! Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** For more information see Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** The program 'node' uses the Apple Bonjour compatibility layer of Avahi. Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** Please fix your application to use the native API of Avahi! Aug 02 13:43:30 volumiopi3 volumio[782]: *** WARNING *** For more information see Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** Please fix your application to use the native API of Avahi! Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** For more information see Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** The program 'node' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi. Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** Please fix your application to use the native API of Avahi! Aug 02 13:43:30 volumiopi3 node[782]: *** WARNING *** For more information see Aug 02 13:43:30 volumiopi3 volumio[782]: info: Applying required configuration parameters for plugin volumiodiscovery Aug 02 13:43:30 volumiopi3 volumio[782]: info: Discovery: Started advertising with name: VolumioPi3 Aug 02 13:43:30 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "outputs"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "albumart"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Plugin example_plugin is not enabled Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "inputs"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "updater_comm"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Plugin mpdemulation is not enabled Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "rest_api"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "websocket"... Aug 02 13:43:30 volumiopi3 volumio[782]: info: Loading plugin "spop"... Aug 02 13:43:30 volumiopi3 volumio[782]: Forking 3 albumart workers Aug 02 13:43:31 volumiopi3 volumio[782]: Starting albumart workers Aug 02 13:43:31 volumiopi3 volumio[782]: Starting albumart workers Aug 02 13:43:31 volumiopi3 volumio[782]: Starting albumart workers Aug 02 13:43:32 volumiopi3 sudo[832]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:32 volumiopi3 volumio[782]: info: Loading i18n strings for locale en Aug 02 13:43:32 volumiopi3 volumio[782]: Updating browse sources language Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::initPlayerControls Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Aug 02 13:43:32 volumiopi3 volumio[782]: Express server listening on port 3000 Aug 02 13:43:32 volumiopi3 volumio[782]: [Metrics] WebUI: 8s 478.01ms Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreStateMachine::resetVolumioState Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreStateMachine::getcurrentVolume Aug 02 13:43:32 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioRetrievevolume Aug 02 13:43:32 volumiopi3 volumio[782]: info: Cannot read play queue from file Aug 02 13:43:32 volumiopi3 volumio[782]: info: MPD Permissions set Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 1 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 2 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 3 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 4 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 5 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 6 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 7 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 8 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 9 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 10 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 11 Aug 02 13:43:32 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 12 Aug 02 13:43:32 volumiopi3 volumio[782]: info: MPD running with PID847 Aug 02 13:43:32 volumiopi3 volumio[782]: ,establishing connection Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 13 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 14 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 15 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 16 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 17 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 18 Aug 02 13:43:33 volumiopi3 volumio[782]: error: updateQueue error: null Aug 02 13:43:33 volumiopi3 volumio[782]: error: Failed LSINFO: Error: [50@0] {lsinfo} No such directory Aug 02 13:43:33 volumiopi3 volumio[782]: info: VolumeController:: Volume=100 Mute =false Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::pushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioPushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::updateTrackBlock Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrackBlock Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioRetrievevolume Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::setRepeat null single undefined Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::pushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioPushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::setRandom null Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::pushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioPushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: Setting Device type: Raspberry PI Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 19 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 20 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 21 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 22 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 23 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 24 Aug 02 13:43:33 volumiopi3 volumio[782]: info: Completed loading Core Plugins Aug 02 13:43:33 volumiopi3 volumio[782]: info: Preparing to generate the ALSA configuration file Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 25 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 26 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 27 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 28 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 29 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 30 Aug 02 13:43:33 volumiopi3 volumio[782]: error: updateQueue error: null Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 31 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 32 Aug 02 13:43:33 volumiopi3 volumio[782]: info: VolumeController:: Volume=100 Mute =false Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreStateMachine::pushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioPushState Aug 02 13:43:33 volumiopi3 volumio[782]: info: Asound.conf file unchanged, so no further update is needed Aug 02 13:43:33 volumiopi3 volumio[782]: info: Output device has changed, restarting MPD Aug 02 13:43:33 volumiopi3 volumio[782]: info: Output device has changed, restarting Shairport Sync Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 sudo[925]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /etc/mpd.conf Aug 02 13:43:33 volumiopi3 sudo[925]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:33 volumiopi3 sudo[925]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:33 volumiopi3 sudo[927]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart mpd.service Aug 02 13:43:33 volumiopi3 sudo[927]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:33 volumiopi3 systemd[1]: Stopping Music Player Daemon... Aug 02 13:43:33 volumiopi3 volumio[782]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: ___________ START PLUGINS ___________ Aug 02 13:43:33 volumiopi3 systemd[1]: mpd.service: Succeeded. Aug 02 13:43:33 volumiopi3 systemd[1]: Stopped Music Player Daemon. Aug 02 13:43:33 volumiopi3 systemd[1]: Starting Music Player Daemon... Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: mpd , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Aug 02 13:43:33 volumiopi3 volumio[782]: info: [1659447813453] CoreMusicLibrary::Adding element Media Servers Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:43:33 volumiopi3 volumio[782]: Cannot find translation for sourceMedia Servers Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: Could not detect Primo: Error: Command failed: aplay -l | grep es90x8q2m-dac-dai-0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Aug 02 13:43:33 volumiopi3 volumio[782]: info: [1659447813586] CoreMusicLibrary::Adding element Last_100 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:43:33 volumiopi3 volumio[782]: Cannot find translation for sourceMedia Servers Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Aug 02 13:43:33 volumiopi3 volumio[782]: info: [1659447813592] CoreMusicLibrary::Adding element Webradio Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:43:33 volumiopi3 volumio[782]: Cannot find translation for sourceMedia Servers Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , registerCallback Aug 02 13:43:33 volumiopi3 volumio[782]: [SpotifyConnect] Creating VLS config file Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:33 volumiopi3 volumio[782]: [SpotifyConnect] Starting metadata listener Aug 02 13:43:33 volumiopi3 sudo[943]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/chmod 777 /etc/hosts Aug 02 13:43:33 volumiopi3 sudo[943]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:33 volumiopi3 sudo[943]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:33 volumiopi3 volumio[782]: info: Volumio Calling Home Aug 02 13:43:33 volumiopi3 sudo[946]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start volspotconnect.service Aug 02 13:43:33 volumiopi3 sudo[946]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:33 volumiopi3 systemd[1]: Started Volspotconnect2 Daemon. Aug 02 13:43:33 volumiopi3 sudo[946]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:33 volumiopi3 volumio[782]: info: Discovery: adding b4a52a8c-b7a1-4bd7-87be-847f49b6b396 Aug 02 13:43:33 volumiopi3 volumio[782]: info: mDNS: Found device VolumioPi3 Aug 02 13:43:33 volumiopi3 volumio[951]: vollibrespot v0.2.5 8922128 2022-05-31 (librespot 08d8bcc 2020-10-07) -- Built On 2022-05-31 Aug 02 13:43:33 volumiopi3 volumio[951]: Reading Config from "/tmp/volspotify.toml" Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: info: Discovery: this is already registered, b4a52a8c-b7a1-4bd7-87be-847f49b6b396 Aug 02 13:43:33 volumiopi3 volumio[951]: Malformed config key: missing field `Authentication` Aug 02 13:43:33 volumiopi3 systemd[1]: volspotconnect.service: Main process exited, code=exited, status=1/FAILURE Aug 02 13:43:33 volumiopi3 volumio[782]: info: mDNS: Found device VolumioPi3 Aug 02 13:43:33 volumiopi3 systemd[1]: volspotconnect.service: Failed with result 'exit-code'. Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:33 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 33 Aug 02 13:43:33 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetState Aug 02 13:43:33 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:34 volumiopi3 volumio[782]: [SpotifyConnect] Vollibrespot Daemon service started! Aug 02 13:43:34 volumiopi3 volumio[782]: [Metrics] SpotifyConnect: 0s 356.90ms Aug 02 13:43:34 volumiopi3 volumio[782]: info: Completed starting Core Plugins Aug 02 13:43:34 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:34 volumiopi3 volumio[782]: info: ----- MyVolumio plugins startup ---- Aug 02 13:43:34 volumiopi3 volumio[782]: info: ------------------------------------------- Aug 02 13:43:34 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Fetching plans data.... Aug 02 13:43:34 volumiopi3 volumio[782]: info: MPD Permissions set Aug 02 13:43:34 volumiopi3 volumio[782]: info: Volumio called home Aug 02 13:43:34 volumiopi3 volumio[782]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Total Clients: 34 Aug 02 13:43:34 volumiopi3 volumio[782]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Total Clients: 35 Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:43:34 volumiopi3 volumio[782]: info: Starting Shairport Sync Aug 02 13:43:34 volumiopi3 volumio[782]: info: Starting Shairport Sync Aug 02 13:43:34 volumiopi3 volumio[782]: info: Starting Shairport Sync Aug 02 13:43:34 volumiopi3 sudo[958]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Aug 02 13:43:34 volumiopi3 sudo[958]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:34 volumiopi3 sudo[960]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Aug 02 13:43:34 volumiopi3 sudo[960]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:34 volumiopi3 systemd[1]: Stopping Shairport Sync - AirPlay Audio Receiver... Aug 02 13:43:34 volumiopi3 systemd[1]: shairport-sync.service: Succeeded. Aug 02 13:43:34 volumiopi3 systemd[1]: Stopped Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 sudo[963]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart shairport-sync Aug 02 13:43:34 volumiopi3 sudo[963]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:34 volumiopi3 systemd[1]: Started Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 sudo[958]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:34 volumiopi3 systemd[1]: Stopping Shairport Sync - AirPlay Audio Receiver... Aug 02 13:43:34 volumiopi3 systemd[1]: shairport-sync.service: Main process exited, code=killed, status=15/TERM Aug 02 13:43:34 volumiopi3 systemd[1]: shairport-sync.service: Succeeded. Aug 02 13:43:34 volumiopi3 systemd[1]: Stopped Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 systemd[1]: Started Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 sudo[960]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:34 volumiopi3 systemd[1]: Stopping Shairport Sync - AirPlay Audio Receiver... Aug 02 13:43:34 volumiopi3 systemd[1]: shairport-sync.service: Main process exited, code=killed, status=15/TERM Aug 02 13:43:34 volumiopi3 systemd[1]: shairport-sync.service: Succeeded. Aug 02 13:43:34 volumiopi3 systemd[1]: Stopped Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 systemd[1]: Started Shairport Sync - AirPlay Audio Receiver. Aug 02 13:43:34 volumiopi3 sudo[963]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:34 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 192.168.1.242 from 192.168.1.140 UA: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36 Total Clients: 36 Aug 02 13:43:34 volumiopi3 volumio[782]: info: Shairport-Sync Started Aug 02 13:43:34 volumiopi3 volumio[782]: Error adding Membership: Error: addMembership EINVAL Aug 02 13:43:34 volumiopi3 volumio[782]: info: Shairport-Sync Started Aug 02 13:43:34 volumiopi3 volumio[782]: info: Shairport-Sync Started Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreStateMachine::getQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CorePlayQueue::getQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetState Aug 02 13:43:34 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetState Aug 02 13:43:34 volumiopi3 volumio[782]: info: CorePlayQueue::getTrack 0 Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: multiroom , getMultiroom Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetVisibleSources Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:43:34 volumiopi3 volumio[782]: info: Listing playlists Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioGetQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreStateMachine::getQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CorePlayQueue::getQueue Aug 02 13:43:34 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getHwuuid Aug 02 13:43:34 volumiopi3 mpd[941]: Aug 02 13:43 : exception: Decoder plugin 'wildmidi' is unavailable: configuration file does not exist: /etc/timidity/timidity.cfg Aug 02 13:43:34 volumiopi3 mpd[941]: Aug 02 13:43 : exception: Input plugin 'tidal' is unavailable: No Tidal application token configured Aug 02 13:43:34 volumiopi3 mpd[941]: Aug 02 13:43 : exception: Input plugin 'qobuz' is unavailable: No Qobuz app_id configured Aug 02 13:43:34 volumiopi3 systemd[1]: Started Music Player Daemon. Aug 02 13:43:34 volumiopi3 sudo[927]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:34 volumiopi3 volumio[782]: error: updateQueue error: null Aug 02 13:43:36 volumiopi3 systemd[1]: volspotconnect.service: Service RestartSec=2s expired, scheduling restart. Aug 02 13:43:36 volumiopi3 systemd[1]: volspotconnect.service: Scheduled restart job, restart counter is at 1. Aug 02 13:43:36 volumiopi3 systemd[1]: Stopped Volspotconnect2 Daemon. Aug 02 13:43:36 volumiopi3 systemd[1]: Started Volspotconnect2 Daemon. Aug 02 13:43:36 volumiopi3 volumio[973]: vollibrespot v0.2.5 8922128 2022-05-31 (librespot 08d8bcc 2020-10-07) -- Built On 2022-05-31 Aug 02 13:43:36 volumiopi3 volumio[973]: Reading Config from "/tmp/volspotify.toml" Aug 02 13:43:36 volumiopi3 volumio[973]: [Vollibrespot] : Using Alsa backend with device: volumio Aug 02 13:43:36 volumiopi3 volumio[973]: [Vollibrespot] : Failed to register IPv6 receiver: Os { code: 19, kind: Uncategorized, message: "No such device" } Aug 02 13:43:38 volumiopi3 sudo[976]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig eth0 Aug 02 13:43:38 volumiopi3 sudo[976]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:38 volumiopi3 volumio[782]: info: Checking Spotify Web API Aug 02 13:43:38 volumiopi3 sudo[976]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:38 volumiopi3 sudo[978]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/ifconfig wlan0 Aug 02 13:43:38 volumiopi3 sudo[978]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:38 volumiopi3 sudo[978]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:38 volumiopi3 sudo[982]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl start upmpdcli.service Aug 02 13:43:38 volumiopi3 sudo[982]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:38 volumiopi3 systemd[1]: Started UPnP Renderer front-end to MPD. Aug 02 13:43:38 volumiopi3 sudo[982]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:38 volumiopi3 volumio[782]: info: Upmpdcli Daemon Started Aug 02 13:43:38 volumiopi3 volumio[984]: Generating RSA private key, 4096 bit long modulus (2 primes) Aug 02 13:43:39 volumiopi3 systemd[1]: systemd-fsckd.service: Succeeded. Aug 02 13:43:42 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:42] [connect] Successful connection Aug 02 13:43:42 volumiopi3 volumio-remote-updater[456]: [2022-08-02 13:43:42] [connect] WebSocket Connection 127.0.0.1:3000 v-2 "WebSocket++/0.8.2" /socket.io/?EIO=4&transport=websocket&t=1659447822 101 Aug 02 13:43:42 volumiopi3 volumio[782]: verbose: New Socket.io Connection to 127.0.0.1:3000 from 127.0.0.1 UA: WebSocket++/0.8.2 Total Clients: 37 Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin bluetooth to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin multiroom to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin metavolumio to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin manifestui to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin cd_controller to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin smart_inputs to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin hi_res_audio to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidal to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin qobuz to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidalconnect to plan premium Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin bluetooth to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin multiroom to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin metavolumio to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin manifestui to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin cd_controller to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin smart_inputs to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin hi_res_audio to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidal to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin qobuz to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidalconnect to plan superstar Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin bluetooth to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin manifestui to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin cd_controller to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidal to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin qobuz to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Adding plugin tidalconnect to plan virtuoso Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin bluetooth to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin multiroom to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin metavolumio to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin cd_controller to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin smart_inputs to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: Adding plugin tidalconnect to MyMusic Plugins Aug 02 13:43:42 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Loading plugin "my_volumio"... Aug 02 13:43:43 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] MyVolumio plugin successfully loaded Aug 02 13:43:43 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Starting plugin system_controller.my_volumio Aug 02 13:43:43 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:43 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:43 volumiopi3 volumio[782]: info: Starting MyVolumio Remote Streaming Endpoints Aug 02 13:43:43 volumiopi3 volumio[782]: info: MyVolumio login type: Token Aug 02 13:43:43 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] MyVolumio plugin successfully started Aug 02 13:43:43 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Loading plugin "streaming_services"... Aug 02 13:43:44 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Streaming Services plugin successfully loaded Aug 02 13:43:44 volumiopi3 volumio[782]: info: [MyVolumio PluginManager] Starting plugin music_service.streaming_services Aug 02 13:43:44 volumiopi3 volumio[782]: info: Streaming services startup Aug 02 13:43:44 volumiopi3 volumio[782]: info: Starting Streaming Daemon Aug 02 13:43:44 volumiopi3 sudo[1001]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volumio-streaming-daemon.service Aug 02 13:43:44 volumiopi3 sudo[1001]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:44 volumiopi3 systemd[1]: Stopping Volumio Streaming Daemon... Aug 02 13:43:44 volumiopi3 systemd[1]: volumio-streaming-daemon.service: Main process exited, code=killed, status=15/TERM Aug 02 13:43:44 volumiopi3 systemd[1]: volumio-streaming-daemon.service: Succeeded. Aug 02 13:43:44 volumiopi3 systemd[1]: Stopped Volumio Streaming Daemon. Aug 02 13:43:44 volumiopi3 systemd[1]: Started Volumio Streaming Daemon. Aug 02 13:43:44 volumiopi3 sudo[1001]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:44 volumiopi3 volumio-streaming-daemon[1007]: ############################ Aug 02 13:43:44 volumiopi3 volumio-streaming-daemon[1007]: # Volumio Streaming Daemon # Aug 02 13:43:44 volumiopi3 volumio-streaming-daemon[1007]: # Running on port 7777 # Aug 02 13:43:44 volumiopi3 volumio-streaming-daemon[1007]: ############################ Aug 02 13:43:44 volumiopi3 volumio-streaming-daemon[1007]: Environment: production Aug 02 13:43:44 volumiopi3 volumio[984]: .....................................................++++ Aug 02 13:43:44 volumiopi3 volumio[782]: info: MYVOLUMIO SUCCESSFULLY LOGGED IN Aug 02 13:43:44 volumiopi3 volumio[782]: info: MYVOLUMIO: Adding device Aug 02 13:43:44 volumiopi3 volumio[782]: info: MYVOLUMIO: Evaluating Server Aug 02 13:43:45 volumiopi3 volumio[782]: info: MyVolumio status changed Aug 02 13:43:45 volumiopi3 volumio[782]: info: Streaming services startup Aug 02 13:43:45 volumiopi3 volumio[782]: info: Re-Starting Streaming Daemon Aug 02 13:43:45 volumiopi3 volumio[782]: info: Removing browser output: myVolumio user plan is not superstar Aug 02 13:43:45 volumiopi3 volumio[782]: info: Removing audio output: Aug 02 13:43:45 volumiopi3 volumio[782]: info: Stoppping Tunnel 1 Aug 02 13:43:45 volumiopi3 sudo[1029]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl stop sshtunnel.service Aug 02 13:43:45 volumiopi3 sudo[1029]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:43:45 volumiopi3 volumio-streaming-daemon[1007]: Restarting daemon Aug 02 13:43:45 volumiopi3 volumio-streaming-daemon[1007]: Environment: production Aug 02 13:43:45 volumiopi3 sudo[1029]: pam_unix(sudo:session): session closed for user root Aug 02 13:43:45 volumiopi3 volumio[782]: info: Remote SSH Stopped Aug 02 13:43:45 volumiopi3 volumio[782]: info: Setting Geolocation for MyVolumio to eu4 Aug 02 13:43:45 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:45 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:45 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:46 volumiopi3 volumio[782]: info: Successfully Added MyVolumio device Aug 02 13:43:46 volumiopi3 volumio-streaming-daemon[1007]: Environment: production Aug 02 13:43:46 volumiopi3 volumio[782]: info: Fetching Streaming Services browse cache Aug 02 13:43:46 volumiopi3 volumio-streaming-daemon[1007]: Environment: production Aug 02 13:43:46 volumiopi3 volumio[782]: info: Fetching Streaming Services browse cache Aug 02 13:43:47 volumiopi3 volumio[782]: info: Updating MyVolumio device info Aug 02 13:43:47 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:47 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:47 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:43:47 volumiopi3 volumio[984]: ....................++++ Aug 02 13:43:47 volumiopi3 volumio[984]: e is 65537 (0x010001) Aug 02 13:43:47 volumiopi3 volumio[984]: writing RSA key Aug 02 13:43:48 volumiopi3 volumio[782]: info: Successfully Updated MyVolumio device Aug 02 13:43:49 volumiopi3 systemd[1]: systemd-hostnamed.service: Succeeded. Aug 02 13:44:03 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getSystemVersion Aug 02 13:44:03 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:44:04 volumiopi3 volumio[782]: error: MyVolumio Plugin failed to authenticate in a timely fashion Aug 02 13:44:04 volumiopi3 volumio[782]: info: Completed starting MyVolumio Plugin Aug 02 13:44:04 volumiopi3 volumio[782]: info: BOOT COMPLETED Aug 02 13:44:04 volumiopi3 volumio[782]: [Metrics] CommandRouter: 39s 134.27ms Aug 02 13:44:04 volumiopi3 volumio[782]: info: CoreCommandRouter::volumiosetStartupVolume Aug 02 13:44:04 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:04 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , getConfigParam Aug 02 13:44:04 volumiopi3 volumio[782]: info: CoreCommandRouter::Close All Modals sent Aug 02 13:44:04 volumiopi3 volumio[782]: info: CoreCommandRouter::Close All Modals sent Aug 02 13:44:04 volumiopi3 kernel: pcm512x 1-004d: No SCLK, using BCLK: -2 Aug 02 13:44:05 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , checkAudioDeviceAvailable Aug 02 13:44:05 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: i2s_dacs , getI2sStatus Aug 02 13:44:05 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , versionChangeDetect Aug 02 13:44:22 volumiopi3 ntpd[641]: Soliciting pool server 176.9.157.155 Aug 02 13:44:22 volumiopi3 ntpd[641]: Soliciting pool server 162.159.200.123 Aug 02 13:44:23 volumiopi3 ntpd[641]: Soliciting pool server 5.145.135.89 Aug 02 13:44:23 volumiopi3 ntpd[641]: Soliciting pool server 185.157.229.254 Aug 02 13:44:23 volumiopi3 ntpd[641]: Soliciting pool server 131.188.3.223 Aug 02 13:44:23 volumiopi3 ntpd[641]: Soliciting pool server 212.45.144.88 Aug 02 13:44:24 volumiopi3 ntpd[641]: Soliciting pool server 176.9.42.91 Aug 02 13:44:24 volumiopi3 ntpd[641]: Soliciting pool server 31.209.85.242 Aug 02 13:44:24 volumiopi3 ntpd[641]: Soliciting pool server 212.237.31.130 Aug 02 13:44:24 volumiopi3 ntpd[641]: Soliciting pool server 37.247.53.178 Aug 02 13:44:25 volumiopi3 ntpd[641]: Soliciting pool server 129.70.132.36 Aug 02 13:44:25 volumiopi3 ntpd[641]: Soliciting pool server 37.114.40.20 Aug 02 13:44:25 volumiopi3 ntpd[641]: Soliciting pool server 135.125.165.132 Aug 02 13:44:25 volumiopi3 ntpd[641]: Soliciting pool server 80.88.90.14 Aug 02 13:44:26 volumiopi3 ntpd[641]: Soliciting pool server 78.46.162.102 Aug 02 13:44:26 volumiopi3 ntpd[641]: Soliciting pool server 2606:4700:f1::1 Aug 02 13:44:26 volumiopi3 ntpd[641]: Soliciting pool server 188.213.165.209 Aug 02 13:44:26 volumiopi3 volumio[782]: info: CALLMETHOD: music_service spop saveVolspotconnectAccount [object Object] Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , saveVolspotconnectAccount Aug 02 13:44:26 volumiopi3 volumio[782]: [SpotifyConnect] Creating VLS config file Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:26 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: alsa_controller , getConfigParam Aug 02 13:44:26 volumiopi3 volumio[782]: [SpotifyConnect] Restarting Vollibrespot Daemon Aug 02 13:44:26 volumiopi3 sudo[1057]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart volspotconnect.service Aug 02 13:44:26 volumiopi3 sudo[1057]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:44:26 volumiopi3 systemd[1]: Stopping Volspotconnect2 Daemon... Aug 02 13:44:26 volumiopi3 systemd[1]: volspotconnect.service: Main process exited, code=killed, status=15/TERM Aug 02 13:44:26 volumiopi3 systemd[1]: volspotconnect.service: Succeeded. Aug 02 13:44:26 volumiopi3 systemd[1]: Stopped Volspotconnect2 Daemon. Aug 02 13:44:26 volumiopi3 systemd[1]: Started Volspotconnect2 Daemon. Aug 02 13:44:26 volumiopi3 sudo[1057]: pam_unix(sudo:session): session closed for user root Aug 02 13:44:26 volumiopi3 volumio[782]: [SpotifyConnect] Vollibrespot Daemon service restarted! Aug 02 13:44:26 volumiopi3 volumio[1059]: vollibrespot v0.2.5 8922128 2022-05-31 (librespot 08d8bcc 2020-10-07) -- Built On 2022-05-31 Aug 02 13:44:26 volumiopi3 volumio[1059]: Reading Config from "/tmp/volspotify.toml" Aug 02 13:44:26 volumiopi3 volumio[1059]: [Vollibrespot] : Using Alsa backend with device: volumio Aug 02 13:44:26 volumiopi3 volumio[1059]: [Vollibrespot] : Connecting to AP "ap-gew4.spotify.com:443" Aug 02 13:44:27 volumiopi3 volumio[1059]: [Vollibrespot] : Authenticated as "bjj3q6xvvuk17zpt9ohreqc3j" ! Aug 02 13:44:27 volumiopi3 volumio[1059]: [Vollibrespot] : Using alsa sink Aug 02 13:44:27 volumiopi3 volumio[1059]: [Vollibrespot] : Metadata pipe established Aug 02 13:44:27 volumiopi3 volumio[1059]: [Vollibrespot] : Country: "IT" Aug 02 13:44:27 volumiopi3 volumio[1059]: [Vollibrespot] : Event: Volume { volume_to_mixer: 32768 } Aug 02 13:44:27 volumiopi3 volumio[782]: [SpotifyConnect] Volume Spotify: 50.000762951094835 Volumio: 50 Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) Aug 02 13:44:28 volumiopi3 volumio[782]: (Use `node --trace-warnings ...` to show where the warning was created) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 7) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 8) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 10) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 11) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 13) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 15) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 16) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 17) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 18) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 19) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 20) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 21) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 23) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 24) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 25) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 26) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 27) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 28) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 29) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 31) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 32) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 33) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 34) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 35) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 36) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 37) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 38) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 39) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 40) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 41) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 42) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 43) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 44) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 45) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 46) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 47) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 48) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 49) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 50) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 51) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 53) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 54) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 55) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 56) Aug 02 13:44:28 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 57) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 58) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 59) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 60) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 61) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 62) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 63) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 64) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 65) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 66) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 67) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 68) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 69) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 70) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 71) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 72) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 73) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 74) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 75) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 76) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 77) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 78) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 79) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 80) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 81) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 82) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 83) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 84) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 85) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 86) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 87) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 88) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 89) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 90) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 91) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 92) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 93) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 94) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 95) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 96) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 97) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 98) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 99) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 100) Aug 02 13:44:29 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 101) Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.750f96d9 does not match aorg 0000000000.00000000 from server@135.125.165.132 xmt 0xe693a8d1.5d8432ea Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.751cb670 does not match aorg 0000000000.00000000 from server@131.188.3.223 xmt 0xe693a8d1.5dde1522 Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.75064b17 does not match aorg 0000000000.00000000 from server@188.213.165.209 xmt 0xe693a8d1.5ce0980b Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.7518c713 does not match aorg 0000000000.00000000 from server@212.237.31.130 xmt 0xe693a8d1.5cc3fb10 Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.750dfef8 does not match aorg 0000000000.00000000 from server@129.70.132.36 xmt 0xe693a8d1.5e993c44 Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.75168828 does not match aorg 0000000000.00000000 from server@31.209.85.242 xmt 0xe693a8d1.5e618375 Aug 02 13:44:49 volumiopi3 ntpd[641]: receive: Unexpected origin timestamp 0xe693a8bd.75143fca does not match aorg 0000000000.00000000 from server@176.9.42.91 xmt 0xe693a8d1.5dd23d68 Aug 02 13:44:52 volumiopi3 volumio[782]: info: Checking Spotify Web API Aug 02 13:44:53 volumiopi3 volumio[1059]: [Vollibrespot] : ReqToken Aug 02 13:44:53 volumiopi3 volumio[782]: info: New Spotify Access Token Received Aug 02 13:44:53 volumiopi3 volumio[782]: info: Initializing Spotify Web API Aug 02 13:44:53 volumiopi3 volumio[782]: info: Initliazing Spotify Browsing Facility Aug 02 13:44:53 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Aug 02 13:44:53 volumiopi3 volumio[782]: info: [1659447893113] CoreMusicLibrary::Adding element Spotify Aug 02 13:44:53 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:44:53 volumiopi3 volumio[782]: Cannot find translation for sourceMedia Servers Aug 02 13:44:53 volumiopi3 volumio[782]: Cannot find translation for sourceSpotify Aug 02 13:44:53 volumiopi3 volumio[782]: error: Failed to retrieve spotify devices lists: WebapiError: Bad OAuth request Aug 02 13:44:53 volumiopi3 volumio[782]: (node:782) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 104) Aug 02 13:44:53 volumiopi3 volumio[1059]: [Vollibrespot] : ReqToken Aug 02 13:44:53 volumiopi3 volumio[782]: info: New Spotify Access Token Received Aug 02 13:44:53 volumiopi3 volumio[782]: info: Initializing Spotify Web API Aug 02 13:44:53 volumiopi3 volumio[782]: info: Initliazing Spotify Browsing Facility Aug 02 13:44:53 volumiopi3 volumio[782]: info: CoreCommandRouter::volumioAddToBrowseSources[object Object] Aug 02 13:44:53 volumiopi3 volumio[782]: info: [1659447893650] CoreMusicLibrary::Adding element Spotify Aug 02 13:44:53 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_music , getDisabledSources Aug 02 13:44:53 volumiopi3 volumio[782]: Cannot find translation for sourceMedia Servers Aug 02 13:44:53 volumiopi3 volumio[782]: Cannot find translation for sourceSpotify Aug 02 13:45:02 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioStatus Aug 02 13:45:02 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: my_volumio , getMyVolumioToken Aug 02 13:45:04 volumiopi3 volumio[782]: info: CoreCommandRouter::getUIConfigOnPlugin Aug 02 13:45:11 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:11 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:11 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: Bad OAuth request Aug 02 13:45:11 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: Bad OAuth request Aug 02 13:45:11 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: API rate limit exceeded Aug 02 13:45:13 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:13 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:13 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: Bad OAuth request Aug 02 13:45:13 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: Bad OAuth request Aug 02 13:45:13 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: Bad OAuth request Aug 02 13:45:14 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:14 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:14 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: Bad OAuth request Aug 02 13:45:17 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:17 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:17 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: API rate limit exceeded Aug 02 13:45:17 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: API rate limit exceeded Aug 02 13:45:32 volumiopi3 volumio[782]: info: CALLMETHOD: system_controller system enableLiveLog true Aug 02 13:45:32 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , enableLiveLog Aug 02 13:45:32 volumiopi3 volumio[782]: info: Launching a new LiveLog session Aug 02 13:45:49 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:49 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:49 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: Bad OAuth request Aug 02 13:45:49 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: Bad OAuth request Aug 02 13:45:49 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: API rate limit exceeded Aug 02 13:45:58 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:45:58 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:45:58 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: Bad OAuth request Aug 02 13:45:58 volumiopi3 volumio[782]: error: An error occurred while listing Spotify categories WebapiError: Bad OAuth request Aug 02 13:48:24 volumiopi3 nmbd[618]: [2022/08/02 13:48:24.034497, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response) Aug 02 13:48:24 volumiopi3 nmbd[618]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.242 for name WORKGROUP<1d>. Aug 02 13:48:24 volumiopi3 nmbd[618]: This response was from IP 192.168.1.193, reporting an IP address of 192.168.1.193. Aug 02 13:49:37 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:49:37 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:49:37 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: API rate limit exceeded Aug 02 13:49:37 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: API rate limit exceeded Aug 02 13:49:45 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: spop , handleBrowseUri Aug 02 13:49:45 volumiopi3 volumio[782]: info: In handleBrowseUri, curUri=spotify Aug 02 13:49:45 volumiopi3 volumio[782]: error: An error occurred while listing Spotify featured playlists WebapiError: Bad OAuth request Aug 02 13:49:45 volumiopi3 volumio[782]: error: An error occurred while listing Spotify new albums WebapiError: Bad OAuth request Aug 02 13:50:27 volumiopi3 ntpd[641]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized Aug 02 13:52:38 volumiopi3 volumio[782]: info: CALLMETHOD: system_controller system sendBugReport [object Object] Aug 02 13:52:38 volumiopi3 volumio[782]: info: CoreCommandRouter::executeOnPlugin: system , sendBugReport Aug 02 13:52:39 volumiopi3 sudo[1107]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/sbin/iwconfig Aug 02 13:52:39 volumiopi3 sudo[1107]: pam_unix(sudo:session): session opened for user root by (uid=0) Aug 02 13:52:39 volumiopi3 sudo[1107]: pam_unix(sudo:session): session closed for user root Aug 02 13:52:44 volumiopi3 sudo[1150]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl -p 7 Aug 02 13:52:44 volumiopi3 sudo[1150]: pam_unix(sudo:session): session opened for user root by (uid=0)