Thread View: net.bugs.uucp
3 messages
3 total messages
Started by Mike Wescott
Tue, 09 Sep 1986 01:49
problems with Honey Danber UUCP and 4.3BSD uucp
Author: Mike Wescott
Date: Tue, 09 Sep 1986 01:49
Date: Tue, 09 Sep 1986 01:49
71 lines
2774 bytes
2774 bytes
A neighboring site just converted to 4.3BSD. We've had a uucp connection
with them for several years. We switched to HDuucp some time ago and had no
problems connecting/communicating with 4.2 sites, System V machines, and even
with a pyramid. Since our neighbor converted to 4.3 all we've been able to
get is a connection to startup, begin work and then die with:
ASSERT ERROR (uucico) pid: 10566 (9/8-21:33:17) WRONG ROLE (1) [FILE: cntrl.c, LINE: 397]
Anybody else seen this?
Fixed it? ... How?
Anybody have any good ideas?
What's protocol 't' ?
-Mike Wescott
ncrcae!wescott
Partial debug trace (-x9) follows:
expect: (CONNECT)
^M^JCONNECTgot it
getto ret 5
.
.
.
imsg >:^M^J^PShere=pqrs^@Login Successful: System=pqrs
omsg "Sncrcae -Q0 -x9"
imsg >^J^PROK^@msg-ROK
Rmtname pqrs, Role MASTER, Ifn - 5, Loginuser - root
rmesg - 'P' imsg >^PPtfg^@got Ptfg
wmesg 'U'g
omsg "Ug"
send 73
pkgetpack: Connodata=1
rec h->cntl 73
send 61
state - [INIT code a] (1)
pkgetpack: Connodata=2
rec h->cntl 61
send 53
state - [INIT code a]&[INIT code b] (3)
pkgetpack: Connodata=3
rec h->cntl 53
state - [O.K.] (10)
Proto started g
*** TOP *** - role=1, setline - X
gtwvec: dir /usr/spool/uucp/pqrs
insert(C.pqrsN43eb) insert C.pqrsN43eb at 0
insert(C.pqrsN43ec) insert C.pqrsN43ec at 1
insert(C.pqrsN43ee) insert C.pqrsN43ee at 2
insert(C.pqrsN43f0) insert C.pqrsN43f0 at 3
insert(C.pqrsN43f1) insert C.pqrsN43f1 at 4
return - 8
Wfile - /usr/spool/uucp/pqrs/C.pqrsN43eb,Jobid = pqrsN43eb
Request: ncrcae!D.ncrcaeff3e09 --> pqrs!D.ncrcaeff3e09 (nuucp)
setline - S
wrktype - S
wmesg 'S' D.ncrcaeff3e09 D.ncrcaeff3e09 nuucp - D.ncrcaeff3e09 0666 nuucp
send 37777777610
send 37777777620
rmesg - 'S' alarm 1
send 37777777610
pkgetpack: Connodata=4
rec h->cntl 37777777610
send 37777777621
pkgetpack: Connodata=1
rec h->cntl 37777777621
send 42
got S D.ncrcaeff3e09 D.ncrcaeff3e09 nuucp - D.ncrcaeff3e09 0666 nuucp
PROCESS: msg - S D.ncrcaeff3e09 D.ncrcaeff3e09 nuucp - D.ncrcaeff3e09 0666 nuucp
SNDFILE:
ASSERT ERROR (uucico) pid: 10566 (9/8-21:33:17) WRONG ROLE (1) [FILE: cntrl.c, LINE: 397]
Re: problems with Honey Danber UUCP and 4.3BSD uucp
Author: wescott
Date: Tue, 09 Sep 1986 02:18
Date: Tue, 09 Sep 1986 02:18
28 lines
1424 bytes
1424 bytes
In article <2327@ncrcae.UUCP> wescott@ncrcae.UUCP (Mike Wescott,x278) writes: > A neighboring site just converted to 4.3BSD ...and all we've been able to > get is a connection to startup, begin work and then die with: > > ASSERT ERROR (uucico) pid: 10566 (9/8-21:33:17) WRONG ROLE (1) [FILE: cntrl.c, LINE: 397] > > Anybody else seen this? > Fixed it? ... How? > What's protocol 't' ? Looks like I get to answer my own questions. > Anybody else seen this? I don't know, but ... > Fixed it? ... How? The 4.3 system didn't have a /usr/spool/uucp/STST directory. They did but it had another name. I mv'd it and everything works. > What's protocol 't' ? For TCP/IP connections. Sounds like the equivalent of the HDuucp 'e' protocol. -Mike Wescott ncrcae!wescott
Re: problems with Honey Danber UUCP and 4.3BSD uucp
Author: David Herron, NPR Lover
Date: Thu, 11 Sep 1986 15:23
Date: Thu, 11 Sep 1986 15:23
10 lines
1069 bytes
1069 bytes
We're running 4.3bsd and have been talking to at least 4 HDuucp neighbors without any problems. They are cbosgd, cbatt, ukecc, and a 3b2 or two in our machine room. protocol t is a tcp/ip gadget and shouldn't be used over a modem line. I'd say that's the problem. -- David Herron, cbosgd!ukma!david, david@UKMA.BITNET, david@ms.uky.csnet (I'm also "postmaster" at all those addresses) (And "news" and "netnews" and "uucp" and ....)
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