[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::ase

Title:	ase

Moderator:	SMURF::GROSSO

Created:	Thu Jul 29 1993
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2114
Total number of notes:	7347

1856.0. "are these doti_tcp_open messages just informational?" by COMICS::HAWLEYI (668 - the neighbour of the beast!) Tue Feb 04 1997 05:05

Hi all,

Ive got a customer thats receiving bursts of certain messages into kern.log.
He's running ASE 1.3 on DUnix 3.2. He has applied certain patches to ASE but at
present i'm not sure which ones.

The messages will fire into kern.log for a while before stopping for a while and
then starting up again. I have seen a related note that seems to state that
these messages could be related to unterminated ethernet.

I guess what I really need to know is whether his ASE configuration could be
under any threat.

extract from kern.log. the numbers in parentheses increment on each message, the
number 1234 is for example purposes only.


vmunix: doti_tcp_open: nc[1234]: soconnect failed 65doti_nc_acquire:
doti_tcp_open failed: 65

can anyone help?


thanks,

Ian Hawley.

T.R	Title	User	Personal Name	Date	Lines
1856.1		usr405.zko.dec.com::Marshall	Rob Marshall	`Tue Feb 04 1997 21:24`	16
	Hi Ian, > vmunix: doti_tcp_open: nc[1234]: soconnect failed 65doti_nc_acquire: > doti_tcp_open failed: 65 I have no idea what routine that is supposed to be. All I know is that an error 65 is EHOSTUNREACH - ie the host is unreachable. So whoever is trying to open a socket to whatever host, is finding out that the host is not answering. But, I could not find any trace of a routine called either doti_tcp_open, or doti_nc_acquire. Are you sure this is the exact text of the error message? Is there such a thing as an 'nc' network interface?? Rob
1856.2	hmmmmmmm	COMICS::HAWLEYI	668 - the neighbour of the beast!	`Wed Feb 05 1997 08:39`	8
	Thanks for your reply Rob, yeah, thats the exact error alright. Theres a single previous occurance of this on comet. same error. It was caused by 'unterminated ethernet'. nc....hmmm....NetConnect? not sure. As it is, I think we will take a close look at what his machine is trying to talk to... Thanks, ian.
1856.3	DECnet-OSI installed?	VIRGIN::SUTTER	Who are you ??? - I'm BATMAN !!!	`Thu Feb 06 1997 05:35`	14
	> vmunix: doti_tcp_open: nc[1234]: soconnect failed 65doti_nc_acquire: > doti_tcp_open failed: 65 These messages come from DECnet-OSI, particularly DECnet over TCP (doti). Maybe doti got problems with IP Aliases or some such. Deconfigure doti and these messages should go away. Don't know wether DECnet-OSI is supported in a TruCluster (not according to Code Warrior anyway ...) Regards, Arnold