On Fri, Sep 21, 2007 at 01:49:19PM +0200, Petr Holub wrote: > Hi, > > I've encountered the following problem while building xorg from > ports: > > TCP: [134.76.12.3]:21 to [147.251.54.186]:56914 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:62424 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:55989 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > TCP: [134.76.12.3]:21 to [147.251.54.186]:52923 tcpflags 0x18<PUSH,ACK>; tcp_do_ > segment: FIN_WAIT_1: Received data after socket was closed, sending RST and remo > ving tcpcb > > It occurred from several different addresses and results in being > unable event to ping that IP until reboot. This is "normal" for the current time being, as the output in question is being used to help track down a TCP-related bug in -CURRENT: http://lists.freebsd.org/pipermail/freebsd-current/2007-August/075984.html If the log messages annoy you, set the following sysctl. net.inet.tcp.log_debug=0 -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |Received on Fri Sep 21 2007 - 11:51:06 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:17 UTC