Conference turris::digital_unix

8936.0. "TCP inbound connections "magically" dissapear?" by 16.181.128.8::jpt (FIS and Chips) Mon Feb 24 1997 10:44

	I'm in need for (urgent) help:

	After instaling PATHWORKS V6.1 from Jan Layered products CD
	TCP inbound connections all just stopped working. That means that
	even inetd runs, no-one or nothing can connect to any tcp sockets,
	aka when connection will be tried, it waits until connection
	times out.

	What works:

		- inbound/outbound UDP (NFS etc)
		- outbound TCP (telnet etc)

	What doesn't work:

		- direct inbound TCP connections
		- rsh outbound commands to aother system (but rlogin)

	As this system is AlphaSTation 500/400, it means that there are
	some major issues:

		- X Server/CDE DT session doesn't start correctly
		- LSM vold hasn't started (it stays in booted state)

	System directories are on AdvFS (/var = ufs), and system 
	directories don't use LSM, but because no component can
	connect LSM vold, it means that user data can't be recovered
	from LSM volumes.

	All tcp (in)sockets are in LISTEN state, but it seems like the
	connections never "reach" the socket but just hang on until
	timeout. If I for example finger the system, request stays in
	SYS_SENT state until timeout. (netstat -a)

	netstat -I for tu0 and lo0 shows nothing special. ifconfig states
	that interface is up and running....eh... I'm running out of
	guesses.

	So, any good hints, guesses, touches of magic wand...?

	Btw: PATHWORKS has now been removed, no effects.

	Thanks for help,

		-jari

	FYI:

	LAT works just fine both ways, inbound and outbound connections.

	And UNIX version is V4.0A.

		-jari

	Just to add:

	Nothing in syslog.dated logs.

	inetd -d gives no messages at all after normal start messages (aka
	no messages from inbound connects).

	No uerf errors.

	Puzzled,

		-jari