jeffrey@sci.ccny.cuny.edu (Jeffrey L Bromberger) (01/23/91)
Hi. We're trying to run UUCP through a Bridge (now 3com) terminal
server. By using a complicated chat script, it is able to log in, and
start up uucico. But that's when things get fouled up. Here is the
debug output (level 99) from uucico (4.3Tahoe version):
vax ccnysci (1/22-16:23-12404) DEBUG Remote Enabled
omsg <ROK>
Rmtname ccnysci, Role SLAVE, Ifn - 0, Loginuser - vax
wmesg 'P' tfg
omsg <Ptfg>
rmesg - 'U' imsg looking for SYNC< 20\20>
imsg input< 125U 147g 0\0>got 2 characters
got Ug
send 077
rec h->cntl 077
bad header (k==9) 077
pkcget: alarm 4001
send 077 <- These lines get repeated
rec h->cntl 077 <- before each of the following
bad header (k==9) 077 <- alarms
pkcget: alarm 6002
[those same 3 lines deleted here]
pkcget: alarm 8003
pkcget: alarm 10004
pkcget: alarm 12005
pkcget: alarm 14006
pkcget: alarm 16007
pkcget: alarm 18008
pkcget: alarm 20009
pkcget: alarm 22010
vax ccnysci (1/22-16:26-12404) FAILED (startup)
OK. What exactly does this mean? It sends a 077, gets a 077 and
complains??
Any help would be appreciated.
j
--
Jeffrey L. Bromberger
System Operator---City College of New York---Science Computing Facility
jeffrey@sci.ccny.cuny.edu jeffrey@ccnysci.BITNET
Anywhere!{cmcl2,philabs,phri}!ccnysci!jeffreyromain@salt.pyramid.com (Romain Kang) (01/24/91)
I suspect you are running into various flow control/echoing problems. I once used something similar to this successfully (though I connected directly to the uucp TCP port). Some of these commands may not work on your version of the 3com server; if they do, you could code them into a macro. erewhon Any ACU 19200 5551212 "" \d\r\d > c\serewhon\sECM connected \c > SET\sIT=1\sECMC=DIS\sXB=ON\sFCT=N\sFCF=N \ > RESUME in: nuucp word: FatChance Notes: IT=1 input dispatch timer (in 60ths of seconds? I forget) ECMC=DIS disable escape character, in case it appears in uucp data stream XB=ON transmit binary on FCT=N FCF=N No flow control; presumably 'g' protocol will do it all; hardware flow control recommended if available...
lancelot@spock.UUCP (Thor Lancelot Simon) (01/26/91)
In article <1991Jan22.213637.20338@sci.ccny.cuny.edu> jeffrey@sci.ccny.cuny.edu (Jeffrey L Bromberger) writes: >imsg input< 125U 147g 0\0>got 2 characters >got Ug >send 077 >rec h->cntl 077 >bad header (k==9) 077 >pkcget: alarm 4001 >send 077 <- These lines get repeated >rec h->cntl 077 <- before each of the following >bad header (k==9) 077 <- alarms This looks to me like your bridge is not 8-bit clean. UUCP is probably getting a bad character in the header, and timing out (this is what alarm means), then sending a 077 (I think this is the 'retry' signal), getting another bad header, and so forth. The reason the alarm is different each time is because the alarm number is computed by multiplying the timeout by the number of alarms already generated and adding the last alarm number (or something like that). 4001 is usually the first one in any sequence. >Jeffrey L. Bromberger >System Operator---City College of New York---Science Computing Facility >jeffrey@sci.ccny.cuny.edu jeffrey@ccnysci.BITNET > Anywhere!{cmcl2,philabs,phri}!ccnysci!jeffrey ******************************************************************************* *Thor Simon * Okay, just a little pin-prick...There'll be no more-* *lancelot@spock.UUCP * Aieeeeaaaugh!-but you may feel a little _sick_. * *uunet!hsi!yale!lancelot* ---Pink Floyd * *******************************************************************************