VOLUMIO 11/8/2026-5:11:3 socket hang up
VOLUMIO 11/8/2026-5:10:31 Chaining cycle detected for promise #
VOLUMIO 11/8/2026-5:10:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-5:9:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-5:8:32 socket hang up
VOLUMIO 11/8/2026-5:3:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-5:1:16 socket hang up
FERRUMBROEN 11/8/2026-4:59:44 Cannot read properties of undefined (reading then)
VOLUMIO 11/8/2026-4:58:37 self is not defined
VOLUMIO 11/8/2026-4:58:25 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:58:7 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-4:57:13 socket hang up
VOLUMIO 11/8/2026-4:54:24 connect ETIMEDOUT 185.60.216.36:443
VOLUMIO 11/8/2026-4:46:24 socket hang up
VOLUMIO 11/8/2026-4:45:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:45:32 socket hang up
VOLUMIO 11/8/2026-4:45:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:45:11 Chaining cycle detected for promise #
VOLUMIO 11/8/2026-4:43:14 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-4:40:49 socket hang up
VOLUMIO 11/8/2026-4:39:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:38:12 socket hang up
PRIMOPLUS 11/8/2026-4:37:25 connect ETIMEDOUT 151.101.222.79:443
VOLUMIO 11/8/2026-4:37:14 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:36:36 Cannot read properties of undefined (reading split)
OPERA 11/8/2026-4:36:33 connect ETIMEDOUT 168.143.162.42:443
VOLUMIO 11/8/2026-4:35:35 socket hang up
VOLUMIO 11/8/2026-4:34:37 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:31:5 socket hang up
VOLUMIO 11/8/2026-4:30:55 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-4:30:15 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-4:29:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:29:18 connect ETIMEDOUT 74.86.228.110:443
VOLUMIO 11/8/2026-4:27:54 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/8/2026-4:25:34 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-4:23:38 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-4:22:40 socket hang up
VOLUMIO 11/8/2026-4:22:29 Cannot read property slice of null
VOLUMIO 11/8/2026-4:21:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:20:58 socket hang up
VOLUMIO 11/8/2026-4:20:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:18:18 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-4:17:58 addMembership ENODEV
VOLUMIO 11/8/2026-4:15:4 Chaining cycle detected for promise #
VOLUMIO 11/8/2026-4:13:32 Cannot set properties of undefined (setting name)
VOLUMIO 11/8/2026-4:13:11 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:12:57 socket hang up
VOLUMIO 11/8/2026-4:11:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:11:4 fetch failed
VOLUMIO 11/8/2026-4:11:0 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-4:10:51 socket hang up
VOLUMIO 11/8/2026-4:3:14 socket hang up
VOLUMIO 11/8/2026-4:2:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-4:1:33 socket hang up
VOLUMIO 11/8/2026-3:59:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:54:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:53:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:52:21 socket hang up
VOLUMIO 11/8/2026-3:51:41 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-3:51:4 socket hang up
VOLUMIO 11/8/2026-3:50:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:49:35 connect ETIMEDOUT 108.160.172.200:443
VOLUMIO 11/8/2026-3:49:31 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-3:48:16 socket hang up
VOLUMIO 11/8/2026-3:46:39 socket hang up
VOLUMIO 11/8/2026-3:45:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:37:59 socket hang up
VOLUMIO 11/8/2026-3:37:6 EBADF: bad file descriptor, write
VOLUMIO 11/8/2026-3:37:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:33:10 socket hang up
VOLUMIO 11/8/2026-3:32:13 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:31:4 socket hang up
VOLUMIO 11/8/2026-3:31:0 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:30:36 socket hang up
VOLUMIO 11/8/2026-3:30:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:27:41 socket hang up
VOLUMIO 11/8/2026-3:26:58 Cannot read property then of undefined
VOLUMIO 11/8/2026-3:26:48 Cannot read property slice of null
VOLUMIO 11/8/2026-3:26:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:18:14 socket hang up
VOLUMIO 11/8/2026-3:17:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:16:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:14:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:14:15 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-3:13:52 socket hang up
VOLUMIO 11/8/2026-3:7:57 socket hang up
VOLUMIO 11/8/2026-3:6:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:6:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-3:4:51 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-3:4:36 socket hang up
VOLUMIO 11/8/2026-3:1:14 read ECONNRESET
VOLUMIO 11/8/2026-3:0:18 Cannot read property name of undefined
VOLUMIO 11/8/2026-2:57:48 socket hang up
VOLUMIO 11/8/2026-2:56:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:56:29 socket hang up
VOLUMIO 11/8/2026-2:56:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:52:38 socket hang up
VOLUMIO 11/8/2026-2:51:56 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-2:51:39 dns service error: unknown
VOLUMIO 11/8/2026-2:51:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:50:7 socket hang up
VOLUMIO 11/8/2026-2:49:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-2:49:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:45:59 socket hang up
VOLUMIO 11/8/2026-2:44:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:43:16 connect ETIMEDOUT 69.63.178.13:443
VOLUMIO 11/8/2026-2:40:27 dns service error: unknown
VOLUMIO 11/8/2026-2:40:10 socket hang up
VOLUMIO 11/8/2026-2:39:7 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:33:44 socket hang up
VOLUMIO 11/8/2026-2:33:3 spawn ENOMEM
VOLUMIO 11/8/2026-2:32:22 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:31:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:31:17 socket hang up
VOLUMIO 11/8/2026-2:30:26 socket hang up
VOLUMIO 11/8/2026-2:29:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:26:5 dns service error: unknown
VOLUMIO 11/8/2026-2:25:57 Unable to resolve or reject the same promise twice
PRIMOPLUS 11/8/2026-2:25:3 connect EHOSTUNREACH 192.168.10.178:1400
VOLUMIO 11/8/2026-2:24:26 Cannot read property then of undefined
PRIMOPLUS 11/8/2026-2:24:17 connect EHOSTUNREACH 192.168.10.131:1400
PRIMOPLUS 11/8/2026-2:23:48 connect EHOSTUNREACH 192.168.10.171:1400
VOLUMIO 11/8/2026-2:17:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:16:49 socket hang up
VOLUMIO 11/8/2026-2:16:2 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/8/2026-2:15:0 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-2:11:43 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Connection timed out See system logs and systemctl
VOLUMIO 11/8/2026-2:7:59 dns service error: unknown
VOLUMIO 11/8/2026-2:7:19 dns service error: unknown
VOLUMIO 11/8/2026-2:5:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-2:3:3 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-2:2:56 socket hang up
VOLUMIO 11/8/2026-2:1:56 Chaining cycle detected for promise #
VOLUMIO 11/8/2026-2:1:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:58:47 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-1:58:29 VM operation timed out
VOLUMIO 11/8/2026-1:58:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:57:0 socket hang up
VOLUMIO 11/8/2026-1:56:26 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-1:55:54 Cannot read properties of null (reading 0)
VOLUMIO 11/8/2026-1:54:42 Cannot read properties of undefined (reading split)
VOLUMIO 11/8/2026-1:53:40 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-1:53:22 socket hang up
VOLUMIO 11/8/2026-1:52:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:48:22 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-1:47:21 Chaining cycle detected for promise #
VOLUMIO 11/8/2026-1:43:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:43:18 socket hang up
VOLUMIO 11/8/2026-1:42:53 getaddrinfo -3007
VOLUMIO 11/8/2026-1:41:13 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-1:36:4 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-1:28:7 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/8/2026-1:26:29 connect ETIMEDOUT 168.143.162.58:443
VOLUMIO 11/8/2026-1:20:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:19:14 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-1:17:49 socket hang up
VOLUMIO 11/8/2026-1:17:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-1:14:39 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-1:9:37 socket hang up
VOLUMIO 11/8/2026-1:8:25 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:8:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-1:6:55 socket hang up
OPERA 11/8/2026-1:2:9 connect ETIMEDOUT 108.160.169.171:443
VOLUMIO 11/8/2026-0:58:5 Cannot read properties of null (reading 0)
OPERA 11/8/2026-0:56:20 connect ECONNREFUSED 162.125.32.13:443
VOLUMIO 11/8/2026-0:55:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:54:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:53:25 socket hang up
VOLUMIO 11/8/2026-0:50:8 Cannot read properties of null (reading 0)
VOLUMIO 11/8/2026-0:48:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:45:47 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-0:43:52 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:41:17 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-0:40:7 Cannot read properties of null (reading 0)
VOLUMIO 11/8/2026-0:39:21 socket hang up
VOLUMIO 11/8/2026-0:38:23 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:37:40 connect ECONNREFUSED 127.0.0.1:9879
FERRUMBROEN 11/8/2026-0:35:54 write EPIPE
VOLUMIO 11/8/2026-0:35:8 socket hang up
VOLUMIO 11/8/2026-0:34:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:34:9 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/8/2026-0:32:47 Unable to resolve or reject the same promise twice
VOLUMIO 11/8/2026-0:27:47 socket hang up
VOLUMIO 11/8/2026-0:26:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:26:28 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(). The promise rejected with the reason undefined.
VOLUMIO 11/8/2026-0:25:44 self is not defined
VOLUMIO 11/8/2026-0:22:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:21:37 socket hang up
FERRUMBROEN 11/8/2026-0:20:57 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/8/2026-0:18:45 socket hang up
VOLUMIO 11/8/2026-0:17:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:16:27 socket hang up
VOLUMIO 11/8/2026-0:16:19 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/8/2026-0:15:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:12:25 socket hang up
VOLUMIO 11/8/2026-0:11:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:10:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:9:53 socket hang up
VOLUMIO 11/8/2026-0:8:52 socket hang up
VOLUMIO 11/8/2026-0:6:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:2:57 socket hang up
VOLUMIO 11/8/2026-0:1:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:1:11 socket hang up
VOLUMIO 11/8/2026-0:1:0 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/8/2026-0:0:30 socket hang up
VOLUMIO 11/8/2026-0:0:13 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:57:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:56:37 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-23:55:55 socket hang up
VOLUMIO 11/7/2026-23:54:23 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(). The promise rejected with the reason undefined.
VOLUMIO 11/7/2026-23:54:13 Cannot read property volumio_info of undefined
VOLUMIO 11/7/2026-23:54:3 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:53:36 socket hang up
VOLUMIO 11/7/2026-23:49:52 socket hang up
VOLUMIO 11/7/2026-23:48:58 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-23:48:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:48:7 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-23:47:9 EBADF: bad file descriptor, write
VOLUMIO 11/7/2026-23:47:7 dns service error: unknown
VOLUMIO 11/7/2026-23:45:18 socket hang up
VOLUMIO 11/7/2026-23:44:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:44:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:42:35 socket hang up
VOLUMIO 11/7/2026-23:42:26 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-23:39:24 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-23:38:17 socket hang up
VOLUMIO 11/7/2026-23:37:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:36:36 socket hang up
VOLUMIO 11/7/2026-23:35:38 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:34:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-23:33:31 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-23:32:42 socket hang up
VOLUMIO 11/7/2026-23:31:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:29:20 CamillaDSP is not running
VOLUMIO 11/7/2026-23:28:59 connect ECONNREFUSED 0.0.0.0:443
VOLUMIO 11/7/2026-23:27:21 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-23:26:38 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:26:33 socket hang up
VOLUMIO 11/7/2026-23:25:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:22:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:21:49 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-23:20:23 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-23:19:21 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-23:18:57 socket hang up
VOLUMIO 11/7/2026-23:17:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:16:24 Failed to activate service org.bluez: timed out (service_start_timeout=25000ms)
VOLUMIO 11/7/2026-23:16:16 dns service error: unknown
VOLUMIO 11/7/2026-23:15:24 socket hang up
VOLUMIO 11/7/2026-23:14:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:12:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:11:55 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-23:5:18 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-23:3:50 dns service error: unknown
VOLUMIO 11/7/2026-23:3:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-23:3:0 socket hang up
VOLUMIO 11/7/2026-22:56:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:55:14 socket hang up
VOLUMIO 11/7/2026-22:55:9 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(). The promise rejected with the reason undefined.
VOLUMIO 11/7/2026-22:50:59 Unable to resolve or reject the same promise twice
RIVOPLUS 11/7/2026-22:50:26 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-22:49:38 dns service error: unknown
VOLUMIO 11/7/2026-22:49:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:45:57 socket hang up
VOLUMIO 11/7/2026-22:42:21 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-22:39:19 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-22:37:24 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-22:36:17 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-22:34:45 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(). The promise rejected with the reason undefined.
VOLUMIO 11/7/2026-22:34:2 socket hang up
VOLUMIO 11/7/2026-22:32:40 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:32:8 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-22:31:57 socket hang up
VOLUMIO 11/7/2026-22:30:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:29:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:27:51 socket hang up
VOLUMIO 11/7/2026-22:27:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:26:38 socket hang up
VOLUMIO 11/7/2026-22:22:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:20:36 socket hang up
VOLUMIO 11/7/2026-22:15:15 send ENETUNREACH 255.255.255.255:3483
VOLUMIO 11/7/2026-22:14:11 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-22:14:11 Cannot read property replace of undefined
VOLUMIO 11/7/2026-22:13:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:13:22 socket hang up
RIVOULTRA 11/7/2026-22:12:40 write EPIPE
VOLUMIO 11/7/2026-22:9:59 socket hang up
VOLUMIO 11/7/2026-22:9:18 fetch failed
VOLUMIO 11/7/2026-22:8:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:8:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:7:53 socket hang up
VOLUMIO 11/7/2026-22:7:21 socket hang up
VOLUMIO 11/7/2026-22:6:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:4:58 Cannot read property slice of null
RIVOULTRA 11/7/2026-22:4:3 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-22:3:22 socket hang up
VOLUMIO 11/7/2026-22:3:2 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-22:2:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:1:51 socket hang up
VOLUMIO 11/7/2026-22:1:1 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-22:0:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-22:0:10 socket hang up
VOLUMIO 11/7/2026-21:59:53 connect ETIMEDOUT 34.49.30.2:80
VOLUMIO 11/7/2026-21:59:48 socket hang up
VOLUMIO 11/7/2026-21:59:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-21:58:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-21:57:16 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-21:54:22 fetch failed
VOLUMIO 11/7/2026-21:54:11 Cannot read properties of undefined (reading sendCommand)
RIVOPLUS 11/7/2026-21:52:57 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/7/2026-21:49:51 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-21:49:16 socket hang up
VOLUMIO 11/7/2026-21:47:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-21:41:39 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-21:32:24 Unable to resolve or reject the same promise twice
RIVOPLUS 11/7/2026-21:29:0 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/7/2026-21:24:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-21:24:29 socket hang up
VOLUMIO 11/7/2026-21:18:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-21:16:52 EIO: i/o error, scandir /data/plugins/
VOLUMIO 11/7/2026-21:15:19 Cannot read property name of undefined
VOLUMIO 11/7/2026-21:14:15 socket hang up
VOLUMIO 11/7/2026-21:10:25 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(). The promise rejected with the reason undefined.
VOLUMIO 11/7/2026-20:59:24 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-20:57:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:57:21 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-20:56:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:55:46 socket hang up
VOLUMIO 11/7/2026-20:55:35 socket hang up
VOLUMIO 11/7/2026-20:54:40 Cannot read property name of null
VOLUMIO 11/7/2026-20:50:28 write EPIPE
VOLUMIO 11/7/2026-20:50:1 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
RIVO 11/7/2026-20:48:34 Command failed: /usr/bin/wget -O /tmp/EQfile.txt https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results4360 Sennheiser HD 800 S (ZMF sheepskin earpads)/Sennheiser%20HD%20800%20S%20(ZMF%20sheepskin%20earpads)%20ParametricEQ.txt --2026-11-07 20:48:33-- https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results4360%20%20Sennheiser%20HD%20800%20S%20(ZMF%20sheepskin%20earpads)/Sennheiser%20HD%20800%20S%20(ZMF%20sheepskin%20earpads)%20ParametricEQ.txt Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.109.133, 185.199.110.133, 185.199.111.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.109.133|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2026-11-07 20:48:33 ERROR 404: Not Found.
VOLUMIO 11/7/2026-20:46:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:45:52 socket hang up
VOLUMIO 11/7/2026-20:40:46 getaddrinfo -3007
VOLUMIO 11/7/2026-20:38:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:37:58 socket hang up
VOLUMIO 11/7/2026-20:37:39 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
PROJECTSBUS2 11/7/2026-20:37:11 Cannot read property slice of null
VOLUMIO 11/7/2026-20:35:17 socket hang up
VOLUMIO 11/7/2026-20:34:28 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-20:34:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:31:28 socket hang up
VOLUMIO 11/7/2026-20:30:9 Cannot read property service of undefined
VOLUMIO 11/7/2026-20:30:6 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/7/2026-20:28:53 Cannot read property service of undefined
VOLUMIO 11/7/2026-20:19:50 Cannot read property off of undefined
VOLUMIO 11/7/2026-20:18:55 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-20:18:45 socket hang up
VOLUMIO 11/7/2026-20:17:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:15:16 Cannot read properties of null (reading slice)
VOLUMIO 11/7/2026-20:14:34 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-20:13:40 socket hang up
VOLUMIO 11/7/2026-20:13:2 The data argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
VOLUMIO 11/7/2026-20:12:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:6:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:6:43 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-20:6:30 socket hang up
VOLUMIO 11/7/2026-20:6:18 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-20:5:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:5:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-20:5:29 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-20:4:37 socket hang up
VOLUMIO 11/7/2026-20:3:51 socket hang up
VOLUMIO 11/7/2026-20:2:46 Cannot read properties of null (reading slice)
VOLUMIO 11/7/2026-20:2:12 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/7/2026-20:2:9 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-20:0:11 Cannot read property stop of null
PRIMO2REV2 11/7/2026-19:57:49 Premature end of data in tag br line 187 (Line: 195, Column: 7)
RIVO 11/7/2026-19:57:36 Cannot read properties of undefined (reading url)
VOLUMIO 11/7/2026-19:57:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:56:41 Cannot read property service of undefined
VOLUMIO 11/7/2026-19:55:51 connect ECONNREFUSED 127.0.0.1:9879
PRIMO2REV2 11/7/2026-19:54:3 Cannot read properties of undefined (reading length)
VOLUMIO 11/7/2026-19:53:47 Cannot read property slice of null
VOLUMIO 11/7/2026-19:53:19 socket hang up
VOLUMIO 11/7/2026-19:51:57 connect ECONNREFUSED 127.0.0.1:9879
PRIMOPLUS 11/7/2026-19:51:22 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-19:51:21 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:51:4 read ECONNRESET
VOLUMIO 11/7/2026-19:49:11 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-19:48:21 socket hang up
VOLUMIO 11/7/2026-19:47:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:46:44 socket hang up
VOLUMIO 11/7/2026-19:45:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:45:13 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-19:43:10 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-19:42:55 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-19:42:48 Cannot read property writeSync of undefined
VOLUMIO 11/7/2026-19:42:29 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
RIVO 11/7/2026-19:41:40 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-19:39:15 socket hang up
VOLUMIO 11/7/2026-19:38:50 Command failed: /usr/bin/sudo /usr/bin/timedatectl set-timezone Europe/London sudo: no tty present and no askpass program specified
VOLUMIO 11/7/2026-19:38:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:37:34 socket hang up
VOLUMIO 11/7/2026-19:36:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:35:56 socket hang up
VOLUMIO 11/7/2026-19:35:40 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:34:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:34:22 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:32:52 socket hang up
VOLUMIO 11/7/2026-19:32:44 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-19:30:51 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-19:30:18 socket hang up
VOLUMIO 11/7/2026-19:29:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-19:29:21 connect ECONNREFUSED 127.0.0.1:9879
PRIMO2REV2 11/7/2026-19:28:44 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-19:28:39 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-19:26:14 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
RIVOPLUS 11/7/2026-19:26:10 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/7/2026-19:25:10 socket hang up
VOLUMIO 11/7/2026-19:21:33 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-19:21:25 connect EHOSTUNREACH 192.168.1.133:1400
VOLUMIO 11/7/2026-19:19:30 unable to verify the first certificate
VOLUMIO 11/7/2026-19:18:28 c.push is not a function
VOLUMIO 11/7/2026-19:15:2 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:14:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:13:20 socket hang up
VOLUMIO 11/7/2026-19:13:0 socket hang up
MF 11/7/2026-19:8:58 connect ETIMEDOUT 151.101.222.79:443
VOLUMIO 11/7/2026-19:7:15 socket hang up
VOLUMIO 11/7/2026-19:5:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-19:5:0 socket hang up
VOLUMIO 11/7/2026-19:3:54 CamillaDSP is not running
VOLUMIO 11/7/2026-19:0:50 /data/configuration/plugins.json: Unexpected end of JSON input
MINIDSPSHD 11/7/2026-18:57:44 Cannot read property service of undefined
VOLUMIO 11/7/2026-18:57:38 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:57:17 socket hang up
VOLUMIO 11/7/2026-18:54:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:54:21 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Transport endpoint is not connected See system logs and systemctl
VOLUMIO 11/7/2026-18:53:51 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-18:50:32 dns service error: unknown
VOLUMIO 11/7/2026-18:50:23 dns service error: unknown
VOLUMIO 11/7/2026-18:49:35 Cannot read property service of undefined
VOLUMIO 11/7/2026-18:49:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:49:2 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-18:48:39 CamillaDSP is not running
VOLUMIO 11/7/2026-18:48:27 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-18:48:18 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-18:47:28 socket hang up
VOLUMIO 11/7/2026-18:46:31 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-18:45:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:42:54 socket hang up
VOLUMIO 11/7/2026-18:42:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:41:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:41:34 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-18:37:13 CamillaDSP reload timed out after 10000 ms (14 connection attempts
VOLUMIO 11/7/2026-18:36:14 FusionDsp - Error in eqv! Cannot split values for Eq14
VOLUMIO 11/7/2026-18:34:59 Cannot read property service of undefined
VOLUMIO 11/7/2026-18:34:8 socket hang up
VOLUMIO 11/7/2026-18:33:40 Cannot read property slice of null
VOLUMIO 11/7/2026-18:33:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:29:20 socket hang up
VOLUMIO 11/7/2026-18:27:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:27:26 write EPIPE
VOLUMIO 11/7/2026-18:26:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:26:27 socket hang up
VOLUMIO 11/7/2026-18:18:51 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/7/2026-18:18:16 Cannot read property slice of null
VOLUMIO 11/7/2026-18:17:22 spawnSync /bin/sh EMFILE
VOLUMIO 11/7/2026-18:17:11 Cannot read properties of null (reading slice)
MINIDSPSHD 11/7/2026-18:16:16 this.sendSpopCommand is not a function
VOLUMIO 11/7/2026-18:16:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:15:39 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-18:15:23 Cannot read properties of null (reading reset)
VOLUMIO 11/7/2026-18:14:59 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-18:14:45 socket hang up
SMSL 11/7/2026-18:14:20 read ECONNRESET
VOLUMIO 11/7/2026-18:12:1 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-18:9:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-18:9:2 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-18:7:15 socket hang up
VOLUMIO 11/7/2026-18:2:30 certificate is not yet valid
VOLUMIO 11/7/2026-17:56:10 connect ETIMEDOUT 23.49.104.47:443
VOLUMIO 11/7/2026-17:56:2 Cannot read property slice of null
VOLUMIO 11/7/2026-17:55:1 dns service error: unknown
VOLUMIO 11/7/2026-17:43:27 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-17:43:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:42:44 socket hang up
VOLUMIO 11/7/2026-17:42:16 socket hang up
VOLUMIO 11/7/2026-17:41:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:38:39 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/7/2026-17:37:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-17:33:58 socket hang up
VOLUMIO 11/7/2026-17:33:53 socket hang up
VOLUMIO 11/7/2026-17:33:5 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-17:32:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:32:24 Unable to resolve or reject the same promise twice
RIVO 11/7/2026-17:31:20 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-17:27:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:26:40 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-17:26:7 socket hang up
VOLUMIO 11/7/2026-17:25:59 getaddrinfo ENOTFOUND ext-strm-rukzn03rtk-01.strm.yandex.net
VOLUMIO 11/7/2026-17:25:57 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-17:25:53 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-17:25:26 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-17:25:8 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-17:24:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:23:1 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-17:22:25 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:21:24 socket hang up
RIVOPLUS 11/7/2026-17:21:18 write EPIPE
VOLUMIO 11/7/2026-17:21:3 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-17:19:42 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-17:18:34 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-17:17:22 socket hang up
VOLUMIO 11/7/2026-17:16:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:15:21 ENOSPC: no space left on device, write
VOLUMIO 11/7/2026-17:14:25 socket hang up
VOLUMIO 11/7/2026-17:12:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:10:55 Cannot read property service of undefined
VOLUMIO 11/7/2026-17:9:37 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-17:5:8 socket hang up
VOLUMIO 11/7/2026-17:5:4 Cannot read property writeSync of undefined
VOLUMIO 11/7/2026-17:4:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-17:4:4 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-17:2:32 Premature end of data in tag br line 187 (Line: 195, Column: 7)
VOLUMIO 11/7/2026-17:1:8 write EPIPE
VOLUMIO 11/7/2026-16:58:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:57:32 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:56:58 socket hang up
RIVO 11/7/2026-16:56:17 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/7/2026-16:54:44 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:52:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:51:57 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/7/2026-16:49:20 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:46:54 socket hang up
VOLUMIO 11/7/2026-16:45:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:45:23 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/7/2026-16:45:11 certificate is not yet valid
VOLUMIO 11/7/2026-16:42:37 connect ETIMEDOUT 162.125.18.133:443
VOLUMIO 11/7/2026-16:33:47 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:33:30 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-16:32:35 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/7/2026-16:28:53 dns service error: refused
VOLUMIO 11/7/2026-16:28:15 socket hang up
VOLUMIO 11/7/2026-16:26:25 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-16:26:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:26:13 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-16:23:32 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-16:22:14 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:21:50 socket hang up
VOLUMIO 11/7/2026-16:18:56 socket hang up
VOLUMIO 11/7/2026-16:17:44 Premature end of data in tag br line 187 (Line: 195, Column: 7)
VOLUMIO 11/7/2026-16:17:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:17:10 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-16:15:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:12:40 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/7/2026-16:11:14 Cannot read property replace of undefined
VOLUMIO 11/7/2026-16:10:51 socket hang up
VOLUMIO 11/7/2026-16:9:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:8:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:5:11 socket hang up
VOLUMIO 11/7/2026-16:4:58 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-16:3:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:3:24 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-16:1:43 socket hang up
VOLUMIO 11/7/2026-16:0:21 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-16:0:4 fetch failed
VOLUMIO 11/7/2026-15:58:56 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-15:53:36 connect ECONNREFUSED 127.0.0.1:9879
RIVO 11/7/2026-15:51:4 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/7/2026-15:46:31 socket hang up
VOLUMIO 11/7/2026-15:45:25 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-15:44:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:44:17 socket hang up
RIVO 11/7/2026-15:43:54 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-15:42:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:41:16 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-15:40:4 socket hang up
VOLUMIO 11/7/2026-15:40:3 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-15:39:4 Cannot read property slice of null
VOLUMIO 11/7/2026-15:38:37 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:38:22 Cannot read properties of undefined (reading on)
VOLUMIO 11/7/2026-15:38:8 connect ECONNREFUSED 0.0.0.0:443
VOLUMIO 11/7/2026-15:37:57 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-15:37:36 Cannot read property slice of null
VOLUMIO 11/7/2026-15:28:27 socket hang up
VOLUMIO 11/7/2026-15:27:39 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-15:27:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:25:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-15:23:59 Cannot read property slice of null
VOLUMIO 11/7/2026-15:22:17 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-15:15:59 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-15:13:19 socket hang up
VOLUMIO 11/7/2026-15:11:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:11:18 socket hang up
MF 11/7/2026-15:11:11 Cannot read property slice of null
VOLUMIO 11/7/2026-15:9:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:4:41 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-15:4:11 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-15:2:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-15:0:23 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-15:0:16 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:59:59 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:59:46 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-14:59:38 Cannot read property cats of undefined
VOLUMIO 11/7/2026-14:58:18 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-14:57:55 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:57:8 socket hang up
VOLUMIO 11/7/2026-14:55:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:53:40 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-14:51:3 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-14:50:59 socket hang up
VOLUMIO 11/7/2026-14:48:20 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-14:44:3 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-14:43:10 Cannot read property replace of undefined
VOLUMIO 11/7/2026-14:40:38 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-14:40:30 Cannot read property service of undefined
VOLUMIO 11/7/2026-14:40:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:39:50 socket hang up
VOLUMIO 11/7/2026-14:39:31 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:38:28 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:36:39 connect ETIMEDOUT 151.101.222.53:443
VOLUMIO 11/7/2026-14:32:14 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-14:30:36 Cannot read properties of undefined (reading url)
VOLUMIO 11/7/2026-14:27:44 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-14:26:49 Cannot read properties of undefined (reading url)
VOLUMIO 11/7/2026-14:26:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:23:23 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:21:43 socket hang up
VOLUMIO 11/7/2026-14:20:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:20:42 Cannot read property slice of null
VOLUMIO 11/7/2026-14:18:2 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:17:38 socket hang up
VOLUMIO 11/7/2026-14:17:17 Cannot read property service of undefined
VOLUMIO 11/7/2026-14:16:56 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-14:15:4 dns service error: unknown
VOLUMIO 11/7/2026-14:13:22 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-14:11:51 Cannot read property service of undefined
VOLUMIO 11/7/2026-14:10:36 certificate is not yet valid
VOLUMIO 11/7/2026-14:10:31 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-14:10:15 write EPIPE
VOLUMIO 11/7/2026-14:10:13 connect ECONNREFUSED 98.159.108.58:443
VOLUMIO 11/7/2026-14:9:7 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-14:8:43 send ENETUNREACH 255.255.255.255:3483
VOLUMIO 11/7/2026-14:6:27 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/7/2026-14:3:39 socket hang up
VOLUMIO 11/7/2026-14:3:36 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-14:2:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:2:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:2:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-14:2:21 socket hang up
VOLUMIO 11/7/2026-14:0:37 socket hang up
VOLUMIO 11/7/2026-13:59:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:58:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:57:30 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:55:49 socket hang up
VOLUMIO 11/7/2026-13:54:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:50:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:49:34 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/7/2026-13:48:53 socket hang up
VOLUMIO 11/7/2026-13:48:11 socket hang up
VOLUMIO 11/7/2026-13:47:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:45:16 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-13:43:19 connect ETIMEDOUT 179.60.193.9:443
VOLUMIO 11/7/2026-13:41:21 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-13:41:5 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-13:39:54 Cannot read properties of undefined (reading highestSoundQuality)
UNDEFINED 11/7/2026-13:38:1 Cannot read property then of undefined
VOLUMIO 11/7/2026-13:37:13 socket hang up
VOLUMIO 11/7/2026-13:37:11 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:36:28 deferred is not defined
VOLUMIO 11/7/2026-13:36:14 socket hang up
VOLUMIO 11/7/2026-13:35:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:35:43 fetch failed
VOLUMIO 11/7/2026-13:34:12 socket hang up
OPERA 11/7/2026-13:33:52 connect ETIMEDOUT 108.160.165.147:443
VOLUMIO 11/7/2026-13:33:52 socket hang up
VOLUMIO 11/7/2026-13:33:20 connect ETIMEDOUT 192.168.1.227:1400
VOLUMIO 11/7/2026-13:33:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:30:34 socket hang up
VOLUMIO 11/7/2026-13:29:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:28:31 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:28:15 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-13:27:57 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:27:37 socket hang up
VOLUMIO 11/7/2026-13:27:34 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-13:27:30 Cannot read property then of undefined
VOLUMIO 11/7/2026-13:26:34 connect ECONNREFUSED 127.0.0.1:9879
PRIMOPLUS 11/7/2026-13:25:42 Cannot read properties of undefined (reading then)
PRIMOPLUS 11/7/2026-13:25:21 Cannot read properties of undefined (reading rparadise)
VOLUMIO 11/7/2026-13:25:14 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:24:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:23:56 socket hang up
VOLUMIO 11/7/2026-13:23:50 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:23:47 socket hang up
VOLUMIO 11/7/2026-13:19:40 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/7/2026-13:19:9 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:17:8 socket hang up
VOLUMIO 11/7/2026-13:16:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:15:56 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:15:22 socket hang up
VOLUMIO 11/7/2026-13:15:20 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-13:14:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:14:8 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:13:3 Unable to resolve or reject the same promise twice
RIVO 11/7/2026-13:12:56 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-13:12:36 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-13:11:50 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-13:11:45 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-13:10:52 Cannot read property then of undefined
VOLUMIO 11/7/2026-13:9:3 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-13:8:56 VM operation timed out
VOLUMIO 11/7/2026-13:8:38 socket hang up
VOLUMIO 11/7/2026-13:8:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:8:25 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-13:8:14 socket hang up
VOLUMIO 11/7/2026-13:7:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-13:5:6 Connection :1.25 is not allowed to add more match rules (increase limits in configuration file if required
VOLUMIO 11/7/2026-13:3:25 socket hang up
VOLUMIO 11/7/2026-13:2:46 Cannot read property slice of null
VOLUMIO 11/7/2026-13:2:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:59:40 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:58:22 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/7/2026-12:56:14 socket hang up
VOLUMIO 11/7/2026-12:55:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:55:4 dns service error: unknown
VOLUMIO 11/7/2026-12:54:45 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:54:7 dns service error: unknown
VOLUMIO 11/7/2026-12:53:59 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:53:55 connect ETIMEDOUT 31.13.75.5:443
OPERA 11/7/2026-12:53:20 connect ETIMEDOUT 108.160.167.159:443
OPERA 11/7/2026-12:51:17 connect ETIMEDOUT 199.59.150.44:443
VOLUMIO 11/7/2026-12:50:32 connect ETIMEDOUT 157.240.2.36:443
VOLUMIO 11/7/2026-12:48:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:47:51 socket hang up
VOLUMIO 11/7/2026-12:46:46 connect ETIMEDOUT 108.160.172.208:443
VOLUMIO 11/7/2026-12:46:26 socket hang up
VOLUMIO 11/7/2026-12:44:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:43:44 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:43:31 connect ETIMEDOUT 39.109.122.128:443
VOLUMIO 11/7/2026-12:43:19 socket hang up
VOLUMIO 11/7/2026-12:41:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:40:45 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-12:40:14 connect ETIMEDOUT 202.160.128.238:443
VOLUMIO 11/7/2026-12:39:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:38:8 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-12:36:8 socket hang up
VOLUMIO 11/7/2026-12:35:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:35:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:34:22 socket hang up
VOLUMIO 11/7/2026-12:34:17 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-12:34:15 Cannot read property service of undefined
VOLUMIO 11/7/2026-12:33:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:32:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:32:5 socket hang up
VOLUMIO 11/7/2026-12:30:45 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Unit volumio5-onboarding.service is masked.
VOLUMIO 11/7/2026-12:29:11 write EPIPE
VOLUMIO 11/7/2026-12:28:55 Cannot read properties of undefined (reading highestSoundQuality)
VOLUMIO 11/7/2026-12:28:46 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:27:14 connect ETIMEDOUT 108.160.166.142:443
VOLUMIO 11/7/2026-12:23:59 socket hang up
VOLUMIO 11/7/2026-12:23:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:22:11 Cannot read property service of undefined
VOLUMIO 11/7/2026-12:21:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:17:55 connect ETIMEDOUT 31.13.112.9:443
VOLUMIO 11/7/2026-12:17:53 file /mnt/NAS/NAS/HIFI人声/人声 - 蔡琴 -《试音 蔡琴》/蔡琴.-.[试音.蔡琴].专辑.(APE).cue does not exist
VOLUMIO 11/7/2026-12:17:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:17:10 socket hang up
VOLUMIO 11/7/2026-12:16:58 getaddrinfo -3007
VOLUMIO 11/7/2026-12:15:27 connect ETIMEDOUT 103.252.114.61:443
VOLUMIO 11/7/2026-12:13:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-12:12:15 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-12:12:5 CamillaDSP reload timed out after 10000 ms (35 connection attempts
VOLUMIO 11/7/2026-12:11:31 connect ETIMEDOUT 108.160.169.55:443
VOLUMIO 11/7/2026-12:8:38 Cannot read property slice of null
VOLUMIO 11/7/2026-12:6:49 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-12:6:41 Unable to resolve or reject the same promise twice
OPERA 11/7/2026-12:2:31 connect ETIMEDOUT 67.228.102.32:443
VOLUMIO 11/7/2026-12:0:21 socket hang up
VOLUMIO 11/7/2026-11:59:23 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:59:1 Cannot read property slice of null
VOLUMIO 11/7/2026-11:56:28 write EPIPE
VOLUMIO 11/7/2026-11:54:16 socket hang up
VOLUMIO 11/7/2026-11:53:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:52:31 Cannot read properties of undefined (reading split)
OPERA 11/7/2026-11:52:18 connect ETIMEDOUT 199.59.148.246:443
VOLUMIO 11/7/2026-11:51:59 Cannot read property title of undefined
VOLUMIO 11/7/2026-11:51:13 unable to verify the first certificate
VOLUMIO 11/7/2026-11:46:52 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-11:45:55 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-11:45:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-11:44:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:44:29 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/7/2026-11:43:25 socket hang up
VOLUMIO 11/7/2026-11:39:11 dns service error: unknown
VOLUMIO 11/7/2026-11:38:43 socket hang up
VOLUMIO 11/7/2026-11:38:32 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-11:37:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:36:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:36:11 socket hang up
VOLUMIO 11/7/2026-11:35:9 dns service error: unknown
VOLUMIO 11/7/2026-11:35:7 Cannot read property service of undefined
VOLUMIO 11/7/2026-11:34:11 socket hang up
VOLUMIO 11/7/2026-11:33:13 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:28:31 self.sendCommand(...).then(...).then(...).catch is not a function
VOLUMIO 11/7/2026-11:27:30 Cannot read properties of null (reading reset)
VOLUMIO 11/7/2026-11:27:5 socket hang up
VOLUMIO 11/7/2026-11:26:7 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:25:9 Cannot read property then of undefined
VOLUMIO 11/7/2026-11:24:8 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-11:24:3 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-11:21:58 Cannot read property service of undefined
VOLUMIO 11/7/2026-11:20:53 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-11:20:29 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-11:18:51 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-11:16:22 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-11:12:4 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-11:11:54 Cannot read properties of null (reading reset)
VOLUMIO 11/7/2026-11:10:6 socket hang up
VOLUMIO 11/7/2026-11:9:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:5:38 Cannot read property then of undefined
VOLUMIO 11/7/2026-11:5:38 Cannot read property slice of null
VOLUMIO 11/7/2026-11:0:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-11:0:8 socket hang up
VOLUMIO 11/7/2026-10:59:48 No media streams found for song 03 laura
VOLUMIO 11/7/2026-10:58:4 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-10:56:27 socket hang up
VOLUMIO 11/7/2026-10:55:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:52:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:51:46 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-10:51:22 CamillaDSP reload timed out after 10000 ms (28 connection attempts
VOLUMIO 11/7/2026-10:51:14 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-10:51:8 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(). The promise rejected with the reason undefined.
VOLUMIO 11/7/2026-10:50:7 CamillaDSP reload timed out after 10000 ms (21 connection attempts
VOLUMIO 11/7/2026-10:44:59 write EPIPE
VOLUMIO 11/7/2026-10:37:7 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-10:34:47 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-10:34:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:31:55 socket hang up
VOLUMIO 11/7/2026-10:31:47 socket hang up
VOLUMIO 11/7/2026-10:30:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:28:37 socket hang up
VOLUMIO 11/7/2026-10:28:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:27:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:27:38 socket hang up
VOLUMIO 11/7/2026-10:24:36 dns service error: unknown
MOTIVO 11/7/2026-10:24:26 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
OPERA 11/7/2026-10:24:17 Unexpected end of JSON input
VOLUMIO 11/7/2026-10:20:56 deferred is not defined
VOLUMIO 11/7/2026-10:19:15 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-10:18:15 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-10:13:43 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-10:13:40 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/7/2026-10:13:1 Cannot read property slice of null
VOLUMIO 11/7/2026-10:9:33 socket hang up
VOLUMIO 11/7/2026-10:8:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:6:24 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-10:5:20 socket hang up
VOLUMIO 11/7/2026-10:4:22 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-10:3:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-10:3:7 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/7/2026-10:2:11 Cannot read property stop of null
VOLUMIO 11/7/2026-10:1:49 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-9:59:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:59:9 socket hang up
VOLUMIO 11/7/2026-9:56:11 Cannot read property service of undefined
VOLUMIO 11/7/2026-9:55:34 Unable to resolve or reject the same promise twice
RIVO 11/7/2026-9:54:36 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 sudo: unable to resolve host yordans-rivo: System error Job for vtcs.service canceled.
VOLUMIO 11/7/2026-9:52:5 socket hang up
VOLUMIO 11/7/2026-9:51:3 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-9:50:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:50:22 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-9:41:31 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-9:39:45 getaddrinfo ENOTFOUND strm-mar-227.strm.yandex.net
VOLUMIO 11/7/2026-9:39:42 connect ETIMEDOUT 31.13.95.35:443
VOLUMIO 11/7/2026-9:39:8 dns service error: unknown
VOLUMIO 11/7/2026-9:37:59 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/7/2026-9:35:56 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-9:33:51 Unexpected end of JSON input
VOLUMIO 11/7/2026-9:33:8 Cannot read property stop of null
VOLUMIO 11/7/2026-9:31:8 Cannot read properties of null (reading slice)
VOLUMIO 11/7/2026-9:27:37 socket hang up
VOLUMIO 11/7/2026-9:26:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:25:56 socket hang up
VOLUMIO 11/7/2026-9:25:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:24:55 Cannot read property service of undefined
VOLUMIO 11/7/2026-9:24:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:24:50 socket hang up
VOLUMIO 11/7/2026-9:19:41 socket hang up
VOLUMIO 11/7/2026-9:18:46 connect ETIMEDOUT 31.13.70.9:443
VOLUMIO 11/7/2026-9:18:43 connect ECONNREFUSED 127.0.0.1:9879
SMSL 11/7/2026-9:16:54 Cannot read property slice of null
VOLUMIO 11/7/2026-9:16:22 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-9:16:11 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/7/2026-9:15:25 Cannot read properties of null (reading coreCommand)
VOLUMIO 11/7/2026-9:13:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:13:17 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-9:12:55 socket hang up
VOLUMIO 11/7/2026-9:10:56 Cannot read property name of undefined
VOLUMIO 11/7/2026-9:10:50 Cannot read property writeSync of undefined
VOLUMIO 11/7/2026-9:9:18 connect EHOSTUNREACH 192.168.30.229:1400
VOLUMIO 11/7/2026-9:8:41 socket hang up
VOLUMIO 11/7/2026-9:7:1 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-9:6:25 Failed to activate service org.bluez: timed out (service_start_timeout=25000ms)
VOLUMIO 11/7/2026-9:4:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-9:4:0 Cannot read property writeSync of undefined
VOLUMIO 11/7/2026-9:3:14 socket hang up
VOLUMIO 11/7/2026-9:2:16 socket hang up
VOLUMIO 11/7/2026-9:1:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:58:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-8:57:8 socket hang up
VOLUMIO 11/7/2026-8:56:59 fetch failed
VOLUMIO 11/7/2026-8:56:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:55:29 connect ETIMEDOUT 146.75.118.79:443
VOLUMIO 11/7/2026-8:53:55 Failed to convert napi value Null into rust type on TimelineInfo.duration
VOLUMIO 11/7/2026-8:45:4 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-8:44:19 socket hang up
VOLUMIO 11/7/2026-8:44:5 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-8:43:21 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:42:11 connect ETIMEDOUT 108.160.162.31:443
VOLUMIO 11/7/2026-8:41:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:40:43 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-8:40:35 write EPIPE
VOLUMIO 11/7/2026-8:39:46 socket hang up
VOLUMIO 11/7/2026-8:39:9 socket hang up
VOLUMIO 11/7/2026-8:38:19 socket hang up
VOLUMIO 11/7/2026-8:37:49 connect ETIMEDOUT 173.236.212.42:443
VOLUMIO 11/7/2026-8:37:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:36:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:36:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:35:33 socket hang up
VOLUMIO 11/7/2026-8:35:25 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-8:35:16 socket hang up
VOLUMIO 11/7/2026-8:33:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:32:40 Cannot read property writeSync of undefined
VOLUMIO 11/7/2026-8:25:11 Cannot read properties of null (reading message)
VOLUMIO 11/7/2026-8:24:13 socket hang up
VOLUMIO 11/7/2026-8:23:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:22:24 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/7/2026-8:20:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:20:24 socket hang up
VOLUMIO 11/7/2026-8:19:15 Cannot read property charAt of undefined
VOLUMIO 11/7/2026-8:19:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:18:38 socket hang up
VOLUMIO 11/7/2026-8:18:32 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-8:15:29 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-8:14:35 socket hang up
VOLUMIO 11/7/2026-8:13:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:10:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:9:27 socket hang up
VOLUMIO 11/7/2026-8:8:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:8:4 socket hang up
VOLUMIO 11/7/2026-8:7:21 Cannot read properties of undefined (reading split)
RIVOPLUS 11/7/2026-8:7:14 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/7/2026-8:3:8 socket hang up
VOLUMIO 11/7/2026-8:2:45 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-8:2:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:2:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:1:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-8:1:5 socket hang up
VOLUMIO 11/7/2026-7:59:30 socket hang up
VOLUMIO 11/7/2026-7:59:23 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-7:58:23 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:56:52 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:56:25 socket hang up
VOLUMIO 11/7/2026-7:49:38 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-7:49:21 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-7:48:41 socket hang up
VOLUMIO 11/7/2026-7:47:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:46:34 socket hang up
VOLUMIO 11/7/2026-7:45:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:45:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:44:49 socket hang up
VOLUMIO 11/7/2026-7:42:28 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:39:45 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:39:44 socket hang up
VOLUMIO 11/7/2026-7:38:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:38:8 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-7:31:40 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:28:55 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:28:52 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:28:25 socket hang up
RIVOPLUS 11/7/2026-7:26:15 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-7:24:39 socket hang up
VOLUMIO 11/7/2026-7:23:41 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:22:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:22:7 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:21:19 socket hang up
VOLUMIO 11/7/2026-7:18:34 PERMISSION_DENIED: Permission denied
VOLUMIO 11/7/2026-7:16:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:16:27 socket hang up
OPERA 11/7/2026-7:15:19 connect ETIMEDOUT 69.63.186.30:443
VOLUMIO 11/7/2026-7:14:45 socket hang up
VOLUMIO 11/7/2026-7:13:23 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:11:12 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-7:11:6 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-7:5:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-7:3:39 socket hang up
VOLUMIO 11/7/2026-7:2:59 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-7:1:38 socket hang up
VOLUMIO 11/7/2026-7:0:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:58:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:56:17 socket hang up
VOLUMIO 11/7/2026-6:50:31 socket hang up
VOLUMIO 11/7/2026-6:49:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:44:57 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-6:43:21 socket hang up
VOLUMIO 11/7/2026-6:43:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:42:31 socket hang up
VOLUMIO 11/7/2026-6:42:28 Cannot read property service of undefined
VOLUMIO 11/7/2026-6:41:59 connect ECONNREFUSED 127.0.0.1:9879
SMSL 11/7/2026-6:40:54 connect ETIMEDOUT 151.101.2.79:443
VOLUMIO 11/7/2026-6:38:3 socket hang up
VOLUMIO 11/7/2026-6:37:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:36:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:34:25 socket hang up
VOLUMIO 11/7/2026-6:33:32 socket hang up
VOLUMIO 11/7/2026-6:32:36 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-6:32:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:28:49 socket hang up
VOLUMIO 11/7/2026-6:27:58 deferred is not defined
VOLUMIO 11/7/2026-6:27:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:24:55 connect ETIMEDOUT 111.243.214.169:443
VOLUMIO 11/7/2026-6:24:43 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-6:21:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:20:6 connect ETIMEDOUT 185.60.216.11:443
VOLUMIO 11/7/2026-6:19:55 socket hang up
VOLUMIO 11/7/2026-6:17:24 VM operation timed out
OPERA 11/7/2026-6:16:34 connect ETIMEDOUT 104.244.46.85:443
VOLUMIO 11/7/2026-6:11:6 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-6:10:41 socket hang up
VOLUMIO 11/7/2026-6:9:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:8:11 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/7/2026-6:7:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:7:8 socket hang up
VOLUMIO 11/7/2026-6:6:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-6:5:8 socket hang up
VOLUMIO 11/7/2026-6:4:56 connect ETIMEDOUT 69.63.178.13:443
VOLUMIO 11/7/2026-6:1:21 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-6:0:27 socket hang up
VOLUMIO 11/7/2026-5:59:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:58:14 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-5:57:50 socket hang up
VOLUMIO 11/7/2026-5:56:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:55:12 socket hang up
VOLUMIO 11/7/2026-5:55:4 connect ECONNREFUSED 127.0.0.1:9879
OPERA 11/7/2026-5:54:57 connect ETIMEDOUT 162.125.34.133:443
VOLUMIO 11/7/2026-5:54:37 socket hang up
VOLUMIO 11/7/2026-5:53:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:52:17 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-5:51:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-5:48:51 deferred is not defined
VOLUMIO 11/7/2026-5:48:0 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-5:45:46 socket hang up
VOLUMIO 11/7/2026-5:44:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:43:57 Cannot set property name of undefined
VOLUMIO 11/7/2026-5:40:6 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-5:33:8 connect ETIMEDOUT 108.160.170.26:443
VOLUMIO 11/7/2026-5:33:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:32:38 socket hang up
VOLUMIO 11/7/2026-5:31:20 socket hang up
VOLUMIO 11/7/2026-5:29:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:28:14 connect ETIMEDOUT 157.240.17.14:443
VOLUMIO 11/7/2026-5:27:12 Cannot read property name of undefined
VOLUMIO 11/7/2026-5:21:55 socket hang up
VOLUMIO 11/7/2026-5:21:15 ENOTDIR: not a directory, scandir /tmp/peppyrunning
VOLUMIO 11/7/2026-5:20:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:17:30 socket hang up
VOLUMIO 11/7/2026-5:16:17 connect ETIMEDOUT 199.16.156.39:443
VOLUMIO 11/7/2026-5:16:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:11:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-5:9:22 Cannot read property slice of null
VOLUMIO 11/7/2026-5:9:0 socket hang up
VOLUMIO 11/7/2026-5:3:40 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-5:3:38 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/7/2026-5:1:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:59:49 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-4:59:47 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-4:58:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:57:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:57:25 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-4:56:36 socket hang up
VOLUMIO 11/7/2026-4:55:29 socket hang up
VOLUMIO 11/7/2026-4:51:27 socket hang up
VOLUMIO 11/7/2026-4:49:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:49:13 connect ETIMEDOUT 199.96.63.163:443
VOLUMIO 11/7/2026-4:46:58 socket hang up
VOLUMIO 11/7/2026-4:46:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:45:27 Cannot read property then of undefined
VOLUMIO 11/7/2026-4:40:54 socket hang up
VOLUMIO 11/7/2026-4:39:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:35:33 Failed to activate service org.bluez: timed out (service_start_timeout=25000ms)
VOLUMIO 11/7/2026-4:35:2 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-4:34:37 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-4:34:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-4:33:3 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:32:41 dns service error: unknown
VOLUMIO 11/7/2026-4:31:55 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:31:32 socket hang up
SMSL 11/7/2026-4:31:29 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/7/2026-4:30:43 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:30:33 connect ECONNREFUSED 127.0.0.1:9879
OPERA 11/7/2026-4:29:8 connect ETIMEDOUT 173.255.209.47:443
VOLUMIO 11/7/2026-4:27:58 socket hang up
VOLUMIO 11/7/2026-4:27:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:26:52 connect ETIMEDOUT 199.59.150.13:443
VOLUMIO 11/7/2026-4:25:41 Cannot read property slice of null
VOLUMIO 11/7/2026-4:23:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:19:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:12:57 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/no
VOLUMIO 11/7/2026-4:12:30 socket hang up
VOLUMIO 11/7/2026-4:10:15 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:8:59 Cannot read property slice of null
VOLUMIO 11/7/2026-4:8:14 socket hang up
VOLUMIO 11/7/2026-4:7:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:6:33 socket hang up
VOLUMIO 11/7/2026-4:6:23 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:5:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-4:5:13 Cannot read property volumio_info of undefined
VOLUMIO 11/7/2026-4:3:53 Cannot read property slice of null
VOLUMIO 11/7/2026-4:3:30 socket hang up
VOLUMIO 11/7/2026-4:2:32 connect ECONNREFUSED 127.0.0.1:9879
SIGMASTAR 11/7/2026-4:1:30 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-4:1:1 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-4:0:33 connect ETIMEDOUT 31.13.87.19:443
VOLUMIO 11/7/2026-3:57:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-3:53:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:53:29 Cannot read property then of undefined
VOLUMIO 11/7/2026-3:53:26 socket hang up
VOLUMIO 11/7/2026-3:52:42 socket hang up
VOLUMIO 11/7/2026-3:51:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:50:32 Not connected
VOLUMIO 11/7/2026-3:45:58 socket hang up
VOLUMIO 11/7/2026-3:45:18 connect ETIMEDOUT 108.160.166.148:443
OPERA 11/7/2026-3:43:57 connect ETIMEDOUT 128.242.240.221:443
VOLUMIO 11/7/2026-3:42:42 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-3:42:35 connect ETIMEDOUT 31.13.96.195:443
VOLUMIO 11/7/2026-3:40:27 socket hang up
VOLUMIO 11/7/2026-3:39:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:37:56 connect ETIMEDOUT 128.121.146.235:443
VOLUMIO 11/7/2026-3:35:34 Unexpected end of JSON input
VOLUMIO 11/7/2026-3:32:20 connect ETIMEDOUT 111.243.214.169:443
VOLUMIO 11/7/2026-3:29:29 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-3:23:0 connect ETIMEDOUT 54.234.18.200:443
VOLUMIO 11/7/2026-3:18:57 connect ETIMEDOUT 128.242.240.149:443
VOLUMIO 11/7/2026-3:16:34 EPERM: operation not permitted, write
VOLUMIO 11/7/2026-3:13:51 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-3:12:38 connect ETIMEDOUT 31.13.88.26:443
VOLUMIO 11/7/2026-3:11:21 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:10:51 socket hang up
VOLUMIO 11/7/2026-3:10:25 connect ETIMEDOUT 98.159.108.57:443
VOLUMIO 11/7/2026-3:10:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-3:9:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:8:44 socket hang up
VOLUMIO 11/7/2026-3:7:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:4:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-3:3:53 socket hang up
VOLUMIO 11/7/2026-2:59:57 Unable to resolve or reject the same promise twice
IFI 11/7/2026-2:59:9 certificate is not yet valid
PRIMO2REV2 11/7/2026-2:58:28 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 sudo: unable to resolve host volumioroof: System error Job for vtcs.service canceled.
VOLUMIO 11/7/2026-2:53:38 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/7/2026-2:53:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:52:24 URI malformed
VOLUMIO 11/7/2026-2:51:8 socket hang up
RIVO 11/7/2026-2:50:18 Unable to resolve or reject the same promise twice
OPERA 11/7/2026-2:48:57 Cannot read property slice of null
VOLUMIO 11/7/2026-2:48:5 socket hang up
VOLUMIO 11/7/2026-2:47:7 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:46:52 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(). The promise rejected with the reason Error:
VOLUMIO 11/7/2026-2:43:36 socket hang up
VOLUMIO 11/7/2026-2:42:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:42:13 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-2:35:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:34:50 socket hang up
VOLUMIO 11/7/2026-2:33:41 Cannot read properties of undefined (reading split)
VOLUMIO 11/7/2026-2:30:53 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-2:29:36 Cannot read property then of undefined
VOLUMIO 11/7/2026-2:27:13 socket hang up
VOLUMIO 11/7/2026-2:26:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:25:5 socket hang up
VOLUMIO 11/7/2026-2:23:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:23:33 connect ECONNREFUSED 127.0.0.1:9879
RIVOPLUS 11/7/2026-2:21:45 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-2:20:38 socket hang up
VOLUMIO 11/7/2026-2:19:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:14:38 socket hang up
VOLUMIO 11/7/2026-2:13:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:13:9 socket hang up
VOLUMIO 11/7/2026-2:11:0 socket hang up
VOLUMIO 11/7/2026-2:9:57 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-2:8:19 Chaining cycle detected for promise #
RIVOPLUS 11/7/2026-2:6:49 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-2:2:27 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-2:0:22 socket hang up
VOLUMIO 11/7/2026-2:0:4 Failed to activate service org.bluez: timed out (service_start_timeout=25000ms)
VOLUMIO 11/7/2026-1:59:45 Cannot read property slice of null
VOLUMIO 11/7/2026-1:59:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:58:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:57:29 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-1:55:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-1:54:56 connect ECONNREFUSED 202.160.129.36:443
VOLUMIO 11/7/2026-1:51:55 Cannot read property slice of null
VOLUMIO 11/7/2026-1:47:35 socket hang up
VOLUMIO 11/7/2026-1:37:18 socket hang up
VOLUMIO 11/7/2026-1:36:21 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:33:49 socket hang up
VOLUMIO 11/7/2026-1:32:28 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:31:13 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:30:48 socket hang up
VOLUMIO 11/7/2026-1:30:18 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:29:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:29:46 socket hang up
VOLUMIO 11/7/2026-1:28:11 socket hang up
VOLUMIO 11/7/2026-1:27:48 fetch failed
VOLUMIO 11/7/2026-1:27:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:25:48 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-1:21:49 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-1:21:8 Cannot read properties of undefined (reading then)
VOLUMIO 11/7/2026-1:20:25 socket hang up
VOLUMIO 11/7/2026-1:20:25 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/7/2026-1:20:10 fetch failed
VOLUMIO 11/7/2026-1:19:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:8:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:8:15 dns service error: unknown
VOLUMIO 11/7/2026-1:8:0 socket hang up
VOLUMIO 11/7/2026-1:6:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-1:5:24 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-0:57:41 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:56:4 socket hang up
VOLUMIO 11/7/2026-0:54:11 socket hang up
VOLUMIO 11/7/2026-0:52:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:52:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:52:1 socket hang up
VOLUMIO 11/7/2026-0:51:45 Unable to resolve or reject the same promise twice
VOLUMIO 11/7/2026-0:51:17 socket hang up
VOLUMIO 11/7/2026-0:51:3 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:43:20 socket hang up
VOLUMIO 11/7/2026-0:42:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:40:36 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-0:40:14 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:39:47 socket hang up
VOLUMIO 11/7/2026-0:32:32 Chaining cycle detected for promise #
RIVOPLUS 11/7/2026-0:30:41 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Transaction for volumio5-onboarding.service/start is destructive (systemd-tmpfiles-setup.service has stop job queued, but start is included in transaction). See system logs and systemctl
VOLUMIO 11/7/2026-0:30:4 socket hang up
VOLUMIO 11/7/2026-0:29:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:26:8 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/7/2026-0:23:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:22:33 socket hang up
VOLUMIO 11/7/2026-0:18:20 socket hang up
VOLUMIO 11/7/2026-0:17:53 Failed to activate service org.bluez: timed out (service_start_timeout=25000ms)
VOLUMIO 11/7/2026-0:17:50 Cannot read properties of undefined (reading service)
VOLUMIO 11/7/2026-0:16:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:14:47 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/7/2026-0:11:40 socket hang up
VOLUMIO 11/7/2026-0:10:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:10:4 Chaining cycle detected for promise #
VOLUMIO 11/7/2026-0:9:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:9:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/7/2026-0:8:41 socket hang up
VOLUMIO 11/7/2026-0:7:6 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/7/2026-0:2:18 socket hang up
VOLUMIO 11/7/2026-0:1:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:58:48 connect ETIMEDOUT 199.59.149.207:443
RIVO 11/6/2026-23:55:43 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
RIVOPLUS 11/6/2026-23:52:32 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-23:52:23 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-23:52:10 socket hang up
VOLUMIO 11/6/2026-23:51:13 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:50:45 Cannot read property service of undefined
VOLUMIO 11/6/2026-23:49:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:47:42 socket hang up
VOLUMIO 11/6/2026-23:47:3 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-23:46:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:44:43 socket hang up
VOLUMIO 11/6/2026-23:43:39 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-23:43:6 connect ECONNREFUSED 67.230.169.182:443
VOLUMIO 11/6/2026-23:42:46 connect ECONNREFUSED 127.0.0.1:9879
RIVOPLUS 11/6/2026-23:42:17 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-23:36:33 socket hang up
VOLUMIO 11/6/2026-23:35:45 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-23:35:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:35:26 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-23:33:42 CamillaDSP is not running
VOLUMIO 11/6/2026-23:31:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:29:8 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/6/2026-23:24:23 socket hang up
VOLUMIO 11/6/2026-23:23:25 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-23:21:20 socket hang up
VOLUMIO 11/6/2026-23:20:48 socket hang up
VOLUMIO 11/6/2026-23:20:22 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/6/2026-23:17:54 Cannot read property then of undefined
VOLUMIO 11/6/2026-23:15:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-23:11:42 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-23:0:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:59:16 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-22:57:36 Cannot read property stop of null
VOLUMIO 11/6/2026-22:57:11 dns service error: unknown
VOLUMIO 11/6/2026-22:57:3 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/6/2026-22:52:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:51:0 socket hang up
VOLUMIO 11/6/2026-22:49:18 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-22:45:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:43:11 socket hang up
RIVOPLUS 11/6/2026-22:42:49 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-22:40:22 connect ETIMEDOUT 146.75.2.79:443
VOLUMIO 11/6/2026-22:38:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:37:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:36:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:36:0 socket hang up
EMOTIVADRS1 11/6/2026-22:34:53 [object Object]
RIVOPLUS 11/6/2026-22:34:27 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(). The promise rejected with the reason Error:
VOLUMIO 11/6/2026-22:28:38 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/6/2026-22:28:29 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-22:25:52 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-22:25:43 socket hang up
VOLUMIO 11/6/2026-22:23:22 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-22:21:55 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-22:14:10 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-22:9:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-22:7:55 dns service error: unknown
VOLUMIO 11/6/2026-22:7:31 socket hang up
VOLUMIO 11/6/2026-22:6:58 Chaining cycle detected for promise #
RIVO 11/6/2026-22:4:17 upnp: statusCode 500 & upnpErrorCode s:ClientUPnPError701
VOLUMIO 11/6/2026-22:4:3 Cannot read property slice of null
RIVOPLUS 11/6/2026-22:4:2 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-22:3:2 connect ETIMEDOUT 151.101.222.79:443
VOLUMIO 11/6/2026-21:57:22 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-21:56:50 unable to verify the first certificate
VOLUMIO 11/6/2026-21:53:35 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-21:53:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-21:48:49 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(). The promise rejected with the reason Error:
UNDEFINED 11/6/2026-21:41:59 Cannot read property type of undefined
VOLUMIO 11/6/2026-21:41:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-21:41:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-21:40:59 socket hang up
VOLUMIO 11/6/2026-21:36:3 Unable to resolve or reject the same promise twice
UNDEFINED 11/6/2026-21:35:10 write EPIPE
RIVOPLUS 11/6/2026-21:31:31 dns service error: unknown
RIVOPLUS 11/6/2026-21:24:44 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-21:24:30 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-21:24:27 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-21:21:45 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-21:20:41 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-21:20:18 socket hang up
VOLUMIO 11/6/2026-21:11:6 connect EHOSTUNREACH 192.168.1.126:1400
VOLUMIO 11/6/2026-21:10:12 VM operation timed out
VOLUMIO 11/6/2026-21:6:7 Command failed: /usr/bin/sudo /bin/mv /home/volumio/.asoundrc /etc/asound.conf /bin/mv: cannot move /home/volumio/.asoundrc to /etc/asound.conf: Operation not permitted
VOLUMIO 11/6/2026-20:59:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-20:57:58 socket hang up
VOLUMIO 11/6/2026-20:56:5 dns service error: unknown
VOLUMIO 11/6/2026-20:54:45 Unable to resolve or reject the same promise twice
RIVOPLUS 11/6/2026-20:51:47 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-20:46:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-20:45:51 socket hang up
VOLUMIO 11/6/2026-20:45:29 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-20:43:50 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-20:38:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-20:37:13 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-20:36:22 connect ECONNRESET 127.0.0.1:9879
VOLUMIO 11/6/2026-20:35:24 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-20:26:18 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-20:25:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-20:23:57 socket hang up
VOLUMIO 11/6/2026-20:19:59 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-20:18:10 Cannot read property service of undefined
VOLUMIO 11/6/2026-20:16:10 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-20:13:53 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-20:12:42 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-20:10:53 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-20:10:36 getaddrinfo -3007
VOLUMIO 11/6/2026-20:9:0 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-20:7:25 Cannot read property service of null
VOLUMIO 11/6/2026-20:7:0 connect ECONNREFUSED 127.0.0.1:9879
RIVOPLUS 11/6/2026-20:5:23 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-20:5:12 socket hang up
VOLUMIO 11/6/2026-20:3:38 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(). The promise rejected with the reason undefined.
VOLUMIO 11/6/2026-20:2:15 Maximum call stack size exceeded
VOLUMIO 11/6/2026-20:2:1 Unable to resolve or reject the same promise twice
RIVO 11/6/2026-19:59:41 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-19:56:23 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:51:4 Cannot read property slice of null
VOLUMIO 11/6/2026-19:47:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-19:46:8 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-19:45:58 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(). The promise rejected with the reason Error:
VOLUMIO 11/6/2026-19:39:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-19:39:40 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:37:35 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-19:36:50 socket hang up
VOLUMIO 11/6/2026-19:36:24 Cannot read property length of undefined
VOLUMIO 11/6/2026-19:36:19 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:35:14 CamillaDSP reload timed out after 10000 ms (39 connection attempts
VOLUMIO 11/6/2026-19:34:33 Cannot read property then of undefined
VOLUMIO 11/6/2026-19:33:56 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-19:33:53 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:33:29 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-19:31:42 socket hang up
VOLUMIO 11/6/2026-19:25:31 Failed to convert napi value Null into rust type on TimelineInfo.duration
VOLUMIO 11/6/2026-19:24:47 Cannot read properties of null (reading slice)
VOLUMIO 11/6/2026-19:23:51 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-19:23:37 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-19:23:10 socket hang up
VOLUMIO 11/6/2026-19:21:53 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:19:49 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:18:22 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:16:19 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-19:16:8 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-19:13:28 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-19:12:1 [50@0] {addtagid} No such song
VOLUMIO 11/6/2026-19:10:50 dns service error: unknown
VOLUMIO 11/6/2026-19:9:13 unable to verify the first certificate
VOLUMIO 11/6/2026-19:7:50 Cannot read property @ of null
PRIMO2REV2 11/6/2026-19:5:37 Cannot read properties of undefined (reading service)
RIVO 11/6/2026-19:5:22 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-19:2:58 Cannot read properties of undefined (reading split)
PRIMO2REV2 11/6/2026-19:2:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-18:57:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-18:55:38 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/6/2026-18:54:38 read ECONNRESET
VOLUMIO 11/6/2026-18:52:59 Unable to resolve or reject the same promise twice
RIVOPLUS 11/6/2026-18:49:23 write EPIPE
VOLUMIO 11/6/2026-18:46:49 socket hang up
VOLUMIO 11/6/2026-18:45:11 Message recipient disconnected from message bus without replying
VOLUMIO 11/6/2026-18:41:10 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-18:37:9 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-18:36:51 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/6/2026-18:35:3 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-18:33:32 socket hang up
VOLUMIO 11/6/2026-18:31:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-18:31:21 socket hang up
VOLUMIO 11/6/2026-18:29:46 Unable to resolve or reject the same promise twice
UNDEFINED 11/6/2026-18:27:50 Cannot read property then of undefined
VOLUMIO 11/6/2026-18:25:13 write EPIPE
VOLUMIO 11/6/2026-18:22:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-18:20:34 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-18:16:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-18:14:46 Cannot read property service of undefined
VOLUMIO 11/6/2026-18:12:35 Cannot read property slice of null
VOLUMIO 11/6/2026-18:10:51 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-18:6:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-18:4:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-18:3:39 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-18:3:8 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-18:2:54 dns service error: unknown
VOLUMIO 11/6/2026-18:2:19 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-17:57:53 Cannot read property slice of null
VOLUMIO 11/6/2026-17:56:12 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/6/2026-17:56:6 connect ECONNREFUSED 127.0.0.1:9879
OPERA 11/6/2026-17:55:26 connect ETIMEDOUT 31.13.91.6:443
VOLUMIO 11/6/2026-17:55:4 Cannot read property then of undefined
VOLUMIO 11/6/2026-17:54:34 connect ETIMEDOUT 104.244.43.104:443
VOLUMIO 11/6/2026-17:53:55 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-17:51:16 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/6/2026-17:49:35 The maximum number of active connections for UID 1000 has been reached
VOLUMIO 11/6/2026-17:46:43 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-17:46:42 Cannot read properties of undefined (reading refreshI18nConfig)
VOLUMIO 11/6/2026-17:45:34 connect ETIMEDOUT 108.160.166.142:443
VOLUMIO 11/6/2026-17:44:3 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-17:43:59 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/6/2026-17:42:9 Cannot read property service of undefined
VOLUMIO 11/6/2026-17:39:37 file /mnt/USB/KINGSTON/audio/DDT_-_Inache/CD1/Ddt - Inache- Disc 1 of 2.cue does not exist
VOLUMIO 11/6/2026-17:35:58 Cannot read property service of undefined
PROJECTSBUS2 11/6/2026-17:28:34 write EPIPE
VOLUMIO 11/6/2026-17:27:41 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-17:27:4 Cannot read properties of undefined (reading sendMpdCommand)
VOLUMIO 11/6/2026-17:26:53 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-17:26:44 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-17:26:14 socket hang up
VOLUMIO 11/6/2026-17:26:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-17:24:8 socket hang up
VOLUMIO 11/6/2026-17:23:5 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-17:15:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-17:15:8 socket hang up
VOLUMIO 11/6/2026-17:13:25 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-17:12:13 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-17:9:21 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-17:6:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-16:57:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-16:56:53 socket hang up
VOLUMIO 11/6/2026-16:56:46 read ETIMEDOUT
VOLUMIO 11/6/2026-16:54:57 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-16:52:33 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-16:48:53 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-16:46:19 Cannot read property then of undefined
VOLUMIO 11/6/2026-16:44:47 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/6/2026-16:42:15 Cannot read properties of null (reading slice)
VOLUMIO 11/6/2026-16:42:8 connect ECONNREFUSED 31.13.87.34:443
VOLUMIO 11/6/2026-16:37:54 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-16:37:5 Cannot read property name of null
VOLUMIO 11/6/2026-16:37:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-16:35:42 socket hang up
VOLUMIO 11/6/2026-16:31:15 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/6/2026-16:29:46 connect ETIMEDOUT 45.114.11.25:443
VOLUMIO 11/6/2026-16:24:2 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-16:23:3 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-16:21:30 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-16:18:56 exec is not defined
VOLUMIO 11/6/2026-16:18:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-16:18:21 socket hang up
VOLUMIO 11/6/2026-16:16:20 Cannot read property then of undefined
VOLUMIO 11/6/2026-16:16:8 dns service error: unknown
VOLUMIO 11/6/2026-16:15:42 exec is not defined
VOLUMIO 11/6/2026-16:15:15 Not connected
VOLUMIO 11/6/2026-16:12:52 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-16:9:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-16:8:53 socket hang up
VOLUMIO 11/6/2026-16:8:19 EBADF: bad file descriptor, close
VOLUMIO 11/6/2026-16:7:1 connect ETIMEDOUT 128.242.240.218:443
VOLUMIO 11/6/2026-16:3:55 Cannot convert argument to a ByteString because the character at index 512 has a value of 8230 which is greater than 255.
VOLUMIO 11/6/2026-16:2:56 exec is not defined
VOLUMIO 11/6/2026-15:58:35 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:58:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-15:57:54 Failed to send server command subscribe
VOLUMIO 11/6/2026-15:57:43 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-15:55:26 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-15:55:11 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-15:54:59 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-15:53:39 Cannot read properties of null (reading slice)
VOLUMIO 11/6/2026-15:53:10 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/6/2026-15:52:31 connect ECONNREFUSED 127.0.0.1:9879
PRIMOPLUS 11/6/2026-15:49:47 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/6/2026-15:48:17 The value NaN is not a number
VOLUMIO 11/6/2026-15:47:47 addMembership ENODEV
VOLUMIO 11/6/2026-15:45:22 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-15:44:37 socket hang up
VOLUMIO 11/6/2026-15:41:48 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-15:40:25 socket hang up
VOLUMIO 11/6/2026-15:38:37 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:37:18 connect ETIMEDOUT 199.96.59.61:443
VOLUMIO 11/6/2026-15:35:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:33:51 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-15:33:42 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-15:31:57 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:31:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-15:31:11 socket hang up
VOLUMIO 11/6/2026-15:30:57 Cannot read property length of null
VOLUMIO 11/6/2026-15:29:56 read ECONNRESET
VOLUMIO 11/6/2026-15:28:29 dns service error: unknown
VOLUMIO 11/6/2026-15:19:24 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:17:22 connect ENETUNREACH 104.244.46.63:443
VOLUMIO 11/6/2026-15:14:3 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-15:13:10 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:12:9 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-15:9:40 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-15:6:48 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-15:6:12 Cannot read property slice of null
RIVOPLUS 11/6/2026-15:4:40 Cannot read properties of undefined (reading toUpperCase)
VOLUMIO 11/6/2026-15:3:38 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-15:2:53 socket hang up
RIVOPLUS 11/6/2026-15:1:8 Cannot read property slice of null
VOLUMIO 11/6/2026-15:1:6 dns service error: unknown
VOLUMIO 11/6/2026-14:58:57 deferred is not defined
VOLUMIO 11/6/2026-14:57:54 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/6/2026-14:56:3 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-14:55:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-14:55:12 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-14:54:17 socket hang up
VOLUMIO 11/6/2026-14:53:21 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-14:51:40 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-14:51:21 Cannot read property service of undefined
VOLUMIO 11/6/2026-14:51:19 socket hang up
VOLUMIO 11/6/2026-14:47:25 connect ETIMEDOUT 31.13.70.13:443
VOLUMIO 11/6/2026-14:47:2 Cannot set properties of undefined (setting name)
VOLUMIO 11/6/2026-14:46:9 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:44:48 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:41:1 Cannot read property charAt of undefined
VOLUMIO 11/6/2026-14:40:39 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-14:38:36 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-14:38:17 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-14:36:44 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-14:36:33 connect ETIMEDOUT 104.244.46.186:443
VOLUMIO 11/6/2026-14:36:4 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:32:57 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-14:32:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-14:31:49 socket hang up
VOLUMIO 11/6/2026-14:30:47 getaddrinfo -3007
VOLUMIO 11/6/2026-14:29:13 connect ETIMEDOUT 199.59.149.205:443
VOLUMIO 11/6/2026-14:28:16 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-14:28:6 Operation timeout
RIVOPLUS 11/6/2026-14:27:27 Premature end of data in tag br line 187 (Line: 195, Column: 7)
VOLUMIO 11/6/2026-14:27:9 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(). The promise rejected with the reason undefined.
VOLUMIO 11/6/2026-14:23:6 dns service error: unknown
VOLUMIO 11/6/2026-14:18:50 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-14:18:36 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-14:17:33 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-14:17:5 Cannot read properties of undefined (reading plugin_type)
VOLUMIO 11/6/2026-14:16:13 dns service error: unknown
VOLUMIO 11/6/2026-14:13:54 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:11:46 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-14:9:12 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:9:9 Command failed: /usr/bin/wget -O /tmp/EQfile.txt https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/resultsChoose your headphone/%20ParametricEQ.txt --2026-11-06 14:09:09-- https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/resultsChoose%20your%20headphone/%20ParametricEQ.txt Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.111.133, 185.199.110.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2026-11-06 14:09:09 ERROR 404: Not Found.
VOLUMIO 11/6/2026-14:9:4 Command failed: /usr/bin/wget -O /tmp/EQfile.txt https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/resultsChoose your headphone/%20ParametricEQ.txt --2026-11-06 14:08:58-- https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/resultsChoose%20your%20headphone/%20ParametricEQ.txt Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133, 185.199.110.133, 185.199.108.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2026-11-06 14:08:58 ERROR 404: Not Found.
VOLUMIO 11/6/2026-14:9:1 connect ETIMEDOUT 108.160.166.9:443
VOLUMIO 11/6/2026-14:6:5 EPERM: operation not permitted, write
VOLUMIO 11/6/2026-14:5:42 Cannot read property unexport of undefined
VOLUMIO 11/6/2026-14:4:52 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-14:0:13 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/6/2026-13:55:28 connect ETIMEDOUT 128.242.240.91:443
VOLUMIO 11/6/2026-13:54:33 Cannot read properties of null (reading slice)
FERRUMBROEN 11/6/2026-13:54:26 write EPIPE
VOLUMIO 11/6/2026-13:53:58 Cannot read property writeSync of undefined
VOLUMIO 11/6/2026-13:51:40 connect ETIMEDOUT 69.171.227.37:443
FERRUMBROEN 11/6/2026-13:51:27 write EPIPE
RIVO 11/6/2026-13:51:18 addMembership ENODEV
VOLUMIO 11/6/2026-13:51:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:51:10 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-13:50:49 socket hang up
VOLUMIO 11/6/2026-13:50:4 Cannot read property then of undefined
FERRUMBROEN 11/6/2026-13:45:20 dns service error: unknown
OPERA 11/6/2026-13:44:57 connect ETIMEDOUT 108.160.172.200:443
FERRUMBROEN 11/6/2026-13:43:22 write EPIPE
VOLUMIO 11/6/2026-13:42:11 socket hang up
FERRUMBROEN 11/6/2026-13:39:51 write EPIPE
VOLUMIO 11/6/2026-13:39:30 Cannot read property then of undefined
MOTIVO 11/6/2026-13:37:41 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(). The promise rejected with the reason Error:
OPERA 11/6/2026-13:35:58 connect ETIMEDOUT 154.92.16.97:443
VOLUMIO 11/6/2026-13:35:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:35:7 socket hang up
OPERA 11/6/2026-13:33:38 connect ETIMEDOUT 185.60.219.41:443
VOLUMIO 11/6/2026-13:32:26 connect ETIMEDOUT 202.160.129.37:443
VOLUMIO 11/6/2026-13:31:40 PERMISSION_DENIED: Permission denied
UNDEFINED 11/6/2026-13:31:36 Cannot read properties of null (reading replace)
UNDEFINED 11/6/2026-13:31:8 connect ECONNRESET 34.49.30.2:80
VOLUMIO 11/6/2026-13:30:25 Cannot read property slice of null
VOLUMIO 11/6/2026-13:25:36 dns service error: unknown
VOLUMIO 11/6/2026-13:24:1 connect ECONNREFUSED 103.246.246.144:443
VOLUMIO 11/6/2026-13:23:31 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/6/2026-13:20:44 dns service error: unknown
VOLUMIO 11/6/2026-13:20:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:19:56 connect ETIMEDOUT 202.160.129.37:443
VOLUMIO 11/6/2026-13:19:32 dns service error: unknown
VOLUMIO 11/6/2026-13:19:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:18:56 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-13:18:46 socket hang up
VOLUMIO 11/6/2026-13:18:29 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-13:17:11 Cannot read property slice of null
VOLUMIO 11/6/2026-13:16:6 Cannot read property slice of null
VOLUMIO 11/6/2026-13:13:17 connect ETIMEDOUT 74.86.151.167:443
VOLUMIO 11/6/2026-13:11:5 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:10:44 connect ETIMEDOUT 174.36.228.136:443
VOLUMIO 11/6/2026-13:9:32 socket hang up
VOLUMIO 11/6/2026-13:6:27 connect ETIMEDOUT 128.242.240.85:443
VOLUMIO 11/6/2026-13:6:22 connect ETIMEDOUT 199.59.150.12:443
VOLUMIO 11/6/2026-13:3:28 connect ETIMEDOUT 31.13.88.169:443
VOLUMIO 11/6/2026-13:2:59 Not running
VOLUMIO 11/6/2026-13:0:37 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-13:0:14 socket hang up
VOLUMIO 11/6/2026-12:59:56 dns service error: unknown
VOLUMIO 11/6/2026-12:59:19 getaddrinfo ENOTFOUND ws.audioscrobbler.com
VOLUMIO 11/6/2026-12:59:15 connect ETIMEDOUT 150.107.3.176:443
VOLUMIO 11/6/2026-12:57:16 connect ECONNREFUSED 128.242.240.157:443
VOLUMIO 11/6/2026-12:56:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-12:53:42 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:53:36 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:53:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:52:12 connect ETIMEDOUT 199.59.149.231:443
OPERA 11/6/2026-12:52:0 connect ETIMEDOUT 31.13.73.169:443
VOLUMIO 11/6/2026-12:50:45 connect ETIMEDOUT 168.143.171.189:443
VOLUMIO 11/6/2026-12:49:25 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-12:49:5 connect ETIMEDOUT 104.244.43.167:443
VOLUMIO 11/6/2026-12:48:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-12:47:32 socket hang up
VOLUMIO 11/6/2026-12:43:53 connect ETIMEDOUT 199.96.59.19:443
VOLUMIO 11/6/2026-12:43:7 connect ETIMEDOUT 104.244.43.231:443
VOLUMIO 11/6/2026-12:40:53 socket hang up
VOLUMIO 11/6/2026-12:39:45 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-12:37:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-12:37:7 socket hang up
OPERA 11/6/2026-12:29:54 connect ETIMEDOUT 118.193.240.41:443
VOLUMIO 11/6/2026-12:29:22 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:24:25 ENOENT: no such file or directory, unlink /tmp/ptDGVO3JFfSyTQcNyCD3LPDk5DNomcZwbape3kd30UslVeyA3AhfDLB8XQ58udq27l9tDN9gTPZwbzmiWyZ7xi1oFzUPbUCjcqWU
VOLUMIO 11/6/2026-12:22:37 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:19:54 Chaining cycle detected for promise #
RIVOPLUS 11/6/2026-12:19:46 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:19:36 connect ETIMEDOUT 128.121.146.235:443
VOLUMIO 11/6/2026-12:17:32 Unable to resolve or reject the same promise twice
RIVOPLUS 11/6/2026-12:17:29 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:12:22 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-12:6:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:5:47 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-12:3:2 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-12:0:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-12:0:34 socket hang up
VOLUMIO 11/6/2026-12:0:6 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(). The promise rejected with the reason Error:
VOLUMIO 11/6/2026-11:55:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-11:55:11 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-11:53:23 socket hang up
VOLUMIO 11/6/2026-11:53:16 The data argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received undefined
VOLUMIO 11/6/2026-11:51:42 CamillaDSP is not running
VOLUMIO 11/6/2026-11:45:41 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-11:44:2 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-11:43:40 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-11:42:55 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-11:38:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-11:38:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-11:37:50 socket hang up
VOLUMIO 11/6/2026-11:36:56 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/6/2026-11:36:40 Cannot read properties of null (reading printToastMessage)
VOLUMIO 11/6/2026-11:36:17 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-11:31:11 connect ETIMEDOUT 96.44.137.28:443
VOLUMIO 11/6/2026-11:29:21 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-11:28:48 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-11:28:36 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-11:27:38 write EPIPE
VOLUMIO 11/6/2026-11:16:39 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-11:13:49 certificate is not yet valid
VOLUMIO 11/6/2026-11:12:14 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-11:11:50 socket hang up
VOLUMIO 11/6/2026-11:11:41 Cannot read property replace of undefined
VOLUMIO 11/6/2026-11:9:28 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-11:8:51 Unable to resolve or reject the same promise twice
SIGMASTAR 11/6/2026-11:6:30 connect ETIMEDOUT 74.86.226.234:443
VOLUMIO 11/6/2026-11:4:6 addMembership ENODEV
VOLUMIO 11/6/2026-11:4:3 Cannot read property replace of undefined
OPERA 11/6/2026-11:3:26 connect ETIMEDOUT 168.143.171.189:443
VOLUMIO 11/6/2026-11:2:29 connect ETIMEDOUT 168.143.171.186:443
VOLUMIO 11/6/2026-11:1:33 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-10:59:55 connect ETIMEDOUT 128.121.243.76:443
VOLUMIO 11/6/2026-10:59:29 socket hang up
VOLUMIO 11/6/2026-10:59:26 connect ETIMEDOUT 128.121.146.235:443
VOLUMIO 11/6/2026-10:57:39 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
VOLUMIO 11/6/2026-10:55:44 dns service error: unknown
VOLUMIO 11/6/2026-10:51:34 connect ECONNREFUSED 127.0.0.1:9879
SIGMASTAR 11/6/2026-10:51:7 MCU command failed: no MCU confirmation for SET LEDR 255 after 3 attempts (exit 1)
VOLUMIO 11/6/2026-10:49:11 Cannot read properties of undefined (reading plugin_type)
VOLUMIO 11/6/2026-10:48:46 connect ETIMEDOUT 108.160.169.179:443
VOLUMIO 11/6/2026-10:47:30 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-10:45:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-10:44:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-10:44:5 socket hang up
VOLUMIO 11/6/2026-10:42:3 Chaining cycle detected for promise #
OPERA 11/6/2026-10:38:34 connect ETIMEDOUT 104.244.46.52:443
VOLUMIO 11/6/2026-10:37:8 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-10:28:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-10:28:7 socket hang up
PRIMO2REV2 11/6/2026-10:27:7 Cannot read property service of undefined
UNDEFINED 11/6/2026-10:24:24
VOLUMIO 11/6/2026-10:24:2 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-10:23:17 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-10:14:1 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-10:9:54 dns service error: unknown
VOLUMIO 11/6/2026-10:9:14 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-10:6:1 Cannot read property writeSync of undefined
VOLUMIO 11/6/2026-10:5:58 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-10:4:32 socket hang up
UNDEFINED 11/6/2026-10:3:2 Cannot read property then of undefined
VOLUMIO 11/6/2026-10:3:1 Cannot read property stop of null
VOLUMIO 11/6/2026-9:59:54 Cannot read property service of undefined
VOLUMIO 11/6/2026-9:59:48 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-9:58:51 connect ETIMEDOUT 108.160.167.159:443
VOLUMIO 11/6/2026-9:58:39 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-9:58:7 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
OPERA 11/6/2026-9:57:20 connect ETIMEDOUT 108.160.165.11:443
PRIMO2REV2 11/6/2026-9:52:11 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-9:50:9 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-9:49:27 socket hang up
VOLUMIO 11/6/2026-9:49:2 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-9:48:14 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Job for volumio5-onboarding.service failed because the control process exited with error code. See systemctl
OPERA 11/6/2026-9:46:11 connect ETIMEDOUT 50.23.209.199:443
VOLUMIO 11/6/2026-9:44:7 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-9:42:48 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/6/2026-9:42:48 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/no
VOLUMIO 11/6/2026-9:41:33 Command failed: /usr/bin/wget -O /tmp/EQfile.txt https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results4882 Sony WH-1000XM3/Sony%20WH-1000XM3%20ParametricEQ.txt --2026-11-06 09:41:31-- https://raw.githubusercontent.com/jaakkopasanen/AutoEq/master/results4882%20%20Sony%20WH-1000XM3/Sony%20WH-1000XM3%20ParametricEQ.txt Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.111.133, 185.199.109.133, 185.199.110.133, ... Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.111.133|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2026-11-06 09:41:31 ERROR 404: Not Found.
VOLUMIO 11/6/2026-9:40:11 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-9:38:25 socket hang up
VOLUMIO 11/6/2026-9:36:50 Unable to resolve or reject the same promise twice
RIVO 11/6/2026-9:28:46 Cannot read properties of null (reading 0)
VOLUMIO 11/6/2026-9:27:47 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/6/2026-9:25:46 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-9:25:19 spawn /data/plugins/audio_interface/fusiondsp/camilladsp ENOENT
VOLUMIO 11/6/2026-9:22:18 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-9:22:16 Cannot read property service of undefined
VOLUMIO 11/6/2026-9:21:30 listen EADDRINUSE: address already in use :::6599
RIVO 11/6/2026-9:19:52 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-9:18:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-9:16:58 socket hang up
VOLUMIO 11/6/2026-9:16:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-9:15:51 socket hang up
VOLUMIO 11/6/2026-9:12:10 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-9:7:49 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-9:6:53 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-9:4:20 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-9:3:58 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-8:59:56 connect ETIMEDOUT 104.244.46.185:443
VOLUMIO 11/6/2026-8:58:38 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-8:56:59 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-8:49:47 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-8:45:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-8:43:39 socket hang up
VOLUMIO 11/6/2026-8:41:27 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-8:33:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-8:33:27 socket hang up
VOLUMIO 11/6/2026-8:26:54 addMembership ENODEV
VOLUMIO 11/6/2026-8:20:47 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-8:19:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-8:19:24 socket hang up
VOLUMIO 11/6/2026-8:13:16 fetch failed
VOLUMIO 11/6/2026-8:9:30 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-8:0:44 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-7:59:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-7:58:58 Chaining cycle detected for promise #
OPERA 11/6/2026-7:58:56 connect ETIMEDOUT 199.59.150.45:443
VOLUMIO 11/6/2026-7:56:29 file /mnt/NAS/Public/Tsuyoshi Yamamoto Trio - Misty/Tsuyoshi Yamamoto trio - Misty.cue does not exist
VOLUMIO 11/6/2026-7:55:3 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-7:50:48 socket hang up
VOLUMIO 11/6/2026-7:48:42 socket hang up
MINIDSPSHD 11/6/2026-7:43:34 Cannot read property service of undefined
VOLUMIO 11/6/2026-7:34:45 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-7:31:25 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-7:31:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-7:28:32 socket hang up
VOLUMIO 11/6/2026-7:25:31 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/6/2026-7:25:19 Unable to resolve or reject the same promise twice
UNDEFINED 11/6/2026-7:11:9 Cannot read property then of undefined
VOLUMIO 11/6/2026-7:10:6 Unable to resolve or reject the same promise twice
RIVOPLUS 11/6/2026-7:6:58 CamillaDSP reload timed out after 10000 ms (38 connection attempts
VOLUMIO 11/6/2026-7:5:50 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-7:5:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-7:4:28 socket hang up
VOLUMIO 11/6/2026-6:59:48 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-6:58:10 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-6:57:32 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-6:47:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-6:46:59 socket hang up
VOLUMIO 11/6/2026-6:42:38 getaddrinfo ENOTFOUND ws.audioscrobbler.com
VOLUMIO 11/6/2026-6:38:42 Cannot read properties of undefined (reading then)
VOLUMIO 11/6/2026-6:37:49 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-6:36:31 read ECONNRESET
VOLUMIO 11/6/2026-6:31:58 read ECONNRESET
VOLUMIO 11/6/2026-6:31:58 read ECONNRESET
VOLUMIO 11/6/2026-6:31:32 read ECONNRESET
VOLUMIO 11/6/2026-6:22:5 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-6:22:2 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-6:21:35 socket hang up
VOLUMIO 11/6/2026-6:12:28 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-6:8:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-6:7:47 socket hang up
VOLUMIO 11/6/2026-6:1:54 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/6/2026-6:1:19 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-5:59:40 connect ETIMEDOUT 103.39.76.66:443
VOLUMIO 11/6/2026-5:57:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-5:57:21 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-5:57:4 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-5:56:14 socket hang up
VOLUMIO 11/6/2026-5:48:30 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-5:45:39 Unable to resolve or reject the same promise twice
SMSL 11/6/2026-5:45:0 connect ETIMEDOUT 108.160.165.139:443
VOLUMIO 11/6/2026-5:43:30 read ETIMEDOUT
SMSL 11/6/2026-5:41:39 connect ETIMEDOUT 151.101.2.79:443
VOLUMIO 11/6/2026-5:40:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-5:39:31 socket hang up
VOLUMIO 11/6/2026-5:32:2 Cannot read properties of undefined (reading on)
VOLUMIO 11/6/2026-5:31:32 Cannot read properties of undefined (reading split)
VOLUMIO 11/6/2026-5:20:46 socket hang up
VOLUMIO 11/6/2026-5:15:31 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-5:14:44 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-5:12:53 socket hang up
OPERA 11/6/2026-5:9:46 connect ETIMEDOUT 173.208.182.68:443
SMSL 11/6/2026-5:8:52 connect ETIMEDOUT 67.228.235.93:443
VOLUMIO 11/6/2026-4:58:17 Cannot read property service of undefined
VOLUMIO 11/6/2026-4:50:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:50:10 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-4:49:47 socket hang up
VOLUMIO 11/6/2026-4:39:17 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-4:38:51 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(). The promise rejected with the reason Error:
VOLUMIO 11/6/2026-4:37:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:36:12 socket hang up
VOLUMIO 11/6/2026-4:33:51 Cannot read properties of undefined (reading service)
VOLUMIO 11/6/2026-4:30:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:28:6 socket hang up
VOLUMIO 11/6/2026-4:22:4 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:21:37 socket hang up
VOLUMIO 11/6/2026-4:12:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:11:11 socket hang up
VOLUMIO 11/6/2026-4:9:28 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:8:3 socket hang up
VOLUMIO 11/6/2026-4:3:52 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-4:1:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-4:0:41 socket hang up
VOLUMIO 11/6/2026-3:59:20 write EPIPE
VOLUMIO 11/6/2026-3:57:5 fetch failed
VOLUMIO 11/6/2026-3:55:54 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-3:55:27 socket hang up
VOLUMIO 11/6/2026-3:49:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-3:46:26 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-3:38:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-3:37:8 socket hang up
VOLUMIO 11/6/2026-3:37:4 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/6/2026-3:36:20 socket hang up
VOLUMIO 11/6/2026-3:33:21 Chaining cycle detected for promise #
RIVO 11/6/2026-3:31:47 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-3:19:45 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-3:19:31 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-3:13:59 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-3:12:42 socket hang up
VOLUMIO 11/6/2026-3:12:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-3:12:10 socket hang up
VOLUMIO 11/6/2026-3:8:59 ENOENT: no such file or directory, unlink /tmp/dm5YtduUGqrIiFOeQymgQDULTDU7I78Yd3ZOCAODAt58ID2JQRBEDDORRaRJfPDZBabLaymUvjiR7vVzjl8M3DHbVbnDaAmBwr1D
SMSL 11/6/2026-3:6:34 The value NaN is not a number
VOLUMIO 11/6/2026-3:1:44 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(). The promise rejected with the reason undefined.
VOLUMIO 11/6/2026-2:58:25 Cannot read property replace of undefined
SIGMASTAR 11/6/2026-2:57:50 MCU command failed: no MCU confirmation for SET LEDR 171 after 3 attempts (exit 1)
VOLUMIO 11/6/2026-2:57:36 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/6/2026-2:57:34 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-2:57:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-2:57:7 socket hang up
VOLUMIO 11/6/2026-2:55:42 socket hang up
VOLUMIO 11/6/2026-2:55:6 certificate is not yet valid
SIGMASTAR 11/6/2026-2:50:45 Port is not open
VOLUMIO 11/6/2026-2:40:12 ENOENT: no such file or directory, unlink /tmp/zzBdYLLXLfiRuexaUQibwt1wkslCqASWlNi9bY2CtBLDd6E1fgigrne0XxiRK0fGQNgFFTvDX5Kr5KHFbk2vTLAgBznEjtmwNhbu
VOLUMIO 11/6/2026-2:34:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-2:33:7 socket hang up
VOLUMIO 11/6/2026-2:29:18 ENOENT: no such file or directory, unlink /tmp/ESDgRV4BvcnSq0PMBIofI1aRqOUR5fcFsezqT3MIZjd0jvPKlt22ZBTDaaVY66MS2lBPtPBZKv5xOAk7FDo38rhEvF7bjUOo6gL5
VOLUMIO 11/6/2026-2:29:11 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-2:27:37 ENOSPC: no space left on device, mkdir /data/plugins/music_service/ytmusic/.yt-dlp/cookies
VOLUMIO 11/6/2026-2:24:49 Chaining cycle detected for promise #
VOLUMIO 11/6/2026-2:14:8 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/6/2026-2:12:29 ENOENT: no such file or directory, unlink /tmp/r5o1u5jpS0Fshxp2IMacSaMmtcCa9W2QnEGP9hDoH3f3oUnG0nWBKVMcPp6MU9FiEQbmnYdeqUrVXMY1oYTXLusI0wGqq5im9CI7
VOLUMIO 11/6/2026-2:5:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-2:4:57 socket hang up
VOLUMIO 11/6/2026-1:57:58 ENOENT: no such file or directory, unlink /tmp/Q6gcOJ6VKaKwP2TRIlTciN6isDL6z9UoTOMBsaIqgr0Fz631atRY6exBex1jpBQo5Ftw8ayzN3h0ZGc58QarjxeRSvDFP9wV5oAC
VOLUMIO 11/6/2026-1:55:7 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-1:54:11 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-1:53:2 socket hang up
VOLUMIO 11/6/2026-1:51:58 connect ECONNREFUSED 127.0.0.1:9879
UNDEFINED 11/6/2026-1:51:38 Cannot read properties of null (reading replace)
UNDEFINED 11/6/2026-1:51:11 read ECONNRESET
VOLUMIO 11/6/2026-1:50:34 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-1:49:15 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
VOLUMIO 11/6/2026-1:46:45 Cannot read property split of undefined
VOLUMIO 11/6/2026-1:40:58 Cannot read property split of undefined
VOLUMIO 11/6/2026-1:35:43 Chaining cycle detected for promise #
SMSL 11/6/2026-1:31:59 send ENETUNREACH 255.255.255.255:3483
VOLUMIO 11/6/2026-1:31:19 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-1:30:52 socket hang up
VOLUMIO 11/6/2026-1:29:43 Cannot read properties of undefined (reading highestSoundQuality)
VOLUMIO 11/6/2026-1:28:46 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-1:27:7 socket hang up
VOLUMIO 11/6/2026-1:26:5 ENOENT: no such file or directory, unlink /tmp/SoAQSllrHnyBLDm2Zed1kwpuz0kjHBUviFQQX0eP8O1KkKQOPuxlGK8c6m0FLZzEIPMMIyYdsqwWOgviWF1tSAtJIOsO7v1ejFfh
VOLUMIO 11/6/2026-1:26:3 getaddrinfo -3007
VOLUMIO 11/6/2026-1:25:21 dns service error: unknown
VOLUMIO 11/6/2026-1:19:56 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-1:15:10 Unable to resolve or reject the same promise twice
VOLUMIO 11/6/2026-1:3:47 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-1:3:20 socket hang up
VOLUMIO 11/6/2026-0:55:46 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/6/2026-0:55:16 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/6/2026-0:50:42 write EPIPE
VOLUMIO 11/6/2026-0:49:53 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-0:49:50 getaddrinfo -3007
MINIDSPSHD 11/6/2026-0:49:2 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:48:42 socket hang up
VOLUMIO 11/6/2026-0:46:30 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/6/2026-0:46:18 write EPIPE
MINIDSPSHD 11/6/2026-0:45:12 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:44:11 socket hang up
VOLUMIO 11/6/2026-0:43:24 ENOENT: no such file or directory, unlink /tmp/FjWmto8DhxqVHe4qa2Rl3syAHNZ459l5J8iTnbCCnbTC5cSyPbZ5sjOsPmGQfp54kgHgwwsOqAGvVQD9wVAq1Y9eNwIRnxcSPD4x
MINIDSPSHD 11/6/2026-0:41:32 write EPIPE
VOLUMIO 11/6/2026-0:41:1 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/6/2026-0:40:0 Cannot read property fn of undefined
MINIDSPSHD 11/6/2026-0:37:53 write EPIPE
MINIDSPSHD 11/6/2026-0:36:16 Cannot read property fn of undefined
MINIDSPSHD 11/6/2026-0:32:20 write EPIPE
VOLUMIO 11/6/2026-0:32:0 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/6/2026-0:31:6 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/6/2026-0:30:50 connect ETIMEDOUT 103.252.115.169:443
VOLUMIO 11/6/2026-0:30:39 socket hang up
MINIDSPSHD 11/6/2026-0:30:32 Cannot read property fn of undefined
MINIDSPSHD 11/6/2026-0:28:12 write EPIPE
MINIDSPSHD 11/6/2026-0:26:47 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:23:52 ENOENT: no such file or directory, unlink /tmp/xq6OU88PUSMtja4WCymrYugkI0tdMTGXFJytU3KXaFTD4FhFnfDeibThRZG7OcoxNqmROGdwRrPkQCOOljqwzqKmziHARXNDlBjp
MINIDSPSHD 11/6/2026-0:20:12 write EPIPE
VOLUMIO 11/6/2026-0:18:56 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/6/2026-0:18:28 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:17:57 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/6/2026-0:15:51 write EPIPE
MINIDSPSHD 11/6/2026-0:14:6 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:12:52 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/6/2026-0:11:29 write EPIPE
MINIDSPSHD 11/6/2026-0:9:55 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:9:13 Chaining cycle detected for promise #
MINIDSPSHD 11/6/2026-0:6:3 write EPIPE
VOLUMIO 11/6/2026-0:4:57 ENOENT: no such file or directory, unlink /tmp/KYVMxSrZ5qlflGk5XTIbaCdN837uEbSpraESB2iH8nERvA2CCzCUeQw1AbeijUwRybjghccPYP52AMI3lRNEO17e9cpT4x2c1IEg
MINIDSPSHD 11/6/2026-0:4:37 Cannot read property fn of undefined
MINIDSPSHD 11/6/2026-0:2:13 write EPIPE
VOLUMIO 11/6/2026-0:1:26 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/6/2026-0:0:42 Cannot read property fn of undefined
VOLUMIO 11/6/2026-0:0:10 socket hang up
VOLUMIO 11/5/2026-23:57:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:56:57 socket hang up
VOLUMIO 11/5/2026-23:56:31 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-23:55:22 write EPIPE
VOLUMIO 11/5/2026-23:55:5 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-23:54:56 connect EHOSTUNREACH 192.168.30.229:1400
MINIDSPSHD 11/5/2026-23:54:13 Cannot read property fn of undefined
RIVO 11/5/2026-23:53:1 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-23:51:31 write EPIPE
MINIDSPSHD 11/5/2026-23:50:9 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:48:38 send ENETUNREACH 255.255.255.255:3483
VOLUMIO 11/5/2026-23:46:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:44:41 socket hang up
MINIDSPSHD 11/5/2026-23:44:15 write EPIPE
VOLUMIO 11/5/2026-23:43:11 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-23:42:51 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-23:40:20 write EPIPE
VOLUMIO 11/5/2026-23:39:40 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:39:14 socket hang up
MINIDSPSHD 11/5/2026-23:38:50 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:37:7 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-23:36:30 write EPIPE
MINIDSPSHD 11/5/2026-23:34:53 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:32:36 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/no
MINIDSPSHD 11/5/2026-23:32:8 write EPIPE
MINIDSPSHD 11/5/2026-23:30:34 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:29:36 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/5/2026-23:25:35 write EPIPE
MINIDSPSHD 11/5/2026-23:24:5 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:23:17 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:21:47 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-23:21:36 write EPIPE
MINIDSPSHD 11/5/2026-23:20:12 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:17:35 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(). The promise rejected with the reason Error:
MINIDSPSHD 11/5/2026-23:16:5 write EPIPE
MINIDSPSHD 11/5/2026-23:14:34 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-23:12:0 write EPIPE
MINIDSPSHD 11/5/2026-23:10:43 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:10:2 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/5/2026-23:8:26 write EPIPE
MINIDSPSHD 11/5/2026-23:7:7 Cannot read property fn of undefined
VOLUMIO 11/5/2026-23:6:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:6:27 socket hang up
VOLUMIO 11/5/2026-23:4:26 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-23:4:15 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(). The promise rejected with the reason undefined.
VOLUMIO 11/5/2026-23:3:52 fetch failed
MINIDSPSHD 11/5/2026-23:1:37 write EPIPE
VOLUMIO 11/5/2026-23:1:3 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-23:0:49 socket hang up
MINIDSPSHD 11/5/2026-23:0:9 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:59:25 socket hang up
VOLUMIO 11/5/2026-22:57:41 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-22:57:23 write EPIPE
MINIDSPSHD 11/5/2026-22:56:0 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:51:59 write EPIPE
VOLUMIO 11/5/2026-22:51:46 listen EADDRINUSE: address already in use :::6599
MINIDSPSHD 11/5/2026-22:50:42 Cannot read property fn of undefined
EMOTIVADRS1 11/5/2026-22:48:28 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-22:48:8 write EPIPE
VOLUMIO 11/5/2026-22:47:5 dns service error: unknown
MINIDSPSHD 11/5/2026-22:46:39 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:45:50 Cannot read property slice of null
MINIDSPSHD 11/5/2026-22:44:26 write EPIPE
MINIDSPSHD 11/5/2026-22:43:4 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:42:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-22:42:4 socket hang up
MINIDSPSHD 11/5/2026-22:40:34 write EPIPE
MINIDSPSHD 11/5/2026-22:39:6 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:36:34 write EPIPE
MINIDSPSHD 11/5/2026-22:35:18 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:33:0 write EPIPE
MINIDSPSHD 11/5/2026-22:31:34 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:30:56 Cannot read property slice of null
MINIDSPSHD 11/5/2026-22:27:44 write EPIPE
MINIDSPSHD 11/5/2026-22:26:25 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:23:1 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-22:22:43 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-22:22:16 socket hang up
VOLUMIO 11/5/2026-22:22:12 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/5/2026-22:22:8 dns service error: unknown
MINIDSPSHD 11/5/2026-22:21:22 write EPIPE
VOLUMIO 11/5/2026-22:20:16 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-22:20:2 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:17:23 write EPIPE
MINIDSPSHD 11/5/2026-22:15:55 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:13:28 write EPIPE
MINIDSPSHD 11/5/2026-22:11:53 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-22:6:43 write EPIPE
MINIDSPSHD 11/5/2026-22:5:28 Cannot read property fn of undefined
VOLUMIO 11/5/2026-22:3:46 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-22:2:41 write EPIPE
VOLUMIO 11/5/2026-22:2:37 socket hang up
MINIDSPSHD 11/5/2026-22:1:20 Cannot read property fn of undefined
PROJECTSBUS2 11/5/2026-22:1:0 Cannot read property slice of null
VOLUMIO 11/5/2026-22:0:0 connect EISCONN /tmp/.X11-unix/X0
VOLUMIO 11/5/2026-21:58:14 fetch failed
MINIDSPSHD 11/5/2026-21:57:16 write EPIPE
MINIDSPSHD 11/5/2026-21:55:28 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-21:51:37 write EPIPE
VOLUMIO 11/5/2026-21:50:31 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-21:50:16 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:49:47 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-21:49:15 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-21:48:51 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-21:48:48 socket hang up
VOLUMIO 11/5/2026-21:48:13 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-21:47:43 write EPIPE
MINIDSPSHD 11/5/2026-21:46:17 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:45:16 file /mnt/USB/KINGSTON/audio/DDT_-_Inache/CD1/Ddt - Inache- Disc 1 of 2.cue does not exist
VOLUMIO 11/5/2026-21:41:57 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-21:41:52 write EPIPE
MINIDSPSHD 11/5/2026-21:40:28 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:37:4 socket hang up
MINIDSPSHD 11/5/2026-21:36:56 write EPIPE
MINIDSPSHD 11/5/2026-21:35:30 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-21:33:5 write EPIPE
MINIDSPSHD 11/5/2026-21:31:46 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:30:40 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-21:28:38 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-21:26:2 write EPIPE
MINIDSPSHD 11/5/2026-21:24:51 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:22:58 Cannot read property slice of null
MINIDSPSHD 11/5/2026-21:22:45 write EPIPE
MINIDSPSHD 11/5/2026-21:21:23 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:19:59 EEXIST: file already exists, mkdir /mnt/NAS/ds918
VOLUMIO 11/5/2026-21:19:40 Connection :1.475 is not allowed to add more match rules (increase limits in configuration file if required
VOLUMIO 11/5/2026-21:19:31 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-21:18:12 write EPIPE
VOLUMIO 11/5/2026-21:18:7 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-21:17:46 A network error (such as timeout, interrupted connection or unreachable host) has occurred.
RIVOPLUS 11/5/2026-21:17:16 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-21:17:4 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-21:17:1 socket hang up
MINIDSPSHD 11/5/2026-21:16:47 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:15:1 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-21:14:23 write EPIPE
MINIDSPSHD 11/5/2026-21:13:4 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:11:33 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-21:7:29 write EPIPE
VOLUMIO 11/5/2026-21:6:10 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-21:5:56 Cannot read property fn of undefined
VOLUMIO 11/5/2026-21:3:51 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-21:1:51 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-21:0:55 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-20:59:46 write EPIPE
VOLUMIO 11/5/2026-20:59:28 VM operation timed out
MINIDSPSHD 11/5/2026-20:58:27 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-20:56:6 write EPIPE
VOLUMIO 11/5/2026-20:55:43 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:54:35 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:54:8 socket hang up
VOLUMIO 11/5/2026-20:52:21 Connection error in fetching pairing code
MINIDSPSHD 11/5/2026-20:52:11 read ECONNRESET
VOLUMIO 11/5/2026-20:51:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-20:51:45 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-20:51:18 socket hang up
MINIDSPSHD 11/5/2026-20:50:41 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:49:50 socket hang up
VOLUMIO 11/5/2026-20:49:47 connect EHOSTUNREACH 192.168.30.229:1400
VOLUMIO 11/5/2026-20:48:23 fetch failed
MINIDSPSHD 11/5/2026-20:48:8 write EPIPE
MINIDSPSHD 11/5/2026-20:44:0 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-20:41:26 write EPIPE
MINIDSPSHD 11/5/2026-20:40:5 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-20:36:4 write EPIPE
VOLUMIO 11/5/2026-20:35:29 Message recipient disconnected from message bus without replying
MINIDSPSHD 11/5/2026-20:34:33 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:34:12 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:32:9 write EPIPE
MINIDSPSHD 11/5/2026-20:30:40 Cannot read property fn of undefined
UNDEFINED 11/5/2026-20:28:33 Cannot read properties of null (reading replace)
MINIDSPSHD 11/5/2026-20:28:28 write EPIPE
VOLUMIO 11/5/2026-20:27:56 connect EISCONN /tmp/.X11-unix/X0
MINIDSPSHD 11/5/2026-20:27:10 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:26:30 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-20:24:42 write EPIPE
MINIDSPSHD 11/5/2026-20:23:20 Cannot read property fn of undefined
PRIMO2REV2 11/5/2026-20:23:7 Connection :1.2551 is not allowed to add more match rules (increase limits in configuration file if required
VOLUMIO 11/5/2026-20:20:35 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-20:20:33 write EPIPE
VOLUMIO 11/5/2026-20:20:30 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-20:20:0 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-20:19:50 socket hang up
MINIDSPSHD 11/5/2026-20:19:12 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:18:31 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-20:16:55 write EPIPE
VOLUMIO 11/5/2026-20:16:8 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-20:15:35 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:12:52 socket hang up
MINIDSPSHD 11/5/2026-20:12:39 write EPIPE
VOLUMIO 11/5/2026-20:12:15 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:11:3 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:10:20 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:8:39 write EPIPE
VOLUMIO 11/5/2026-20:7:49 socket hang up
VOLUMIO 11/5/2026-20:7:18 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:7:8 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:5:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-20:5:24 socket hang up
VOLUMIO 11/5/2026-20:4:44 socket hang up
VOLUMIO 11/5/2026-20:4:15 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-20:3:31 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:2:17 write EPIPE
VOLUMIO 11/5/2026-20:1:28 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-20:0:51 Cannot read property fn of undefined
VOLUMIO 11/5/2026-20:0:36 CamillaDSP is not running
VOLUMIO 11/5/2026-20:0:36 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-20:0:25 socket hang up
MINIDSPSHD 11/5/2026-19:58:36 write EPIPE
VOLUMIO 11/5/2026-19:57:42 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-19:57:11 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:56:41 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-19:56:24 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
RIVOPLUS 11/5/2026-19:56:16 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-19:55:15 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-19:54:36 write EPIPE
VOLUMIO 11/5/2026-19:53:41 socket hang up
MINIDSPSHD 11/5/2026-19:53:21 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:52:21 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/5/2026-19:50:58 write EPIPE
MINIDSPSHD 11/5/2026-19:49:13 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:48:15 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-19:44:23 write EPIPE
MINIDSPSHD 11/5/2026-19:42:51 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:41:31 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-19:41:5 socket hang up
PRIMO2REV2 11/5/2026-19:40:59 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-19:40:30 write EPIPE
UNDEFINED 11/5/2026-19:40:16 Cannot read property then of undefined
MINIDSPSHD 11/5/2026-19:38:53 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-19:35:0 write EPIPE
MINIDSPSHD 11/5/2026-19:33:34 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-19:30:38 write EPIPE
VOLUMIO 11/5/2026-19:30:26 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/No
VOLUMIO 11/5/2026-19:30:12 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-19:29:18 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:29:12 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-19:28:45 socket hang up
VOLUMIO 11/5/2026-19:28:14 Connection :1.249 is not allowed to add more match rules (increase limits in configuration file if required
VOLUMIO 11/5/2026-19:27:1 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-19:26:47 write EPIPE
MINIDSPSHD 11/5/2026-19:25:19 Cannot read property fn of undefined
RIVOPLUS 11/5/2026-19:24:11 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-19:23:36 Cannot read property then of undefined
MINIDSPSHD 11/5/2026-19:22:43 write EPIPE
MINIDSPSHD 11/5/2026-19:21:3 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:20:45 socket hang up
VOLUMIO 11/5/2026-19:18:27 write EPIPE
VOLUMIO 11/5/2026-19:18:20 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-19:17:53 socket hang up
VOLUMIO 11/5/2026-19:17:32 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-19:17:0 write EPIPE
VOLUMIO 11/5/2026-19:16:49 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-19:15:37 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:15:17 dns service error: unknown
VOLUMIO 11/5/2026-19:14:0 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
MINIDSPSHD 11/5/2026-19:13:16 write EPIPE
MINIDSPSHD 11/5/2026-19:11:57 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-19:7:59 write EPIPE
MINIDSPSHD 11/5/2026-19:6:32 Cannot read property fn of undefined
VOLUMIO 11/5/2026-19:5:42 dns service error: unknown
VOLUMIO 11/5/2026-19:4:16 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-19:3:10 Cannot read properties of null (reading broadcastMessage)
RIVO 11/5/2026-19:2:15 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-19:1:34 Cannot read properties of null (reading printToastMessage)
MINIDSPSHD 11/5/2026-19:1:31 write EPIPE
MINIDSPSHD 11/5/2026-19:0:24 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:56:22 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-18:55:38 file /mnt/NAS/Sinology/PETER GABRIEL - DISCOGRAPHY/(1985) Birdy (CAS CD 1167) [Nimbus]/Peter Gabriel - Birdy (CAS CD 1167).cue does not exist
MINIDSPSHD 11/5/2026-18:55:5 write EPIPE
MINIDSPSHD 11/5/2026-18:53:49 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:53:39 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-18:52:20 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-18:51:26 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-18:49:50 write EPIPE
MINIDSPSHD 11/5/2026-18:48:31 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:46:34 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-18:46:21 write EPIPE
VOLUMIO 11/5/2026-18:45:46 socket hang up
RIVO 11/5/2026-18:45:29 Cannot read properties of undefined (reading sendCommand)
MINIDSPSHD 11/5/2026-18:44:58 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:44:2 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-18:42:42 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-18:42:26 write EPIPE
VOLUMIO 11/5/2026-18:42:3 socket hang up
VOLUMIO 11/5/2026-18:41:0 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-18:38:36 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:38:20 socket hang up
VOLUMIO 11/5/2026-18:38:8 Cannot read properties of undefined (reading replace)
VOLUMIO 11/5/2026-18:36:44 socket hang up
MINIDSPSHD 11/5/2026-18:36:9 write EPIPE
MINIDSPSHD 11/5/2026-18:34:50 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:34:41 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-18:34:14 socket hang up
MINIDSPSHD 11/5/2026-18:32:27 write EPIPE
MINIDSPSHD 11/5/2026-18:30:37 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-18:28:13 write EPIPE
MINIDSPSHD 11/5/2026-18:26:50 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:25:42 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-18:24:26 socket hang up
MINIDSPSHD 11/5/2026-18:24:3 write EPIPE
VOLUMIO 11/5/2026-18:22:55 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-18:22:28 socket hang up
MINIDSPSHD 11/5/2026-18:22:22 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:20:27 socket hang up
MINIDSPSHD 11/5/2026-18:19:49 write EPIPE
MINIDSPSHD 11/5/2026-18:18:34 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:17:17 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-18:16:10 write EPIPE
VOLUMIO 11/5/2026-18:15:3 dns service error: unknown
MINIDSPSHD 11/5/2026-18:14:52 Cannot read property fn of undefined
UNDEFINED 11/5/2026-18:14:47 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-18:12:49 Cannot read property writeSync of undefined
MINIDSPSHD 11/5/2026-18:12:21 write EPIPE
RIVO 11/5/2026-18:11:30 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-18:11:9 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:8:54 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-18:8:37 write EPIPE
VOLUMIO 11/5/2026-18:8:30 socket hang up
MINIDSPSHD 11/5/2026-18:7:18 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:6:29 Cannot read property then of undefined
MINIDSPSHD 11/5/2026-18:4:31 write EPIPE
VOLUMIO 11/5/2026-18:3:29 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-18:3:23 Cannot read property fn of undefined
VOLUMIO 11/5/2026-18:1:24 ENOSPC: no space left on device, write
MINIDSPSHD 11/5/2026-18:1:2 write EPIPE
MINIDSPSHD 11/5/2026-17:59:53 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:57:26 write EPIPE
VOLUMIO 11/5/2026-17:57:16 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-17:56:4 Cannot read property @ of undefined
MINIDSPSHD 11/5/2026-17:55:51 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:53:34 write EPIPE
MINIDSPSHD 11/5/2026-17:52:27 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:50:18 write EPIPE
VOLUMIO 11/5/2026-17:49:47 Premature end of data in tag br line 187 (Line: 195, Column: 7)
VOLUMIO 11/5/2026-17:48:31 Connection :1.23 is not allowed to add more match rules (increase limits in configuration file if required
MINIDSPSHD 11/5/2026-17:46:35 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:45:37 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-17:45:19 write EPIPE
MINIDSPSHD 11/5/2026-17:43:54 write EPIPE
VOLUMIO 11/5/2026-17:43:9 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Job for volumio5-onboarding.service failed because the control process exited with error code. See systemctl
VOLUMIO 11/5/2026-17:40:57 Cannot read property slice of null
VOLUMIO 11/5/2026-17:40:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-17:40:14 socket hang up
VOLUMIO 11/5/2026-17:39:46 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-17:39:43 Cannot read property service of undefined
VOLUMIO 11/5/2026-17:38:32 [50@0] {addtagid} No such song
RIVOPLUS 11/5/2026-17:37:14 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-17:35:29 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:33:8 write EPIPE
VOLUMIO 11/5/2026-17:32:30 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-17:31:44 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:31:29 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-17:31:1 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-17:30:57 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-17:29:13 write EPIPE
VOLUMIO 11/5/2026-17:29:1 socket hang up
MINIDSPSHD 11/5/2026-17:25:17 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:24:42 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-17:22:48 write EPIPE
VOLUMIO 11/5/2026-17:22:6 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-17:21:27 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:18:53 write EPIPE
VOLUMIO 11/5/2026-17:18:50 Cannot read property then of undefined
VOLUMIO 11/5/2026-17:18:15 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-17:17:41 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:15:27 write EPIPE
MINIDSPSHD 11/5/2026-17:13:57 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:12:48 Cannot read properties of undefined (reading split)
MOTIVO 11/5/2026-17:12:32 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/5/2026-17:11:32 write EPIPE
VOLUMIO 11/5/2026-17:11:14 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(). The promise rejected with the reason Error:
VOLUMIO 11/5/2026-17:11:3 Cannot read properties of undefined (reading then)
VOLUMIO 11/5/2026-17:10:54 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-17:10:21 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:8:23 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-17:7:10 socket hang up
MINIDSPSHD 11/5/2026-17:6:29 write EPIPE
MINIDSPSHD 11/5/2026-17:5:21 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-17:3:9 write EPIPE
VOLUMIO 11/5/2026-17:2:30 socket hang up
VOLUMIO 11/5/2026-17:2:7 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-17:1:56 Cannot read property fn of undefined
VOLUMIO 11/5/2026-17:1:12 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-16:59:25 write EPIPE
VOLUMIO 11/5/2026-16:58:29 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-16:58:16 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:58:3 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-16:57:40 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-16:56:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-16:56:2 socket hang up
VOLUMIO 11/5/2026-16:55:56 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-16:55:27 write EPIPE
MINIDSPSHD 11/5/2026-16:54:19 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:54:11 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-16:52:55 connect ECONNREFUSED 127.0.0.1:9879
RIVOPLUS 11/5/2026-16:52:10 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/5/2026-16:52:5 write EPIPE
VOLUMIO 11/5/2026-16:51:31 socket hang up
VOLUMIO 11/5/2026-16:50:59 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/5/2026-16:50:58 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:50:29 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-16:48:54 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-16:48:41 write EPIPE
VOLUMIO 11/5/2026-16:47:22 connect ETIMEDOUT 199.96.58.157:443
MINIDSPSHD 11/5/2026-16:47:11 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-16:44:57 write EPIPE
MINIDSPSHD 11/5/2026-16:43:30 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:42:27 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-16:40:27 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-16:39:58 write EPIPE
VOLUMIO 11/5/2026-16:39:0 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-16:38:42 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:38:9 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-16:36:38 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-16:36:15 write EPIPE
VOLUMIO 11/5/2026-16:33:35 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-16:32:38 socket hang up
MINIDSPSHD 11/5/2026-16:32:22 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-16:30:10 write EPIPE
MINIDSPSHD 11/5/2026-16:28:49 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:28:32 socket hang up
VOLUMIO 11/5/2026-16:27:10 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-16:26:25 write EPIPE
MINIDSPSHD 11/5/2026-16:25:8 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:23:21 socket hang up
PRIMO2REV2 11/5/2026-16:22:49 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-16:22:35 write EPIPE
MINIDSPSHD 11/5/2026-16:20:59 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:19:59 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-16:18:43 write EPIPE
VOLUMIO 11/5/2026-16:18:6 socket hang up
VOLUMIO 11/5/2026-16:17:30 ENOSPC: no space left on device, write
MINIDSPSHD 11/5/2026-16:17:22 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:16:51 Cannot read properties of undefined (reading split)
RIVOPLUS 11/5/2026-16:16:22 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/PEQ/nopreset
MINIDSPSHD 11/5/2026-16:15:7 write EPIPE
MINIDSPSHD 11/5/2026-16:13:28 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:12:39 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-16:11:22 write EPIPE
RIVOPLUS 11/5/2026-16:10:26 Premature end of data in tag br line 187 (Line: 195, Column: 7)
MINIDSPSHD 11/5/2026-16:9:57 Cannot read property fn of undefined
OPERA 11/5/2026-16:8:13 connect ETIMEDOUT 31.13.76.99:443
VOLUMIO 11/5/2026-16:7:35 Premature end of data in tag br line 187 (Line: 195, Column: 7)
MINIDSPSHD 11/5/2026-16:7:30 write EPIPE
MINIDSPSHD 11/5/2026-16:6:14 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:6:9 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-16:4:8 write EPIPE
MINIDSPSHD 11/5/2026-16:2:54 Cannot read property fn of undefined
VOLUMIO 11/5/2026-16:1:27 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-16:1:8 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-16:0:33 socket hang up
MINIDSPSHD 11/5/2026-16:0:22 write EPIPE
MINIDSPSHD 11/5/2026-15:59:15 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-15:57:1 write EPIPE
MINIDSPSHD 11/5/2026-15:55:23 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:54:0 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-15:53:52 connect ETIMEDOUT 213.155.157.155:443
VOLUMIO 11/5/2026-15:53:18 connect ETIMEDOUT 192.168.1.154:1400
MINIDSPSHD 11/5/2026-15:53:5 write EPIPE
MINIDSPSHD 11/5/2026-15:51:49 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:50:37 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-15:49:17 write EPIPE
VOLUMIO 11/5/2026-15:49:17 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-15:48:6 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:47:58 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-15:46:7 Cannot read property length of undefined
VOLUMIO 11/5/2026-15:44:47 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-15:44:28 Cannot read property slice of null
MINIDSPSHD 11/5/2026-15:44:26 write EPIPE
VOLUMIO 11/5/2026-15:44:15 VM operation timed out
VOLUMIO 11/5/2026-15:44:6 read ECONNRESET
MINIDSPSHD 11/5/2026-15:43:6 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-15:40:43 write EPIPE
VOLUMIO 11/5/2026-15:40:30 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-15:39:14 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:38:16 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-15:37:55 socket hang up
MINIDSPSHD 11/5/2026-15:36:57 write EPIPE
MINIDSPSHD 11/5/2026-15:35:32 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:34:24 connect EHOSTUNREACH 192.168.1.101:14999
MINIDSPSHD 11/5/2026-15:33:25 write EPIPE
VOLUMIO 11/5/2026-15:32:47 [50@0] {addtagid} No such song
VOLUMIO 11/5/2026-15:30:7 write EPIPE
MINIDSPSHD 11/5/2026-15:29:31 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:28:18 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-15:25:55 write EPIPE
VOLUMIO 11/5/2026-15:25:11 Cannot read property split of undefined
MINIDSPSHD 11/5/2026-15:24:38 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:22:30 connect ETIMEDOUT 192.168.1.154:1400
MINIDSPSHD 11/5/2026-15:22:25 write EPIPE
MINIDSPSHD 11/5/2026-15:20:59 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-15:18:44 write EPIPE
VOLUMIO 11/5/2026-15:18:11 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-15:17:34 write EPIPE
VOLUMIO 11/5/2026-15:17:25 Cannot read property split of undefined
MINIDSPSHD 11/5/2026-15:17:3 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:16:49 Cannot read properties of undefined (reading split)
OPERA 11/5/2026-15:15:40 connect ETIMEDOUT 185.60.218.50:443
VOLUMIO 11/5/2026-15:14:54 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-15:13:31 write EPIPE
VOLUMIO 11/5/2026-15:11:30 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-15:9:47 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:9:2 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-15:8:3 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Unit volumio5-onboarding.service is masked.
MINIDSPSHD 11/5/2026-15:7:25 write EPIPE
MINIDSPSHD 11/5/2026-15:6:8 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:5:14 Cannot read property split of undefined
VOLUMIO 11/5/2026-15:5:11 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-15:4:20 Cannot read properties of undefined (reading charAt)
VOLUMIO 11/5/2026-15:4:14 Command failed: /usr/bin/sudo /bin/systemctl start volumio5-onboarding.service Failed to start volumio5-onboarding.service: Unit volumio5-onboarding.service is masked.
MINIDSPSHD 11/5/2026-15:3:43 write EPIPE
VOLUMIO 11/5/2026-15:2:10 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-15:2:1 Cannot read property fn of undefined
VOLUMIO 11/5/2026-15:1:40 socket hang up
VOLUMIO 11/5/2026-15:0:37 write EPIPE
VOLUMIO 11/5/2026-14:59:39 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-14:58:57 socket hang up
MINIDSPSHD 11/5/2026-14:58:38 write EPIPE
VOLUMIO 11/5/2026-14:56:40 Cannot read properties of undefined (reading charAt)
PRIMO2REV2 11/5/2026-14:55:49 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-14:55:42 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-14:55:18 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:54:47 Cannot read property indexOf of undefined
VOLUMIO 11/5/2026-14:53:56 connect ETIMEDOUT 103.252.115.169:443
VOLUMIO 11/5/2026-14:51:48 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-14:51:42 write EPIPE
MINIDSPSHD 11/5/2026-14:50:29 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:48:36 connect ECONNREFUSED 199.59.148.9:443
MINIDSPSHD 11/5/2026-14:47:55 write EPIPE
MINIDSPSHD 11/5/2026-14:46:41 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:46:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-14:45:51 socket hang up
MINIDSPSHD 11/5/2026-14:44:29 write EPIPE
VOLUMIO 11/5/2026-14:41:53 Cannot read property volumio_info of undefined
MINIDSPSHD 11/5/2026-14:40:39 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-14:37:50 write EPIPE
MINIDSPSHD 11/5/2026-14:36:21 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-14:34:4 write EPIPE
MINIDSPSHD 11/5/2026-14:30:24 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:30:10 connect ETIMEDOUT 213.155.157.201:443
MINIDSPSHD 11/5/2026-14:28:11 read ECONNRESET
VOLUMIO 11/5/2026-14:27:38 connect ETIMEDOUT 202.53.137.209:443
MINIDSPSHD 11/5/2026-14:26:57 write EPIPE
VOLUMIO 11/5/2026-14:25:12 Cannot read properties of undefined (reading charAt)
MINIDSPSHD 11/5/2026-14:25:9 Cannot read property fn of undefined
OPERA 11/5/2026-14:23:47 connect ECONNREFUSED 202.160.129.36:443
VOLUMIO 11/5/2026-14:23:24 connect ECONNREFUSED 202.160.129.36:443
VOLUMIO 11/5/2026-14:22:59 connect ETIMEDOUT 213.155.157.155:443
MINIDSPSHD 11/5/2026-14:22:55 write EPIPE
VOLUMIO 11/5/2026-14:22:16 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-14:21:48 ENOENT: no such file or directory, open /data/INTERNAL/FusionDsp/presets/EQ15/nopreset
MINIDSPSHD 11/5/2026-14:21:24 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:20:29 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-14:20:5 socket hang up
VOLUMIO 11/5/2026-14:19:36 connect ETIMEDOUT 157.240.2.36:443
VOLUMIO 11/5/2026-14:19:26 Cannot read properties of undefined (reading charAt)
MINIDSPSHD 11/5/2026-14:19:14 write EPIPE
VOLUMIO 11/5/2026-14:18:34 connect ECONNREFUSED 127.0.0.1:9879
MINIDSPSHD 11/5/2026-14:18:0 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:17:46 socket hang up
VOLUMIO 11/5/2026-14:17:39 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-14:15:17 write EPIPE
VOLUMIO 11/5/2026-14:15:14 connect ETIMEDOUT 199.59.149.232:443
MINIDSPSHD 11/5/2026-14:13:57 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-14:11:47 read ECONNRESET
VOLUMIO 11/5/2026-14:10:16 socket hang up
MINIDSPSHD 11/5/2026-14:10:7 Cannot read property fn of undefined
VOLUMIO 11/5/2026-14:8:21 connect ETIMEDOUT 188.43.75.88:443
MINIDSPSHD 11/5/2026-14:7:53 write EPIPE
VOLUMIO 11/5/2026-14:6:24 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-14:4:50 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-14:2:5 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
MINIDSPSHD 11/5/2026-13:59:50 Cannot read property fn of undefined
VOLUMIO 11/5/2026-13:58:48 connect ETIMEDOUT 103.56.16.112:443
PRIMOPLUS 11/5/2026-13:57:27 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/5/2026-13:57:12 write EPIPE
VOLUMIO 11/5/2026-13:56:26 Cannot read properties of undefined (reading charAt)
VOLUMIO 11/5/2026-13:55:5 connect ETIMEDOUT 62.115.252.184:443
MINIDSPSHD 11/5/2026-13:51:3 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-13:48:41 write EPIPE
MINIDSPSHD 11/5/2026-13:47:18 Cannot read property fn of undefined
VOLUMIO 11/5/2026-13:45:45 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
MINIDSPSHD 11/5/2026-13:44:37 write EPIPE
VOLUMIO 11/5/2026-13:44:17 connect ECONNREFUSED 127.0.0.1:9879
OPERA 11/5/2026-13:43:58 connect ETIMEDOUT 108.160.167.174:443
VOLUMIO 11/5/2026-13:43:54 socket hang up
MINIDSPSHD 11/5/2026-13:43:21 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-13:41:14 write EPIPE
MINIDSPSHD 11/5/2026-13:40:3 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-13:37:39 write EPIPE
VOLUMIO 11/5/2026-13:36:50 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-13:35:11 socket hang up
UNDEFINED 11/5/2026-13:31:32 Cannot read property then of undefined
MINIDSPSHD 11/5/2026-13:29:49 Cannot read property fn of undefined
VOLUMIO 11/5/2026-13:28:18 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-13:27:9 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-13:26:35 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-13:25:49 write EPIPE
RIVOPLUS 11/5/2026-13:25:29 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-13:24:34 Cannot read property fn of undefined
OPERA 11/5/2026-13:22:21 connect ETIMEDOUT 199.16.158.9:443
MINIDSPSHD 11/5/2026-13:22:11 write EPIPE
VOLUMIO 11/5/2026-13:21:35 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-13:21:33 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-13:21:31 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-13:21:3 Cannot read property stop of null
MINIDSPSHD 11/5/2026-13:18:35 Cannot read property fn of undefined
VOLUMIO 11/5/2026-13:16:49 Cannot read properties of undefined (reading split)
MINIDSPSHD 11/5/2026-13:16:17 write EPIPE
VOLUMIO 11/5/2026-13:15:8 Cannot read property replace of undefined
MINIDSPSHD 11/5/2026-13:14:59 Cannot read property fn of undefined
VOLUMIO 11/5/2026-13:14:24 connect ETIMEDOUT 162.125.80.3:443
VOLUMIO 11/5/2026-13:13:26 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-13:12:36 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-13:12:9 socket hang up
VOLUMIO 11/5/2026-13:11:21 send ENETUNREACH 255.255.255.255:3483
MINIDSPSHD 11/5/2026-13:11:18 write EPIPE
VOLUMIO 11/5/2026-13:11:7 Cannot read properties of undefined (reading split)
UNDEFINED 11/5/2026-13:10:11 Cannot read properties of null (reading replace)
UNDEFINED 11/5/2026-13:9:44 read ECONNRESET
VOLUMIO 11/5/2026-13:9:40 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-13:6:54 Cannot read property slice of null
VOLUMIO 11/5/2026-13:4:15 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-13:1:32 Cannot read properties of null (reading slice)
VOLUMIO 11/5/2026-13:0:52 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-13:0:25 socket hang up
VOLUMIO 11/5/2026-13:0:16 read ECONNRESET
VOLUMIO 11/5/2026-13:0:1 read ECONNRESET
OPERA 11/5/2026-12:59:15 connect ETIMEDOUT 199.16.156.103:443
VOLUMIO 11/5/2026-12:58:54 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
RIVOPLUS 11/5/2026-12:57:22 Unable to resolve or reject the same promise twice
VOLUMIO 11/5/2026-12:57:3 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-12:56:38 Client network socket disconnected before secure TLS connection was established
VOLUMIO 11/5/2026-12:56:32 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-12:56:5 socket hang up
RIVO 11/5/2026-12:55:53 Command failed: /usr/bin/sudo /bin/systemctl stop vtcs.service && sleep 3 Job for vtcs.service canceled.
VOLUMIO 11/5/2026-12:54:58 Chaining cycle detected for promise #
VOLUMIO 11/5/2026-12:53:44 connect ETIMEDOUT 213.155.157.121:443
VOLUMIO 11/5/2026-12:52:23 listen EADDRINUSE: address already in use :::6599
VOLUMIO 11/5/2026-12:52:13 Cannot read properties of undefined (reading split)
VOLUMIO 11/5/2026-12:51:47 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/5/2026-12:50:48 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-12:48:11 Cannot read property fn of undefined
VOLUMIO 11/5/2026-12:46:16 connect ETIMEDOUT 128.242.240.61:443
MINIDSPSHD 11/5/2026-12:46:8 write EPIPE
RIVO 11/5/2026-12:45:45 Cannot read properties of null (reading deviceDescription)
VOLUMIO 11/5/2026-12:44:19 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-12:44:2 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-12:43:2 Cannot read properties of undefined (reading service)
VOLUMIO 11/5/2026-12:42:54 Cannot read properties of undefined (reading sendCommand)
MINIDSPSHD 11/5/2026-12:42:48 Cannot read property fn of undefined
VOLUMIO 11/5/2026-12:42:0 certificate is not yet valid
VOLUMIO 11/5/2026-12:41:55 Connection :1.33 is not allowed to add more match rules (increase limits in configuration file if required
VOLUMIO 11/5/2026-12:41:47 Cannot read properties of undefined (reading then)
MINIDSPSHD 11/5/2026-12:40:35 write EPIPE
VOLUMIO 11/5/2026-12:40:11 Cannot read properties of undefined (reading split)
OPERA 11/5/2026-12:39:45 connect ETIMEDOUT 199.59.149.210:443
MINIDSPSHD 11/5/2026-12:39:20 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-12:34:35 write EPIPE
PRIMOPLUS 11/5/2026-12:33:40 connect EHOSTUNREACH 192.168.10.171:1400
PRIMOPLUS 11/5/2026-12:33:11 connect EHOSTUNREACH 192.168.10.160:1400
VOLUMIO 11/5/2026-12:32:40 channel closed
VOLUMIO 11/5/2026-12:32:2 dns service error: unknown
VOLUMIO 11/5/2026-12:31:1 connect ECONNREFUSED 127.0.0.1:9879
VOLUMIO 11/5/2026-12:30:37 connect ETIMEDOUT 31.13.94.49:443
VOLUMIO 11/5/2026-12:28:52 socket hang up
RIVO 11/5/2026-12:27:37 upnp: statusCode 500 & upnpErrorCode
MINIDSPSHD 11/5/2026-12:26:34 Cannot read property fn of undefined
VOLUMIO 11/5/2026-12:24:18 Cannot read properties of undefined (reading sendCommand)
VOLUMIO 11/5/2026-12:23:48 Unable to resolve or reject the same promise twice
MINIDSPSHD 11/5/2026-12:22:51 write EPIPE
VOLUMIO 11/5/2026-12:22:25 This is caused by either a bug in Node.js or incorrect usage of Node.js internals. Please open an issue with this stack trace at https://github.com/nodejs/node/issues
VOLUMIO 11/5/2026-12:21:20 The value of byteLength is out of range. It must be >= 1 and <= 6. Received 8
VOLUMIO 11/5/2026-12:16:43 Cannot read property service of null
VOLUMIO 11/5/2026-12:16:13 Command failed: /usr/bin/sudo /usr/bin/timedatectl set-timezone Asia/Shanghai Failed to set time zone: Access denied
RIVO 11/5/2026-12:14:20 upnp: statusCode 500 & upnpErrorCode s:ClientUPnPError701
VOLUMIO 11/5/2026-12:13:42 Cannot read properties of undefined (reading service)
MINIDSPSHD 11/5/2026-12:12:43 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-12:10:51 write EPIPE
VOLUMIO 11/5/2026-12:10:38 Chaining cycle detected for promise #
MINIDSPSHD 11/5/2026-12:9:40 Cannot read property fn of undefined
VOLUMIO 11/5/2026-12:8:0 00A553F7:error:03000082:digital envelope routines:EVP_CIPHER_CTX_set_key_length:invalid key length:../deps/openssl/openssl/crypto/evp/evp_enc.c:1005:
VOLUMIO 11/5/2026-12:7:45 0095B8F7:error:03000082:digital envelope routines:EVP_CIPHER_CTX_set_key_length:invalid key length:../deps/openssl/openssl/crypto/evp/evp_enc.c:1005:
VOLUMIO 11/5/2026-12:7:27 Cannot read properties of null (reading slice)
MINIDSPSHD 11/5/2026-12:7:13 write EPIPE
MINIDSPSHD 11/5/2026-12:5:52 Cannot read property fn of undefined
MINIDSPSHD 11/5/2026-12:3:51 write EPIPE
VOLUMIO 11/5/2026-12:0:55 getaddrinfo EBUSY ws.audioscrobbler.com