*BSD News Article 93565


Return to BSD News archive

#! rnews 3902 bsd
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!arclight.uoregon.edu!enews.sgi.com!news.corp.sgi.com!news.sgi.com!howland.erols.net!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!hermes.sovam.com!sovam!Gamma.RU!srcc!news.nevalink.ru!news.wplus.spb.ru!not-for-mail
From: "Igor N Kovalenko" <infoh@mail.wplus.net>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: FreeBSD 2.2.0 & 2.2.1
Date: 14 Apr 1997 18:08:25 GMT
Organization: InfoMarket Ltd.
Lines: 85
Message-ID: <01bc48fb$2f130ca0$35b708c2@owl.wplus.net>
References: <5is2ga$nq1@dailyplanet.wam.umd.edu>
NNTP-Posting-Host: ip-160.wplus.net
X-Newsreader: Microsoft Internet News 4.70.1155
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:39073


Hi there,

This is very interesting thread for me, as I had experienced *exactly* the
same behaviour on one completely different UNIX-like OS (QNX), which have
BSD-derived TCP stack however.

So, I guess this problem is related to TCP stack, rather than to an OS.
Tony and Byung suggested good ideas to check out, but it seems that the
problem is "smart" enough.

First, some notes about my situation:

1. All noticed symptoms are the same.
2. PING works fine (both via IP-addr and via DNS-name).
3. No firewalls of any matter (LAN access)
4. No problems with /etc/services, /etc/protocols and /etc/inetd.conf
5. Routing table is good (and quite simple).
6. All interfaces are ok.
7. I can't type on keyboard, but can switch VC (but can't type there 
again) and can do soft reboot (handled by keyboard driver).

BUT ... (unbelievable)

1. Just after reboot *everything* is ok. Nothing in syslog. Filesystem is
ok.
2. After a not so long time situation occurs again.
3. Reboot again and it is fine again ...

After a hard time of guessing what the hell is going on, without any chance
to analize anything :-(, I found only one bad thing - there was no
"localhost" definition in DNS zone (/etc/hosts was not used by resolver).

I would be agreed that the problem was related to this missed definition,
but why my system ever worked for some (*long*) time before?

Situation was happened after Apache 1.1.3 was installed (there was no
problems with 1.1b and another kind of problems with 1.2b4 and b7).

The software running on that system (except for OS) was: 

syslogd
inetd (listening to FTP, TELNET, POP3 and IMAP4)
sendmail 8.6.12
Apache 1.1.3


Hey, BSD networking gurus, have you any ideas what *may* be wrong to lead
to such weird situation?

Regards,
Igor Kovalenko

Byung Yang <byung@wam.umd.edu> wrote in article 

<5is2ga$nq1@dailyplanet.wam.umd.edu>...
> I am using FreeBSD 2.2.0 and there is some server that uses FreeBSD
2.2.1.
> The problem is that I cannot connect to the server.  When I try to telnet
> to the server, it shows :
> Trying ???.???.???.???...
> Connected to ???????.???.
> Escape character is '^]'.
> but after that, it just gets stuck there.  I found one weird error that
if
> I try to use rlogin instead, i get :
> -> rcmd: server.com: Undefined error: 0
> and if I try to execute using rsh, then I get :
> -> select: protocol failure in circuit setup
> When I use ftp to connect to the server, it says connected to blah.com
but
> after that, i don't see any login prompts.  Samething happens to www.  It
> says connected to blah.com. waiting for connection. and then it sits
> there.
> I can't access any of the ports on that server.   When I try different
> operating system like windows, then I don't get this error.  It just
> connects.  Other people said it worked.  I used to connect to the server
> using the same setup / OS when the server ran Linux, but after it
switched
> to freebsd 2.2.1, i just can't connect directly from my box.
> Does anyone have any idea? or is it one of the bugs in the new releases?
> THanks all.
> 
> Byung
> 
>