date:20160505

[Puppet Users] Update Windows server timezone using Puppet Enterprise

2016-05-05 Thread Karthik Durairajan

Hi,

I'm new to Puppet and still trying to get my head around it. Just wondering 
if anybody out there, by any chance, have a working module to set Windows 
system timezone automatically. There are a few modules on pupperforge to do 
the same but not a single one for Windows platform. Thanks.

Karthik

-- 
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/bfe4f386-e763-4479-9bdc-4342c79c08dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Problem with puppetdb encoding

2016-05-05 Thread Wyatt Alt

Hey Angel,

This sounds like a bug to me but I haven't had time to reproduce it. Would
you mind filing a ticket at tickets.puppet.com?

Wyatt



On Wed, May 4, 2016 at 1:37 AM, Angel L. Mateo  wrote:

> Hello,
>
> I'm having a problem with puppetdb. I have deploy a new
> puppetserver (running in a ubuntu 14.04 server and installed from AIO
> package) that uses an already existing puppetdb (2.3.8, I know there are
> newer versions, but this puppetdb is also used by a puppet 3.8 master).
>
> With my current puppet 3.8 server I don't have any problem, but in
> the new puppetserver I'm having problem with the encoding of the stored
> resources.
>
> For example, I have a resource like this:
>
> @@omd_nagios_service {"${::nagios_hostname}_Trafico_eth0":
>   ensure  => hiera('profile::nagios::ensure', 'present'),
>   host_name   => $::nagios_hostname,
>   service_description => 'Tráfico eth0',
>   contact_groups  => hiera('profile::nagios::contact_groups',
> undef),
>   use => 'Servicio_Generico_Telematica_Grafica',
>   check_command   => 'check_interface_traffic!eth0 90 95 public
> 1000',
>   tag => 'omd-nagios-telematica',
>   site=> 'telematica',
> }
>
> This resource is in catalogs applid in puppet 3.8 master and
> puppetserver. For clients using the puppet 3.8 master the information
> stored in the puppetdb database are like:
>
>  resource |name |
>value
>
> --+-+--
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | check_command   |
> "check_interface_traffic!eth0 90 95 public 1000"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | contact_groups  | ""
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | site|
> "telematica"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | use |
> "Servicio_Generico_Telematica_Grafica"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | host_name   |
> "tlm_xenon21"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | ensure  | "present"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | tag |
> "omd-nagios-telematica"
>  5aaad4db237176d84701792d35fd9c04ce0b26ae | service_description | "Tráfico
> eth0"
>
> but for clients in the new puppetserver are like:
>
>  resource |name |
>value
>
> --+-+--
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | ensure  | "present"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | host_name   |
> "tlm_mus31"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | service_description |
> "Tr��fico eth0"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | use |
> "Servicio_Generico_Telematica_Grafica"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | check_command   |
> "check_interface_traffic!eth0 90 95 public 1000"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | tag |
> "omd-nagios-telematica"
>  ff19d1eaf82d344bc406f6a4ba5b5c21d48fc10d | site|
> "telematica"
>
> where the service_description attribute that should be 'Tráfico
> eth0' is 'Tr��fico eth0'.
>
> I have checked that encoding in the database is correct:
>
> ~$ sudo -u postgres psql -P pager=off -l
>  List of databases
>  Name |  Owner   | Encoding |   Collate   |Ctype| Access
> privileges
>
> --+--+--+-+-+---
> ...
>  puppetdb | postgres | UTF8 | es_ES.UTF-8 | es_ES.UTF-8 |
> =T/postgres  +
>   |  |  | | |
> postgres=CTc/postgres+
>
> The only different I have found is that puppet 3.8 master (run
> with passenger) has LANG=C, but puppetserver java process has
> LANG=es_ES.UTF-8.
>
> Any help? Thank you.
>
>
> --
> Angel L. Mateo Martínez
> Sección de Telemática
> Área de Tecnologías de la Información
> y las Comunicaciones Aplicadas (ATICA)
> http://www.um.es/atica
> Tfo: 868887590
> Fax: 86337
>
> --
> 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/5729B4CC.9010202%40um.es.
> 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

[Puppet Users] Why can't I see my external facts from inside a Ruby script?

2016-05-05 Thread Eric Rodriguez

Running Facter v2.4.6, Puppet 3.8.6 on Ubuntu Trusty
One Puppet master host and one Agent

I have a custom Puppet report and I'd like to read some of my external 
Facts from within this report. I can see the external Fact from the cli and 
ALSO when running:

ruby -e "require 'facter'; puts Facter.value(:external_fact)"


I don't understand why this is. My external facts are in 
/etc/facter/facts.d/external.json.

Any idea what I am doing wrong here? Why can't I see this custom Fact from 
a Puppet report?

Thanks...

-- 
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/0890b9b6-f833-48ce-bb0a-884f930fb57c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Error: Could not find a suitable provider for ec2_instance : puppet Enterprise 2016.1

2016-05-05 Thread Saurabh Agrahari

Hi James,
Thanks for your reply.
I am following the below document to configure AWS module 
https://forge.puppet.com/puppetlabs/aws

I could install and see gems (aws-sdk-core) only if I install them from 
/*opt/puppetlabs/puppet/bin/gem 
install *location,
and as per this document as well i should install from this location only.
I tried installing from /opt/puppetlabs/bin/puppetserver gem install but 
gem did not get installed.

On Wednesday, May 4, 2016 at 8:19:35 PM UTC+5:30, James Pryor wrote:
>
> pupeptserver is running it's own ruby by way of JRuby and 
> '/*opt/puppetlabs/puppet/bin/gem 
> install' *is puppet (the client) agent's ruby.
>
> I'm pretty sure to install gems for pupetserver, you need to do it very 
> differently:
>
> https://github.com/puppetlabs/puppetserver/blob/master/documentation/gems.markdown#installing-and-removing-gems
>
> I hope I'm correct and I hope this helps.
>
> James
>
> On Wed, May 4, 2016 at 6:04 AM, Saurabh Agrahari  > wrote:
>
>> I keep getting error "Could not find a suitable provider for 
>> ec2_instance" while running a pp file to create ec2 instance from puppet 
>> Enterprise 2016.1 .
>> Installed version are
>> Ruby - ruby 1.9.3p484 (2013-11-22 revision 43786)
>> puppet - 4.4.1
>> puppetlabs-aws (v1.4.0)
>>
>> gem list --
>> *** LOCAL GEMS ***
>>
>> aws-sdk-core (2.3.0)
>> jmespath (1.2.4)
>> json_pure (1.8.3)
>> retries (0.0.5)
>>
>>
>> I installed aws module using "*/opt/puppetlabs/puppet/bin# gem install 
>> aws-sdk-core retries*". as mentioned in read me.
>> Everything seems correct configuration, still keep getting the same 
>> error. I followed the suggestions given in similar threads but it is not 
>> helping
>> Please advise.
>>
>> -- 
>> 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/b2f07466-b213-43d0-9ded-7dd46248b27b%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/39c5749d-4d4e-4234-b73f-363a696c0e2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] ERROR: The puppet master service failed to start within 120 seconds; unable to proceed

2016-05-05 Thread rakesh balusa


up votedown votefavorite 


I'm trying to install puppet-enterprise (2016.1.1) on EC2 in AWS. It keeps 
failing all the time by showing the error message below :

** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140
** HTTP_PROXY= http_proxy= HTTPS_PROXY= https_proxy= 
/opt/puppetlabs/puppet/bin/curl --tlsv1 -f -s 
MY_EC2_INSTANCE_PUBLIC_HOSTNAME:8140


** cp 
/opt/puppetlabs/puppet/share/installer/install_log.lastrun.ec2-52-9-200-155.us-west-1.compute.amazonaws.com.log
 /var/log/puppetlabs/installer
** sed "s/^\(q_.*password\)=.*/#\1=REDACTED/g" < 
"/tmp/pe-installer-M5BopSNZ/install/answers.lastrun.ec2-52-9-200-155.us-west-1.compute.amazonaws.com"
 > "/var/log/puppetlabs/installer/answers.install"
!! ERROR: The puppet master service failed to start within 120
   seconds; unable to proceed

thanks, your help is much appreciated.

-- 
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/209d73b3-6a29-4909-a5bd-e99bd976f819%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Problem with snmpd service in new ubuntu 16.04

2016-05-05 Thread Angel L. Mateo


Hello,

I'm testing my puppet code in the new ubuntu 16.04.

	I'm using razorsedge/snmp module from the forge to manage snmpd. In 
this module, it manages snmpd service with:


  service { 'snmpd':
ensure => $service_ensure_real,
name   => $service_name,
enable => $service_enable_real,
hasstatus  => $service_hasstatus,
hasrestart => $service_hasrestart,
require=> [ Package['snmpd'], File['var-net-snmp'], ],
  }

In concrete, in my config, $service_enable_real has the value of true.

The problem I'm having is that every run shows the message:

Notice: /Stage[main]/Snmp/Service[snmpd]/enable: enable changed 'false' 
to 'true'


Running puppet in debug mode shows:

Debug: Executing '/usr/bin/dpkg-query -W --showformat '${Status} 
${Package} ${Version}\n''

Debug: Executing: '/bin/systemctl is-active snmpd'
Debug: Executing: '/bin/systemctl show snmpd --property LoadState 
--property UnitFileState --no-pager'

Debug: Executing: '/bin/systemctl unmask snmpd'
Debug: Executing: '/bin/systemctl enable snmpd'
Notice: /Stage[main]/Snmp/Service[snmpd]/enable: enable changed 'false' 
to 'true'
Debug: /Stage[main]/Snmp/Service[snmpd]: The container Class[Snmp] will 
propagate my refresh event
Debug: Class[Snmp]: The container Stage[main] will propagate my refresh 
event


	I have manually run each systemctl command and all of them returns 
error code 0. The displayed output is:


root@ubuntu-16-04:~# /bin/systemctl is-active snmpd
active
root@ubuntu-16-04:~# /bin/systemctl show snmpd --property LoadState 
--property UnitFileState --no-pager

LoadState=loaded
UnitFileState=bad
root@ubuntu-16-04:~# /bin/systemctl unmask snmpd
root@ubuntu-16-04:~# /bin/systemctl enable snmpd
snmpd.service is not a native service, redirecting to systemd-sysv-install
Executing /lib/systemd/systemd-sysv-install enable snmpd

Any help? Thank you.

--
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información
y las Comunicaciones Aplicadas (ATICA)
http://www.um.es/atica
Tfo: 868887590
Fax: 86337

--
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/572AED73.8010805%40um.es.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Update Windows server timezone using Puppet Enterprise

Re: [Puppet Users] Problem with puppetdb encoding

[Puppet Users] Why can't I see my external facts from inside a Ruby script?

Re: [Puppet Users] Error: Could not find a suitable provider for ec2_instance : puppet Enterprise 2016.1

[Puppet Users] ERROR: The puppet master service failed to start within 120 seconds; unable to proceed

[Puppet Users] Problem with snmpd service in new ubuntu 16.04

6 matches

Site Navigation

Mail list logo

Footer information