[net.micro.att] uucp problems on UNIX pc

chute@hscfvax.UUCP (850154@NDSK@M.Zalkalns) (08/19/86)

I have had some unexpected trouble with uucp on my system.  The following
relates my LOGFILE during some expensive and fruitless transactions.  I
should add that the session finally did complete, the file was transferred.
  I have used THE STORE! in the past without any of this trouble.

   1 shop!uucp (8/16-0:29:41) (C,2451,0) OK (DIAL  P 33)
   1 shop!uucp (8/16-0:29:46) (C,2451,0) SUCCEEDED (call to shop )
   1 shop!uucp (8/16-0:29:54) (C,2451,0) OK (startup)
   1 shop!root (8/16-0:29:55) (C,2451,0) REQUEST (S /usr/lib/ua/.ST.REG /n1/store/STOREROOM/REGISTRATION/chutepc.chute root)
   1 shop!root (8/16-0:30:13) (C,2451,1) REQUESTED (CY)
   1 shop!root (8/16-0:30:14) (C,2451,1) REQUEST (R /n1/store/STOREROOM/CATALOG+IN /usr/spool/uucppublic/STORE/CATALOG+IN root)
   1 shop!root (8/16-1:13:43) (C,2451,2) FAILED (conversation complete)
   1 shop!uucp (8/16-2:29:41) (C,2506,0) OK (DIAL  P 33)
   1 shop!uucp (8/16-2:29:46) (C,2506,0) SUCCEEDED (call to shop )
   1 shop!uucp (8/16-2:30:06) (C,2506,0) OK (startup)
   1 shop!root (8/16-2:30:06) (C,2506,0) REQUEST (R /n1/store/STOREROOM/CATALOG+IN /usr/spool/uucppublic/STORE/CATALOG+IN root)
   1 shop!root (8/16-3:08:49) (C,2506,1) FAILED (conversation complete)
etc.  There's more, but you get the point.

The following informative error messages greeted me in /usr/spool/uucp/ERRLOG:

ASSERT ERROR (uucico)  pid: 2451  (8/16-1:13:43) PKXSTART ret  (0)
ASSERT ERROR (uucico)  pid: 2506  (8/16-3:08:49) PKXSTART ret  (0)
ASSERT ERROR (uucico)  pid: 2583  (8/16-5:04:34) PKXSTART ret  (0)

Questions: What was the problem?  What is PKXSTART?  How can I avoid
expensive but pointless 40 minute phone calls to New Jersey?

Thanks in advance for any insight.

Cheers,
Chris Chute M.D.			UUCP: ...!harvard!hscfvax!chute OR
Harvard School of Public Health		UUCP: ...!harvard!hscfvax!chutepc!chute
Department of Epidemiology		Voice:   (617)732-1480
677 Huntington Ave			Data:    (617)732-1843
Boston, MA 02115

jhc@mtune.UUCP (Jonathan Clark) (08/22/86)

Almost certainly you got a noisy phone trunk and eventually the
transfer had too many errors and the call was dropped. Or the Freehold
Dimension which is notoriously unstable decided to have a bad night and
drop your calls on you. That's just the way that phone lines and
switches are sometimes. These problems will be resolved soon, honest.

-- 
Jonathan Clark
[NAC,attmail]!mtune!jhc

My walk has become rather more silly lately.