Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.Hawaii.Edu!news.lava.net!news-w.ans.net!newsfeeds.ans.net!chi-news.cic.net!arclight.uoregon.edu!news.sprintlink.net!news-peer.sprintlink.net!howland.erols.net!news.bbnplanet.com!cam-news-hub1.bbnplanet.com!uunet!in3.uu.net!199.232.136.71!venus.os.com!craigs From: craigs@os.com (Craig Shrimpton) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Hung sockets and innd problem Date: Wed, 11 Dec 1996 08:47:00 -0500 Organization: Orbit Systems Lines: 38 Message-ID: <craigs-ya023180001112960847000001@news.os.com> NNTP-Posting-Host: titan.os.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: Yet Another NewsWatcher 2.3.1 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32442 Folks, I'm running 2.1-STABLE and have been experiencing a problem with news feeds stuck in a CLOSE_WAIT state. It seems only a reboot will fix it. What is causing this and can I clear it without rebooting? Innd reports: Dec 11 08:35:01 venus innd: news1.netusa.net:21 wakeup Dec 11 08:35:01 venus innd: newsie.cent.net:8 wakeup Dec 11 08:35:01 venus innd: newsie.cent.net:16 wakeup Dec 11 08:35:01 venus innd: news1.netusa.net:21 cant write No route to host Dec 11 08:35:01 venus innd: news1.netusa.net:21 sleeping Dec 11 08:35:01 venus innd: newsie.cent.net:8 cant write No route to host Dec 11 08:35:01 venus innd: newsie.cent.net:8 sleeping Dec 11 08:35:01 venus innd: newsie.cent.net:16 cant write No route to host Dec 11 08:35:01 venus innd: newsie.cent.net:16 sleeping Netstat reports: tcp 0 0 venus.nntp newsie.dmc.com.3878 ESTABLISHED tcp 0 80 venus.login solar.1023 ESTABLISHED tcp 0 0 venus.nntp newsie.dmc.com.1792 CLOSE_WAIT tcp 0 0 venus.nntp news1.NetUSA.Net.1576 ESTABLISHED tcp 0 0 venus.nntp news1.NetUSA.Net.1708 CLOSE_WAIT tcp 0 0 venus.nntp newsie.dmc.com.1296 CLOSE_WAIT The processes marked as established are delivering news normally. As you can see they come from the same source so the "No route to host" message is in error. Any pointers are appreciated. Thanks, Craig