hello @pierre-g
it depends on your network but that seems huge to me!
Have you checked the status of the container?
Edit: I moved this thread into a separate post
my network : outdoors : fiber optic
en indoors : wifi from Livebox 6 from Orange
state of the containers : with a docker ps -a, my 3 containers (gladys, watchtower and nodered) have been active for 12 h including since 10 PM last night when I reinstalled.
in the server tree under /var/lib/gladys the sqlite dbs seem to be there (15.3 GB of database) but not completely reinstalled
db and duckdb files are dated 13/9 at 00:35 so they haven’t moved since.
should I try doing a stop/start of gladys ?
And what do the logs of the gladys container say?
Did you launch Gladys with the command on the site ( Installation avec Docker | Gladys Assistant ) including the --restart=always? During the restore, Gladys automatically stops at the end and relies on Docker to restart the container
Excerpt from the Gladys log :
2024-09-13T11:23:31+0200 \u003cerror\u003e index.js:16 (process.\u003canonymous\u003e) Error: ConnectionManager.getConnection was called after the connection manager was closed!
at ConnectionManager.getConnection (/src/server/node_modules/sequelize/src/dialects/abstract/connection-manager.js:113:13)
at /src/server/node_modules/sequelize/src/sequelize.js:637:111
at /src/server/node_modules/retry-as-promised/index.js:64:21
at new Promise (\u003canonymous\u003e)
at retryAsPromised (/src/server/node_modules/retry-as-promised/index.js:54:10)
at Sequelize.query (/src/server/node_modules/sequelize/src/sequelize.js:630:12)
at SQLiteQueryInterface.select (/src/server/node_modules/sequelize/src/dialects/abstract/query-interface.js:1001:33)
at Function.findAll (/src/server/node_modules/sequelize/src/model.js:1816:47)
at Function.findOne (/src/server/node_modules/sequelize/src/model.js:1982:12)
at DeviceManager.get (/src/server/lib/device/device.get.js:97:21)
at LANManager.scanPresence (/src/server/services/lan-manager/lib/lan-manager.scanPresence.js:11:19)
2024-09-13T11:24:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:25 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 13 Sep 2024 09:24:00 GMT
2024-09-13T11:25:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:25 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 13 Sep 2024 09:25:00 GMT
2024-09-13T11:25:31+0200 \u003cerror\u003e index.js:15 (process.\u003canonymous\u003e) unhandledRejection catched: Promise {
\u003crejected\u003e Error: ConnectionManager.getConnection was called after the connection manager was closed!
at ConnectionManager.getConnection (/src/server/node_modules/sequelize/src/dialects/abstract/connection-manager.js:113:13)
at /src/server/node_modules/sequelize/src/sequelize.js:637:111
at /src/server/node_modules/retry-as-promised/index.js:64:21
at new Promise (\u003canonymous\u003e)
at retryAsPromised (/src/server/node_modules/retry-as-promised/index.js:54:10)
at Sequelize.query (/src/server/node_modules/sequelize/src/sequelize.js:630:12)
at SQLiteQueryInterface.select (/src/server/node_modules/sequelize/src/dialects/abstract/query-interface.js:1001:33)
at Function.findAll (/src/server/node_modules/sequelize/src/model.js:1816:47)
at Function.findOne (/src/server/node_modules/sequelize/src/model.js:1982:12)
at DeviceManager.get (/src/server/lib/device/device.get.js:97:21)
at LANManager.scanPresence (/src/server/services/lan-manager/lib/lan-manager.scanPresence.js:11:19)
}
2024-09-13T11:25:31+0200 \u003cerror\u003e index.js:16 (process.\u003canonymous\u003e) Error: ConnectionManager.getConnection was called after the connection manager was closed!
at ConnectionManager.getConnection (/src/server/node_modules/sequelize/src/dialects/abstract/connection-manager.js:113:13)
at /src/server/node_modules/sequelize/src/sequelize.js:637:111
at /src/server/node_modules/retry-as-promised/index.js:64:21
at new Promise (\u003canonymous\u003e)
at retryAsPromised (/src/server/node_modules/retry-as-promised/index.js:54:10)
at Sequelize.query (/src/server/node_modules/sequelize/src/sequelize.js:630:12)
at SQLiteQueryInterface.select (/src/server/node_modules/sequelize/src/dialects/abstract/query-interface.js:1001:33)
at Function.findAll (/src/server/node_modules/sequelize/src/model.js:1816:47)
at Function.findOne (/src/server/node_modules/sequelize/src/model.js:1982:12)
at DeviceManager.get (/src/server/lib/device/device.get.js:97:21)
at LANManager.scanPresence (/src/server/services/lan-manager/lib/lan-manager.scanPresence.js:11:19)
2024-09-13T11:26:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:25 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 13 Sep 2024 09:26:00 GMT
2024-09-13T11:27:00+0200 \u003cinfo\u003e scene.checkCalendarTriggers.js:25 (SceneManager.checkCalendarTriggers) Checking calendar triggers at Fri, 13 Sep 2024 09:27:00 GMT
Yes, the installation was performed by strictly following the commands you had posted on the site.
Including the Node-RED installation commands from your presentation on YouTube.
Ok! Try restarting Gladys, I think the restore worked but it didn’t restart
docker restart gladys
re,
ok apparently the restart seems to have worked, I can find my dashboards, objects, conversations … I just need to recover my Node-RED flows to integrate my weather station via MQTT.
par contre quick question, shouldn’t I rerun the duck migration that was supposed to be incomplete during the Ubuntu crash? I have more than 3
1 Like
Indeed, I recommend that you restart the migration!
hello @pierre-gilles,
quick update after my server crash.
server reinstalled with Ubuntu 24.04.
Gladys reinstalled using the standard script
Node-RED reinstalled too (outside Gladys)
database restoration from a GladysPlus backup (long and slowing the server, missing screens showing progress)
duck migration restarted, SQLite state purge performed and apparently effective.
SQLite database cleanup run twice but the database remains surprisingly large (13.5 GB).
I still need to redo my Node-RED flows for my weather station and my EDF meter (using Pitinfo and Wemos, which is ideal when I see all the headaches with the Enedis API and/or Lixee).
upgraded to the new Gladys version this morning without any issues.
Great, thanks for the feedback!
Are you sending a lot of messages in your scenes? Your « message » table is probably full; there is a cleanup task that was introduced in v4.45.1 — it will run
@Einstein8854 Have you restarted your machine after the cleanup?