On Fri, Mar 04, 2011 at 07:42:22AM -0800, Forrie wrote:
> I manually created the mount points and incorrectly assumed the mount
> process would automatically create the point if it didn't exist.
Afraid it doesn't, they have to exist before hand.
> Can you explain the wrap you were talking about?
On Fri, Mar 04, 2011 at 09:35:36AM +, toneeeda...@googlemail.com wrote:
> Hi Im running on centos 5.5, with the latest puppet from the epel repos. if
> i manually unlock the account i can login fine with ssh keys, so i was
> wondering if its to do with creating a user without a password?
Odd.
On 4 March 2011 13:21, Rich Rauenzahn wrote:
> This visudo checker I've written (based on some examples from the web
> and puppet training materials) causes a dependency loop -- but only
>
I've approached the problem from another direction and we have a subversion
pre-commit hook for the sudoers
You might find a thread in this list with a subject of "Variable
scopes and overriding" helpful.
Mohamed.
On Sat, Mar 5, 2011 at 6:22 PM, . wrote:
> Hello puppeteers.
>
> I'm trying to find out the 'puppet' way of overwriting a config/variable.
> I've tried using a define (http://pastebin.co
Hello puppeteers.
I'm trying to find out the 'puppet' way of overwriting a
config/variable. I've tried using a define
(http://pastebin.com/ncVwtwGj) and a parameterized class
(http://pastebin.com/3UysCgi7). But both end up with duplicate definitions.
I'm trying to avoid setting up gl
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
