[Puppet Users] Re: Unknown resource type after Upgrade

2018-09-28 Thread Christian Reiß
Hey,

thank you-- 
that clears that up. Seems like time will solve the issue; postponing the 
update for now.

Am Donnerstag, 27. September 2018 11:14:19 UTC+1 schrieb Christian Reiß:
>
> Hey folks,
>
> I am currently upgrading to 6.x on a test setup using my live puppet code; 
> trying to get it to work with 6.x.
> One weird issue I am getting is that alle default definitions (upper case 
> classes) are faulting:
>
> Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
> Server Error: Evaluation Error: Resource type not found: Nagios_service (
> file: /etc/puppetlabs/code/environments/production/modules/pn_icinga/
> manifests/client/checks.pp, line: 83, column: 3) on node outleapt.test
> Warning: Not using cache on failed catalog
> Error: Could not retrieve catalog; skipping run
>
>
>
> The corresponding manifest looks like this:
>
> Nagios_service {
> check_period  => '24x7',
> ensure=> $::pn_icinga::client::installed,
> host_name => $::trusted['certname'],
> initial_state => 'o',
> max_check_attempts=> '3',
> notification_interval => '5',
> notification_options  => 'w,u,c,r',
> notification_period   => $notification_period,
> notifications_enabled => '0',
> [...]
> }
>
> Did I miss a regression somewhere?
> Any help is greatly appreciated!
>
> -Chris.
>

-- 
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/8a5b4fed-cf93-4c8a-8652-5fc3222952c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Puppetserver does not auto-load.

2018-09-27 Thread Christian Reiß
I have a wierd question:

On a fresh Server (Centos 7, PuppetServer 6) with only one nagios class 
(with nagios_core from forge I am getting this error:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Evaluation Error: Error while evaluating a Resource 
Statement, Could not autoload puppet/type/nagios_service: no such file to 
load -- puppet/util/nagios_maker (file: 
/etc/puppetlabs/code/environments/production/manifests/site.pp, line: 4, 
column: 3) on node hyposulphuric

If I do a puppet apply however, the same site.pp applies correctly without 
issues (well, it complains about exporting ressources not possible). Why 
would a puppet apply correctly load the puppet forge module when then 
puppet server (puppet agent --test) does not and yields above error?

I have been hitting my head against the issue all day.
Any help is greatly appreciated.

-Chris.

-- 
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/b0c75235-39ab-434d-850a-84912a6a1fb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Puppet Users] Unknown resource type after Upgrade

2018-09-27 Thread Christian Reiß
Hey Rafael,

thanks for your reply. Ironically I was readind the deprecated logs and 
seem to have missed that, After doing a puppet module install the error 
changed to

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Evaluation Error: Error while evaluating a Type-Name, Could 
not autoload puppet/type/nagios_service: no such file to load -- puppet/util
/nagios_maker (file: /etc/puppetlabs/code/environments/production/modules/
pn_icinga/manifests/client/raid.pp, line: 15, column: 3) on node outleapt.
test

Mind pushing me once more in the right direction?

-Chris.


Am Donnerstag, 27. September 2018 11:25:34 UTC+1 schrieb Rafael Tomelin:
>
> Hi dear,
>
> This link the puppet6 release notes.
> https://puppet.com/docs/puppet/6.0/release_notes.html#deprecations
>
>
>- The Nagios types no longer ship with Puppet, and are now available 
>as the puppetlabs/nagios_core module from the Forge.
>
>
> Em qui, 27 de set de 2018 às 07:14, Christian Reiß  > escreveu:
>
>> Hey folks,
>>
>> I am currently upgrading to 6.x on a test setup using my live puppet 
>> code; trying to get it to work with 6.x.
>> One weird issue I am getting is that alle default definitions (upper case 
>> classes) are faulting:
>>
>> Error: Could not retrieve catalog from remote server: Error 500 on SERVER
>> : Server Error: Evaluation Error: Resource type not found: Nagios_service 
>> (file: /etc/puppetlabs/code/environments/production/modules/pn_icinga/
>> manifests/client/checks.pp, line: 83, column: 3) on node outleapt.test
>> Warning: Not using cache on failed catalog
>> Error: Could not retrieve catalog; skipping run
>>
>>
>>
>> The corresponding manifest looks like this:
>>
>> Nagios_service {
>> check_period  => '24x7',
>> ensure=> $::pn_icinga::client::installed,
>> host_name => $::trusted['certname'],
>> initial_state => 'o',
>> max_check_attempts=> '3',
>> notification_interval => '5',
>> notification_options  => 'w,u,c,r',
>> notification_period   => $notification_period,
>> notifications_enabled => '0',
>> [...]
>> }
>>
>> Did I miss a regression somewhere?
>> Any help is greatly appreciated!
>>
>> -Chris.
>>
>> -- 
>> 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/bde5ac1d-f1ef-4454-885d-b499f22062c8%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/puppet-users/bde5ac1d-f1ef-4454-885d-b499f22062c8%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
>
> Atenciosamente,
>
> Rafael Tomelin
>
> skype: rafael.tomelin
>
> E-mail: rafael@gmail.com 
>
> RHCE  - Red Hat Certified Engineer
> PPT-205 - Puppet Certified Professional 2017
> Zabbix- ZABBIX Certified Specialist
> LPI3 
> ITIL v3
>

-- 
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/c2b29923-114f-4a82-8a66-cba5e428ca4b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Unknown resource type after Upgrade

2018-09-27 Thread Christian Reiß
Hey folks,

I am currently upgrading to 6.x on a test setup using my live puppet code; 
trying to get it to work with 6.x.
One weird issue I am getting is that alle default definitions (upper case 
classes) are faulting:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Evaluation Error: Resource type not found: Nagios_service (
file: /etc/puppetlabs/code/environments/production/modules/pn_icinga/
manifests/client/checks.pp, line: 83, column: 3) on node outleapt.test
Warning: Not using cache on failed catalog
Error: Could not retrieve catalog; skipping run



The corresponding manifest looks like this:

Nagios_service {
check_period  => '24x7',
ensure=> $::pn_icinga::client::installed,
host_name => $::trusted['certname'],
initial_state => 'o',
max_check_attempts=> '3',
notification_interval => '5',
notification_options  => 'w,u,c,r',
notification_period   => $notification_period,
notifications_enabled => '0',
[...]
}

Did I miss a regression somewhere?
Any help is greatly appreciated!

-Chris.

-- 
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/bde5ac1d-f1ef-4454-885d-b499f22062c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Puppet Users] Puppet, Facter, looping through IPs

2013-08-14 Thread Christian Reiß
Hello all,

I am trying to set up ssh keys (sshkeys) for populate 
/etc/ssh/ssh_known_hosts. So far it works great, but I want to have aliases 
for all ips online on that host. 

Two problems:

- The assumption is that the interface count and names are unknown. There 
can be one eth or many, none but a xapi device etc. There is, however, 
interfaces variable from facter, which holds all the interfaces.

- I need to loop through the array and use the contents of that variable, 
ie:

interfaces = eth0,eth1,lo,tun0
ipaddress = 46.229.47.132
ipaddress_eth0 = 46.229.47.132
ipaddress_eth1 = 10.1.0.2
ipaddress_lo = 127.0.0.1
ipaddress_tun0 = 10.10.0.1

So I would need to loop through interfaces, query the variable with the 
same name to get the ip address. All this by acoiding loopback.

- I dont know a good way to then add all compiled aliases into sshkeys.

Does anyone have a pointer / solution?

Thank you for your help in advance,
Chris.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.




[Puppet Users] Nagios Puppet

2013-06-27 Thread Christian Reiß
Hello folks,

I am currently using Puppet to forge the nagios configuration files. Using 
exported ressources it really works well - to a point.

The one thing I am banging my head against is the service definitions. The 
services use stuff like remote-nrpe-zombie-procs, which of course, is not 
defined anywhere:

define service {
## --PUPPET_NAME-- (called '_naginator_name' in the 
manifest)check_zombie_procs_gaming
useremote-nrpe-zombie-procs
host_name  gaming.alpha-labs.net
}

So far I am letting puppet generate the three configs:

nagios_host.cfg
nagios_hostextinfo.cfg
nagios_service.cfg

Tho for this to work I would need a corresponding commands.cfg and all the 
Howtos out there do not seem to have my problem. The important snipplet 
from my config would be this:


 Nagios_host || {
 require = File[resource-d],
 notify = Service[icinga],
 }

 Nagios_service || {
 require = File[resource-d],
 notify = Service[icinga],
 }

 Nagios_hostextinfo || {
 require = File[resource-d],
 notify = Service[icinga],
 }

 Nagios_command || {
 require = File[resource-d],
 notify = Service[icinga],
 }


After banging my head for 3 evenings on this I really need your help.
Thanks for any pointers.

-Chris.

-- 
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.