-
Notifications
You must be signed in to change notification settings - Fork 31
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
Zevenet Kestrel Backend Timeout Problem #118
Comments
Hi, the message indicates that the TCP socket against the backend server is
taking more than 5 seconds, you can increase the timeout in order to avoid
this kind of errors.
Thanks!
El jue, 18 ago 2022 a las 9:27, rifateroglu ***@***.***>)
escribió:
… When we use kestrel (.net core cross platform default web server) server
as a backend, Zevenet serve web page as expected but however logs error
(false negative) like that below.
Aug 18 10:21:19 ZEN-LB zproxy: [f:FARMNAME][th:ebf9b700]
[st:2419911][svc:SERVICENAME][bk:192.168.2.21:5003][cl:31.142.225.20]
timeout on backend response after 5 seconds
Aug 18 10:21:19 ZEN-LB zproxy: [f:f:FARMNAME][th:ebf9b700]
[st:2419911][svc:SERVICENAME][bk:192.168.2.21:5003]cl:31.142.225.20
<http://no-response> timeout (5 seconds) reached in the backend response
—
Reply to this email directly, view it on GitHub
<#118>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBQEPAKQGNZTSFJ7CMX6S3VZXQU5ANCNFSM564DH2TQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Emilio CamposZEVENET Teamwww.zevenet.com
Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr>
<https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet>
<https://www.facebook.com/zevenet> <https://github.com/zevenet>
[image: ZEVENET] <https://www.zevenet.com/signature/>
DISCLAIMER: This message contains confidential information and is intended
only for the individual named. If you
are not the named addressee please notify the sender immediately by email
if you have received it by mistake and
delete it from your system, you should not disseminate, distribute or copy
this email in whole or in part.
|
Hi Emilio, I've increased it up to 45 seconds, as I told, Zevent serves web page in miliseconds, but still logs error. |
Do the change and restart the process, ZEVENET uses time in seconds not in
milliseconds.
On the other hand please share config file with us.
Regards
El jue, 18 ago 2022 a las 10:04, rifateroglu ***@***.***>)
escribió:
… Hi Emilio, I've increased it up to 45 seconds, as I told, Zevent serves
web page in miliseconds, but still logs error.
—
Reply to this email directly, view it on GitHub
<#118 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFBQEPF4OGTGCJRXFKX6IBTVZXU7XANCNFSM564DH2TQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Emilio CamposZEVENET Teamwww.zevenet.com
Review ZEVENET Product at Gartner Insights <https://gtnr.io/LfXtqnsSr>
<https://www.linkedin.com/company/zevenet> <https://twitter.com/zevenet>
<https://www.facebook.com/zevenet> <https://github.com/zevenet>
[image: ZEVENET] <https://www.zevenet.com/signature/>
DISCLAIMER: This message contains confidential information and is intended
only for the individual named. If you
are not the named addressee please notify the sender immediately by email
if you have received it by mistake and
delete it from your system, you should not disseminate, distribute or copy
this email in whole or in part.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When we use kestrel (.net core cross platform default web server) server as a backend, Zevenet serve web page as expected but however logs error (false negative) like that below.
Aug 18 10:21:19 ZEN-LB zproxy: [f:FARMNAME][th:ebf9b700] [st:2419911][svc:SERVICENAME][bk:192.168.2.21:5003][cl:31.142.225.20] timeout on backend response after 5 seconds
Aug 18 10:21:19 ZEN-LB zproxy: [f:f:FARMNAME][th:ebf9b700] [st:2419911][svc:SERVICENAME][bk:192.168.2.21:5003]cl:31.142.225.20 timeout (5 seconds) reached in the backend response
Could it be related with Content-Length header? Because Kestrel is not sending this header.
The text was updated successfully, but these errors were encountered: