Gladys restarts on startup

Configuration
21

Oh ok, I thought it was rebooting in a loop!

In that case, if version 4.71.0 doesn’t fix your issue, it rather indicates a problem specific to your instance rather than an issue related to the update.

I would be curious to see the disk bandwidth usage. An HDD remains quite slow and not necessarily suitable for this type of software like Gladys.

By the way, DuckDB itself states this on its website:

DuckDB’s disk-based mode is designed to work best with SSD and NVMe disks. While HDDs are supported, they will result in low performance, especially for write operations.

22

And it looks like Gladys v4.71 has been running since 3:00 p.m.

1 Like
23

Yes but apparently he also doesn’t have access on 4.71:

24

Is your Gladys port properly bound to the host?

Which command did you use to start your container?

For reference:

or

I wonder if port 80 is not already listening on your machine and this is not causing your frontend inaccessibility issue?

Try binding it to another free port for your test?