-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
httpd possible a race condition for lru purge enable (IDFGH-2680) #4753
Comments
@patrykkrz , we will check this, but what happens if you keep config.backlog_conn at the default value of 5? Is the observation same? |
When backlog_conn is 5, I have the same effect. But I think, I need more tries to repeat. |
I can confirm I am experiencing the same issue. HTTPD config: I experience httpd using lots of CPU time (but not causing WDT).
I will try @patrykkrz patch, and let you know. EDIT: With the patch I now get this: Maybe something else? I am also running a sort of DNS hijacker, which may be messing with things. (for captive portal functionality) |
I can confirm I am experiencing the same issue. I'm also tring to use the patch by Patrykkrz but now I have this assert fail: "assertion "invalid state" failed: file "/home/gdvecchia/esp/esp-idf/components/lwip/lwip/src/core/tcp.c", line 1758, function: tcp_kill_state" |
It's another problem: #1194 Try this: SLICAN@0622415 |
…680) espressif#4753" This reverts commit 49058bb.
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes espressif#4753
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes #4753
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes #4753
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes #4753
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes #4753
LRU counter should be started from 1, and not 0, so that all checks work fine. Closes espressif/esp-idf#4753
esp-idf version - tag v4.0
When the server has a lot of open connections (for testing I run several browsers on several computers and connect to the http server).
I expect that the lru purge enable option to allow next clients to connect. Unfortunately, this does not happen. The browser is waiting for a response, and on the server side I see a lot of logs printing over and over:
my http server configuration:
This logs are printing when lru_counter is 0. Maybe in httpd_sess_close_lru, when searching the smallest lru, zero should not be assigned ?
This patch works for me, but I don't know if it's correct.
The text was updated successfully, but these errors were encountered: