# Socket problem **URL:** \ **Category:** Configuration\ **Tags:** socket\ **Created:** [December 9, 2023, 6:10pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610 "2023-12-09T18:10:39Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 9, 2023, 6:10pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/1 "2023-12-09T18:10:39Z")
Hello ! I’m having trouble accessing Gladys, no matter the page, I have an endless loading with this error in the console : > WebSocket connection to ‹ ws://192.168.1.30:8420/ › failed: The operation couldn’t be completed. Socket is not connected ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/c/c3eb4fff50e52a0533d00bf1df22688cd068fbef.png) ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/e/ec8974c720190a6079ff7bdb5912419c10de0658.png) On the G+ side ![image](https://gladys-assistant-community.b-cdn.net/uploads/default/original/2X/8/8d60f9b17f064bf568d4211a1af81d7e190dba65.png) So no access to the dashboard or via Gladys+. I tried to restart my container (nothing works). The logs I don’t see anything but it seems to be running : > **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 caught: 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 caught: 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 caught: 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 caught: 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 caught: 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 caught: 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 Presence Sensor 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.calculateAggregateChildProcess.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 Presence Sensor 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 Presence Sensor 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 Presence Sensor 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 Presence Sensor 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 Presence Sensor 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 Presence Sensor 1, feature target\_distance not configured in Gladys. EDIT: The DB seems to be locked but why? ☹ How to unlock it? It’s been 3 hours ---
**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\ **Post date:** [December 9, 2023, 7:19pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/2 "2023-12-09T19:19:49Z")
I don’t remember your setup, but do you have Gladys on an SD card? On an SSD? Could it be disk corruption? ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 9, 2023, 7:21pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/3 "2023-12-09T19:21:52Z")
Indeed I didn’t specify, I’m on Synology, it’s the only service that’s down 😕 My HDDs are healthy ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 9, 2023, 8:46pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/4 "2023-12-09T20:46:01Z")
As soon as the container is 5 or 6 minutes old I lose the ws etc ☹ ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 9, 2023, 9:29pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/5 "2023-12-09T21:29:43Z")
Hi @spenceur is this in addition to your tablet session problems…maybe a weak power supply, disk saturation, data corruption, or a RAM stick on your Synology (syno) gone bad. Stop your containers, check that your Synology is OK first, verify your disk(s) (what Synology do you have, a DS1… or DS2…?), if all that is OK then maybe corruption of the container or of the DB, are you on « Gladys Plus »? possibly do a clean install of Gladys rather than searching for ages if it’s data corruption! how do you know your HDDs are healthy? (so ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 9, 2023, 9:45pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/6 "2023-12-09T21:45:25Z")
Actually I think I’ve found it: I left Gladys running and it seems that this task was blocking everything: Cleaning old device states I can understand that it would take a lock, but why does it run in the middle of the day? ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 9, 2023, 9:56pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/7 "2023-12-09T21:56:37Z")
That’s good, but it’s annoying that it’s a blocking event that doesn’t indicate its start and shows the processing as in progress… as much as not being able to configure its start! I’ve never encountered this problem! Maybe submit a feature request to that effect… ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 9, 2023, 9:59pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/8 "2023-12-09T21:59:22Z")
For me this falls more into the category of a blocking bug than a feature; let’s see what @pierre-gilles thinks 🤔 ---
**Author:** ![cce66](https://gladys-assistant-community.b-cdn.net/letter_avatar_proxy/v4/letter/c/8797f3/32.png) [@cce66](https://community.gladysassistant.com/u/cce66)\ **Post date:** [December 10, 2023, 12:38am UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/9 "2023-12-10T00:38:38Z")
I was talking about display features to show that a process is in progress and to allow scheduling the start of cleaning old devices at a given time! 😊 ---
**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\ **Post date:** [December 10, 2023, 12:17pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/10 "2023-12-10T12:17:38Z")
How much RAM does your Synology have? ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 10, 2023, 5:02pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/11 "2023-12-10T17:02:26Z")
20GB of RAM 🙂 ---
**Author:** ![guim31](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/guim31/32/4840_2.png) [@guim31](https://community.gladysassistant.com/u/guim31)\ **Post date:** [December 10, 2023, 5:40pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/12 "2023-12-10T17:40:52Z")
Let’s forget this one 😂😋 ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 11, 2023, 10:27am UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/13 "2023-12-11T10:27:46Z")
> [@spenceur](#): > > I can understand that it creates a lock, but why does it run in the middle of the day? It’s a bug since the latest version of Gladys; the task runs at minute 4 of every hour instead of at 4 AM (cron problem) > > > Currently, it's executed at minute 4 of every hour and not at 4AM like it should… > > > https://github.com/GladysAssistant/Gladys/blob/master/server/config/scheduler-jobs.js#L11 ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 11, 2023, 11:39am UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/14 "2023-12-11T11:39:04Z")
Ok! So the fix won’t be in the new release yet? ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 11, 2023, 12:44pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/15 "2023-12-11T12:44:03Z")
No, the fix hasn’t been made yet. ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 11, 2023, 3:00pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/16 "2023-12-11T15:00:01Z")
The fix: > > > \### Pull Request check-list > > To ensure your Pull Request can be accepted as fa…st as possible, make sure to review and check all of these items: > > \- \[x\] If your changes affects code, did your write the tests? > \- \[x\] Are tests passing? (\`npm test\` on both front/server) > \- \[x\] Is the linter passing? (\`npm run eslint\` on both front/server) > \- \[x\] Did you run prettier? (\`npm run prettier\` on both front/server) > \- \[x\] If you are adding a new features/services, did you run integration comparator? (\`npm run compare-translations\` on front) > \- \[x\] Did you test this pull request in real life? With real devices? If this development is a big feature or a new service, we recommend that you provide a Docker image to the community (\[french forum\](https://community.gladysassistant.com/)/\[english forum\](https://en-community.gladysassistant.com/)) for testing before merging. > \- \[x\] If your changes modify the API (REST or Node.js), did you modify the API documentation? (Documentation is based on comments in code) > > \### Description of change > > Fix https://github.com/GladysAssistant/Gladys/issues/1973 ---
**Author:** ![spenceur](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/spenceur/32/1961_2.png) [@spenceur](https://community.gladysassistant.com/u/spenceur)\ **Post date:** [December 11, 2023, 7:41pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/17 "2023-12-11T19:41:03Z")
Super thx ! ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 18, 2023, 4:31pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/18 "2023-12-18T16:31:52Z")
The bug has been fixed in Gladys Assistant 4.33! > [@Gladys Assistant 4.33 : Joyeux Noël à tous christmas\_tree](https://community.gladysassistant.com/t/gladys-assistant-4-33-joyeux-noel-a-tous/8635): > > Salut à tous ! C’est la dernière release de l’année, je vous présente Gladys Assistant 4.33 santa Au programme, un paquet de correctifs et surtout une fonctionnalité que tout le monde attendait : la possibilité de faire parler Gladys speaking_headspeaker C’est une première alpha, et je suis vraiment content du rendu : Gladys parle dans n’importe quelle langue, avec une voix fluide ( et féminine ! ), que j’ai mis du temps à choisir slight_smile Cette fonctionnalité est disponibl… ---
**Author:** ![pierre-gilles](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/pierre-gilles/32/5886_2.png) [@pierre-gilles](https://community.gladysassistant.com/u/pierre-gilles)\ **Post date:** [December 18, 2023, 4:31pm UTC](https://community.gladysassistant.com/t/probleme-de-socket/8610/19 "2023-12-18T16:31:55Z")