-
Notifications
You must be signed in to change notification settings - Fork 104
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
Server backend connection data is not cleared when the connection socket is closed #52
Comments
This issue is closely related to #46 - |
The log bit outdated. The function offsets pints somewhere just after tfw_sess_conn() call (now the addresses are different):
And now the Oops looks as following
|
krizhanovsky
added a commit
that referenced
this issue
Mar 24, 2015
and #52; 2. Introduce TLS/SSL support in tls.c; 3. Rename backend/frontend sockets server/client correspondingly with forward proxy in mind; 4. Many code cleanups and and some small fixes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After a period of inactivity the socket that serves the server backend connection is closed. However the related Tempesta connection data is not cleared. That leads to a stale pointer to the connection data that no longer exists. Consequently, we get a kernel crash on first attempt to use that connection data, which happens on the very next http request.
The text was updated successfully, but these errors were encountered: