On Tue, 2017-09-12 at 09:20 +1000, Morgan Reed wrote:
> In all likelihood the process wasn't "hung" per-se, more likely
> random
> hadn't been seeded yet and as such you *can't* get 4096b of entropy
> out of
> it (so the process was attempting to do its job,
In all likelihood the process wasn't "hung" per-se, more likely random
hadn't been seeded yet and as such you *can't* get 4096b of entropy out of
it (so the process was attempting to do its job, just nothing on the
device).
The issue is basically that there are very few
I just had a VM running in Google's cloud become totally useless, and I
tracked it down to the save-entropy operation.
Basically this process was sucking up all CPU, even when nothing else
running other than my ssh shell:
% ps axuw803
USER PID %CPU %MEM VSZ RSS TT STAT STARTED
Adding FreeBSD stable to see if they can provide some insight on this since
it affects everything from 11 and beyond
>
> On Sat, Nov 26, 2016 at 7:01 AM, Bertram Scharpf > wrote:
>
>> On Friday, 25. Nov 2016, 20:06:55 -0800, Jack L. wrote:
>> > On Fri, Nov 25, 2016 at 7:32 PM, Bertram Scharpf <
>
; > >> shutdown -r now
> > >>
> > >>
> > >> 2011/2/17 Doug Barton do...@dougbarton.us>>
> > >>
> > >>
> > >>On 02/16/2011 21:56, Ken Chen wrote:
> > >>
> > >>Hello All,
> >
reboot with 8.1 kernel.
> >>
> >> nextboot -k GENERIC
> >> shutdown -r now
> >>
> >>
> >> 2011/2/17 Doug Barton mailto:do...@dougbarton.us>>
> >>
> >>
> >>On 02/16/2011 21:56, Ken Chen wrote:
> >>
>
2011 21:56, Ken Chen wrote:
>>
>>Hello All,
>>
>>I upgrade a very old machine from 6.3-RELEASE to 8.1-RELEASE by
>>'freebsd-update'. After boot with 8.1 GENERIC kernel, it holds-on
>> at
>>''Entropy harves
r now
2011/2/17 Doug Barton mailto:do...@dougbarton.us>>
On 02/16/2011 21:56, Ken Chen wrote:
Hello All,
I upgrade a very old machine from 6.3-RELEASE to 8.1-RELEASE by
'freebsd-update'. After boot with 8.1 GENERIC kernel, it holds-on at
'&#x
boot with 8.1 GENERIC kernel, it holds-on at
>> ''Entropy harvesting: '. I try to change configuration in
>> /etc/defaults/rc.conf, it helpless.
>>
>
> Did you update /etc after updating the binaries, or is this the first
> reboot after freebsd-update installs
On 02/16/2011 21:56, Ken Chen wrote:
Hello All,
I upgrade a very old machine from 6.3-RELEASE to 8.1-RELEASE by
'freebsd-update'. After boot with 8.1 GENERIC kernel, it holds-on at
''Entropy harvesting: '. I try to change configuration in
/etc/defaults/rc.conf, it h
On 17/02/2011, at 16:26, Ken Chen wrote:
> I upgrade a very old machine from 6.3-RELEASE to 8.1-RELEASE by
> 'freebsd-update'. After boot with 8.1 GENERIC kernel, it holds-on at
> ''Entropy harvesting: '. I try to change configuration in
&g
Hello All,
I upgrade a very old machine from 6.3-RELEASE to 8.1-RELEASE by
'freebsd-update'. After boot with 8.1 GENERIC kernel, it holds-on at
''Entropy harvesting: '. I try to change configuration in
/etc/defaults/rc.conf, it helpless.
harvest_interrupt="
David Southwell wrote:
Receiving Automated message from cron
No such messages under 6.3
Is there anything I need to attend to here?
Subject: Cron <...> /usr/libexec/save-entropy
Date: Thursday 17 July 2008
From: Cron Daemon
To: >[EMAIL PROTECTED]
unlink: /var/db/entropy/saved-entr
Receiving Automated message from cron
No such messages under 6.3
Is there anything I need to attend to here?
Subject: Cron <...> /usr/libexec/save-entropy
Date: Thursday 17 July 2008
From: Cron Daemon
To: >[EMAIL PROTECTED]
unlink: /var/db/entropy/saved-entropy.8: No such file or dir
FreeBSD ghreen.sphere 6.2-STABLE FreeBSD 6.2-STABLE #0: Sun Aug 19
20:10:46 CDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GHREEN
i386
Attached dmesg, attached kernel config.
During bootup about 1 out of 5 times my box freezes right after it
enters userland at the "Gathering entropy:&
ginal Message -
From: "Doug Barton" <[EMAIL PROTECTED]>
To: "Clayton Milos" <[EMAIL PROTECTED]>
Cc:
Sent: Monday, October 30, 2006 11:51 PM
Subject: Re: Entropy
Clayton Milos wrote:
Hi there
I'm having the same problem as Greg Bernard (bsd_at_
Clayton Milos wrote:
> Hi there
>
>
> I'm having the same problem as Greg Bernard (bsd_at_todoo.biz).
>
> Every 11 minutes I get a mail from my servers but instead of it
> containing -- which is what Greg is getting it contains this:
>
> COPYRIGHT: not found
>
> Upon further investigation if I
ld be something wrong in my environment
variables and not with the entropy harvestig file. It did not happen with a
clean install so it is probably some software that I installed that may have
affected root's profile.
My env is as such:
[EMAIL PROTECTED]:/ #> env
STY=1065.ttyp0.bart
TERM=scre
I do not
anticipate any problems, but please consider this a mini-heads up.
Doug
--
This .signature sanitized for your protection
Original Message
Subject: cvs commit: src/libexec/save-entropy save-entropy.sh
Date: Mon, 28 Aug 2006 06:41:50 + (UTC)
From: Doug B
Olivier,
That process is meant to be there. I don't know why it has the '--' argument
but it isn't likely to be a symptom of the problem you are having.
Try
sh -x /usr/libexec/save-entropy
To get more insight into when it is failing. This will show you surrounding
#x27;--' command but most people ignore these.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of olivier.taylor
Sent: Thursday, 15 June 2006 8:59 PM
To: [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Subject: Re: save-entropy
freebsd 5.4
#!/bin/s
tartup that will also complain about the
'--' command but most people ignore these.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of olivier.taylor
Sent: Thursday, 15 June 2006 8:59 PM
To: [EMAIL PROTECTED]
Cc: freebsd-stable@freebsd.org
Su
UCH DAMAGE.
#
# $FreeBSD: src/libexec/save-entropy/save-entropy.sh,v 1.2.12.1
2005/04/14 21:49:13 dougb Exp $
# This script is called by cron to store bits of randomness which are
# then used to seed /dev/random on boot.
# Originally developed by Doug Barton, [EMAIL PROTECTED]
PATH=/bi
envelope-from operator)
> Date: Thu, 15 Jun 2006 11:11:00 +0200 (CEST)
> Message-Id: <[EMAIL PROTECTED]>
> From: [EMAIL PROTECTED] (Cron Daemon)
> To: [EMAIL PROTECTED]
> Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy
> X-Cron-Env:
> X-Cron-Env:
&
-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED] (Cron Daemon)
To: [EMAIL PROTECTED]
Subject: Cron <[EMAIL PROTECTED]> /usr/libexec/save-entropy
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
--: not found
___
freebsd-stable@freeb
> What happens if you run it from the command line?
Same thing. The problem's now gone away though following an installworld.
-pcf.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send
Pete French wrote:
> About an hour ago I started getting regular
> messages from cron running /usr/libexec/save-entropy which
> contail the single line "IPv4: not found"
What happens if you run it from the command line?
Doug
--
This .signature sanitized
About an hour ago I started getting regular
messages from cron running /usr/libexec/save-entropy which
contail the single line "IPv4: not found"
Anybody got any ideas ? The only thing I did at that porint
was to do an 'rm' of /usr/obj in preparation for compiling
this morning
27;t seem to be the case in my
situation.
However I did notice things like nslookup and host are now
reporting this error after attempting to start /etc/rc.d/sshd start
# host www.freebsd.org
Entropy device is blocking.
# nslookup www.freebsd.org
Entropy device is blocking.
I confirmed by r
Thanks for the suggestion, but it doesn't seem to be the case in my
situation.
However I did notice things like nslookup and host are now reporting
this error after attempting to start /etc/rc.d/sshd start
# host www.freebsd.org
Entropy device is blocking.
# nslookup www.freebs
ra wrote:
On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote:
Type a full screenful of random junk to unblock
it and remember to finish with . This will
timeout in 300 seconds, but waiting for
the timeout without typing junk may make the
entropy source deliver predictable output.
Just hit fo
worked just fine.
Kurt
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Stephane Raimbault
> Sent: Thursday, September 01, 2005 13:18
> To: Vivek Khera
> Cc: freebsd-stable@freebsd.org
> Subject: Re: 5.4: Can't start ssh d
On Sep 1, 2005, at 1:29 PM, Stephane Raimbault wrote:
Type a full screenful of random junk to unblock
it and remember to finish with . This will
timeout in 300 seconds, but waiting for
the timeout without typing junk may make the
entropy source deliver predictable output.
Just hit for fast
I installed a fresh 5.4-RELEASE/amd64 system on a Dell PE1850 and
when attempting to setup sshd for the server I'm getting a weird error:
# /etc/rc.d/sshd start
/etc/rc.d/sshd: WARNING: Setting entropy source to blocking mode.
Type a
Renato Botelho wrote:
I updated my box and a jail that runs inside this box to 5.4-RELEASE yesterday.
After it, I'm receiving emails from this jail with error messages
about /usr/libexec/save-entropy
I'm receiving messages like this:
mv: /var/db/entropy/saved-entropy.7: No such file or
I updated my box and a jail that runs inside this box to 5.4-RELEASE yesterday.
After it, I'm receiving emails from this jail with error messages
about /usr/libexec/save-entropy
I'm receiving messages like this:
mv: /var/db/entropy/saved-entropy.7: No such file or directory
mv: /var/
Karol Kwiatkowski wrote:
I'm not using 5.4 but I would look in the save-entropy script for a
line that starts with 'X '. Also, looking at the source, have a look
at /etc/rc.conf and/or /etc/defaults/rc.conf as they are read at the
beginning of that script.
Actually, I can reproduce
L PROTECTED]> /usr/libexec/save-entropy
> X: not found
I'm not using 5.4 but I would look in the save-entropy script for a
line that starts with 'X '. Also, looking at the source, have a look
at /etc/rc.conf and/or /etc/defaults/rc.conf as they are read at the
beginning of that
Can anybody indicate to me what is causing the attached email and how to
fix it? I upgraded to the 5.4-STABLE as of yesterday and I am now
getting the attached email several time a day. Is this simply a script
error?
Thanks,
Tom Veldhouse
--- Begin Message ---
X: not found
--- End Message ---
Giovanni P. Tirloni wrote:
Hi,
save-entropy never exists and eats all CPU.
# uname -a
FreeBSD srv-01 5.3-STABLE-SNAP001 FreeBSD 5.3-STABLE-SNAP001 #0: Sun
Jan 30 03:57:47 UTC 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
# ps axl |grep entropy
2 14833 14832 0 8 0 1640
Hi,
save-entropy never exists and eats all CPU.
# uname -a
FreeBSD srv-01 5.3-STABLE-SNAP001 FreeBSD 5.3-STABLE-SNAP001 #0: Sun
Jan 30 03:57:47 UTC 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
# ps axl |grep entropy
2 14833 14832 0 8 0 1640 928 wait Is??0
41 matches
Mail list logo
