Actually... we have two puppet masters on two different servers. Both are
sourcing their /etc/puppet from the same working copy, and clients
connecting to both puppet masters are displaying this PSON message.
Also, it isn't the .puppet directory problem. A 'find . -name .puppet' on
both puppetmast
Trouble is that there isn't a lot more information here. Is it always
the same error?
Actually you might have the same .puppet directory problem that I had
but it would have to be in the home directory of whoever last started
puppetmasterd (so not on the client).
On Mar 6, 8:01 pm, Douglas Garst
On Sun, Mar 6, 2011 at 2:48 AM, Bill Proud wrote:
> SSL_write is the function that writes to an SSL connection. Evidently
> in this case there was an error - perhaps the connection was lost.
>
>
This error is occurring on multiple clients at regular intervals in a new
data centre, sometimes on V
SSL_write is the function that writes to an SSL connection. Evidently
in this case there was an error - perhaps the connection was lost.
Bill
> Okidoki. below is what appeared in the masterhttp.log file when this
> client tried to connect.
>
> [2011-03-06 06:46:34] ERROR OpenSSL::SSL::SSLEr
On Fri, Mar 4, 2011 at 9:31 AM, James Turnbull wrote:
> Bill Proud wrote:
> > Sorry Jed I didn't realise that you didn't know about .puppet
> > directories. A .puppet directory is created in your home directory if
> > you accidentally run puppet as yourself and not as root. The problem
> > that
Bill Proud wrote:
> Sorry Jed I didn't realise that you didn't know about .puppet
> directories. A .puppet directory is created in your home directory if
> you accidentally run puppet as yourself and not as root. The problem
> that I had was that sometimes puppetd was correctly reading SSL
> sett
Sorry Jed I didn't realise that you didn't know about .puppet
directories. A .puppet directory is created in your home directory if
you accidentally run puppet as yourself and not as root. The problem
that I had was that sometimes puppetd was correctly reading SSL
settings from /var/lib/puppet/ss
Hi doug, I've been getting this as well , someone suggested searching
the entire filesystem on the client for a directory called .puppet and
delete any found. I haven't tried this yet though
On Mar 3, 2:36 pm, Douglas Garstang wrote:
> I'm sure it must already be a known bug, but I've been getti
