You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
As Snap Chromium is used for GoWitness, it will fill up the '/tmp' directory until is has either finished or disk usage is at 100%.
To Reproduce
Steps to reproduce the behaviour:
Have a list of subdomains 9190 lines long
Have 9GB of disk space free
Run GoWitness
Wait for Subdomain on line ~4713 to be reached
See process has hung and disk usage is 100%
Expected behaviour
Disk not the be filled up and clutter to be automatically removed.
Version Information:
OS: Ubuntu 20.04.6
gowitness: 2.5.0
Additional context
I have a list of 9190 subdomains. My tmp folder was empty, as I had just recently restarted my server. Upon checking back a day later, I noticed it had hung and when checking my disk usage, I was a 100% with 6.9GB '/tmp' folder, 6.9GB of which being '/tmp/snap-private-tmp/snap.chromium'. I checked what line the last subdomain was at, and it only made it to line 4713 before reaching 100% disk usage.
The text was updated successfully, but these errors were encountered:
I just want to add my workaround just in case anyone faces the same issue, it may not be desirable but it works: DISCLAIMER: Only do this is you're ONLY using Snap Chromium for GoWitness. This will delete any profiles or runners you have setup for your headless Chromium or other tools/scripts.
Add user ALL=(ALL:ALL) NOPASSWD: /bin/rm -rf /tmp/snap-private-tmp/snap.chromium to the bottom of /etc/sudoers
Describe the bug
As Snap Chromium is used for GoWitness, it will fill up the '/tmp' directory until is has either finished or disk usage is at 100%.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
Disk not the be filled up and clutter to be automatically removed.
Version Information:
Additional context
I have a list of 9190 subdomains. My tmp folder was empty, as I had just recently restarted my server. Upon checking back a day later, I noticed it had hung and when checking my disk usage, I was a 100% with 6.9GB '/tmp' folder, 6.9GB of which being '/tmp/snap-private-tmp/snap.chromium'. I checked what line the last subdomain was at, and it only made it to line 4713 before reaching 100% disk usage.
The text was updated successfully, but these errors were encountered: