Mailing List Archive: Unable to use rdist in parrellel mode with 2.1.0p2 ...

Unable to use rdist in parrellel mode with 2.1.0p2 ...

May 30, 2000, 8:40 AM

Post #1 of 3 (1010 views)

Morning all ...

using the following command to sync up the binaries on several
machines:

rdist -P /usr/slocal/bin/ssh -Rf /root/sync-systems

generates the following error message(s):

jasper: updating host jasper
hermes: updating host hermes
attila: updating host attila
hercules: updating host hercules
".rcules: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
hercules: updating of hercules finished
".rmes: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
hermes: updating of hermes finished
webster: updating host webster
iceberg: updating host iceberg
".sper: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
jasper: updating of jasper finished
".eberg: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
hawk: updating host hawk
iceberg: updating of iceberg finished
".bster: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
webster: updating of webster finished
dalmation: updating host dalmation
owl: updating host owl
".wk: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
hawk: updating of hawk finished
".lmation: LOCAL ERROR: Unexpected input from server: "Couldn't initialise builtin random number generator -- exiting.
dalmation: updating of dalmation finished

If I change the -Rf to -RFf, to force it to do one at a time, it
will work ... even narrowing it down to only 2 hosts at once generates the
same errors ...

This is on a Solaris 7/sparc machine ... contention for the
entropy pool? *raised eyebrow*

Thanks ..

Marc G. Fournier marc.fournier@acadiau.ca
Senior Systems Administrator Acadia University

"These are my opinions, which are not necessarily shared by my employer"

Re: Unable to use rdist in parrellel mode with 2.1.0p2 ... [ In reply to ]

djm at mindrot

May 30, 2000, 5:28 PM

Post #2 of 3 (984 views)

Permalink

On Tue, 30 May 2000, Marc G. Fournier wrote:

>
> Morning all ...
>
> using the following command to sync up the binaries on several
> machines:
>
> rdist -P /usr/slocal/bin/ssh -Rf /root/sync-systems
>
> generates the following error message(s):
>
(snip)

> If I change the -Rf to -RFf, to force it to do one at a time, it
> will work ... even narrowing it down to only 2 hosts at once generates the
> same errors ...
>
> This is on a Solaris 7/sparc machine ... contention for the
> entropy pool? *raised eyebrow*

Are you using EGD or the builtin entropy collection code?

In any case what is really needed here is the full output from
a failing client. Would it be possible to run the client with a wrapper
to collect its log output to a file?

-d

--
| "Bombay is 250ms from New York in the new world order" - Alan Cox
| Damien Miller - http://www.mindrot.org/
| Email: djm@mindrot.org (home) -or- djm@ibs.com.au (work)

Re: Unable to use rdist in parrellel mode with 2.1.0p2 ... [ In reply to ]

marc.fournier at acadiau

May 31, 2000, 4:20 AM

Post #3 of 3 (986 views)

Permalink

On Wed, 31 May 2000, Damien Miller wrote:

> On Tue, 30 May 2000, Marc G. Fournier wrote:
>
> >
> > Morning all ...
> >
> > using the following command to sync up the binaries on several
> > machines:
> >
> > rdist -P /usr/slocal/bin/ssh -Rf /root/sync-systems
> >
> > generates the following error message(s):
> >
> (snip)
>
> > If I change the -Rf to -RFf, to force it to do one at a time, it
> > will work ... even narrowing it down to only 2 hosts at once generates the
> > same errors ...
> >
> > This is on a Solaris 7/sparc machine ... contention for the
> > entropy pool? *raised eyebrow*
>
> Are you using EGD or the builtin entropy collection code?

builtin entropy code ...

> In any case what is really needed here is the full output from
> a failing client. Would it be possible to run the client with a wrapper
> to collect its log output to a file?

okay, when you say 'client', do you mean the side that I'm sending from
(ie. ssh -> sshd) or the side I'm connecting to? if the first, I tried to
create simple wrapper of:

#!/bin/tcsh
/usr/slocal/bin/ssh -v ${*} >& /tmp/out.$$

that appears to generate a bunch of code, but I can't see any of them fail
this way :(

on the 'sshd' side of things, when I try to do a connect, I see (without
running with the above wrapper on the 'ssh' side of things):

RSA key generation complete.
debug: Server will not fork when running in debugging mode.
Connection from 131.162.200.78 port 34960
Did not receive ident string from 131.162.200.78.
debug: Calling cleanup 0x4a888(0x0)
debug: Calling cleanup 0x50418(0x0)
debug: writing PRNG seed to file //.ssh/prng_seed

the above wrapper, when I run with it, doesn't appear to try to do a
connection to the remote end, so either I'm writtin that wrong, or rdist
is expecting something that I'm not anticipating :(

Marc G. Fournier marc.fournier@acadiau.ca
Senior Systems Administrator Acadia University

"These are my opinions, which are not necessarily shared by my employer"