[Resolved] net:ERR_CONNECTION_RESET

[fehrudi]

Hello,

I'm using LiteSpeed 5.0 build 21, but I'm running into problem with HTTP2 & SPDY enabled - without it, everything is fine.
The problem is rare, and not always reproducible. The error usually shows up after 5-15 min of idle time on the site, and then if I reload, or navigate on the site, several (but not always the same) resource load fails with net:ERR_CONNECTION_RESET, even after several reloads.

When I open a new window/tab, the site is loading fine again.
I'm experiencing this problem since the first build of 5.0 using Chrome.

Related rows in the log file:

2015-06-17 10:30:02.227 [INFO] [188.227.xxx.xxx:53466:HTTP2-15] Abort request processing by PID:6175, kill: 0, begin time: 1, sent time: 1, req processed: 12
2015-06-17 10:30:02.230 [INFO] [188.227.xxx.xxx:53466:HTTP2-17] Abort request processing by PID:6173, kill: 0, begin time: 1, sent time: 1, req processed: 4
2015-06-17 10:30:02.230 [INFO] [188.227.xxx.xxx:53466:HTTP2-19] Abort request processing by PID:6174, kill: 0, begin time: 1, sent time: 1, req processed: 28
2015-06-17 10:36:13.937 [INFO] [188.227.xxx.xxx:53729:HTTP2-11] Abort request processing by PID:6435, kill: 0, begin time: 0, sent time: 0, req processed: 9
2015-06-17 10:36:21.213 [INFO] [188.227.xxx.xxx:53747] PID: 13375, add child process pid: 6445, procinfo: 0x9625b38
2015-06-17 10:36:57.088 [INFO] Process with PID: 6445 is dead

Could you help me?

Thanks!

 

[mistwang]

How about firefox?
It is more likely a HTTP/2 protocol error.
Can this problem be easily reproduced? If yes and you would like, please make temp root access available to the server. We need to investigate.

 

[raymond]

We've finally made the move to upgrade to LiteSpeed 5 and my partner has also experienced this problem in Chrome but weirdly I haven't seen this happening on my computer.
Please see attached screenshot.

Another one.

 

[mistwang]

We need to somehow reproduce this or capture some debug logging when it happens to find out what is the root cause.

 

[raymond]

How can I capture debug logging and send it to you to investigate on this problem?

 

[mistwang]

If it is easy for your partner to reproduce this problem. you can turn on full debug logging for a short while, let your partner to reproduce the problem.
We will locate related log entries by using his IP.
For chrome, the HTTP/2 and SPDY indicator should be installed. click the indicator, you will see a list of HTTP/2 sessions, click the session to your site, it will shows some HTTP/2 related log on client side, we need that log as well.

 

[raymond]

The problem seem to have been solved by clearing the cookies.
Once the cookies on the browser is cleared, my partner stopped experiencing this problem.

 

[mistwang]

If it happens again, please check request cookie headers.
It could be a bug in handling the cookie header during HTTP/2 header compression. We need to figure it out.