[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

695.0. "kprop not running correctly" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Apr 18 1994 13:13

Date Of Receipt: 	18-APR-1994 11:13:59.52
From: 	FLAMBE::glidden "Mark Glidden USG  18-Apr-1994 1114"
To: 	odehelp@DEC:.zko.flambe, tes@DEC:.zko.flambe
CC: 	admin@DEC:.zko.flambe
Subj: 	kprop not running correctly

This is to inform you that kprop is not
running correctly on the hosts listed below.
Please let me and [email protected] know if this
is going to be a long term problem.
				thanks
				Mark G

Start slave propagation: Mon Apr 18 09:10:10 1994
abyss.zk3.dec.com: success.
flume.zk3.dec.com: success.
lastin.zk3.dec.com: connect: Connection refused
krisis.zk3.dec.com: success.
ravine.zk3.dec.com: success.
ronyon.zk3.dec.com: success.
xirtlu.zk3.dec.com: success.
grvlpt.zk3.dec.com: success.
rust.zso.dec.com: connect: Connection refused
ode2.mlo.dec.com: success.
odie.unx.dec.com: connect: Host is unreachable
vindo.zso.dec.com: connect: Connection refused
mossey.zso.dec.com: connect: Connection refused
lastin.zk3.dec.com: connect: Connection refused
rust.zso.dec.com: connect: Connection refused
odie.unx.dec.com: connect: Host is unreachable
vindo.zso.dec.com: connect: Connection refused
mossey.zso.dec.com: connect: Connection refused
kprop: propagation failed.
.

T.RTitleUserPersonal
Name
DateLines
695.1Re: kprop not running correctlySMURF::FILTERAutomatic Posting Software - mail to flume::puckMon Apr 18 1994 13:1529
Date Of Receipt: 	18-APR-1994 11:35:15.38
From: 	YUCKY::beikman "Steve Beikman USG/REng  18-Apr-1994 1135"
To: 	glidden@DEC:.zko.yucky
CC: 	odehelp@DEC:.zko.yucky, tea@DEC:.zko.yucky, [email protected],
	beikman@DEC:.zko.yucky
Subj: 	Re: kprop not running correctly

mark,

 it appears to be a random problem.   if you grep'ed  for it, you'll
see that lastin as well as vindo had several successful updates last week.

 on lastin, part of the problem is that the /usr/etc/kpropd dies during
or after an update from merge.    

 nothing on lastin should have changed that would have caused this to 
happen. That dosen't mean that nothing did change.  Everything I've 
looked at appears to be ok.   

last week, lastin did lose a system disk, but was restored from the 
previous nights full backups.   Supposedly, the kprop problem started 
before the loss of the system disk.


i da know.
/sb