-- Logs begin at Wed 2025-02-05 04:35:03 CET, end at Sat 2025-03-15 19:32:40 CET. -- Mar 15 19:31:01 volumio dnsmasq-dhcp[854]: no address range available for DHCP request via wlan0 Mar 15 19:31:05 volumio ntpd[773]: error resolving pool 3.debian.pool.ntp.org: System error (-11) Mar 15 19:31:07 volumio go-librespot[4169]: time="2025-03-15T19:31:07+01:00" level=fatal msg="failed running with username and spotify token" error="failed getting endpoints from resolver: failed fetching apresolve URL: Get \"https://apresolve.spotify.com/?type=accesspoint&type=dealer&type=spclient\": dial tcp: lookup apresolve.spotify.com: device or resource busy" Mar 15 19:31:07 volumio systemd[1]: go-librespot-daemon.service: Main process exited, code=exited, status=1/FAILURE Mar 15 19:31:07 volumio systemd[1]: go-librespot-daemon.service: Failed with result 'exit-code'. Mar 15 19:31:07 volumio volumio[863]: (node:863) UnhandledPromiseRejectionWarning: Error: socket hang up Mar 15 19:31:07 volumio volumio[863]: at connResetException (internal/errors.js:607:14) Mar 15 19:31:07 volumio volumio[863]: at Socket.socketOnEnd (_http_client.js:493:23) Mar 15 19:31:07 volumio volumio[863]: at Socket.emit (events.js:327:22) Mar 15 19:31:07 volumio volumio[863]: at endReadableNT (internal/streams/readable.js:1327:12) Mar 15 19:31:07 volumio volumio[863]: at processTicksAndRejections (internal/process/task_queues.js:80:21) Mar 15 19:31:07 volumio volumio[863]: (node:863) 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: 2200) Mar 15 19:31:07 volumio volumio[863]: info: Connection to go-librespot Websocket closed Mar 15 19:31:10 volumio volumio[863]: info: Initializing connection to go-librespot Websocket Mar 15 19:31:10 volumio volumio[863]: info: Error connecting to go-librespot Websocket: Error: connect ECONNREFUSED 127.0.0.1:9879 Mar 15 19:31:11 volumio systemd[1]: go-librespot-daemon.service: Service RestartSec=3s expired, scheduling restart. Mar 15 19:31:11 volumio systemd[1]: go-librespot-daemon.service: Scheduled restart job, restart counter is at 1904. Mar 15 19:31:11 volumio systemd[1]: Stopped go-librespot Daemon. Mar 15 19:31:11 volumio systemd[1]: Started go-librespot Daemon. Mar 15 19:31:11 volumio go-librespot[4179]: Librespot-go daemon starting... Mar 15 19:31:11 volumio go-librespot[4179]: time="2025-03-15T19:31:11+01:00" level=info msg="generated new device id: 4f265f3077144b152fc981aea9a5299c94968c03" Mar 15 19:31:11 volumio go-librespot[4179]: time="2025-03-15T19:31:11+01:00" level=debug msg="stored credentials found for wkvjsqebf9trus1u6o62xnjn7" Mar 15 19:31:13 volumio volumio[863]: info: Initializing connection to go-librespot Websocket Mar 15 19:31:13 volumio go-librespot[4179]: time="2025-03-15T19:31:13+01:00" level=debug msg="new websocket client" Mar 15 19:31:13 volumio volumio[863]: info: Connection to go-librespot Websocket established Mar 15 19:31:16 volumio volumio[863]: info: Getting Spotify volume Mar 15 19:31:16 volumio volumio[863]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Engine version: 3 Transport: polling Total Clients: 5 Mar 15 19:31:17 volumio volumio[863]: info: CoreCommandRouter::volumioGetState Mar 15 19:31:17 volumio volumio[863]: SPOTIFY: RECEIVED VOLUMIO VOLUME 38 Mar 15 19:31:22 volumio dnsmasq-dhcp[854]: no address range available for DHCP request via wlan0 Mar 15 19:31:33 volumio ntpd[773]: error resolving pool 2.debian.pool.ntp.org: System error (-11) Mar 15 19:31:39 volumio go-librespot[4179]: time="2025-03-15T19:31:39+01:00" level=fatal msg="failed running with username and spotify token" error="failed getting endpoints from resolver: failed fetching apresolve URL: Get \"https://apresolve.spotify.com/?type=accesspoint&type=dealer&type=spclient\": dial tcp: lookup apresolve.spotify.com: device or resource busy" Mar 15 19:31:39 volumio systemd[1]: go-librespot-daemon.service: Main process exited, code=exited, status=1/FAILURE Mar 15 19:31:39 volumio systemd[1]: go-librespot-daemon.service: Failed with result 'exit-code'. Mar 15 19:31:39 volumio volumio[863]: (node:863) UnhandledPromiseRejectionWarning: Error: socket hang up Mar 15 19:31:39 volumio volumio[863]: at connResetException (internal/errors.js:607:14) Mar 15 19:31:39 volumio volumio[863]: at Socket.socketOnEnd (_http_client.js:493:23) Mar 15 19:31:39 volumio volumio[863]: at Socket.emit (events.js:327:22) Mar 15 19:31:39 volumio volumio[863]: at endReadableNT (internal/streams/readable.js:1327:12) Mar 15 19:31:39 volumio volumio[863]: at processTicksAndRejections (internal/process/task_queues.js:80:21) Mar 15 19:31:39 volumio volumio[863]: (node:863) 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: 2201) Mar 15 19:31:39 volumio volumio[863]: info: Connection to go-librespot Websocket closed Mar 15 19:31:42 volumio volumio[863]: info: Initializing connection to go-librespot Websocket Mar 15 19:31:42 volumio volumio[863]: info: Error connecting to go-librespot Websocket: Error: connect ECONNREFUSED 127.0.0.1:9879 Mar 15 19:31:42 volumio systemd[1]: go-librespot-daemon.service: Service RestartSec=3s expired, scheduling restart. Mar 15 19:31:42 volumio systemd[1]: go-librespot-daemon.service: Scheduled restart job, restart counter is at 1905. Mar 15 19:31:42 volumio systemd[1]: Stopped go-librespot Daemon. Mar 15 19:31:42 volumio systemd[1]: Started go-librespot Daemon. Mar 15 19:31:42 volumio go-librespot[4237]: Librespot-go daemon starting... Mar 15 19:31:42 volumio go-librespot[4237]: time="2025-03-15T19:31:42+01:00" level=info msg="generated new device id: d317376f920bd2315f472dd9ffb343077f0149fc" Mar 15 19:31:42 volumio go-librespot[4237]: time="2025-03-15T19:31:42+01:00" level=debug msg="stored credentials found for wkvjsqebf9trus1u6o62xnjn7" Mar 15 19:31:45 volumio volumio[863]: info: Initializing connection to go-librespot Websocket Mar 15 19:31:45 volumio go-librespot[4237]: time="2025-03-15T19:31:45+01:00" level=debug msg="new websocket client" Mar 15 19:31:45 volumio volumio[863]: info: Connection to go-librespot Websocket established Mar 15 19:31:48 volumio volumio[863]: info: Getting Spotify volume Mar 15 19:31:48 volumio volumio[863]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Engine version: 3 Transport: polling Total Clients: 5 Mar 15 19:31:48 volumio volumio[863]: info: CoreCommandRouter::volumioGetState Mar 15 19:31:48 volumio volumio[863]: SPOTIFY: RECEIVED VOLUMIO VOLUME 38 Mar 15 19:32:01 volumio ntpd[773]: error resolving pool 1.debian.pool.ntp.org: System error (-11) Mar 15 19:32:10 volumio go-librespot[4237]: time="2025-03-15T19:32:10+01:00" level=fatal msg="failed running with username and spotify token" error="failed getting endpoints from resolver: failed fetching apresolve URL: Get \"https://apresolve.spotify.com/?type=accesspoint&type=dealer&type=spclient\": dial tcp: lookup apresolve.spotify.com: device or resource busy" Mar 15 19:32:10 volumio systemd[1]: go-librespot-daemon.service: Main process exited, code=exited, status=1/FAILURE Mar 15 19:32:10 volumio systemd[1]: go-librespot-daemon.service: Failed with result 'exit-code'. Mar 15 19:32:10 volumio volumio[863]: (node:863) UnhandledPromiseRejectionWarning: Error: socket hang up Mar 15 19:32:10 volumio volumio[863]: at connResetException (internal/errors.js:607:14) Mar 15 19:32:10 volumio volumio[863]: at Socket.socketOnEnd (_http_client.js:493:23) Mar 15 19:32:10 volumio volumio[863]: at Socket.emit (events.js:327:22) Mar 15 19:32:10 volumio volumio[863]: at endReadableNT (internal/streams/readable.js:1327:12) Mar 15 19:32:10 volumio volumio[863]: at processTicksAndRejections (internal/process/task_queues.js:80:21) Mar 15 19:32:10 volumio volumio[863]: (node:863) 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: 2202) Mar 15 19:32:10 volumio volumio[863]: info: Connection to go-librespot Websocket closed Mar 15 19:32:13 volumio volumio[863]: info: Initializing connection to go-librespot Websocket Mar 15 19:32:13 volumio systemd[1]: go-librespot-daemon.service: Service RestartSec=3s expired, scheduling restart. Mar 15 19:32:13 volumio systemd[1]: go-librespot-daemon.service: Scheduled restart job, restart counter is at 1906. Mar 15 19:32:13 volumio systemd[1]: Stopped go-librespot Daemon. Mar 15 19:32:13 volumio systemd[1]: Started go-librespot Daemon. Mar 15 19:32:13 volumio go-librespot[4250]: Librespot-go daemon starting... Mar 15 19:32:13 volumio go-librespot[4250]: time="2025-03-15T19:32:13+01:00" level=info msg="generated new device id: ca886b16d697c2c615dd953081a2a405dcdefc0a" Mar 15 19:32:13 volumio go-librespot[4250]: time="2025-03-15T19:32:13+01:00" level=debug msg="stored credentials found for wkvjsqebf9trus1u6o62xnjn7" Mar 15 19:32:29 volumio ntpd[773]: error resolving pool 0.debian.pool.ntp.org: System error (-11) Mar 15 19:32:34 volumio go-librespot[4250]: time="2025-03-15T19:32:34+01:00" level=debug msg="new websocket client" Mar 15 19:32:34 volumio volumio[863]: info: Connection to go-librespot Websocket established Mar 15 19:32:37 volumio volumio[863]: info: Getting Spotify volume Mar 15 19:32:39 volumio volumio[863]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Engine version: 3 Transport: polling Total Clients: 4 Mar 15 19:32:39 volumio volumio[863]: info: CoreCommandRouter::volumioGetState Mar 15 19:32:39 volumio volumio[863]: SPOTIFY: RECEIVED VOLUMIO VOLUME 38 Mar 15 19:32:40 volumio volumio[863]: |||||||||||||||||||||||| WARNING: FATAL ERROR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Mar 15 19:32:40 volumio volumio[863]: [t [Error]: A network error (such as timeout, interrupted connection or unreachable host) has occurred.] { Mar 15 19:32:40 volumio volumio[863]: code: 'auth/network-request-failed', Mar 15 19:32:40 volumio volumio[863]: a: null Mar 15 19:32:40 volumio volumio[863]: } Mar 15 19:32:40 volumio volumio[863]: ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| Mar 15 19:32:40 volumio sudo[4310]: volumio : unable to resolve host volumio Mar 15 19:32:40 volumio sudo[4310]: volumio : problem with defaults entries ; TTY=unknown ; PWD=/ ; USER=root ; Mar 15 19:32:40 volumio sudo[4310]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/journalctl --since=2025-03-15 19:31 Mar 15 19:32:40 volumio sudo[4310]: pam_unix(sudo:session): session opened for user root by (uid=0) 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="bba9e3185e150dd0995f9a49355b34fc6218d5a2" VOLUMIO_FE_VERSION="e7cae168f9927391640a091813b8a9656b6909b6" VOLUMIO_FE3_VERSION="df82a8f23c90a3617c15c55572c8aaea90d8b32a" VOLUMIO_BE_VERSION="8aa57e3ae5b742ea1069404608336a9884ccfb4e" VOLUMIO_ARCH="arm" VOLUMIO_VARIANT="volumio" VOLUMIO_TEST="FALSE" VOLUMIO_BUILD_DATE="Tue 17 Sep 2024 05:01:09 PM CEST" VOLUMIO_VERSION="3.757" VOLUMIO_HARDWARE="pi" VOLUMIO_DEVICENAME="Raspberry Pi" VOLUMIO_HASH="e0a6dc7e914e3fb93cbf2123f2f73eac"