Rising memory load leads to the interactsh-server being killed by OOM reaper or VM crash
#824
Assignees
Labels
Type: Bug
Inconsistencies or issues which will cause an issue or problem for users or implementors.
Comments
interactsh-server being killed by OOM reaper or VM crash
|
Thanks for reporting this issue @MMquant - This will be worked on after the final implementation of projectdiscovery/utils#362. Handling this OOM case in interactsh requires some more attention as one of the security requirement is that data should be encrypted and volatile in RAM, so it's indeed more prone to OOM-killing. As a temporary mitigation, while the internal design is being reworked, I would recommend to try with using disk-storage option (that should reduce the pressure on heap) and (if possible) have some swap configured, so that the OS would try to move first some idle memory pages from interactsh process before proceeding to kill it to free memory. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Interactsh version:
docker image:
projectdiscovery/interactsh-server:v1.1.9Current Behavior:
interactsh-servermemory usage is rising during runtime up to being killed by OOM or VM crash.Expected Behavior:
I would expect some memory management which regularly cleans up the
interactsh-servermemory or fix the memory leak.Steps To Reproduce:
I'm using this
Dockerfileinteractsh-serverconfiguarionI have to set memory limits in
docker-compose.ymlotherwise theinteractsh-serverprocess freezes the host VM. This way it is killed by OOM reaper and gets restarted.Grafana charts from cadvisor + prometheus which is monitoring containers on my VM.
Last 24 hours. You can see that the
interactsh-servercontainer reached the limit and got killed.Last 7 days. Container periodic restarts due to the OOM are evident. Notice the slope of the rising memory load. Previously I used the
interactsh-serverwith SMB enabled. I thought that it's the SMB service what is causing the rising memory load. After disabling it the rising memory load still occurs, not as rapid as with SMB enabled though.The text was updated successfully, but these errors were encountered: