Bad state messages from tmx.mhs.oz/sol.jna.com

Thread View: aus.acsnet

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Gregory N. Bond Mon, 13 Jul 1992 23:42

#64

Author: Gregory N. Bond
Date: Mon, 13 Jul 1992 23:42

67 lines
2973 bytes

I'm running Sun-III (Vn="1.519.21"), connecting to another SUN-III
site.  I have been getting about 15 messages a day about bad state
messages from tmx.mhs.oz / sol.jna.com, because sol is the name of the
machine at deakin.  I understand that this is probably an artifact of
the MHS->SUN-III gatewaying, but is there any way to avoid it?  Is it
just me? I can see this getting much worse as other MHS sites pick
conflicting names.  

Or will I just trash SUN-III and run something that works, like UUCP
(1/2 :-)

(Mail message appended)

Greg.

-----------------------
Date: Tue, 14 Jul 92 08:36:54 EST
From: <daemon>
Message-Id: <9207132236.AA21974@melba.bby.oz.au>
Subject: ACSnet badhandler at melba.bby.oz
Apparently-To: Postmaster



Invoked by "router"

Link "yarra"

Error message <<EOF
	Returned message discarded: Bad exit status 1 from:-
	"/usr2/ACSnet/spool/_lib/stater -B -d3985 -e\036ID=2eMTe3-\
	qv+MTd7\036NOCALL\036NORET\036STATE -hmelba -lyarra -stm\
	x.mhs.oz -t3284 +++6dR++++++CS "
	stderr <<EOF
	Jul 14 08:36:53 stater: error -- Bad exit status 1 from:-
	"/usr/local/ACSnet/acsstate -IRSXc -d711063727 -ftmx.mhs.oz\
	 -hmelba "
	stderr <<EOF
	Jul 14 08:36:52 acsstate: system warning -- /usr2/ACSnet/sp\
	ool/_lib/statsfile: No such file or directory
	Jul 14 08:36:53 acsstate: warning -- Broke putative link be\
	tween "tmx.mhs.oz" and "sol.jna.com" -- node of same name a\
	lready exists called "sol.cc.deakin.oz"
	Jul 14 08:36:53 acsstate: warning -- Rejected export alias \
	"bsdi" for "tmx.mhs.oz" -- already exists
	Jul 14 08:36:53 acsstate: warning -- Rejected export alias \
	"bsdi" for "tmx.mhs.oz" -- already exists
	Jul 14 08:36:53 acsstate: error -- Node "tmx" not a member \
	of any domain in hierarchy
	EOF
	
	EOF
	
EOF

End of message in "/usr2/ACSnet/spool/_bad/1ro+eMUNw3Ku0" <<EOF
	=bsdi.2=oz.0=au\2329=bsdi.3=bsdi.2=oz.0=au\200p\015
	1.3 #5 92/07/04 386-XENIX.2.3.4
	1\000*.oz\000tmx.mhs.oz\000stater\000\036ID=2eMTe3-qv+\
	MTd7\036NOCALL\036NORET\036STATE\00084057\0002343\000\
	,tmx=52,basser=9,munnari=26,yarra=2256\0000\0004B117\000\
	\000\000\000\000
EOF

--
Gregory Bond <gnb@bby.oz.au> Burdett, Buckeridge & Young Ltd, Melbourne 
That's *Mister* Chief Pointyhead to you.

Re: Bad state messages from tmx.mhs.oz/sol.jna.com

#65

Author: Ian Donaldson
Date: Wed, 15 Jul 1992 00:15

36 lines
2469 bytes

gnb@duke.bby.oz.au (Gregory N. Bond) writes:
>I'm running Sun-III (Vn="1.519.21"), connecting to another SUN-III
>site.  I have been getting about 15 messages a day about bad state
>messages from tmx.mhs.oz / sol.jna.com, because sol is the name of the
>machine at deakin.  I understand that this is probably an artifact of
>the MHS->SUN-III gatewaying, but is there any way to avoid it?  Is it
>just me? I can see this getting much worse as other MHS sites pick
>conflicting names.  

As of yesterday I've given up listening to badhandler messages... due 
to this particular problem (>10 bad messages a day from tmx).

I mailed Piers and he said that this was another thing that SunIII just
couldn't cope with.

Now I direct these badhandler warnings to some obscure mailbox that I 
only look at occasionaly (eg: when /usr is getting full :-)   Pity, as 
now I won't get the really *important* ones when I need them.
(I'm contemplating building a simple mail filter for messages about
sites I just don't care about)

My question is also: *why* is tmx sending out so many messages a day?
I've seen this problem over and over again and I thought SunIV was
supposed to *help* in this regard (wrt SunIII).  Previously many
state messages a day have been sent out by SunIV sites that were deemed
to be misconfigured in some way.  Fair enough.  They were usually
fixed (I get no continual badhandler messages from any other site).
However tmx.mhs.oz is a site that I thought shouldn't be in this boat 
(I mean, hey, these people *sell* the product; shouldn't they be trying
to maintain compatability?)

With SunIII the state mesages were only about 300 bytes or so, but SunIV 
they're often 5-10 times larger.  Pity our modem bandwidth hasn't gone
up by the same factor in the last 5 years.

Ian D

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads