On Aug 31, 2010, at 10:47 PM, John Warburton wrote:
Hi All
I am trying to use the section on Centralised Puppet Infrastructure on the
Scaling Puppet page -
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Scalability
No matter what I do, I always end up with the client
There is an open bug with 0.25.x (and 2.6) which breaks certificate
chaining.
this works well for the 0.24.x series, and I hope that will work again
sometime in the near future with 2.6.x series.
I would recommend you at the moment to use one machine as the CA, if you can
accept the fact that its
I think that implementing the desired behaviour you've specified would
definitely be a move in the right direction.
Putting site-wide settings in on place would avoid confusion and frustration!
Regards,
Brett
On 27 Aug 2010, at 23:38, Igal Koshevoy wrote:
Regarding the timezone and date-time
Hello,
I am using puppet 2.6.1rc3 and puppet-dashboard-1.0.3
I set up online reporting setting in puppetmaster configuration:
reports = store,log,tagmail,http
reporturl = http://localhost:3000/reports
It is working, new reports are loaded in puppet-dashboard, but
whenever I execute the
Automatic tags don't work for me but explicit tags do since moving to 2.6.
On Mon, Aug 30, 2010 at 1:47 PM, Todd Zullinger t...@pobox.com wrote:
Jean-Baptiste Quenot wrote:
After upgrading Puppet from 0.24.8 to 2.6.1rc2 at my company, I
notice that puppet agent's --tags option is not
2010/9/1 Héctor Rivas Gándara key...@gmail.com:
I am using puppet 2.6.1rc3 and puppet-dashboard-1.0.3
It is working, new reports are loaded in puppet-dashboard, but
whenever I execute the client I get this error:
err: Could not send report: end of file reached
Do you known why this problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/31/2010 06:41 PM, Trevor Hemsley wrote:
Actually nothing to do with the content of this post but is anyone else
getting a lot of mails from puppet-users at least twice? This particular
one came through 3 times with the same timestamp and
2010/8/30 Héctor Rivas Gándara key...@gmail.com:
The errors appear once or two times, randomly, and if I execute the
client again it works properly. They are usually these kind of errors:
You will probably find life improved by deploying
another mode of operation for the puppetmaster daemon,
On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
I still have random Segmentation Faults with ruby on AIX. I will
ignore them for the moment until I will compile last ruby source (may
be 1.9.x) and test it.
I remember reading somewhere that puppet isn't compatible with 1.9.x versions
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
I still have random Segmentation Faults with ruby on AIX. I will
ignore them for the moment until I will compile last ruby source
(may be 1.9.x) and test it.
I remember reading
On Wed, Sep 1, 2010 at 4:55 PM, Patrick kc7...@gmail.com wrote:
On Sep 1, 2010, at 5:28 AM, Héctor Rivas Gándara wrote:
I still have random Segmentation Faults with ruby on AIX. I will
ignore them for the moment until I will compile last ruby source (may
be 1.9.x) and test it.
I remember
You wouldn't by any chance be able to share those DISA SRR manifests to
others would you?I've got to do the same thing here at work and it could
be a good starting point.
On Thu, Dec 17, 2009 at 8:21 PM, David Pheasant dpheas...@gmail.com wrote:
Hey everyone,
I accidentally sent an
On Aug 26, 4:22 pm, Brice Figureau brice-pup...@daysofwonder.com
wrote:
On Thu, 2010-08-26 at 05:08 -0700, kit wrote:
This server is 7.2-RELEASE-p4 #0
Just want to confirm this.
I am also experiencing this and my setup is new and very simple (3
agents, 1 master and only 2 files).
FreeBSD
On 26 Aug, 16:22, Brice Figureau brice-pup...@daysofwonder.com
wrote:
On Thu, 2010-08-26 at 05:08 -0700, kit wrote:
This server is 7.2-RELEASE-p4 #0
So it has the fix I sent.
debug: file_metadata supports formats: b64_zlib_yaml marshal pson raw
yaml; using pson
debug: file_metadata
Thanks Ohad
I have updated the Wiki entry with a warning (where's the blink tag?) and
references to the bugs on certificate chaining
I'm not 100% comfortable with a single CA, so would it be possible to do the
following:
ca_server = puppet-ca.example.com
rsync the ssl dir every 5 minutes to
15 matches
Mail list logo
