2 Jul
2010
2 Jul
'10
1:55 p.m.
Andrei Pelinescu-Onciul writes:
My guess is that is something else that prevents even
trying to forward
the first time (e.g. blacklisted destination, onsend_route).
What reply does it send back?
there is no blacklists in the config, neither onsend_route.
A dump of the tcp traffic and runnning with a high
debug level will also
help finding out what's happening.
Last but not least: sercmd dst_blacklist.view
i'll come back when i'm able to reproduce this at will. i have noticed
it a few times, but it does not happen every time when i restart sr.
Regarding "quick connect" note that this
message appears only when a
connect() finishes immediately and the following send() is able to
send all the data. This happens mostly on localhost or fast local
networks. In general the connect() will not complete so fast and the
data will be queued for sending later (after the connection is
established).
the problem has occurred on localhost (destination address
127.0.0.1:5082).
-- juha