Re: [Puppet Users] Announce: Ruby 2.3 update planned for puppet-agent 1.6.0

[Francois Lafont]

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 2.3.1.
> 
> Since the update to Ruby 2.3 is a minor release for Ruby, we're including
> it in a minor release of puppet-agent.
> 
> However, user-installed gems in puppet-agent's gem path will require
> re-installation following the upgrade to puppet-agent 1.6.0. (If you think
> this will affect you, please let us know how, and we’ll look into it.)
> 
> If you have any questions about this, please don’t hesitate to ask.

1. So it concerns gems installed via this command:

/opt/puppetlabs/puppet/bin/gem install $gem_foo

Is it correct?


2. And what about gems installed via this command?

/opt/puppetlabs/bin/puppetserver gem install $gem_foo

Is a re-installation after the upgrade needed too?


Thanks in advance for your help.
François Lafont


-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1e32cf87-b2d5-0206-f1ed-48dfa95b396b%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Announce: Ruby 2.3 update planned for puppet-agent 1.6.0

[Geoff Nichols]

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 Ruby, we're including
it in a minor release of puppet-agent.

However, user-installed gems in puppet-agent's gem path will require
re-installation following the upgrade to puppet-agent 1.6.0. (If you think
this will affect you, please let us know how, and we’ll look into it.)

If you have any questions about this, please don’t hesitate to ask.

-- 
Geoff Nichols
Puppet Release Engineering

PuppetConf 2016 , 19 - 21 October, San
Diego, California
*Summer Savings - Register by 15 September and save $240
*

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CADjnYBxeQA_H-dZ71-dsoobEb6fJfpwz7-YnAUXkJgREHTYTrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Puppet web server stops after being started

[Rob Nelson]

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
https://docs.puppet.com/puppetserver/latest/install_from_packages.html#system-requirements
if that seems a likely cause.


Rob Nelson
rnels...@gmail.com

On Fri, Jul 29, 2016 at 12:18 PM, 'Michael Wildey' via Puppet Users <
puppet-users@googlegroups.com> wrote:

> 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 server stops immediately after being started,
> but I don't know why.
>
> Any help is welcome.
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/93e0e0e8-2b10-48ea-82c3-40fa8ec86d91%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAC76iT9dK4XvaxHhzpgD5Lo-Eax2Mj7EFyaxZpHfE9d%2BT2M3_g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Puppet web server stops after being started

['Michael Wildey' via Puppet Users]

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 server stops immediately after being started, 
but I don't know why.

Any help is welcome.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/93e0e0e8-2b10-48ea-82c3-40fa8ec86d91%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Changing namevar of resources triggering alias error

[Luke Bigum]

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 namevar was using 
resource aliases under the hood?

Any ideas on how I could make this work?


[root@localhost ~]# cat test.pp 
nagios_host { 'foo':
  ensure=> present,
  host_name => 'foo',
  address   => 'foo',
  target=> '/tmp/foo',
}

nagios_host { 'foo_again':
  ensure=> present,
  host_name => 'foo',
  address   => 'foo',
  target=> '/tmp/foo_again',
}
[root@localhost ~]# 
[root@localhost ~]# 
[root@localhost ~]# puppet apply test.pp
Notice: Compiled catalog for localhost in environment production in 0.10 seconds
Error: Cannot alias Nagios_host[foo_again] to ["foo"] at /root/test.pp:13; 
resource ["Nagios_host", "foo"] already declared at /root/test.pp:6



--
Luke Bigum
Senior Systems Engineer

Information Systems
---

LMAX Exchange, Yellow Building, 1A Nicholas Road, London W11 4AN
http://www.LMAX.com/

Recognised by the most prestigious business and technology awards
 
2016 Best Trading & Execution, HFM US Technology Awards
2016, 2015, 2014, 2013 Best FX Trading Venue - ECN/MTF, WSL Institutional 
Trading Awards

2015 Winner, Deloitte UK Technology Fast 50
2015, 2014, 2013, One of the UK's fastest growing technology firms, The Sunday 
Times Tech Track 100
2015 Winner, Deloitte EMEA Technology Fast 500
2015, 2014, 2013 Best Margin Sector Platform, Profit & Loss Readers' Choice 
Awards

---

FX and CFDs are leveraged products that can result in losses exceeding your 
deposit. They are not suitable for everyone so please ensure you fully 
understand the risks involved.

This message and its attachments are confidential, may not be disclosed or used 
by any person other than the addressee and are intended only for the named 
recipient(s). This message is not intended for any recipient(s) who based on 
their nationality, place of business, domicile or for any other reason, is/are 
subject to local laws or regulations which prohibit the provision of such 
products and services. This message is subject to the following terms 
(http://lmax.com/pdf/general-disclaimers.pdf), if you cannot access these, 
please notify us by replying to this email and we will send you the terms. If 
you are not the intended recipient, please notify the sender immediately and 
delete any copies of this message.

LMAX Exchange is the trading name of LMAX Limited. LMAX Limited operates a 
multilateral trading facility. LMAX Limited is authorised and regulated by the 
Financial Conduct Authority (firm registration number 509778) and is a company 
registered in England and Wales (number 6505809).

LMAX Hong Kong Limited is a wholly-owned subsidiary of LMAX Limited. LMAX Hong 
Kong is licensed by the Securities and Futures Commission in Hong Kong to 
conduct Type 3 (leveraged foreign exchange trading) regulated activity with CE 
Number BDV088.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/1154755873.4737099.1469807604114.JavaMail.zimbra%40lmax.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] How to manage the service for web server and app?

[Haani Niyaz]

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 (requiring the 
web server service to restart when the app config files changes). 

This is the structure of the mdule (to manage the server & app as a defined 
type):

.

 

├── app 

│   ├── config.pp 

│   ├── install.pp 

│   ├── manage_credentials.pp (defined type)

│   └── params.pp 

├── app.pp (defined type)

├── config.pp 

├── init.pp 

├── install.pp 

├── params.pp 

└── service.pp




I've setup the web server in a typical Package/File/Service style and 
perhaps its also worth noting that in the manifest/config.pp file I notify 
Class['web_server::service'] 
for each file change.




In the app.pp defined type I have the following:


define web_server::app(
  $package_name,
  $repo_name,
  $package_version,
  $credentials
) {

   include web_server

class{'web_server::app::install':

  package_name => $package_name,
  repo_name=> $repo_name,
  package_version  => $package_version,
} ->

class { 'web_server::app::config': 
  credentials => $credentials, 
} 

contain ::web_server::app::install
contain ::web_server::app::config

}



Inside the server::app::config file i have a few  Class['web_server::service'] 
notify statements to restart the service on app file changes. However this 
is causing dependency cycle errors.



Any idea where I'm going wrong with this? How do you generally manage this 
type of scenario? I looked at the apache forge module and it seems to be 
littered with Class['apache::service'] notify statements within 
classes/subclasses - what am I missing here?

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/fa696b73-ed40-49a7-9c0e-a586d55b6ada%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Issues creating a customer type/provider

[Simon Weald]

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 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 type and provider which 
> I can extend further if the need arises. Currently during a run I'm getting 
> an error 400 stating that one of my parameters isn't valid. 
> > 
> > I've provided the relevant code here: 
> https://gist.github.com/analbeard/8560005282856b9302145934730a77a0 
> > 
> > and the run output I'm receiving is: 
> > 
> > Info: Retrieving pluginfacts 
> > Info: Retrieving plugin 
> > Info: Loading facts 
> > Error: Could not retrieve catalog from remote server: Error 400 on 
> SERVER: Invalid parameter keyid on 
> Apt_key[9023A836357AF18193C2F0F8013F8A39FBC95654] at 
> /etc/puppet/environments/development/modules/pkg_mgmnt/manifests/aptkey.pp:10 
> on node test.test.com 
> > Warning: Not using cache on failed catalog 
> > Error: Could not retrieve catalog; skipping run 
>
> Your puppet code is making use of the aptkey type. 
> The type which you created has the name repokey. 
> Puppet::Type.newtype(:repokey) 
>
> You should use the type repokey in you manifest. 
>
> > 
> > 
> > Can anyone shed any light as to why Puppet doesn't like the keyid 
> parameter? 
> > 
> > -- 
> > 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-users...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/9c700d3e-e9bf-49fd-a7fe-8d77271af9c3%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/fa4a2fb3-7207-408b-a137-5b64e2adbf4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Issues creating a customer type/provider

[Martin Alfke]

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 type and provider which I can extend further 
> if the need arises. Currently during a run I'm getting an error 400 stating 
> that one of my parameters isn't valid.
> 
> I've provided the relevant code here: 
> https://gist.github.com/analbeard/8560005282856b9302145934730a77a0
> 
> and the run output I'm receiving is:
> 
> Info: Retrieving pluginfacts
> Info: Retrieving plugin
> Info: Loading facts
> Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
> Invalid parameter keyid on Apt_key[9023A836357AF18193C2F0F8013F8A39FBC95654] 
> at 
> /etc/puppet/environments/development/modules/pkg_mgmnt/manifests/aptkey.pp:10 
> on node test.test.com
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run

Your puppet code is making use of the aptkey type.
The type which you created has the name repokey.
Puppet::Type.newtype(:repokey)

You should use the type repokey in you manifest.

> 
> 
> Can anyone shed any light as to why Puppet doesn't like the keyid parameter?
> 
> -- 
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/9c700d3e-e9bf-49fd-a7fe-8d77271af9c3%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/21F91C94-3FAE-4E44-B6E6-065277C726F6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Question Exec resource

[Martin Alfke]

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 > /opt/openam/install.log' [0m
>  [0;36mDebug: /Stage[main]/Openam::Config/Exec[openam_install]/returns: 
> Certificate was added to keystore [0m
>  [0;36mDebug: /Stage[main]/Openam::Config/Exec[openam_install]/returns: 
> Certificate stored in file  [0m
>  [0;36mDebug: /Stage[main]/Openam::Config/Exec[openam_install]/returns: 
> Certificate was added to keystore [0m
>  [0;36mDebug: /Stage[main]/Openam::Config/Exec[openam_install]/returns: 
> java.net.ConnectException: Connection refused [0m
>  [0;36mDebug: /Stage[main]/Openam::Config/Exec[openam_install]/returns:   
>   at java.net.PlainSocketImpl.socketConnect(Native Method) [0m

This looks like a connection error from within the java process.
This is unrelated to Puppet.
Does the command work when running it from a root shell?
If this is the case: check for further environments setting which might be 
needed by the installer and use the environment parameter of the exec resource 
type.

Best,
Martin

> 
> 
> Could it be an SSL connection issue instead of a path issue with the java 
> -jar command?
> 
> About the idenpotency, by using the creates attribute normally ensure the 
> exec command will be executed only if the file/directory doesn't exist. So i 
> should not have any problem with that.
> 
> 
> -- 
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/cf796f0d-7ddb-4ff5-bbfb-5ce67aeae565%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/C8F54464-11A7-4C69-98B5-C1740EE58B66%40gmail.com.
For more options, visit https://groups.google.com/d/optout.