[root@puppetagentappd /]# sudo puppet agent --test
Info: Caching certificate for puppetagentappd.eng.vmware.com
Info: Caching certificate for puppetagentappd.eng.vmware.com
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: Error 400 on SERVER: Connection refuse
Oh that's clever, thanks :)
Rich
On Thursday, April 10, 2014, John Warburton wrote:
> We are in the middle of a similar task
>
> We are manually fixing lint issues and putting a string '#PUPPET_LINT' at
> the end of each fixed file. The pre commit hook checks for this string
> before doing the
We are in the middle of a similar task
We are manually fixing lint issues and putting a string '#PUPPET_LINT' at
the end of each fixed file. The pre commit hook checks for this string
before doing the lint check
All new puppet modules get the string put in immediately
At some time in the future,
Puppet 3.5.1 RC1 is the first release since 3.5.0 was recalled. It prevents the
new directory environments feature from conflicting with old-style dynamic
environments and fixes the breaking changes that 3.5.0 inadvertently introduced
to the yumrepo resource type. It also fixes a couple of small
Hi John.
It does look as though I've set up the master to manage itself OK, as I'm
seeing my host listed here:
http://snag.gy/sWpfy.jpg
Is this what I should expect?
I also include the class showing as added here:
http://snag.gy/E94QL.jpg
I can't see any way within the Class menu to force assignme
As an experiment, I downgraded back to 3.3.2. However, after restarting
apache I still get the same permission errors I listed in my original post.
On Thursday, 10 April 2014 14:46:48 UTC-7, Guy Knights wrote:
>
> I just upgraded puppet on my master machine (Ubuntu 12.04, running under
> Passeng
I saw one of the Puppet Labs webinars about setting up your Puppet
development environment, and at one point it mentioned using a git hook to
run puppet-lint before committing. We do that where I work with "puppet
parser validate," but right now a lot of our code would not pass a
puppet-lint ru
Does the puppet user have read/execute on all files/dirs under /etc/puppet?
Is the config.ru file owned by the puppet user?
On Thu, Apr 10, 2014 at 3:21 PM, John Pyeatt wrote:
> I've followed all of the documentation at
> http://docs.puppetlabs.com/guides/passenger.html to try to switch from
>
I've followed all of the documentation at
http://docs.puppetlabs.com/guides/passenger.html to try to switch from
webrick to passenger/apache.
I'm obviously doing something wrong however because I can't get passenger
to use /etc/puppet instead of /home/puppet/.puppet to store data.
Any ideas would
I just upgraded puppet on my master machine (Ubuntu 12.04, running under
Passenger/Apache) and it doesn't work properly any more. The upgrade was
from 3.3.2 to 3.4.3.
First of all, after the upgrade I found that the location of config.ru had
changed, from /usr/share/puppet/ext/rack/files/config.ru
We just changed a particular function we use to copy files in 3.4.1 and
then fixed up a couple of things with it in 3.4.3 [1][2]. There were some
more fixes that went into 3.5.0 [3], but it is possible that we missed some
things.
If you don't find this fixed with 3.5.1 when it comes out, then plea
Hi Darin,
Just to clarify - I believe SLES 11 was listed under the section
"Operating Systems that are Not Vulnerable." Are you referring to a
different document that has been posted?
On Thu, Apr 10, 2014 at 3:34 AM, Darin Perusich wrote:
> You've listed SLES 11 as vulnerable, it is not. Howeve
Actually yes, it's 3.4.3
On Thursday, April 10, 2014 12:19:26 PM UTC-4, Rob Reynolds wrote:
>
> What version of puppet agent? Would it happen to be 3.4.x series?
>
>
> On Thu, Apr 10, 2014 at 10:44 AM, Nick Miller
>
> > wrote:
>
>> Hi,
>>
>> I have a manifest that pushes files to some Windows s
What version of puppet agent? Would it happen to be 3.4.x series?
On Thu, Apr 10, 2014 at 10:44 AM, Nick Miller wrote:
> Hi,
>
> I have a manifest that pushes files to some Windows servers. Everything
> seems to work well, except that it sometimes leaves some temp files behind.
> If I have MyA
Hi,
I have a manifest that pushes files to some Windows servers. Everything
seems to work well, except that it sometimes leaves some temp files behind.
If I have MyApp.exe, after a while the directory looks like this:
MyApp.exe
MyApp.exe~RF27dk3hdk.TMP
MyApp.exe~RF27en2n3h.TMP
MyApp.exe~RF27n
I'm not sure what happened but my Passenger virtual host for the puppet
master has stopped working last week. It's running on Amazon Linux
(CentOS) I'm getting the following error.
Error page:
exit (SystemExit)
/usr/lib/ruby/site_ruby/1.8/puppet/util.rb:493:in `exit'
/usr/lib/ruby/site_ruby/
On Wednesday, April 9, 2014 1:27:44 PM UTC-5, Eric Wu wrote:
>
> So I've upgraded the master to 3.2.1
>
> I'm running a local repo and I'm using Oracle Linux 6.5
>
> What do they mean when they say: simplest way to upgrade agents is to
> upgrade the pe-agent package in the repo your package man
Yeah, this one cost me a few hours today.
None of our changes to the manifests were applied to any nodes. There were
no errors so we hadn't even noticed for a few days. Even creating obvious
errors in the code did not cause any problems on the nodes. It seemed like
the master was caching some o
On Thursday, April 10, 2014 1:29:51 AM UTC-5, aspo73 wrote:
>
> Hi all.
>
> I've just installed Puppet Master for the first time. Everything seems to
> be up and running OK on Centos 6.5.
>
> I don't have a local Yum repo so was hoping to use PE Package Management
> method as outlined here:
You've listed SLES 11 as vulnerable, it is not. However OpenSUSE 12.3 and
13.1 are affected and patches have been released.
http://support.novell.com/security/cve/CVE-2014-0160.html
http://lists.opensuse.org/opensuse-security-announce/2014-04/msg5.html
On Apr 10, 2014 1:22 AM, "Eric Sorenson"
Hi,
the sledge hammer approach:
file { 'couchdb.yaml':
path=> '/etc/dd-agent/conf.d/couchdb.yaml',
ensure => $couchDbServer ? {
true => "present",
default => "absent",
},
content =>
21 matches
Mail list logo
