[Puppet Users] Re: Help on Hiera automate
Thanks Jc,
i did what you said..i have changed .yaml like this:
servers:
s10:
sn: de3de
project: b
user: b
dbname: de
dbuser: e
dbpwd: de
s16:
sn: de3dedede
project: b
user: a
dbname: de
dbuser: e
dbpwd: d
...
and obtain params like this hiera('servers') and use create_resources
function
Il giorno martedì 14 gennaio 2014 02:02:29 UTC+1, alessandro mazzoli ha
scritto:
Hi all,
I'm trying to automate the set up of the machines staging,passing by an
php application ServerName , ProjectType,DbCredentials etc..(all strings)
and convert to yaml
Here's my common.yaml:
---
users:
-sn: server.example.com
-project : Symfony
-dbname : test
-dbuser : test
-dbpwd : test
-sn: server2.example.com
-project : Idephix
-dbname : test
-dbuser : test
-dbpwd : test
Here's my hiera.yaml
---
:backends:
-yaml
:yaml:
:datadir: '/etc/puppet/hieradata'
:hierarchy:
-common
Is there any possibility on manifest to get all those variables by not
specifing the index as below ??
$users=hiera('users')
$sn0=$users[*0*]['sn']
$sn1=
..
...
I would like to preserve all the configurations if possible inside
common.yaml
Thanks for the help
--
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/e0c04a5b-d0b0-4432-98fe-e916737c610d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Help on Hiera automate
Yes, i can get the whole string but if i need the parameters inside that
string as sn, project,dbname etc...
example:
file{/var/sites/$sn:
ensure=directory,
mode=0755,
owner=$user,
group=$user,
require=File[/var/sites],
}
Il giorno martedì 14 gennaio 2014 04:11:33 UTC+1, CD ha scritto:
Hi Alessandro,
I think if you specify $users it has all the content of children but in a
single string. Don't know whether this is what you need.
try:
$users=hiera('users')
notify { $users: }
Regards,
CD
On Tuesday, January 14, 2014 11:02:29 AM UTC+10, alessandro mazzoli wrote:
Hi all,
I'm trying to automate the set up of the machines staging,passing by an
php application ServerName , ProjectType,DbCredentials etc..(all strings)
and convert to yaml
Here's my common.yaml:
---
users:
-sn: server.example.com
-project : Symfony
-dbname : test
-dbuser : test
-dbpwd : test
-sn: server2.example.com
-project : Idephix
-dbname : test
-dbuser : test
-dbpwd : test
Here's my hiera.yaml
---
:backends:
-yaml
:yaml:
:datadir: '/etc/puppet/hieradata'
:hierarchy:
-common
Is there any possibility on manifest to get all those variables by not
specifing the index as below ??
$users=hiera('users')
$sn0=$users[*0*]['sn']
$sn1=
..
...
I would like to preserve all the configurations if possible inside
common.yaml
Thanks for the help
--
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/25cf147a-9eee-4e84-a0fe-aca034c44002%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Help on Hiera automate
Hi all,
I'm trying to automate the set up of the machines staging,passing by an php
application ServerName , ProjectType,DbCredentials etc..(all strings) and
convert to yaml
Here's my common.yaml:
---
users:
-sn: server.example.com
-project : Symfony
-dbname : test
-dbuser : test
-dbpwd : test
-sn: server2.example.com
-project : Idephix
-dbname : test
-dbuser : test
-dbpwd : test
Here's my hiera.yaml
---
:backends:
-yaml
:yaml:
:datadir: '/etc/puppet/hieradata'
:hierarchy:
-common
Is there any possibility on manifest to get all those variables by not
specifing the index as below ??
$users=hiera('users')
$sn0=$users[*0*]['sn']
$sn1=
..
...
I would like to preserve all the configurations if possible inside
common.yaml
Thanks for the help
--
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/eb286c5d-07d6-412b-9a2c-202bb49b8140%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Optimize PuppetDashboard fail
Hi all, i can't optimize Puppet Dashboard /opt/puppet/share/puppet-dashboard# sudo -u puppet-dashboard rake RAILS_ENV=production db:raw:optimize Warning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Any suggestion? -- 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/d5335cb6-7ebd-418b-9d67-1d8b80f18e37%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Optimize PuppetDashboard fail
Hi All, sry for that empty post, my bad.. i'm trying to optimize Puppet Dashboard but i get this: /opt/puppet/share/puppet-dashboard# sudo -u puppet-dashboard rake RAILS_ENV=production db:raw:optimize Warning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Don't know how to build task 'db:raw:optimize' (See full trace by running task with --trace) with --trace ; sudo -u puppet-dashboard rake RAILS_ENV=production db:raw:optimize --traceWarning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Don't know how to build task 'db:raw:optimize' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/task_manager.rb:49:in `[]' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:148:in `invoke_task' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `each' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:115:in `run_with_threads' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:100:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:78:in `run' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:165:in `standard_exception_handling' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:75:in `run' /var/lib/gems/1.8/gems/rake-10.1.0/bin/rake:33 /usr/local/bin/rake:19:in `load' /usr/local/bin/rake:19 -- 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/436323b5-8c43-4e36-be89-7f7f70d57e1f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Optimize PuppetDashboard fail
ruby -v 1.8.7 rails -v Rails 2.3.14 rake -v Warning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Don't know how to build task 'default' Il giorno giovedì 14 novembre 2013 12:07:41 UTC+1, alessandro mazzoli ha scritto: Hi All, sry for that empty post, my bad.. i'm trying to optimize Puppet Dashboard but i get this: /opt/puppet/share/puppet-dashboard# sudo -u puppet-dashboard rake RAILS_ENV=production db:raw:optimize Warning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Don't know how to build task 'db:raw:optimize' (See full trace by running task with --trace) with --trace ; sudo -u puppet-dashboard rake RAILS_ENV=production db:raw:optimize --traceWarning: Rails rake tasks currently unavailable because we can't find the 'rails' gem Could not load rdoc/task. Some rake tasks may not be available without rdoc/task. The load error generated the following message: no such file to load -- rdoc/task rake aborted! Don't know how to build task 'db:raw:optimize' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/task_manager.rb:49:in `[]' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:148:in `invoke_task' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `each' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:106:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:115:in `run_with_threads' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:100:in `top_level' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:78:in `run' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:165:in `standard_exception_handling' /var/lib/gems/1.8/gems/rake-10.1.0/lib/rake/application.rb:75:in `run' /var/lib/gems/1.8/gems/rake-10.1.0/bin/rake:33 /usr/local/bin/rake:19:in `load' /usr/local/bin/rake:19 -- 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/9d1c4d23-4a19-499a-a37d-230d1dd9d795%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
FIXED : https://groups.google.com/forum/#!topic/mcollective-users/JBO2BcL8SGA Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto: Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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/449277b8-3692-4924-b733-e60953f665af%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[Puppet Users] Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Here's the log: I, [2013-10-28T16:30:07.990102 #1332] INFO -- : activemq.rb:121:in `on_ssl_connecting' Estblishing SSL session with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:07.990465 #1332] INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 11 to stomp+ssl://mcollective@sisop-virtualbox:61613 E, [2013-10-28T16:30:07.996130 #1332] ERROR -- : activemq.rb:131:in `on_ssl_connectfail' SSL session creation with stomp+ssl://mcollective@sisop-virtualbox:61613 failed: Co$ I, [2013-10-28T16:30:07.996368 #1332] INFO -- : activemq.rb:111:in `on_connectfail' TCP Connection to stomp+ssl://mcollective@sisop-virtualbox:61613 failed on attempt 11 I, [2013-10-28T16:30:28.483057 #1332] INFO -- : activemq.rb:121:in `on_ssl_connecting' Estblishing SSL session with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:28.483657 #1332] INFO -- : activemq.rb:96:in `on_connecting' TCP Connection attempt 12 to stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:29.645117 #1332] INFO -- : activemq.rb:126:in `on_ssl_connected' SSL session established with stomp+ssl://mcollective@sisop-virtualbox:61613 I, [2013-10-28T16:30:29.839742 #1332] INFO -- : activemq.rb:101:in `on_connected' Conncted to stomp+ssl://mcollective@sisop-virtualbox:61613 Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto: Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
fix 1: i syncronized the clocks Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto: Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto: Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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] Re: Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init
issue still exists Il giorno lunedì 28 ottobre 2013 17:31:40 UTC+1, alessandro mazzoli ha scritto: fix 1: i syncronized the clocks Il giorno lunedì 28 ottobre 2013 17:11:27 UTC+1, alessandro mazzoli ha scritto: Hi all, i'm stucked with an error on PE-Mcollective. I have a puppetmaster with PE-Console on it, i have an agent node connected which i want provide to it a module called LAMP, my newbie LAMP module https://github.com/alemazz/lamp.git When i run puppet agent -t on the puppetmaster i dont get any error, and the module will install on it, but when i call puppet agent -t on node agent i get this error: Debug: /Schedule[weekly]: Skipping device resources because running on a host Debug: /Schedule[puppet]: Skipping device resources because running on a host *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective.conf in /etc/init.d* *Debug: Service[pe-mcollective](provider=upstart): Could not find pe-mcollective in /etc/init* Debug: Executing '/etc/init.d/pe-mcollective status' Debug: Executing '/etc/init.d/pe-mcollective start' Notice: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]/ensure: ensure changed 'stopped' to 'running' Debug: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: The container Class[Pe_mcollective::Server] will propagate my refresh event Info: /Stage[main]/Pe_mcollective::Server/Service[pe-mcollective]: Unscheduling refresh on Service[pe-mcollective] Debug: Class[Pe_mcollective::Server]: The container Stage[main] will propagate my refresh event Debug: Executing '/usr/bin/apt-cache policy php5-dev' Debug: Class[Lamp]: The container Stage[main] will propagate my refresh event Debug: Finishing transaction 87463220 Debug: Storing state Debug: Stored state in 0.05 seconds Notice: Finished catalog run in 15.14 seconds Debug: report supports formats: b64_zlib_yaml pson raw yaml; using pson Stderr from the command: stdin: is not a tty Error: /Stage[main]/Lamp/Service[apache2]: Could not evaluate: Execution of '/sbin/status apache2' returned 1: status: Unknown job: apache2 Here's my /etc/init.d on puppetmaster and on agent node -rwxr-xr.x root root pe-mcollective service pe-mcollective statusrunning but on /etc/init i dont have pe-mcollective or pe-mcollective.conf, i dont have any .conf on /etc/init.dis a bug on pe-installer that pe-mcollective service is on /etc/init.d and not on /etc/init? -- 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] Re: Installing ActiveRecord fails
Try this, it helped me: http://help.rubygems.org/discussions/problems/637-rails-installation-fails Il giorno mercoledì 9 ottobre 2013 04:56:06 UTC+2, ytmp123 ha scritto: Hello guys, When I try to execute this: gem install activerecord Then I get the error message: Error installing activerecord. ERROR: Failed to build gem native extension I'm using: Ubuntu 12.10 Ruby 1.9.3p194 Puppet 2.7.18 Can you give me some hint how to solve this problem? -- 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.
Re: [Puppet Users] Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Thanks Jason and Jared, I think, like Jared said, that the user trying to create the tempfile cannot write to it (this user may well be puppet, not root. So i checked on puppetmaster: -permissions:/etc/init.d ls -la -rwsr-xr-x 1 root root 3727 Sep 12 22:57 puppetmaster /var/lib/puppet/yaml$ ls -la total 16 drwxr-xr-x 4 puppet puppet 4096 Sep 27 13:06 . drwxrwxrwx 15 puppet puppet 4096 Sep 27 17:59 .. drwxr-xr-x 2 root root 4096 Oct 9 15:33 facts I also checked for disk full and inodes too. Il giorno mercoledì 9 ottobre 2013 21:52:27 UTC+2, Jared Jennings ha scritto: err: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9' warning: Not using cache on failed catalog err: Could not retrieve catalog; skipping run Security Problem?Suggestion? “Error 400 on SERVER” means that the problem outlined in the next words happened on the server, not the client. The details of the problem are after “Error 400:” there are dozens of things that can cause an error 400. In this case, a tempfile could not be written. Perhaps the directory /var/lib/puppet/yaml/facts does not exist; perhaps the user trying to create the tempfile cannot write to it (this user may well be puppet, not root, even if you ran the server as root); or perhaps the disk is full. That’s where to start; where you will end up I don’t know. -- 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] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Thx so much John as you explained was a permission problem:
as you explained i fixed like this:
On pupputmaster :
service puppetmaster stop
chown puppet:puppet /etc/init.d/puppetmaster
rm -r /var/lib/puppet/yaml/facts
chown puppet:puppet /var/lib/puppet/yaml/node/hostname and puppetmaster
name, before has root permission(my bad)
service puppetmaster restart
I also checked that facts has been created with puppet permission
Il giorno mercoledì 9 ottobre 2013 17:16:20 UTC+2, alessandro mazzoli ha
scritto:
Hi,
i'm a newbie about Puppet( 1 month ~)
i got error on generate temp file, i'll explain my situation:
-i have a puppetmaster(version: 3.3.0),executed on root
and a puppet agent(version 2.7) provisioning by vagrant,executed on root
-my site.pp, where webserv is a parametrized class, and typews is a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring
File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: Finishing
[Puppet Users] Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Hi,
i'm a newbie about Puppet( 1 month ~)
i got error on generate temp file, i'll explain my situation:
-i have a puppetmaster(version: 3.3.0),executed on root
and a puppet agent(version 2.7) provisioning by vagrant,executed on root
-my site.pp, where webserv is a parametrized class, and typews is a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: Finishing transaction -615437368
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Finishing transaction -615696088
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using pson
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Using cached certificate_revocation_list for ca
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
cannot generate tempfile
[Puppet Users] Re: Could not retrieve catalog from remote server: Error 400 on SERVER: cannot generate tempfile `/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie5i-9'
Il giorno mercoledì 9 ottobre 2013 17:16:20 UTC+2, alessandro mazzoli ha
scritto:
Hi,
i'm a newbie about Puppet( 1 month ~)
i got error on generate temp file, i'll explain my situation:
-i have a puppetmaster(version: 3.3.0),executed on root
and a puppet agent(version 2.7) provisioning by vagrant,executed on root
-my site.pp, where webserv is a parametrized class, and typews is a
parameter to choice nginx or lamp module,
-i have my Enc node with path /var/lib/puppet/yaml/facts/ on my
puppetmaster
-Selinux disabled
node 'vagrant1.localdomain'{
include webserv
class{ 'webserv':
typews=[nginx],
}
}
puppet agent -t --debug
debug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not
exist
debug: Puppet::Type::User::ProviderPw: file pw does not exist
debug: Puppet::Type::User::ProviderLdap: true value when expecting false
debug: Puppet::Type::User::ProviderDirectoryservice: file /usr/bin/dscl
does not exist
debug: Failed to load library 'selinux' for feature 'selinux'
debug: Failed to load library 'ldap' for feature 'ldap'
debug: /File[/var/lib/puppet/clientbucket]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/state/graphs]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/state/resources.txt]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/client_yaml]: Autorequiring
File[/var/lib/puppet]
debug: /File[/etc/puppet/puppet.conf]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_report.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state/state.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/state/last_run_summary.yaml]: Autorequiring
File[/var/lib/puppet/state]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/client_data]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/var/lib/puppet/classes.txt]: Autorequiring
File[/var/lib/puppet]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/var/run/puppet/agent.pid]: Autorequiring
File[/var/run/puppet]
debug: Finishing transaction -614883798
debug: /File[/etc/puppet/ssl/private_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/private_keys]
debug: /File[/var/lib/puppet/lib]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certs/ca.pem]: Autorequiring
File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/certs/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/certs]
debug: /File[/etc/puppet/ssl/crl.pem]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/var/lib/puppet/state]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/public_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/private_keys]: Autorequiring
File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/certs]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl/public_keys/vagrant1.localdomain.pem]:
Autorequiring File[/etc/puppet/ssl/public_keys]
debug: /File[/etc/puppet/ssl/private]: Autorequiring File[/etc/puppet/ssl]
debug: /File[/etc/puppet/ssl]: Autorequiring File[/etc/puppet]
debug: /File[/var/lib/puppet/facts]: Autorequiring File[/var/lib/puppet]
debug: /File[/etc/puppet/ssl/certificate_requests]: Autorequiring
File[/etc/puppet/ssl]
debug: Finishing transaction -615437368
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Finishing transaction -615696088
debug: Loaded state in 0.00 seconds
debug: Executing '/etc/puppet/etckeeper-commit-pre'
debug: catalog supports formats: b64_zlib_yaml dot pson raw yaml; using
pson
debug: Using cached certificate for ca
debug: Using cached certificate for vagrant1.localdomain
debug: Using
