'msg- CONVERSATION FAILED (exit code 101)'

Thread View: uunet.forum

4 messages

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

4 total messages Started by Andy Finkenstadt Mon, 27 Jul 1992 21:55

#25

Author: Andy Finkenstadt
Date: Mon, 27 Jul 1992 21:55

68 lines
2309 bytes

Apparently there are problems in some uucico's in the field that
time out waiting for the ROK message back from UUNET.  This can
be caused by timing, I imagine.  Then again, maybe it's a bug
in the Sequent OS.  It used to happen on the machine 'uucp2'
every now and then, but recently my traces show it happened on
'uunet' almost all the time.  (Traces = I did this by hand.)

 <> UUNET Communications Services (uunet)^M^J^M^M^J^Mlogin: rde^M^J
 <> Password:got it
 <> sendthem (????????)
 <> Login Successful: System=uunet
 <> msg-
^^^^  no ROK received in timeout period?  Don't know for sure.
 <> exit code 101
 <> Conversation Complete: Status FAILED

If it matters, I am GE7.03, Interactive Unix 3.0 pl3, stock uucico
using BNU/HDB with a window size request of 7.

-Andy

=== /tmp/uunet
mchFind called (uunet)
conn(uunet)
Device Type ACUpep wanted
mlock ttyaX succeeded
processdev: calling setdevcfg(uucico, ACUpep)
gdial(tbfast) called
expect: ("")
got it
sendthem ()
CLOCAL set
????????PAUSE
????????PAUSE
????????PAUSE
????????PAUSE
????????PAUSE
????????PAUSE
????????)
expect: (OK)
^M^JOKgot it
sendthem (????????)
expect: (CONNECT)
^M^J^M^JCONNECTgot it
sendthem ()
CLOCAL clear
<NO CR>)
getto ret 6
expect: ("")
got it
sendthem (????????)
expect: (gin:)
 FAST/UUCP^M^J^M^JUUNET Communications Services (uunet)^M^J^M^M^J^Mlogin:got it
sendthem (????????)
expect: (word:)
 ^M^JUUNET Communications Services (uunet)^M^J^M^M^J^Mlogin: rde^M^JPassword:got it
sendthem (????????)
Login Successful: System=uunet
msg-
exit code 101
Conversation Complete: Status FAILED

-- 
Andrew Finkenstadt       | Vista-Chrome, Inc.   |    NIC Handle: AF136
GEnie Unix Sysop/Manager | The Printing House   |   ...!uunet!rde!andy
+1 904 222 2639 home     | 1600 Capital Cir SW  |  andy@GEnie.geis.com
+1 904 575 0189 work     | Tallahassee FL 32310 | andy@vistachrome.com

Re: 'msg- CONVERSATION FAILED (exit code 101)'

#26

Author: Jim Logan
Date: Tue, 28 Jul 1992 18:24

14 lines
776 bytes

In article <1992Jul27.215548.11487@homebase.vistachrome.com>
andy@homebase.vistachrome.com writes:
# 
# Apparently there are problems in some uucico's in the field that
# time out waiting for the ROK message back from UUNET.

I have been seeing the same problem.  Are we getting charged for
this dead-time?  

			-Jim
-- 
Jim Logan
logan@gimlet.herndon.va.us     ...There's no place like $HOME.
uunet!gimlet!logan

Re: 'msg- CONVERSATION FAILED (exit code 101)'

#27

Author: Don Lewis
Date: Thu, 30 Jul 1992 01:00

37 lines
2568 bytes

In article <175@gimlet.herndon.va.us> logan@gimlet.herndon.va.us (Jim Logan) writes:
>In article <1992Jul27.215548.11487@homebase.vistachrome.com>
>andy@homebase.vistachrome.com writes:
># 
># Apparently there are problems in some uucico's in the field that
># time out waiting for the ROK message back from UUNET.

I've been seeing a *lot* of these lately.

uucp uunet (7/13-18:41:04,3816,0) DEBUG: icexpect: Got "\r\nRRING\r\n\r\nCONNECT FAST" (found it)
uucp uunet (7/13-18:41:30,3816,0) DEBUG: fcsend: Writing "\r\r"
uucp uunet (7/13-18:41:30,3816,0) DEBUG: icexpect: Looking for 5 "ogin:"
uucp uunet (7/13-18:41:30,3816,0) DEBUG: icexpect: Got "\r\n\r\nUUNET Communications Services (uunet)\r\n\r\r\n\rlogin:" (found it)
uucp uunet (7/13-18:41:33,3816,0) DEBUG: fcsend: Writing "LOGIN\r"
uucp uunet (7/13-18:41:33,3816,0) DEBUG: icexpect: Looking for 7 "ssword:"
uucp uunet (7/13-18:41:33,3816,0) DEBUG: icexpect: Got " \r\nUUNET Communications Services (uunet)\r\n\r\r\n\rlogin: LOGIN\r\n"
uucp uunet (7/13-18:41:38,3816,0) DEBUG: icexpect: Got "Password:" (found it)
uucp uunet (7/13-18:41:38,3816,0) DEBUG: fcsend: Writing "PASSWORD\r"
uucp uunet (7/13-18:41:38,3816,0) Login successful
uucp uunet (7/13-18:41:38,3816,0) DEBUG: zget_uucp_cmd: Got "\r\n\020Shere=uunet\000"
uucp uunet (7/13-18:41:41,3816,0) DEBUG: fport_write: Writing 11 "\020Sssigv -N\000"
uucp uunet (7/13-18:41:41,3816,0) DEBUG: zget_uucp_cmd: Got "\nuucp uunet (7/13-18:41:49,3816,0) ERROR: Line disconnected
" (error)
uucp uunet (7/13-18:41:49,3816,0) DEBUG: fcall_failed: Cause 4 (Handshake failed)

It doesn't look to me like uucp at my end is timing out.  It looks more
like uunet is dropping the connection rather than sending ROK.

>I have been seeing the same problem.  Are we getting charged for
>this dead-time?  

I wouldn't be suprised.

-- 
Don "Truck" Lewis              Phone: +1 916 478-8284   Silicon Systems
Internet: gdonl@ssi1.com       FAX:   +1 916 478-8290   138 New Mohawk Road
UUCP: {uunet,tektronix!gvgpsa.gvg.tek.com}!ssigv!gdonl  Nevada City, CA  95959

Re: 'msg- CONVERSATION FAILED (exit code 101)'

#28

Author: Andrew Partan
Date: Thu, 30 Jul 1992 05:48

21 lines
1298 bytes

In article <175@gimlet.herndon.va.us> logan@gimlet.herndon.va.us (Jim Logan) writes:
>I have been seeing the same problem.  Are we getting charged for
>this dead-time?  

No, you are not being charged.

Timing begins when the uucico processes have started speaking to each
other - the OK(startup) logfile message.  42 seconds are added to
compensate for login time.

If you never see the OK(startup) message, then we will not charge you
for that call.  The call is failing before it even starts.  [If you are
calling us long distance, then the phone company will charge you for
that call.  If you are calling us on our 800 number, then we loose the
money.]

As best as we can determine, the problem seems to be being caused by a
compiler bug in gcc on the Sequent.  We are working on getting this
fixed.

	--asp@uunet.uu.net (Andrew Partan)

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