-
Notifications
You must be signed in to change notification settings - Fork 2.6k
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm receiving a 'non-zero exit status 137' error when running Nuclei as part of a script #4824
Comments
Can you share your script? You're receiving an |
Yes, here's the function that triggers nuclei:
|
I have reviewed the code snippet you shared and cannot determine the exact cause of the OOM error you mentioned. However, I noticed that you are also running Katana, which could be a contributing factor to the error. To avoid such errors, ensure that your system has enough memory to support running multiple tools concurrently and storing the necessary data in memory. |
Do you think running nuclei as the last tool will resolve this issue? |
This is my only suggestion since I don't know all the details -script, resource, etc. |
I'm running this script on Ubuntu with 2 VCPUs and 2 GB of RAM. Might this not be enough? |
Better. It seems like you have tried running nuclei and did not encounter any errors. This suggests that the memory capacity of your system is sufficient for running nuclei. Similarly, if you run a script that includes only one tool, for instance, "nuclei", and it runs without any errors, it means that the memory capacity is also enough for running "nuclei" from your script. The same goes for "katana" as well. Therefore, I would suggest running one tool at a time to see how it performs. If the issue persists, try increasing the system resources and retry. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Hi all,
When I run Nuclei manually, everything goes well.
However, when I call it indirectly through a script that performs other tasks in between, I receive the following error from Nuclei:
'non-zero exit status 137'. Why does this happen?
The parameters/flags that I use are '-list' and '-o'.
The text was updated successfully, but these errors were encountered: