Hi,
On 30/07/2016 02:00, Geoff Nichols wrote:
> Because Ruby 2.1 is approaching end-of-life (upstream bugfix support ended
> March 2016), we need to move puppet-agent to a more modern Ruby version.
>
> If all goes well with testing, the upcoming puppet-agent 1.6.0 release will
> include Ruby
Because Ruby 2.1 is approaching end-of-life (upstream bugfix support ended
March 2016), we need to move puppet-agent to a more modern Ruby version.
If all goes well with testing, the upcoming puppet-agent 1.6.0 release will
include Ruby 2.3.1.
Since the update to Ruby 2.3 is a minor release for
You can check the logs of the puppetserver startup. A common reason is that
VMs have less RAM than the process expects to be allocated. You can either
increase the RAM or adjust the puppetserver settings to use less RAM, with
impact to the performance of course. See
I installed an puppetserver just like ist is written in the
manual https://docs.puppet.com/puppet/4.5/reference/index.html on Debian
Jessie.
My Problem is that as soon as I want to get a cert for an agent it says
that the puppetserver doesn't listen on Port 8140.
Now I found out that the web
Can someone explain this to me? I thought I'd be able to change the title of a
nagios_host resource but leave name_var the same to effectively write two
nagios_host files to disk with the same content, but instead I'm triggering an
error in the resouce alias code. I didn't realise changing
Hi there,
I have a use case where we currently manage a web server, and an app. Now
this similar to deploying tomcat and a webapp or apache and a php app. Both
the server and the app subscribe to the Package/File/Service pattern
however I seem to have hit a problem managing the service
Hi Martin
Thanks for pointing that out; rookie mistake! I spotted a few other issues
which I've now tidied up and I'm happy to say that it now works perfectly.
Thanks for your help!
On Friday, July 29, 2016 at 7:57:07 AM UTC+1, Martin Alfke wrote:
>
> Hi Simon,
>
>
> > On 28 Jul 2016, at
Hi Simon,
> On 28 Jul 2016, at 12:53, Simon Weald wrote:
>
> Hi guys
>
> I'm extending our in-house package management system to include management of
> apt's GPG keys (we're a Debian shop). Ruby isn't my forte, but I've cooked up
> what I think is a decent working
Hi Christian,
> On 28 Jul 2016, at 18:47, Christian Charpentier wrote:
>
> Thnaks for your answer Martin.
>
> Here is the beginning of the stack:
>
> [0;36mDebug: Executing '/bin/sh -c source /etc/profile &&
> /opt/openam/bin/openam_install.sh install cm >