Hi Chris, On Fri, 28 Jul 2023 10:17:49 +0100 "Chris Lamb" <la...@debian.org> wrote:
> > Hm. Do you know what part of the postinst script is sticking? You may > be able to find out by looking at your process table eg. via top or > htop. > > (My initial guess is that redis process itself gets wedged when it has > no diskspace, and then—even after freeing some space—the postinst is > waiting for it to restart?) > I think I saw something like that, indeed, one of my probes into the system showed that a "systemctl stop redis" or something very similar was still running. This seems quite odd to me -- I thought Redis, at least in its default configuration (which is what I use), was an in-memory database. Why would it get stuck over low disk space? And, if it does get stuck -- why wouldn't we just kill it? And how come the postinst script is SIGINT-resistant?
