Problème de socket

Hello !

J’ai un soucis pour accédé a Gladys,

peu importe la page j’ai un chargement interminable avec dans la console cette erreur :

WebSocket connection to ‹ ws://192.168.1.30:8420/ › failed: The operation couldn’t be completed. Socket is not connected

Côté g+

Du coup plus accès au dashboard ni via Gladys+.

j’ai tenté de redémarrer mon container (rien n’y fait).

les logs je n’ai rien vu mais il semble tourné :

Log

2023-12-09T18:15:19.825476657Z > start:prod
2023-12-09T18:15:19.825483219Z > cross-env NODE_ENV=production node index.js
2023-12-09T18:15:19.825504146Z
2023-12-09T18:15:51.551755037Z 2023-12-09T19:15:51+0100 job.purge.js:17 (Job.purge) Deleting all background jobs created before = Sat Dec 02 2023 19:15:51 GMT+0100 (GMT+01:00)
2023-12-09T18:16:01.226710487Z 2023-12-09T19:16:01+0100 index.js:14 (Object.start) starting Alexa service
2023-12-09T18:16:01.489002584Z 2023-12-09T19:16:01+0100 index.js:16 (Object.start) Starting MQTT service
2023-12-09T18:16:01.553661493Z 2023-12-09T19:16:01+0100 updateContainer.js:13 (MqttHandler.updateContainer) MQTT: checking for required changes…
2023-12-09T18:16:01.554081144Z 2023-12-09T19:16:01+0100 updateContainer.js:41 (MqttHandler.updateContainer) MQTT: no container update required
2023-12-09T18:16:01.611726497Z 2023-12-09T19:16:01+0100 connect.js:38 (MqttClient.) Connected to MQTT server mqtt://localhost
2023-12-09T18:16:01.612907180Z 2023-12-09T19:16:01+0100 subscribe.js:12 (MqttHandler.subscribe) Subscribing to MQTT topic gladys/master/#
2023-12-09T18:16:01.662918600Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708237120Z NotFoundError: DeviceFeature zwave:node_id:4:comclass:38:index:0:instance:1 not found
2023-12-09T18:16:01.708260647Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708267404Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708272639Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708277482Z }
2023-12-09T18:16:01.708296996Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:4:comclass:38:index:0:instance:1 not found
2023-12-09T18:16:01.708303035Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708307896Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708312522Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708317224Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708322379Z NotFoundError: DeviceFeature zwave:node_id:4:comclass:49:index:4:instance:1 not found
2023-12-09T18:16:01.708327691Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708333340Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708355047Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708361561Z }
2023-12-09T18:16:01.708367116Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:4:comclass:49:index:4:instance:1 not found
2023-12-09T18:16:01.708373343Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708397375Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708403526Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708408947Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708414485Z NotFoundError: DeviceFeature zwave:node_id:4:comclass:50:index:0:instance:1 not found
2023-12-09T18:16:01.708420401Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708425715Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708430754Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708435840Z }
2023-12-09T18:16:01.708440664Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:4:comclass:50:index:0:instance:1 not found
2023-12-09T18:16:01.708446443Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708451712Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708456784Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708461764Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708469879Z NotFoundError: DeviceFeature zwave:node_id:5:comclass:38:index:0:instance:1 not found
2023-12-09T18:16:01.708475616Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708480888Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708485970Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708491050Z }
2023-12-09T18:16:01.708496533Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:5:comclass:38:index:0:instance:1 not found
2023-12-09T18:16:01.708502293Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708507404Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708512488Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708517548Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708522895Z NotFoundError: DeviceFeature zwave:node_id:5:comclass:49:index:4:instance:1 not found
2023-12-09T18:16:01.708528191Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708533548Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708538426Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708548690Z }
2023-12-09T18:16:01.708554439Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:5:comclass:49:index:4:instance:1 not found
2023-12-09T18:16:01.708560309Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708565565Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708570907Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708576299Z 2023-12-09T19:16:01+0100 index.js:15 (process.) unhandledRejection catched: Promise {
2023-12-09T18:16:01.708582046Z NotFoundError: DeviceFeature zwave:node_id:5:comclass:50:index:0:instance:1 not found
2023-12-09T18:16:01.708587358Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708592597Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708597584Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:01.708602719Z }
2023-12-09T18:16:01.708607695Z 2023-12-09T19:16:01+0100 index.js:16 (process.) NotFoundError: DeviceFeature zwave:node_id:5:comclass:50:index:0:instance:1 not found
2023-12-09T18:16:01.708613301Z at DeviceManager.newStateEvent (/src/server/lib/device/device.newStateEvent.js:17:11)
2023-12-09T18:16:01.708618608Z at EventEmitter.emit (node:events:517:28)
2023-12-09T18:16:01.708624449Z at Event.emit (/src/server/lib/event/index.js:18:16)
2023-12-09T18:16:02.078827923Z 2023-12-09T19:16:02+0100 index.js:18 (Object.start) Starting RTSP service
2023-12-09T18:16:02.512222557Z 2023-12-09T19:16:02+0100 index.js:18 (Object.start) Starting Philips Hue service
2023-12-09T18:16:03.259386763Z 2023-12-09T19:16:03+0100 init.js:14 (NodeRedManager.init) Nodered: is not enabled, skipping…
2023-12-09T18:16:03.857434887Z 2023-12-09T19:16:03+0100 index.js:27 (Object.start) Starting MELCloud service 48522e52-5687-446d-8d43-03ab493f5bdc
2023-12-09T18:16:03.862775158Z 2023-12-09T19:16:03+0100 service.start.js:40 (Service.start) Service melcloud is not configured, so it was not started.
2023-12-09T18:16:04.105695844Z 2023-12-09T19:16:04+0100 index.js:17 (Object.start) Starting Tuya service d9c3cbd0-487d-458c-8e1f-ae94101c3e3d
2023-12-09T18:16:05.862513072Z 2023-12-09T19:16:05+0100 service.start.js:44 (Service.start) Unable to start service tuya TypeError: Cannot destructure property ‹ list › of ‹ result › as it is undefined.
2023-12-09T18:16:05.862572630Z at TuyaHandler.loadDevices (/src/server/services/tuya/lib/tuya.loadDevices.js:25:11)
2023-12-09T18:16:05.862578470Z at processTicksAndRejections (node:internal/process/task_queues:95:5)
2023-12-09T18:16:05.862583364Z at Object.start (/src/server/services/tuya/index.js:19:5)
2023-12-09T18:16:05.862587936Z at Service.start (/src/server/lib/service/service.start.js:33:7)
2023-12-09T18:16:06.224034228Z 2023-12-09T19:16:06+0100 index.js:16 (Object.start) Starting Nextcloud Talk service
2023-12-09T18:16:06.227733648Z 2023-12-09T19:16:06+0100 service.start.js:40 (Service.start) Service nextcloud-talk is not configured, so it was not started.
2023-12-09T18:16:06.244748983Z 2023-12-09T19:16:06+0100 index.js:17 (Object.start) Starting LAN Manager service
2023-12-09T18:16:06.254784955Z 2023-12-09T19:16:06+0100 lan-manager.initPresenceScanner.js:18 (LANManager.initPresenceScanner) LANManager configuration: starting presence scanner
2023-12-09T18:16:06.967486004Z 2023-12-09T19:16:06+0100 index.js:16 (Object.start) starting Broadlink service
2023-12-09T18:16:07.910132976Z 2023-12-09T19:16:07+0100 broadlink.addPeripheral.js:29 (BroadlinkHandler.addPeripheral) Broadlink discovers new peripheral: dabb5a770f78
2023-12-09T18:16:08.148411990Z 2023-12-09T19:16:08+0100 index.js:18 (Object.start) Starting HomeKit service
2023-12-09T18:16:09.834148733Z 2023-12-09T19:16:09+0100 index.js:88 (Object.start) Starting CalDAV service
2023-12-09T18:16:10.144932849Z 2023-12-09T19:16:10+0100 init.js:39 (Zigbee2mqttManager.init) Zigbee2mqtt USB dongle attached to /dev/ttyUSB0
2023-12-09T18:16:10.146584937Z 2023-12-09T19:16:10+0100 checkForContainerUpdates.js:14 (Zigbee2mqttManager.checkForContainerUpdates) Checking for current installed versions and required updates…
2023-12-09T18:16:10.156487538Z 2023-12-09T19:16:10+0100 installMqttContainer.js:120 (Zigbee2mqttManager.installMqttContainer) MQTT broker container successfully started
2023-12-09T18:16:10.171577954Z 2023-12-09T19:16:10+0100 configureContainer.js:19 (Zigbee2mqttManager.configureContainer) Z2M Docker container is being configured…
2023-12-09T18:16:10.181322774Z 2023-12-09T19:16:10+0100 configureContainer.js:30 (Zigbee2mqttManager.configureContainer) Z2M configuration file already exists.
2023-12-09T18:16:10.284604464Z 2023-12-09T19:16:10+0100 installZ2mContainer.js:91 (Zigbee2mqttManager.installZ2mContainer) Zigbee2mqtt container successfully started
2023-12-09T18:16:10.286212141Z 2023-12-09T19:16:10+0100 connect.js:25 (Zigbee2mqttManager.connect) Connecting Gladys to mqtt://localhost:1884 MQTT broker…
2023-12-09T18:16:10.347477376Z 2023-12-09T19:16:10+0100 connect.js:35 (MqttClient.) Connected to MQTT container mqtt://localhost:1884
2023-12-09T18:16:10.501744093Z 2023-12-09T19:16:10+0100 subscribe.js:12 (Zigbee2mqttManager.subscribe) Subscribing to MQTT topic zigbee2mqtt/#
2023-12-09T18:16:10.549810956Z 2023-12-09T19:16:10+0100 index.js:15 (Object.start) Starting enedis service
2023-12-09T18:16:11.959907754Z 2023-12-09T19:16:11+0100 index.js:15 (Object.start) Starting Bluetooth service
2023-12-09T18:16:13.167899966Z 2023-12-09T19:16:13+0100 service.start.js:44 (Service.start) Unable to start service bluetooth Error: EAFNOSUPPORT, Address family not supported by protocol
2023-12-09T18:16:13.167941748Z at new Hci (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/hci.js:80:18)
2023-12-09T18:16:13.167948088Z at new NobleBindings (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/hci-socket/bindings.js:25:15)
2023-12-09T18:16:13.167953403Z at module.exports (/src/server/services/bluetooth/node_modules/@abandonware/noble/lib/resolve-bindings.js:13:12)
2023-12-09T18:16:13.167958407Z at Object. (/src/server/services/bluetooth/node_modules/@abandonware/noble/index.js:2:51)
2023-12-09T18:16:13.167963561Z at Module._compile (node:internal/modules/cjs/loader:1256:14)
2023-12-09T18:16:13.167968191Z at Object.Module._extensions…js (node:internal/modules/cjs/loader:1310:10)
2023-12-09T18:16:13.167973114Z at Module.load (node:internal/modules/cjs/loader:1119:32)
2023-12-09T18:16:13.167977758Z at Function.Module._load (node:internal/modules/cjs/loader:960:12)
2023-12-09T18:16:13.167982395Z at Module.require (node:internal/modules/cjs/loader:1143:19)
2023-12-09T18:16:13.167987111Z at require (node:internal/modules/cjs/helpers:119:18)
2023-12-09T18:16:13.167991734Z at BluetoothManager.start (/src/server/services/bluetooth/lib/commands/bluetooth.start.js:16:20)
2023-12-09T18:16:13.167996462Z at Object.start (/src/server/services/bluetooth/index.js:16:28)
2023-12-09T18:16:13.168002034Z at Service.start (/src/server/lib/service/service.start.js:33:21) {
2023-12-09T18:16:13.168006702Z errno: 97,
2023-12-09T18:16:13.168011359Z code: ‹ EAFNOSUPPORT ›,
2023-12-09T18:16:13.168015821Z syscall: ‹ socket ›
2023-12-09T18:16:13.168020234Z }
2023-12-09T18:16:13.182551390Z 2023-12-09T19:16:13+0100 handleMqttMessage.js:110 (Zigbee2mqttManager.handleMqttMessage) Zigbee2mqtt device Capteur de présence 1 not configured in Gladys.
2023-12-09T18:17:22.310025292Z 2023-12-09T19:17:22+0100 device.calculateAggregate.js:95 (Socket.) device.calculateAggregate stderr: Error
2023-12-09T18:17:22.310076411Z at Database. (/src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:179:27)
2023-12-09T18:17:22.310084432Z at /src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:177:50
2023-12-09T18:17:22.310089780Z at new Promise ()
2023-12-09T18:17:22.310095045Z at Query.run (/src/server/node_modules/sequelize/lib/dialects/sqlite/query.js:177:12)
2023-12-09T18:17:22.310099922Z at /src/server/node_modules/sequelize/lib/sequelize.js:314:28
2023-12-09T18:17:22.310104725Z at async SQLiteQueryInterface.bulkDelete (/src/server/node_modules/sequelize/lib/dialects/abstract/query-interface.js:403:12)
2023-12-09T18:17:22.310109717Z at async /src/server/lib/device/device.calculcateAggregateChildProcess.js:142:7 {
2023-12-09T18:17:22.310114430Z name: ‹ SequelizeTimeoutError ›,
2023-12-09T18:17:22.310119010Z parent: [Error: SQLITE_BUSY: database is locked] {
2023-12-09T18:17:22.310124008Z errno: 5,
2023-12-09T18:17:22.310128258Z code: ‹ SQLITE_BUSY ›,
2023-12-09T18:17:22.310132653Z sql: « DELETE FROM t_device_feature_state_aggregate WHERE type = ‹ hourly › AND device_feature_id = ‹ c27bf5d1-aee5-4df1-850a-b483fa1a7028 › AND created_at BETWEEN ‹ 2023-12-09 15:00:00.000 +00:00 › AND ‹ 2023-12-09 18:00:00.000 +00:00 › »
2023-12-09T18:17:22.310139047Z },
2023-12-09T18:17:22.310143333Z original: [Error: SQLITE_BUSY: database is locked] {
2023-12-09T18:17:22.310147812Z errno: 5,
2023-12-09T18:17:22.310152105Z code: ‹ SQLITE_BUSY ›,
2023-12-09T18:17:22.310156440Z sql: « DELETE FROM t_device_feature_state_aggregate WHERE type = ‹ hourly › AND device_feature_id = ‹ c27bf5d1-aee5-4df1-850a-b483fa1a7028 › AND created_at BETWEEN ‹ 2023-12-09 15:00:00.000 +00:00 › AND ‹ 2023-12-09 18:00:00.000 +00:00 › »
2023-12-09T18:17:22.310161704Z },
2023-12-09T18:17:22.310165979Z sql: « DELETE FROM t_device_feature_state_aggregate WHERE type = ‹ hourly › AND device_feature_id = ‹ c27bf5d1-aee5-4df1-850a-b483fa1a7028 › AND created_at BETWEEN ‹ 2023-12-09 15:00:00.000 +00:00 › AND ‹ 2023-12-09 18:00:00.000 +00:00 › »,
2023-12-09T18:17:22.310171332Z parameters: {}
2023-12-09T18:17:22.310175683Z }
2023-12-09T18:17:22.310180077Z
2023-12-09T18:17:22.326028491Z 2023-12-09T19:17:22+0100 device.calculateAggregate.js:101 (ChildProcess.) device.calculateAggregate: Exiting child process with code 1
2023-12-09T18:17:22.692127769Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature detection_delay not configured in Gladys.
2023-12-09T18:17:22.692498899Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature fading_time not configured in Gladys.
2023-12-09T18:17:22.692926722Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature maximum_range not configured in Gladys.
2023-12-09T18:17:22.693286521Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature minimum_range not configured in Gladys.
2023-12-09T18:17:22.693666268Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature radar_sensitivity not configured in Gladys.
2023-12-09T18:17:22.694506038Z 2023-12-09T19:17:22+0100 handleMqttMessage.js:106 () Zigbee2mqtt device Capteur de présence 1, feature target_distance not configured in Gladys.

EDIT : La DB semble être locké mais pk ? :frowning:
Comment la delock ? cela fais 3h

Je me rappelle plus ta config mais tu as Gladys sur carte SD ? Sur SSD ? Une corruption de disque peut être ?

Effectivement je n’ai pas précisé, je suis sur Synology, c’est le seul service en rad :confused:
Mes DD son sain

Des que le container a 5 ou 6 min de vie je perds le ws etc :frowning:

Salut @spenceur
ca plus tes problèmes de session de tablette…peut-être une faiblesse de l’alim, une saturation des disques, une corruption de données, une barrette ram de ton syno en rade. Arrête tes containers, check que ton syno soit ok en premier, vérifie ton/tes disks (c’est quoi ton syno un ds1…ou ds2…?) si tout cela est ok alors peut-être corruption du container ou de la bd, t’es en « gladys plus » éventuellement refaire une install propre de gladys plutôt que chercher longtemps si c’est une corruption de données !
comment tu sais que tes dd sont sains ? (un ds2 donc)

enfaite je pense avoir trouvé:

J’ai laisser tourné Gladys et il semblerait que ce soit cette tâche qui bloquait tout :
Nettoyage des vieux états d’appareils

Je peu comprendre qu’elle fasse un lock, mais pk elle s’execute en pleine journée ?

tant mieux, mais par contre que ce soit un evenement bloquant qui n’indique pas son lancement et que le traitement soit en cours c’est embêtant…autant que pas pouvoir paramétrer son démarrage ! J’ai jamais été confronté à ce problème ! peut-être faire une demande de fonctionnalités en ce sens…

1 Like

Pour moi ça rentre plus dans le cadre d’un bug bloquant que d’une features, a voir ce qu’en pense @pierre-gilles :thinking:

je parlais de features pour l’affichage comme quoi un traitement est en cours et pour pouvoir paramétrer le lancement du nettoyage des vieux appareils à une heure donnée ! :blush:

Il a combien de RAM ton syno ?

20Go de memoire vive :slight_smile:

On oublie cette piste :joy::yum:

1 Like

C’est un bug depuis la dernière version de Gladys, la tâche s’exécute à chaque minute 4 de chaque heure au lieu d’à 4 heure du matin (problème de cron)

2 Likes

Ok ! Du coup le fix sera pas encore dans la new release ?

Non le fix n’est pas encore fait

Le fix:

2 Likes

Super thx !

1 Like

Le bug est corrigé dans Gladys Assistant 4.33 !