ioBroker/ioBroker.socketio

conn.logout() --> error message adapter.log

fm0609 opened this issue · 0 comments

The adapter works fine. But disconnecting the socket doing conn.logout() triggers an error message in the ioBroker log and shutsdown the socket.io adapter, which automatically is doing a successfull restart.

Here are the logs:

887
LOG HERUNTERLADEN

Log-Größe: 160.5 KB

socketio.0 Zeit silly Nachricht
socketio.0 2023-02-22 15:49:50.138 info ==> Connected system.user.admin from ::ffff:192.168.178.45
socketio.0 2023-02-22 15:49:42.801 info socket.io server listening on port 8084
socketio.0 2023-02-22 15:49:42.622 info starting. Version 4.2.0 in /opt/iobroker/node_modules/iobroker.socketio, node: v16.18.1, js-controller: 4.0.23
socketio.0 2023-02-22 15:49:10.070 warn Terminated (UNCAUGHT_EXCEPTION): Without reason
socketio.0 2023-02-22 15:49:10.068 info terminating
socketio.0 2023-02-22 15:49:10.065 info <== Disconnect system.user.admin from ::ffff:192.168.178.45 Test-Con
socketio.0 2023-02-22 15:49:10.064 info terminating http server on port 8084
socketio.0 2023-02-22 15:49:10.034 error invalid id undefined
socketio.0 2023-02-22 15:49:10.033 error Error: invalid id undefined at Object.maybeCallbackWithError (/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js:2973:17) at StateRedisClient.destroySession (/opt/iobroker/node_modules/@iobroker/db-states-redis/lib/states/statesInRedisClient.js:1282:26) at Adapter.destroySession (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.js:8242:27) at Socket. (/opt/iobroker/node_modules/iobroker.socketio/lib/socket.js:1550:26) at Socket.emit (node:events:513:28) at Socket.emit (node:domain:489:12) at /opt/iobroker/node_modules/iobroker.socketio/node_modules/socket.io/lib/socket.js:531:14 at processTicksAndRejections (node:internal/process/task_queues:78:11)
socketio.0 2023-02-22 15:49:09.693 error unhandled promise rejection: invalid id undefined
socketio.0 2023-02-22 15:49:09.692 error Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
socketio.0 2023-02-22 15:48:46.916 info ==> Connected system.user.admin from ::ffff:192.168.178.45