"Bad Header" during uucp transmition

Alex Beylin alexb at cfctech.cfc.com
Wed Jan 23 04:08:22 AEST 1991


And yet another question to this group that probably belongs
somewhere else, but .....

The players in this drama are as follows:

"cfctech" is a 3B2/1000 running Sys V.3 from AT&T.
"athame" is a 486-based system running Interactive 2.2
FAS is installed on athame.  The modems are V.32 at 9600 bps.

For the last two weeks uucp between athame and cfctech worked fine.
I've moved all kind of source and mail both ways with no problems.

Saturday I've installed cnews on athame and turned-on the feed 
on cfctech.  I've also added "rnews" to the Permissions file.  As
far as I know, nothing else changed.

The very next time I've tried uucp, it was broken.  Checked and
re-checked all the permissions, Permissions file, etc.  Mail goes fine
to cfctech, but uucp attempts going back produce the following
result:

-----------------------------------------------

imsg >^M^JUNIX System V Release 3.2.2 AT&T 3B2^M^Jcfctech^M^JCopyright (c) 1984, 1986, 1987, 1988, 1989 AT&T^M^JAll Rights Reserved^M^J^PShere=cfctech^\@Login Successful: System=cfctech
omsg "Sathame -Q0 -x9"
imsg >^PROK^\@msg-ROK
 Rmtname cfctech, Role MASTER,  Ifn - 6, Loginuser - root
rmesg - 'P' imsg >^PPged^\@got Pged
wmesg 'U'g
omsg "Ug"
send 77
pkgetpack: Connodata=1
rec h->cntl 77
send 61
state - [INIT code a] (1)
pkgetpack: Connodata=2
rec h->cntl 61
send 57
state - [INIT code a]&[INIT code b] (3)
pkgetpack: Connodata=3
rec h->cntl 57
state - [O.K.] (10)
Proto started g
*** TOP ***  -  role=1, setline - X
gtwvec: dir /usr/spool/uucp/cfctech
wmesg 'H'
send 37777777610
rmesg - 'H' pkgetpack: Connodata=4
rec h->cntl 41
pkcntl: RR/RJ: Connodata=0
state - [O.K.] (10)
pkgetpack: Connodata=1
rec h->cntl 37777777611
pkgetpack: Connodata=2
rec h->cntl 37777777631
pkgetpack: Connodata=3
rec h->cntl 37777777611
pkgetpack: Connodata=4
rec h->cntl 110
bad header 132,h->ccntl 116
alarm 1
send 20
pkgetpack: Connodata=5
rec h->cntl 37777777611
pkgetpack: Connodata=6
rec h->cntl 110
bad header 132,h->ccntl 116
pkgetpack: Connodata=7
rec h->cntl 37777777611
pkgetpack: Connodata=8
rec h->cntl 110
bad header 132,h->ccntl 116
alarm 2
send 20
pkgetpack: Connodata=9
rec h->cntl 37777777611
pkgetpack: Connodata=10
rec h->cntl 110
bad header 132,h->ccntl 116
alarm 3

.....  ....... 			(alarms continue, until, as expected...)

got FAIL
send 10
send 10
cntrl - -1
omsg "OOOOOO"
send OO 0,omsg "OOOOOO"
imsg >^\@^\\@^B^R0\@^B^RX^\@^\@^\@^\@\@^B^\@<^\@^H^U-^\@^\@^\@^\@^\@^\@^\@^A^\@^\@^\@^\@.athame^\@^\@^H-&^\@^\@^\@^M^\@^H^A^\@^\@^\@+\@^B^R^\@^POOOOOO^\@exit code -1
Conversation Complete: Status FAILED

TM_cnt: 0

--------------------------------------------------

Can anybody make any suggestions?

Thanks in advance,

-- Alex (alexb at cfctech.cfc.com)



More information about the Comp.unix.sysv386 mailing list