Hi Felix,
It was consuming lot of CPU and causing the host machine to get hanged.. I used
the inline_template for the moment.
Any work around would be nice ??
I don’t know why it is causing hurt to cpu, cause its just a simple math out
there. Let me know ??
> On 15-Nov-2014, at 12:08 am, Feli
Puppet can actually do math inline:
$shmmax = 2 * 1024 * 1024 * 1024
notify { $shmmax: }
Maybe this is the easiest way to solve your problem?
Thanks,
Spencer
On Sun, Nov 16, 2014 at 11:19 AM, Ashish wrote:
> Hi Felix,
>
> It was consuming lot of CPU and causing the host machine to get hanged
Since p-server 3.7 doesn't appear to work on the AWS linux AMI how about
creating an AMI that does work?
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-
Can't run 'facter' either.
$ cat /etc/os-release
NAME="Amazon Linux AMI"
VERSION="2014.09"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2014.09"
PRETTY_NAME="Amazon Linux AMI 2014.09"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2014.09:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/";
I
On 11/16/2014 01:25 PM, JonY wrote:
> Since p-server 3.7 doesn't appear to work on the AWS linux AMI how
> about creating an AMI that does work?
Such as "the official Puppet Linux"?
I don't think that I'd care for that. After all, Puppet aims at
supporting a large range of platforms, not imposing
Hi,
I'm not familiar with the details of the CentOS packages from
puppetlabs. I assume that those explicitly use the ruby1.8 binary.
Try and take a look using "less `which puppet`". The first line
(shebang) holds the Ruby invocation.
If it's indeed ruby1.8, you might need to patch your Puppet
in
On 11/14/2014 10:38 AM, David Schmitt wrote:
> Puppet evaluates which provider to use only once per agent run.
Hmm, are you sure about that?
As far as I know, providers *will* become suitable during the agent
transaction. Support for this has been added, seeing as it is not an
uncommon occurence
On Sun, Nov 16, 2014 at 6:07 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 11/16/2014 01:25 PM, JonY wrote:
> > Since p-server 3.7 doesn't appear to work on the AWS linux AMI how
> > about creating an AMI that does work?
>
> Such as "the official Puppet Linux"?
>
> I don't think t
> Its not for lack of packages...rather how they get installed that's the
> issue. The AMI is installing ruby 1.8 AND 2.0 when 'yum install
> puppet-server' runs. PS can't find its packages when it tries to run.
In any event I'll try a diff package and see if I get any further.
--
You received t
Hi Felix,
Catalog compile time is around 10 seconds
One Node:
Nov 14 14:25:20 puppetmaster01 puppet-master[6884]: Compiled catalog for
test-www01-xxx-com.x.net in environment test in 6.24 seconds
On my search i also find this curious behavior. Any ideas why?
Nov 15 22:08:00 puppetmaster01 pu
10 matches
Mail list logo
