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
First of all, thanks everyone who contributed to sarpedon. This server helped our cyber teams a lot. We have been using it for a while. It is running great, very fast on scoring. It's just we've noticed that for some reason the server will hang once in a while. And, these are the errors we saw:
Oct 30 22:51:15 hpdesk sarpedon[2805868]: 2022/10/30 22:51:15 http: Accept error: accept tcp [::]:4013: accept4: too many open files; retrying in 1s
Oct 30 22:51:16 hpdesk sarpedon[2805868]: 2022/10/30 22:51:16 http: Accept error: accept tcp [::]:4013: accept4: too many open files; retrying in 1s
Oct 30 22:51:17 hpdesk sarpedon[2805868]: 2022/10/30 22:51:17 http: Accept error: accept tcp [::]:4013: accept4: too many open files; retrying in 1s
Hi titanturtles, glad to hear this software has been helpful :) And thanks for the contribution!
We've added a timeout to the web server (9c5baf9), hopefully that upstreams your fix correctly. PR's are always open as well if you have any future fixes.
Although, it's strange that you would run into this issue unless you have a ton of competitors who all have slow uplinks. If you find people receiving timeouts now, you may want to increase the timeout and raise the open file limit for your system and sarpedon (with sysctl/ulimit).
First of all, thanks everyone who contributed to sarpedon. This server helped our cyber teams a lot. We have been using it for a while. It is running great, very fast on scoring. It's just we've noticed that for some reason the server will hang once in a while. And, these are the errors we saw:
We did some research, seems that golang http package does not have a default timeout value https://stackoverflow.com/questions/52456506/getting-too-many-open-files-during-load-test-with-gin-gonic. And, the package we used in this repo is gin gonic, which is also using http package under the hood. So, we tried to add timeout in our local server (line 79, main.go):
This seems to be working so far. But, we haven't tested extensively, yet.
The text was updated successfully, but these errors were encountered: