uucp BAD READ error

uucp BAD READ error

Post by vladimir.soukha.. » Wed, 19 Jan 2000 04:00:00



I have SCO OS 5.04 on both sides. When I try to apply command "uucp
unix1!/usr/spool/uucppublic/aa  unix2!/usr/spool/uucppublic/cc" on "unix2"
system then UUCP dumps core file in "/usr/spool/uucp/unix1" directory and
remains files "A.unix1N1329, C.unix1N1329, TM.03481.000, TM.03491.000" there.
On "unix1" side at the same time 17 lines "root unix2 (1/12-8:45:58,25512,1)
BAD READ (expected 'C' got FAIL)" in "/usr/spool/uucp/.Log/uucico/unix2" file
appear. If I initiate "uucp" process from "unix1" "uucp
unix2!/usr/spool/uucppublic/bb unix1!/usr/spool/uucppublic/cc" then UUCP
dumps core file in "/usr/spool/uucp/unix2" directory and remains files
"A.unix2N1845, C.unix2N1845, C.unix2N1846, TM.29500.000, TM.29579.000" there.
On "unix2" side at the same time 17 lines "root unix1 (1/12-14:16:25,3503,1)
BAD READ (expected 'C' got FAIL)" in "/usr/spool/uucp/.Log/uucico/unix1" file
appear. If I run on "unix2" "uucp unix2!/usr/spool/uucppublic/bb
unix1!/usr/spool/uucppublic/cc" then it works but string "uucp unix2
(1/12-14:19:50,29682,1) BAD READ (expected 'H' got FAIL)" appears in file
"/usr/spool/uucp/.Log/uucico/unix2" on "unix1" and conversation status is
FAILED. If I run on "unix1" "uucp unix1!/usr/spool/uucppublic/bb
unix2!/usr/spool/uucppublic/cc" then it works too but string "uucp unix1
(1/12-14:19:50,29682,1) BAD READ (expected 'H' got FAIL)" in
"/usr/spool/uucp/.Log/uucic/unix1" file appears on "unix2" and conversation
status is FAILED. With other systems "unix1" communicates via "uucp" properly
but "unix2" communicates in the manner described above. Can anybody smart
help me?

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

1. UUCP - BAD READ error

Having a problem with one of my systems dialing into our main UNIX system.
When it connects I'm getting a message in the log 'BAD READ (expected 'C'
got FAIL)'. Anyone have an idea what's going on with this one? I have 7
other systems coming into the same machine with no problems which are set
up (I hope) identical to the one that is misfiring. Please e-mail and
thoughts on the subject. Thanks.

2. do linux memory drivers address the UMB

3. uucp BAD READ error

4. Free Software rules!

5. UUCP - BAD READ error

6. Route based on my sending ip address?

7. is there any linux porting on 68000(dragon ball)

8. Install error: error 2 reading header: cpio: Bad magic

9. Bad, bad, bad error...

10. Device Driver: read error, Bad file number

11. Error reading from connection: Bad file number

12. bsd-gw: Error reading from connection: Bad file number