Describe the bug
If the server on which this container is running comes under heavy pressure, processes like ospd-openvas die.
To Reproduce
Steps to reproduce the behavior:
Have a big server with muchrum and much CPU
Start some scanns
Let this run for some days and keep the mashine under pressure, also RAM etc.
(you can also do it by hand from HV side - kill ospd-openvas like OOM would do....)
when you look to the webinterface you will see some about scans and this is the step where you see ospd-openvas is died!
See error - look into the Container and look for ospd-openvas all gone
Expected behavior
I recommend Supervisor with an initialization script that monitors and restarts the processes. Without monitoring you don't get to know about dead processes in the container.
Additional context
Latest Version and before affacted.
Describe the bug If the server on which this container is running comes under heavy pressure, processes like ospd-openvas die.
To Reproduce Steps to reproduce the behavior:
ospd-openvaslike OOM would do....)ospd-openvasis died!ospd-openvasall goneExpected behavior I recommend Supervisor with an initialization script that monitors and restarts the processes. Without monitoring you don't get to know about dead processes in the container.
Additional context Latest Version and before affacted.