Walter Doekes

Okay. Been looking at it some more, and I saw a lot of memory usage, even as redis-server had been killed a moment ago. I dropped the db that seemed...

Okay. I increased memory (and cpu) on the box, and now there is no excessive redis key usage anymore.. By increasing mem, I probably implemented fix no. 1 suggested at...

In the mean time I've gotten a bunch of OOMs again. Here's a sheet of mem usage / key space and highlighted potential culprits:  It would be nice if...

In the mean time I tried adding some limits, and now I'm running into this when doing a single scan: ```yaml redis-server: image: greenbone/redis-server command: # https://forum.greenbone.net/t/redis-oom-killed-on-one-host-scan/15722/5 - /bin/sh -...

Okay. It turned out the problem was indeed the "caching of web pages during CGI scanning" mentioned in [oom-killing-redis-on-large-scan-with-openvas](https://forum.greenbone.net/t/oom-killing-redis-on-large-scan-with-openvas/14251/7). A HashiCorp Vault server was yielding responses of about 770kB for...

Ok. That looks good. Of course it would be better if we could make that `strlen( res ) < 98304` a bit more dynamic. Responses a few hundred K large...

I summarized the stuff here: https://github.com/greenbone/openvas-scanner/issues/1488#issuecomment-2009522054 I'm fine with closing.

:+1: Just one: ``` # wc -L cert-expiry-finder 88 cert-expiry-finder ``` But I'll fix that up with a little tweak now.

While I could see why you would want that. Supporting specifically jinja or any other preprocessor is not part of the scope of the project. However, you could do one...

proxtop indeed assumes that VM names are unique. I do not recall ever having seen a separate option for the domain name. We use fully qualified (or at least unique)...