Instance down since last night

Configuration
1

Hello everyone,
Since last night my Gladys instance (Docker on a Proxmox VM) is down with the Docker log below:

2025-06-21T13:20:15+0200 \u003cerror\u003e index.js:16 (process.\u003canonymous\u003e) [Error: Connection Error: Connection was never established or has been closed already] {

\u0002
errno: -1,

code: ‹ DUCKDB_NODEJS_ERROR ›,

errorType: ‹ Connection ›

}

There hasn’t been any update; I don’t really understand why I’m suddenly getting this error.
The container keeps restarting in a loop during this time.

The only change on the machine was an apt upgrade yesterday morning, and I have a cron job that restarts Gladys from time to time.

Meanwhile my test instance has no problem.

Does anyone have any leads please? I’d like to avoid having to delete my Docker volume and reconfigure everything.

2

Hi @s7evinLN
do you have backups of your VM on your Proxmox by any chance?
Was your apt upgrade done in the VM or on your Proxmox?
And what does the disk status say in Proxmox? and in your LVM and LVM-Thin?
![image|

3

Yes, I have backups — I’ll restore a version; no disk space issue as far as I can tell.
I’ve patched everything, PVE (Proxmox VE) and the VMs directly

4

I restored an earlier version of the VM, everything is OK.
Strange, I can’t understand the connection.

Edit
Apparently I have 2 accounts on this forum …

5

Data corruption on the disk?

6

Maybe, before a new update I’ll mainly back up my configs and scenes

7

Yes, it’s worth having automated backups :slight_smile:

The simplest/most reliable option is to use the Gladys Plus backup: Gladys Plus | Gladys Assistant

Alternatively, backing up the SQLite database file to disk also works, but you must stop Gladys before saving the file to avoid data corruption.

8

One day I’ll upgrade to Gladys Plus, when my finances

1 Like