[Puppet Users] Re: external facts are not updated
Problem is resoled (and was quite silly) There was an undetected environment issue (definition of path in profile.d) To see it clearly, it is possible to restart manually the service (puppet agent is launched at service start, errors are displayed on console) Regards On Thursday, March 27, 2014 5:13:44 PM UTC+1, yannig rousseau wrote: > > Hello, > I couldn't find any traces explaining this behaviour. > What could be the difference between the process run manually and the one > run by service ?? > > Regards > > On Tuesday, March 25, 2014 5:41:12 PM UTC+1, yannig rousseau wrote: >> >> Hi all, >> >> I use external facts to collect data to our puppetmaster. >> When running the "facter" or the "puppet agent -t" command, the external >> facts are correctly collected. >> >> But as soon as I let the puppet service run, the external facts are no >> more gathered into inventory anymore >> >> I use puppet puppet-3.2.2 and facter-1.7.1 on a RHEL5.10 >> The puppetmaster is puppet-server-3.3.2 on RHEL 6.5 >> >> Does anyone have an idea ? >> >> Regards >> Yannig >> > -- 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/cf43aa4b-b4db-4a74-8169-f5e16147cbb8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] Re: external facts are not updated
Hello, I couldn't find any traces explaining this behaviour. What could be the difference between the process run manually and the one run by service ?? Regards On Tuesday, March 25, 2014 5:41:12 PM UTC+1, yannig rousseau wrote: > > Hi all, > > I use external facts to collect data to our puppetmaster. > When running the "facter" or the "puppet agent -t" command, the external > facts are correctly collected. > > But as soon as I let the puppet service run, the external facts are no > more gathered into inventory anymore > > I use puppet puppet-3.2.2 and facter-1.7.1 on a RHEL5.10 > The puppetmaster is puppet-server-3.3.2 on RHEL 6.5 > > Does anyone have an idea ? > > Regards > Yannig > -- 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/1d1856d6-8181-4e28-861d-67c83a8c0dfa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Puppet Users] external facts are not updated
Hi all, I use external facts to collect data to our puppetmaster. When running the "facter" or the "puppet agent -t" command, the external facts are correctly collected. But as soon as I let the puppet service run, the external facts are no more gathered into inventory anymore I use puppet puppet-3.2.2 and facter-1.7.1 on a RHEL5.10 The puppetmaster is puppet-server-3.3.2 on RHEL 6.5 Does anyone have an idea ? Regards Yannig -- 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/380e69ff-ca41-4e31-8545-55a66a0d961b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [Puppet Users] puppet & RHEL4
Sure and even rhel6... The trouble is that we host application for client which we cannot migrate :-( So we are stuck with a few RHEL4 we cannot upgrade On Fri, Oct 4, 2013 at 3:50 PM, Dan White wrote: > Go to RHEL 5 > Less trouble in the long run > > On Oct 4, 2013, at 9:01 AM, yannig rousseau wrote: > > Hi all, > > We are still running a few dozens of RHEL4 within our Datacenter and I'd > like to install a puppet agent to at least collect some inventory (facter) > and do a little bit of configuration management. > > The only puppet agent I managed to found for el4 is 0.22.4 (quite old) > which we installed with a facter 1.6.4 and a ruby 1.8.7.72. > At first we had issues with "requires" until we export a RUBYLIB variable > to indicate where to find all ruby libraries (/usr/lib/site_ruby/1.8/). > > Currently, there is no more error at start, but the process still do not > run ... > > Any idea ? > > Regards > > > > -- > 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. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/3gwMqrvMJ2g/unsubscribe. > To unsubscribe from this group and all its topics, 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. > -- 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] puppet & RHEL4
Hi all, We are still running a few dozens of RHEL4 within our Datacenter and I'd like to install a puppet agent to at least collect some inventory (facter) and do a little bit of configuration management. The only puppet agent I managed to found for el4 is 0.22.4 (quite old) which we installed with a facter 1.6.4 and a ruby 1.8.7.72. At first we had issues with "requires" until we export a RUBYLIB variable to indicate where to find all ruby libraries (/usr/lib/site_ruby/1.8/). Currently, there is no more error at start, but the process still do not run ... Any idea ? Regards -- 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] Puppetdb module installation error -
Hi,
I don't know if the merge is finished, but module installation seems to no
longer function :
*[root@servername]# puppet module install puppetlabs/puppetdb
Notice: Preparing to install into /etc/puppet/modules ...
Notice: Downloading from https://forge.puppetlabs.com ...
Notice: Installing -- do not interrupt ...
Error: No such file or directory -
/etc/puppet/modules/firewall/spec/fixtures/modules/firewall/manifests
Error: Try 'puppet help module install' for usage*
The file indicated does exist but is a link to another folder which do not
exist...
On Tuesday, August 27, 2013 6:35:58 PM UTC+2, Ken Barber wrote:
>
> We have a patch for this but are assessing the impact before merging.
> For now I'd just ignore the warning, it shouldn't affect operation.
>
> On Tue, Aug 27, 2013 at 9:28 AM, yannig rousseau
> > wrote:
> > Is the module puppetdb from the forge still correct ?
> > Every time I try to install puppetdb from the puppet module ("puppet
> module
> > install puppetlabs/puppetdb"), i got a warning :
> > Warning: cprice404-inifile is deprecated; please update to
> > puppetlabs-inifile
> >
> > How may i install the puppetlabs-inifile instead of cprice404 ??
> >
> > --
> > 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 post to this group, send email to
> > puppet...@googlegroups.com.
>
> > Visit this group at http://groups.google.com/group/puppet-users.
> > For more options, visit https://groups.google.com/groups/opt_out.
>
--
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] Puppetdb module installation error -
Is the module puppetdb from the forge still correct ?
Every time I try to install puppetdb from the puppet module ("puppet module
install puppetlabs/puppetdb"), i got a warning :
*Warning: cprice404-inifile is deprecated; please update to
puppetlabs-inifile*
How may i install the puppetlabs-inifile instead of cprice404 ??
--
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] Re: Decomission node process (puppet / puppetdb / dashboard)
Great ! Thank you John...
If I understand correctly, the "node:del" action will delete the node from
dashboard database, while the "reports:prune:orphaned" will delete reports
& inventory files on the server.
Does anyone see other useful actions to launch while decomissioning a node ?
Best regards
Yannig
On Fri, Jul 26, 2013 at 2:47 AM, John Warburton wrote:
> On 25 July 2013 22:54, yannig rousseau wrote:
>
>> Do you know if it's possible to lauch it from a script (maybe a sql
>> request ?)
>
>
> rake --silent node:del name=deleteme RAILS_ENV=production
>
> I also run a job each day to tidy up the database:
>
> # Purged nodes leave behind orphaned records:
> #
> http://docs.puppetlabs.com/pe/2.0/welcome_known_issues.html#consoles-reportsprune-task-leaves-orphaned-data
> # http://projects.puppetlabs.com/issues/6717
> rake --silent RAILS_ENV=production reports:prune:orphaned >> $LOG 2>&1
>
> # Recover/pack space from deletions with table optimization
> # http://dev.mysql.com/doc/refman/5.0/en/mysqlcheck.html
> DATABASE=`grep database:
> /local/puppet/dashboard/dashboard/config/database.yml | awk '{print $2}'`
> USER=`grep username: /local/puppet/dashboard/dashboard/config/database.yml
> | awk '{print $2}'`
> PASSWORD=`grep password:
> /local/puppet/dashboard/dashboard/config/database.yml | awk '{print $2}'`
> mysqlcheck -u $USER --password=$PASSWORD --optimize --databases $DATABASE
> >> $LOG 2>&1
>
>
> John
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-users/ZsjSJJWxeHk/unsubscribe.
> To unsubscribe from this group and all its topics, 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.
>
>
>
--
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] Re: Decomission node process (puppet / puppetdb / dashboard)
Do you know if it's possible to lauch it from a script (maybe a sql request ?) On Thu, Jul 25, 2013 at 2:17 PM, Klavs Klavsen wrote: > that job just removes reports for hosts - it does't remove the actual >> hosts. > > > You need to pick the node in puppet-dashboard webinterface - and choose > delete (upper right corner) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Puppet Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/puppet-users/ZsjSJJWxeHk/unsubscribe. > To unsubscribe from this group and all its topics, 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. > > > -- 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] Decomission node process (puppet / puppetdb / dashboard)
Hi all,
I have a few nodes which have deen decommissioned but still appear within
my dashboard within the ureported section. I probably have forgot something
but what ?
My puppetmaster (rhel5.9) hosts the 3 roles : puppet-server-3.2.2,
puppetdb-1.1.1, puppet-dashboard-1.2.22
The process I use to decommission :
- Clean the certificate on puppetmaster : *puppet cert clean "node.domain"*
- Delete the node itself from puppetdb : *puppet node deactivate
"node.domain"*
Concerning the dashboard, I use a pruning job in my crontab : *35 6 * * *
/etc/puppet/maintenance/puppet-dashboard.cleanup_reports.cron*
The job itself :
*set -u*
*find /var/lib/puppet/reports/*/ -mtime +7 -exec rm {} \;*
*PUPPET_DB_PATH=/usr/share/puppet-dashboard*
*cd $PUPPET_DB_PATH*
*output=`rake -s -f ${PUPPET_DB_PATH}/Rakefile RAILS_ENV=production
reports:prune upto=1 unit=wk`*
*if [ $? -ne 0 ]; then*
* logger -i "${output}"*
*fi*
*echo $output*
Regards
Yannig
--
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: Puppet agent process get stuck
I managed to kill all of the stuck process with a simple ssh loop in a script. Nevertheless, that's not very cool to proceed so... Don't you think it would be a good option to implement a timeout in the puppet agent ? If the connection / catalog application is too long (this treshold could be set with a specific argument), the puppet agent discard the action and request the puppet master again... Or is it too complicated to implement safely ? Yannig On Thursday, July 18, 2013 3:11:46 PM UTC+2, jcbollinger wrote: > > > > On Wednesday, July 17, 2013 12:00:13 PM UTC-5, yannig rousseau wrote: >> >> Hi, >> >> 3 days ago, we had a production issue where the puppetmaster became >> unreachable for 20 minute. >> All of the puppet clients which tried to connect at this time are now >> failing : "Run of Puppet configuration client already in progress; >> skipping" >> >> Further investigation show that the puppet agent process is still running >> on all of this clients 3 days later. I tried to kille the process on a >> machine, and puppet service came back to normal for this machine. >> >> Is there a way to kill the process on all of the client ? >> > > > Puppet does not provide a built-in mechanism for this. There is a variety > of tools that could do it, but you would have to had already set them up. > > > >> Is there a way to specify a timeout on the process ? This would permit to >> discard the process without human action >> > > > Again, Puppet does not provide this as a built-in feature, but it should > be possible to add external instrumentation to make it happen. That would > probably be facilitated by launching the agent periodically via a scheduler > (such as cron) instead of running it in daemon mode. > > > John > > -- 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] Puppet agent process get stuck
Hi, 3 days ago, we had a production issue where the puppetmaster became unreachable for 20 minute. All of the puppet clients which tried to connect at this time are now failing : "Run of Puppet configuration client already in progress; skipping" Further investigation show that the puppet agent process is still running on all of this clients 3 days later. I tried to kille the process on a machine, and puppet service came back to normal for this machine. Is there a way to kill the process on all of the client ? Is there a way to specify a timeout on the process ? This would permit to discard the process without human action Regards Yannig Configuration : - Puppet master => RHEL5, Puppet 3.2.2 - Puppet client => RHEL5, Puppet 3.1.1 & 3.2.2 -- 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: Certificate errors
OK, I managed to solve my issue by following Reinstalling puppetDB from source<http://docs.puppetlabs.com/puppetdb/latest/install_from_source.html#step-3-option-b-manually-create-a-keystore-and-truststore>(Step 3 Option B) even if /usr/sbin/puppetdb-ssl-setup (option A) did state that the configuration was okay. Regards On Wednesday, July 3, 2013 5:54:49 PM UTC+2, yannig rousseau wrote: > > Hi all, > > I launched a Puppet service a few month ago and it did function pretty > well for some time. > > Last week, I tried to clean old entries but I think I deleted too much > information as I can no more synchronize my clients. > I get a certificate error : > > *[root@REBITPUPPET01 ~]# puppet agent --test > Warning: Unable to fetch my node definition, but the agent run will > continue: > Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server > certificate B: certificate verify failed: [certificate signature failure > for /CN=rebitpuppet01.cegedim] > Info: Retrieving plugin > Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources > using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read > server certificate B: certificate verify failed: [certificate signature > failure for /CN=rebitpuppet01.cegedim] > Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect > returned=1 errno=0 state=SSLv3 read server certificate B: certificate > verify failed: [certificate signature failure for > /CN=rebitpuppet01.cegedim] Could not retrieve file metadata for > puppet://rebitpuppet01.cegedim/plugins: SSL_connect returned=1 errno=0 > state=SSLv3 read server certificate B: certificate verify failed: > [certificate signature failure for /CN=rebitpuppet01.cegedim]* > > I tried a lot of things following the different threads but I only managed > to mess a little bit more with my server :-( > At least, I know my truststore should be wrong as "*keytool -list > -keystore /etc/puppetdb/ssl/truststore*" and "*openssl x509 -noout -in > /var/lib/puppet/ssl/ca/ca_crt.pem -fingerprint*" do not match. The only > thing is that I do not have the first idea on how to solve this... > > Any idea ? > > Puppetmaster, dashboard & puppedb are on the same server (Distro = RHEL5.9) > I get the same error even on the puppetmaster server. > > > Regards > > > -- 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] Certificate errors
Hi all, I launched a Puppet service a few month ago and it did function pretty well for some time. Last week, I tried to clean old entries but I think I deleted too much information as I can no more synchronize my clients. I get a certificate error : *[root@REBITPUPPET01 ~]# puppet agent --test Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=rebitpuppet01.cegedim] Info: Retrieving plugin Error: /File[/var/lib/puppet/lib]: Failed to generate additional resources using 'eval_generate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=rebitpuppet01.cegedim] Error: /File[/var/lib/puppet/lib]: Could not evaluate: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=rebitpuppet01.cegedim] Could not retrieve file metadata for puppet://rebitpuppet01.cegedim/plugins: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [certificate signature failure for /CN=rebitpuppet01.cegedim]* I tried a lot of things following the different threads but I only managed to mess a little bit more with my server :-( At least, I know my truststore should be wrong as "*keytool -list -keystore /etc/puppetdb/ssl/truststore*" and "*openssl x509 -noout -in /var/lib/puppet/ssl/ca/ca_crt.pem -fingerprint*" do not match. The only thing is that I do not have the first idea on how to solve this... Any idea ? Puppetmaster, dashboard & puppedb are on the same server (Distro = RHEL5.9) I get the same error even on the puppetmaster server. Regards -- 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.
