It seems vpp is sending and receiving fins and resets. So if the remote end did
not send fins, probably the resets are the source of the epoll HUPs. If you
want to debug why those resets were sent, you might have to capture a pcap
trace or try to capture them while they are sent. “show tcp stats
Hi,
It can be that vpp reset the connection due to some bogus packets or because
the connection could not be allocated. Check “show errors”.
Given the config, in particular, 30M fifos (those are pretty large) and 32k
event queue size, maybe add:
segment-size 70
add-segment-size 7
[Edited Message Follows]
Hi, Florin,
I'm using epoll with LDP, but sometimes I receive EPOLLRDHUP|EPOLLHUP
unexpectedly when the opposite side didn't send the FIN or RST packet. Here is
my vcl config, am Iconfiguring something wrong? Thank you very much for your
help.
*
vcl {
rx-fifo-size 3
[Edited Message Follows]
Hi, Florin,
I'm using epoll with LDP, but sometimes I receive EPOLLRDHUP|EPOLLHUP
unexpectedly when the opposite side didn't send the FIN packet. Here is my vcl
config, am Iconfiguring something wrong? Thank you very much for your help.
*
vcl {
api-socket-name /run/v
Hi, Florin,
I'm using epoll with LDP, but sometimes I receive EPOLLRDHUP|EPOLLHUP
unexpectedly when the opposite side didn't send the FIN packet. Here is my vcl
config, am Iconfiguring something wrong? Thank you very much for your help.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sen
