Hi John,
Now I moved the server-setting to the section of [agent]. And really I
don't need typing the server option as follow:
puppet agent -t
But the agent can't be started as a daemon now, i.g. the agent can be kept
running and is stopped.
Any suggestion?
Wei
--
You received this messag
Sorry, there is a mistyping. It should be:
...
the agent can't be kept running and is stopped.
...
Am Dienstag, 13. Oktober 2015 11:01:02 UTC+2 schrieb Wei Chen:
>
> Hi John,
>
> Now I moved the server-setting to the section of [agent]. And really I
> don't need typing the server option as foll
Hi Marc,
> On 24.09.2015, at 14:54, Marc Haber wrote:
>
> Hi,
>
> I am looking for a puppet agent rpm that can run against a puppet 4
> server (and can use its features) for RHEL 7 on ppc 64. On
> yum.puppetlabs.com, I can only find binaries for agent 1.2.4 (latest
> version) for x86_64 and i38
Thanks Wyatt, my google fu is weak :)
I'm stuck on puppetserver 1.1.1 and puppetdb 2.3.7 for the time being in my
dev environment.
I'll upgrade to the PC1 packages once I've got this current code deployed
into production and see if it makes life easier.
Then begins the task of upgrading production
On Tuesday, October 13, 2015 at 4:01:02 AM UTC-5, Wei Chen wrote:
>
> Hi John,
>
> Now I moved the server-setting to the section of [agent]. And really I
> don't need typing the server option as follow:
>
> puppet agent -t
>
> But the agent can't be started as a daemon now, i.g. the agent can be
ok, so I have been tinkering a bit more with this and I my problems start
when I upgrade to puppet 3.7.5. So 3.7.4 works fine, but 3.7.5 and 3.8.x is
showing some really terrible performance for me.
Running puppetserver (jvm) with 3.7.4, 9 jruby instances and 12G Xmx I get
really good performa
I'm wanting to make some changes to the conditions used in building the
dashboard lists - is it possible to just edit the erb files
in app/views/dashboard?
I've tried editing one of the conditions in the _status_widget.html.erb but
even after restarting foreman & logging out and back in, the da
Hi guys,
I'm having problems migrating from 3.8 to 4.2...
# puppet agent -tv --tags snmp --noop
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Evaluation Error: Error while evaluating a Functio
On 10/13/2015 04:45 PM, Jakov Sosic wrote:
Hi guys,
I'm having problems migrating from 3.8 to 4.2...
# puppet agent -tv --tags snmp --noop
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Loading facts
Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Evaluat
- Original Message -
> From: "Jakov Sosic"
> To: "puppet-users"
> Sent: Tuesday, October 13, 2015 3:48:24 PM
> Subject: [Puppet Users] Re: Puppet 3.8 to 4.2 migration issue...
> On 10/13/2015 04:45 PM, Jakov Sosic wrote:
>> Hi guys,
>>
>> I'm having problems migrating from 3.8 to 4.2..
Hi,
I'd need to create a number of directories in a fasion similar to that:
/var/extlogs/$stage/$client-$application
For example, if stages are integration, staging, production and clients are
client1 and client2 (there are many morem in reality), I'd like to have
puppet create
/var/extlogs/i
Working on a new implementation and just beginning investigation of
managing anti-virus deployment by Puppet. At this point even the selection
of an anti-virus is open. I'm looking for feedback on any particularly
good or bad experiences with the deployment aspect of particular anti-virus
pro
Dear Puppet Enterprise Users,
Puppet Enterprise 2015.2.2 is now available.
Puppet Enterprise 2015.2.2 is a bug-fix release of Puppet Enterprise. In
particular, this release addresses some issues that may be encountered when
upgrading from previous releases in the 2015.2 series. All users of Puppe
Hi!
I'm working on a custom type for Java Util Preferences files. The files
are XML and, unfortunately, aren't handled correctly by Augeas' XML lens.
I'm using the nokogiri library to modify them, since that parser is more
forgiving to some of the formatting errors that I have to deal with.
Here's a snippet from my user management define that shows how I deal with
making a directory that might be many levels deep :
# create the homedir-dir
exec { "mkdir-${username}":
command => "/bin/mkdir -p ${homedirdir} ; /bin/chgrp ${gname}
${homedirdir}",
unless
PS ! For got one bit that goes in front of the other two lines :
# account creation requires that the homedir directory exists
$homedirdir = dirname ( $userhome )
Ignore the comment about the "chgrp" command. I forgot that it is for the
parent directory.
“Sometimes I think the surest
Hi,
On 12/10/2015 23:02, Rob Braden wrote:
> Puppet Agent 1.2.6 is out! This is a new minor release of the all-in-one
> agent bundle which contains no updated component code, but fixes bugs in
> packaging and service management.
Thanks, good news. ;)
> * Includes a fix for an issue that could,
Sorry I add a third question:
On 13/10/2015 23:38, Francois Lafont wrote:
> Is there somewhere a release note concerning the packaging with the
> references to the fixed bugs reported in https://tickets.puppetlabs.com
> (exactly like the release notes of each component of the AIO puppet-agent)?
>
Excellent thanks guys that got me going on the right path looking at the
certs. I'm using puppet apply to build the initial puppet master so the
agent won't have executed when it gets to installing puppetdb so I'll need
to work around this somehow.
Dan
On Friday, 9 October 2015 21:01:00 UTC+
On 13 October 2015 at 15:54, UK_beginner wrote:
> I'm wanting to make some changes to the conditions used in building the
> dashboard lists - is it possible to just edit the erb files in
> app/views/dashboard?
>
> I've tried editing one of the conditions in the _status_widget.html.erb but
> even a
20 matches
Mail list logo
