I just spent a little time looking into this, and the json gem appears to
work just fine under JRuby. It looks like there *used* to be a gem called
json-jruby that could be used instead, but it appears that it has now been
merged into json - so, long story short, 'json' should work just fine.
On Thu, Dec 11, 2014 at 12:26 AM, Martin Alfke wrote:
>
> AFAIK there is no cert sign request notification directly built into
> puppet.
Martin is correct; this functionality is not built into puppet.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users"
This is likely a memory issue. Can you verify that the machine on which
you're running the server has sufficient memory? You can also try
decreasing the amount of memory allocated to the server - see
https://github.com/puppetlabs/puppet-server/blob/master/documentation/install_from_packages.markd
On Sun, Jan 25, 2015 at 5:07 PM, Trevor Vaughan
wrote:
> I've been able to do everything from the APIs thus far and, yes, having a
> 'puppet master reload' and 'puppet master environment-flush' (or something)
> would be nice.
>
Trevor - I just created https://tickets.puppetlabs.com/browse/SERVER
On Wed, Apr 20, 2016 at 5:58 AM, Geoff Galitz
wrote:
> Is it possible to get compile master, master of master and code manager
> (file sync) working in the open source versions?
>
Code manager and file sync are only available as part of Puppet
Enterprise. I believe the standard alternative is t
It looks like the cause of this all is the last error message:
Caused by: java.net.UnknownHostException: cent_poc
Is 'cent_poc' resolvable from the machine running conosle services?
On Tue, May 3, 2016 at 11:45 AM, Ali wrote:
>
> Any help will be appreciated .
>
> During puppet installatio
Mike,
To add a bit more to the info that Joe already provided, I would encourage
you to open a support ticket if you have a Puppet Enterprise license.
That'll be the easiest way for us to collaboratively get to the bottom of
this issue.
In terms of simply getting it working, I'd try following ste
Matt,
I believe that the 'idle-timeout-milliseconds' is what you're looking for.
You'll want to put this in
/etc/puppetlabs/puppetserver/conf.d/webserver.conf, inside the 'webserver'
section in that file. Here's a link to the documentation for that setting:
https://github.com/puppetlabs/trapperke
On Mon, Dec 12, 2016 at 9:16 AM, Harish Kothuri
wrote:
> Thanks a lot for your quick reply.
>
> 1. I'm not sure if it's a memory leak issue because we have restarted the
> services and restarted the master machine already. ( have also increased
> RAM from 16GB to 32GB + 1 core to 2 cores )
>
30
On Tue, Jul 21, 2015 at 9:33 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> On 07/21/2015 04:14 PM, jcbollinger wrote:
>
>
>> 2)
>> I read in the changelog that the older clients should work with the
>> backward compatibility, but is it worth even trying? Or should I just push
>> out
Hi Felix,
I tried to reproduce your problem on a fresh Debian 7 VM, but couldn't.
Have you been running the agent on this machine? If so, I suspect you're
hitting this issue: https://tickets.puppetlabs.com/browse/SERVER-528
Cheers,
- Kevin
--
You received this message because you are subscrib
Hi Gene,
That looks like a problem with the permissions on that directory. I'd
start by making sure that the 'puppet' user has read permissions on
/etc/puppet/modules/production.
- Kevin
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsu
Hi Steph,
Just to be sure, you've ensured that the clock is correct on all of your
nodes, right? I don't have a great understanding of this problem, but from
what I know, the underlying issue is significant clock skew (> 30 minutes)
between machines.
Failing that, there's also https://tickets.pu
On Tue, Jan 12, 2016 at 10:20 PM, Rudy Gevaert
wrote:
> Hi,
>
> I'm trying to set up puppetserver for the first time. I
> installed puppetserver 2.2.1-1puppetlabs1 on a trusty server with the
> Debian package. I then installed r10k with 'puppetserver gem install r10k
> --no-ri --no-rdoc'.
>
> H
On Wed, Jan 13, 2016 at 9:04 AM, Kevin Corcoran <
kevin.corco...@puppetlabs.com> wrote:
>
> Even though r10k runs on the master, it runs as a separate process (not
> inside of Puppet Server) and uses the system ruby (likely MRI).
>
... unless we're talking about the r1
15 matches
Mail list logo
