Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1531
There are reasons for this creash:
1ãATS try to connect the origin server, but receive RST package. So ATS
try again until retry_times == 0. It will clean the server_entry (mark the VC
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1531
I got this again on Docs.
```
(gdb) bt full
#0 0x2b5b8bd881d7 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
GitHub user zwoop reopened an issue:
https://github.com/apache/trafficserver/issues/1531
Assertion in state_read_server_response_header (v7.1.0)
Seeing this on docs (infrequently):
```
(gdb) bt full
#0 0x757b21d7 in __GI_raise (sig=sig@entry=6) at
Github user zwoop closed the issue at:
https://github.com/apache/trafficserver/issues/1531
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user oknet commented on the issue:
https://github.com/apache/trafficserver/issues/1531
I created a PR #1559 to resolve this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1531
Based on #1522 we need to ensure that all the handler should handle read
error event and write error event at same time.
I'll track it !
---
If your project is set up for it, you
Github user oknet commented on the issue:
https://github.com/apache/trafficserver/issues/1531
@zwoop @shinrich It could run into state_read_server_response_header twice
if the data is point to write.vio and the handler function doest not
do_io_close on vc while the 1st run into it.
Github user oknet commented on the issue:
https://github.com/apache/trafficserver/issues/1531
before #947, the EPOLLERR event only set write.triggered to 1, iocore only
callback SM if write.enabled==1 and write.triggered==1.
after #947 , the EPOLLERR set write.error to 1, iocore
Github user scw00 commented on the issue:
https://github.com/apache/trafficserver/issues/1531
I think, it never call handler with read.enabled = 0(or write.enabled). It
means the handler don not want this type of event .It may never handle this
event and just assert!
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1531
Oh, nevermind. I saw vio = NULL in the stack, but that is the local
variable.
That makes sense that the event would be passing up the write via. It is a
write event we are
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1531
Hmmm, I see
```
(gdb) frame 4
#4 0x0064dbac in HttpSM::state_read_server_response_header
(this=0x2aaab2ecc300, event=3, data=0x2aaadfe10fe0) at HttpSM.cc:1811
Github user shinrich commented on the issue:
https://github.com/apache/trafficserver/issues/1531
The server_entry->read_vio is NULL. From what I can tell this value only
gets set due to do_io_read() calls in attach_server_session() and
setup_server_read_response_header().
GitHub user zwoop opened an issue:
https://github.com/apache/trafficserver/issues/1531
Assertion in state_read_server_response_header (v7.1.0)
Seeing this on docs (infrequently):
```
(gdb) bt full
#0 0x757b21d7 in __GI_raise (sig=sig@entry=6) at
13 matches
Mail list logo
