Hi all,
We have the server installed in CentOS 5.7. The version installed of
puppet-server is 2.7.1.
Some puppet clients have installed CentOS 6.x and the version 2.7.9 of
puppet client.
The problem we have is that the puppet client become unresponsive after a
few minutes. All we can see
Hi,
Will need to see logs but generally you cant have the master at an older
version than the clients - if I remember correctly.
Cheers,
Den
On 30/12/2011, at 19:49, Juan-Francisco Diez moch...@gmail.com wrote:
Hi all,
We have the server installed in CentOS 5.7. The version installed of
Similarly, I believe the docs very clearly say (in one or more places) that
your server always needs to be the newest version out of any of your
clients (ie. The server is usually happy/fine to deal with older clients
(with a few potential exceptions), but a newer client may not work with an
older
Thank to all. We try to put the server in the newest version. But with ruby
in CentOS it's a bit more complicated because the new version is not
packaged in the 5.x version.
I will try to put all in the same version
2011/12/30 Russell Van Tassell russel...@gmail.com
Similarly, I believe the
You can use RVM, or getting a ruby 1.8.7 build/rpm shouldn't be that
difficult (I will have to look at our source, tomorrow, but we store a
similar thing in our own local EL repo, pretty much for puppet and one or
two other things ... At this hour I can't remember if we compiled it or
grabbed it
I have tried to deleted the ssl folder under puppet. And then tried to
clean the certificate from the server but did not work.
#puppetca --clean hostname
notice: Revoked certificate with serial # Inventory of signed certificates
# SERIAL NOT_BEFORE NOT_AFTER SUBJECT
err: Could not call revoke:
I have gone little further nowwhat I have done is to delete the ssl folder
from one of the client and ran this command on server: puppetca --clean
clientname
it has generated new certificate but in the end I get the same error:
err: Could not call revoke: Cannot convert into OpenSSL::BN
Further
I was able to sign the certificate to the client but still I am getting
this error now on the
client:
Client puppet-agent[15030]: Starting Puppet client version 2.6.12
Dec 30 08:52:52 Client puppet-agent[15030]: Could not retrieve catalog from
remote server: certificate verify failed
Dec 30
Consider downgrading the CentOS 6 clients.
Might be an easier solution.
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin Hobbes)
- Juan-Francisco Diez moch...@gmail.com wrote:
On Dec 30, 2011, at 3:31 AM, Juan-Francisco Diez wrote:
Thank to all. We try to put the server in the newest version. But with ruby
in CentOS it's a bit more complicated because the new version is not packaged
in the 5.x version.
I think you will find it much easier to remove any
On Dec 30, 2011, at 3:36 AM, Russell Van Tassell wrote:
You can use RVM, or getting a ruby 1.8.7 build/rpm shouldn't be that
difficult (I will have to look at our source, tomorrow, but we store a
similar thing in our own local EL repo, pretty much for puppet and one or two
other things
On Dec 30, 2011, at 6:59 AM, Dan White wrote:
Consider downgrading the CentOS 6 clients.
Might be an easier solution.
probably not the best idea. his server is 2.7.1 and there's been a lot of bug
fixes between 2.7.1 and 2.7.9 thus bringing his server up to speed makes more
sense long
Do I need to make any changes to server or delete sl info on the server. I
am still getting the certificate verify failed error on clients?
On Fri, Dec 30, 2011 at 8:54 AM, Mohammad Khan makhan...@gmail.com wrote:
I was able to sign the certificate to the client but still I am getting
this
- Craig White craig.wh...@ttiltd.com wrote:
On Dec 30, 2011, at 6:59 AM, Dan White wrote:
Consider downgrading the CentOS 6 clients.
Might be an easier solution.
probably not the best idea. his server is 2.7.1 and there's been a lot of bug
fixes between 2.7.1 and 2.7.9
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Manifest_Documentation
I discovered the self-documentable feature and I am having a fantasic time
going through my puppetmaster.
The first snag I hit was in trying to make lists of more than one level.
A one-level list is made with an
We have a case where we've been requested to create an extra symlink. The
system provides libsomething.so.0.vv.rr and a symlink of
libsomething.so.0. We need create a symlink libsomething.so (without the
.0). I'm afraid maintenance may change the base file and break the
puppeted symlink.
Can
Did you remove the ssldir on the server or the client? Usually to
completely reset the cert you run clean on the server, remove the
contents of the ssldir on the client, then re-run puppet and it should
rebuild the cert. I wouldn't recommend removing the ssldir on the
server except as a last
Hi,
On Dec 30, 2011, at 3:50 AM, Juan-Francisco Diez wrote:
The problem we have is that the puppet client become unresponsive after a few
minutes. All we can see through the logs of the client is that the puppet is
running but never end. We see the process through a ps command but it never
I removed ssldir from clients and ran the puppetca --clean from the server.
It ran fine finally. Now I am stuck on where client complains that
'certificate verify failed I dont know what to do now?
On Fri, Dec 30, 2011 at 11:42 AM, Aaron Grewell aaron.grew...@gmail.comwrote:
Did you remove the
You'll have to re-sign your node's cert using puppetca --sign hostname
On Fri, Dec 30, 2011 at 9:28 AM, Mohammad Khan makhan...@gmail.com wrote:
I removed ssldir from clients and ran the puppetca --clean from the server.
It ran fine finally. Now I am stuck on where client complains that
I have done this already; however, client certificate verify failed is
occurring now where I am stuck.
On Fri, Dec 30, 2011 at 12:51 PM, Aaron Grewell aaron.grew...@gmail.comwrote:
You'll have to re-sign your node's cert using puppetca --sign hostname
On Fri, Dec 30, 2011 at 9:28 AM, Mohammad
I'm using external nodes. I wanted to break up the node files into
directories based on say, the environment, dev, prod etc. Does puppet
set anything besides the host name when it calls the external node
script, such as the environment? Are these variables available as
environment variables ?
You get only the host name from the agent. When I did this using a
YAML-based ENC I checked each environment directory in turn for a file
matching the hostname and just made sure to only create it in the
proper place.
On Fri, Dec 30, 2011 at 12:29 PM, Douglas Garstang
doug.garst...@gmail.com
Thanks.
On Fri, Dec 30, 2011 at 12:51 PM, Aaron Grewell aaron.grew...@gmail.com wrote:
You get only the host name from the agent. When I did this using a
YAML-based ENC I checked each environment directory in turn for a file
matching the hostname and just made sure to only create it in the
On Fri, Dec 30, 2011 at 7:05 AM, Craig White craig.wh...@ttiltd.com wrote:
On Dec 30, 2011, at 3:36 AM, Russell Van Tassell wrote:
You can use RVM, or getting a ruby 1.8.7 build/rpm shouldn't be that
difficult (I will have to look at our source, tomorrow, but we store a
similar thing in
Hi, Maybe a Time related Problem? Check the Time on both, Client and Server
Am 30.12.2011 um 18:55 schrieb Mohammad Khan makhan...@gmail.com:
I have done this already; however, client certificate verify failed is
occurring now where I am stuck.
On Fri, Dec 30, 2011 at 12:51 PM, Aaron
- Original Message -
Thanks.
On Fri, Dec 30, 2011 at 12:51 PM, Aaron Grewell
aaron.grew...@gmail.com wrote:
You get only the host name from the agent. When I did this using a
YAML-based ENC I checked each environment directory in turn for a
file matching the hostname and just
Well isn't that handy!
On Fri, Dec 30, 2011 at 12:57 PM, R.I.Pienaar r...@devco.net wrote:
- Original Message -
Thanks.
On Fri, Dec 30, 2011 at 12:51 PM, Aaron Grewell
aaron.grew...@gmail.com wrote:
You get only the host name from the agent. When I did this using a
YAML-based
On Thu, Dec 29, 2011 at 4:01 PM, seanm reinvigor...@gmail.com wrote:
facter --version is showing: 1.5.7
It looks like there is have been quite a few ec2 fact improvements
since 1.5.7. The current version of facter is 1.6.4. You could try
that (download from apt.puppetlabs.com). I see five or
29 matches
Mail list logo
