Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Anton Fomenko updated an issue Puppet / PUP-9395 provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Change By: Anton Fomenko Comment: [~josh], well yes, but that's an issue and I couldn't find any related bug/task in SERVER project. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290248.1546531587000.107462.1609832760079%40Atlassian.JIRA.
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Anton Fomenko commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Josh Cooper, well yes, but that's an issue and I couldn't find any related bug/task in SERVER project. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290248.1546531587000.107459.1609832700040%40Atlassian.JIRA.
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Anton Fomenko commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 Josh Cooper, well yes, but that's an issue and I couldn't find any related bug/task in SERVER project. Add Comment This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.290248.1546531587000.107460.1609832700059%40Atlassian.JIRA.
Jira (PUP-9395) provider gem in package type doesn't work anymore when rubygems is >= 3.0.0
Title: Message Title Anton Fomenko commented on PUP-9395 Re: provider gem in package type doesn't work anymore when rubygems is >= 3.0.0 # puppetserver gem install --no-rdoc yaml WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by org.jruby.ext.openssl.SecurityHelper (file:/tmp/jruby-8145/jruby10086072876742673271jopenssl.jar) to field java.security.MessageDigest.provider WARNING: Please consider reporting this to the maintainers of org.jruby.ext.openssl.SecurityHelper WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release ERROR: While executing gem ... (OptionParser::InvalidOption) invalid option: --no-rdoc # puppetserver --version puppetserver version: 6.14.0
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title Anton Fomenko commented on PUP-8949 Re: Package pip provide won't work with ensure latest and custom index Nothing changed. Debug: Prefetching pip resources for package Debug: Executing '/usr/bin/pip --version' Debug: Executing '/usr/bin/pip freeze --all' Debug: Executing '/usr/bin/pip --version' Debug: Executing '/usr/bin/pip freeze --all' Debug: Executing: '/usr/bin/pip install -q --index=https://pip.example.com --upgrade pkg' Notice: /Stage[main]/Main/Node[node]/Package[pkg_2]/ensure: created (corrective) Debug: /Package[pkg_2]: The container Node[node] will propagate my refresh event Debug: Prefetching pip3 resources for package Debug: Executing '/usr/bin/pip3 --version' Debug: Executing '/usr/bin/pip3 freeze --all' Debug: Executing '/usr/bin/pip3 --version'
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title Anton Fomenko commented on PUP-8949 Re: Package pip provide won't work with ensure latest and custom index Josh Cooper, up Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.261544.1529423125000.26733.1563884040201%40Atlassian.JIRA.
Jira (PUP-2089) Error messages did not store in last_run_summary.yaml when config failed.
Title: Message Title Anton Fomenko commented on PUP-2089 Re: Error messages did not store in last_run_summary.yaml when config failed. Any chances of this being fixed. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Anton Fomenko commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero Contents of file os being changed as well as file timestamp ofc. Before # cat /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml --- version: config: puppet: 5.5.6 resources: changed: 0 corrective_change: 0 failed: 0 failed_to_restart: 0 out_of_sync: 0 restarted: 0 scheduled: 0 skipped: 0
Jira (PUP-3557) Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero
Title: Message Title Anton Fomenko commented on PUP-3557 Re: Duplicate Resource error generates last_run_summary.yaml with resource failure count of zero I have similar issue: after unsuccessful puppet run there is no data on errors in last_run_summary.yaml # puppet agent -t Info: Using configured environment 'production' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Method call, Class[myclass]: expects a value for parameter 'param' (file: /etc/puppetlabs/code/environments/production/modules/mod/manifests/import.pp, line: 11, column: 73) on node mynode Warning: Not using cache on failed catalog Error: Could not retrieve catalog; skipping run [root@mynode ~]# cat /opt/puppetlabs/puppet/cache/state/last_run_summary.yaml --- version:
Jira (PUP-2621) ssh_authorized_keys should not use the key 'comment' as a unique identifier (name)
Title: Message Title Anton Fomenko commented on PUP-2621 Re: ssh_authorized_keys should not use the key 'comment' as a unique identifier (name) I believe that there is security issue behind this bug. For example we put several users keys to root user. One of them wants to hide some activity or keep access after dismissal or anything else. He copies his key with other key comment, eg Was ssh-rsa a-key a-user@company ssh-rsa b-key b-user@company Now ssh-rsa a-key a-user@company ssh-rsa b-key b-user@company ssh-rsa a-key b-user@company Puppet will not purge extra key and so user will remain ability to login. Add Comment
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title Anton Fomenko updated an issue Puppet / PUP-8949 Package pip provide won't work with ensure latest and custom index Change By: Anton Fomenko Affects Version/s: PUP 5.5.1 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8949) Package pip provide won't work with ensure latest and custom index
Title: Message Title
Anton Fomenko created an issue
Puppet / PUP-8949
Package pip provide won't work with ensure latest and custom index
Issue Type:
Bug
Assignee:
Unassigned
Created:
2018/06/19 8:45 AM
Priority:
Normal
Reporter:
Anton Fomenko
Puppet agent will run every time if you have ensure => latest and custom index, for example
package { 'mypippackage':
ensure => latest,
provider=> 'pip',
install_options => { '--index' => 'https://pip.example.com' },
}
I believe the issue is happening because puppet doesn't test package version against additional index (doesn;t use --index), while using --index on install.
Jira (PUP-6191) Puppet Master successfully compiled catalog on syntax error
Title: Message Title Anton Fomenko commented on PUP-6191 Re: Puppet Master successfully compiled catalog on syntax error I'm not. I will just after we manage to upgrade. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-627) Boolean facts not printed with facter -p if fact value is false
Title: Message Title Anton Fomenko commented on FACT-627 Re: Boolean facts not printed with facter -p if fact value is false Reproducible on 2.4 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6191) Puppet Master successfully compiled catalog on syntax error
Title: Message Title
Anton Fomenko updated an issue
Puppet / PUP-6191
Puppet Master successfully compiled catalog on syntax error
Change By:
Anton Fomenko
Hi.We run open source puppet v.3.8.4 with Passenger + Apache on CentOS7Recently a mistake was made during git merge in our puppet manifests repo, and after this the following string was left in one of manifests between two nodes declarations (in top scope):{code}<<< HEAD{code}After that puppet failed for only one time with the following error:{code}Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Syntax error at '<<' at /etc/puppet/environments/production/manifests/clusters/fr2.pp:4496 on node am3-mgmt-1Warning: Not using cache on failed catalog{code}and all subsequent puppet runs were successful with *empty* catalog.We have environment_timeout set to unlimited in puppet.conf and using restart.txt to reload passenger workers. With environment_timeout = 0 this issue is not reproducible. Reproducible on 3.8.6
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6191) Puppet Master successfully compiled catalog on syntax error
Title: Message Title Anton Fomenko created an issue Puppet / PUP-6191 Puppet Master successfully compiled catalog on syntax error Issue Type: Bug Assignee: Unassigned Created: 2016/04/20 2:10 PM Priority: Normal Reporter: Anton Fomenko Hi. We run open source puppet v.3.8.4 with Passenger + Apache on CentOS7 Recently a mistake was made during git merge in our puppet manifests repo, and after this the following string was left in one of manifests between two nodes declarations (in top scope): <<< HEAD After that puppet failed for only one time with the following error: Error: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not parse for environment production: Syntax error at '<<' at /etc/puppet/environments/production/manifests/clusters/fr2.pp:4496 on node am3-mgmt-1
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage For now all issues were solved, so you can close the ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count 149449 (1 row) Installed Packages Name: puppetdb Arch: noarch Version : 2.3.5
Jira (FACT-1019) Problem overriding system fact (last_run)
Title: Message Title Anton Fomenko created an issue Facter / FACT-1019 Problem overriding system fact (last_run) Issue Type: Bug Affects Versions: FACT 2.4.3 Assignee: Unassigned Created: 2015/05/27 12:26 AM Priority: Normal Reporter: Anton Fomenko In PDB-1124 I was advised to override last_run builtin fact to add nanoseconds. But it seems like it doesn't work on CentOS7 (Ruby 2.0), but ok CentOS5 (Ruby 1.8.7): I have correct new fact in /etc/puppet/modules/my/lib/facter/last_run.rb I have default last_run fact in /var/lib/puppet/lib/facter/last_run.rb On CentOS 7 if I replace 2nd with 1st, during puppet run it get reverted back. On CentOS 5 1st = 2nd and all works as intended. Fact code: Facter.add(last_run) do has_weight 100
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, we have setup two more puppet master on CentOS7 and Ruby 2.0 and have issue with fact repeated on them. Also we registered fact count raise in PuppetDB from ~50 to: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count --- 3617 (1 row) I created ticket https://tickets.puppetlabs.com/browse/FACT-1019 about facter issue. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hello, Wyatt Alt. Any updates? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Installed Packages Name: facter Arch: x86_64 Epoch : 1 Version : 2.4.3 Release : 1.el7 Size: 273 k [root@ed-mgmt-2 ~]# facter -p last_run Tue Apr 28 08:03:18 UTC 2015
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count --- 47146 (1 row) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, I\m putting the following code in my module lib/facter/last_run.rb require 'facter' Facter.add(last_run) do has_weight 100 confine :kernel = [ 'Linux' , 'SunOS' , 'FreeBSD' , 'Darwin' ] setcode do Facter::Util::Resolution.exec(date '+%a %b %d %T:%N %Z %Y') end end And no result: [root@srv puppet]# cfacter --custom-dir modules/my/lib/facter/ | grep last
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, we running 2.3.2. In common it raises but sometimes it falling. Current value is: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count 122622 (1 row) [root@eu6-mgmt-2 ~]# facter -p last_run Thu Apr 16 07:50:54 UTC 2015 [root@eu6-mgmt-2 ~]# facter -p last_run Thu Apr 16 07:51:05 UTC 2015
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: ScreenShot2015-04-16at10.50.00.png Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Also we have messages like this in puppetdb.log: 2015-04-16 10:32:09,634 ERROR [c.p.p.command] [eb62c0fb-d2dc-41cb-8738-55b9270c7d18] [replace facts] Retrying after attempt 9, due to: java.sql.BatchUpdateException: Batch entry 0 DELETE FROM fact_values fv WHERE fv.id in (72,105271,87092921,343,13,28146635,13,86208955,87092925,53183,264,36,225,105244,87092925,53191,105244,312,29112200,105043,87092921,5,53190,38227884,452,225,111,236,87092923,19,21424983,111,13,236,1049,19,44300,264,87092924,8,53175,608,67265556,111,4060,22067637,27126,104967,28146635,104894,105184,105244,105043,53181,104930,53176,87092922,13,53185,264,53170,111,757) AND NOT EXISTS (SELECT 1 FROM facts f WHERE f.fact_value_id in (72,105271,87092921,343,13,28146635,13,86208955,87092925,53183,264,36,225,105244,87092925,53191,105244,312,29112200,105043,87092921,5,53190,38227884,452,225,111,236,87092923,19,21424983,111,13,236,1049,19,44300,264,87092924,8,53175,608,67265556,111,4060,22067637,27126,104967,28146635,104894,105184,105244,105043,53181,104930,53176,87092922,13,53185,264,53170,111,757) AND f.fact_value_id = fv.id AND (f.factset_id, f.fact_path_id) NOT in
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, this number is keep growing though: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count 117227 (1 row) I fear it could end up with the same issue. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hi, Wyatt Alt. We managed to upgrade only to 2.3.0, but not to 2.3.1. We got the following error message: 2015-04-01 09:53:23,167 INFO [c.p.p.c.services] PuppetDB version 2.3.1 2015-04-01 09:53:23,418 INFO [c.p.p.s.migrate] Applying database migration version 28 2015-04-01 09:53:27,443 ERROR [c.p.p.s.migrate] Caught SQLException during migration java.sql.BatchUpdateException: Batch entry 5 DELETE FROM fact_paths t1 WHERE t1.id (SELECT MIN(t2.id) FROM fact_paths t2 WHERE t1.path = t2.path) was aborted. Call getNextException to see the cause. at org.postgresql.jdbc2.AbstractJdbc2Statement$BatchResultHandler.handleError(AbstractJdbc2Statement.java:2746) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl$1.handleError(QueryExecutorImpl.java:457) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1887) ~[puppetdb.jar:na]
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hello, Wyatt Alt. We already raised the limit. What we seeing is: du -sh /var/lib/puppetdb/mq/localhost/* 4.2M /var/lib/puppetdb/mq/localhost/KahaDB 33G /var/lib/puppetdb/mq/localhost/scheduler while [command-processing] store-usage = 10240 temp-usage = 5120 and exceptions like this: 2015-02-22 05:44:29,330 WARN [o.a.a.b.T.Service] Async error occurred: java.lang.IllegalStateException: PageFile is not loaded
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, we continue to suffer from one more issue. Two of our slaves begin to hang from time to time. Following issues can be found in puppetdb.log: 2015-02-19 10:33:00,701 WARN [o.e.j.s.ServerConnector] java.io.IOException: Too many open files at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method) ~[na:1.7.0_51] at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241) ~[na:1.7.0_51] at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:336) ~[puppetdb.jar:na] at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:466) ~[puppetdb.jar:na] at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:607) [puppetdb.jar:na] at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:536) [puppetdb.jar:na] at java.lang.Thread.run(Thread.java:744) [na:1.7.0_51]
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hello, Wyatt Alt. i sent you a message with download link to our exported PuppetDB. We faced this issue one more time and resolved it same way. Also ew had issues on one of our slave with PuppetDB becoming unavailable with tons of java exceptions in puppetdb.log. Restarting PuppetDB helped but not for long. For now we completely erased our mq folder and waiting if any issues will repeat. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1295) Yum provider purge target runs irrespective of package installation status
Title: Message Title Anton Fomenko commented on PUP-1295 Re: Yum provider purge target runs irrespective of package installation status Same on puppet 3.7.3 on centos 5, 6 and 7. Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt db size is 4GB it is fully cached in ram, so disk io is not an issue according to explain DELETE FROM fact_paths fp WHERE fp.id in ( SELECT fp.id FROM fact_paths fp inner join fact_values fv on fp.id = fv.path_id inner join facts f on fv.id = f.fact_value_id WHERE fp.id in ( select fv.path_id from fact_values fv where fv.id in (30877695,30877691,30877694,30877692,30877674) ) GROUP BY fp.id HAVING COUNT(fv.id) = 1)
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, all requested files: https://www.dropbox.com/s/wc06a8f1b16m7m2/pgsql.log.tar.gz?dl=0 https://www.dropbox.com/s/q3jqxe9qsjiv6af/puppetdb.log.tar.gz?dl=0 https://www.dropbox.com/s/u87pdn26jt27hon/puppetdb.conf.d.tar.gz?dl=0 https://www.dropbox.com/s/4g6ywzh9x91ood5/postgresql.conf?dl=0 Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage When we tried to solve this issue last time we fully removed KahaDB and scheduler directories (i think it was 19.01) and now we have no discarded directories at all (there was no of them as well). Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, thanks for your response. We already ran these requests and have responce only from the first one. puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count --- 42765 (1 row) puppetdb=# select count(*) from fact_paths where id not in (select path_id from fact_values); count --- 0
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, any news? puppetdb=# select path_id, fact_paths.name, count(*) cnt from fact_values join fact_paths on path_id=fact_paths.id group by path_id, fact_paths.name order by cnt desc limit 20; path_id | name | cnt -+--+--- 28 | last_run | 42973 117 | clientcert | 4528 4 | fqdn | 4523 7 | hostname | 4517 74 | memoryfree_mb| 4513 47 | uptime_seconds | 4250 82 | ipaddress| 4186
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Hi Wyatt. Pleased to hear a reply. Will try to answer your questions: 1. We finished upgrading to recent puppet, puppetdb and puppet-server version in a middle of December 14 and ran into the first issue with puppet on 10th of January 15. This was the most recent software change. 2. There were no such issues for a long time. 3. It happened on 10th Jan 15 and repeated yesterday several times ( 4 I guess ). First time deleting KahaDB directory helped, but today i had no effect. 4. Catalog and facts 5. Attached screenshot from PuppetDB dashboard 6. 8 Puppet Masters with PuppetDB and PostgreSQL installed. On of them is master and other are slaves in hot-standby streaming replication. PuppetDB on slaves configured with to read from local DB and write to master. Master PuppetDB server (the one with issues) have 32 Cores and 384Gb RAM. 32Gb configured for PostgreSQL shared buffers. 7. Attached. For now the situation returned to normal after executing: delete from fact_values where id not in (select distinct fact_value_id from facts); It deleted more than 300k rows. But now: puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts) ; count --- 11325 (1 row)
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: ScreenShot2015-01-20at22.52.14.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: master.puppetdb.log.strip.tar.gz Attachment: 8_2.slave.puppetdb.log.strip.tar.gz Attachment: 8_1.slave.puppetdb.log.strip.tar.gz Attachment: 7.slave.puppetdb.log.strip.tar.gz Attachment: 6.slave.puppetdb.log.strip.tar.gz Attachment: 4.slave.puppetdb.log.strip.tar.gz Attachment: 3.slave.puppetdb.log.strip.tar.gz Attachment: 2.slave.puppetdb.log.strip.tar.gz Attachment: 1.slave.puppetdb.log.strip.tar.gz
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Affects Version/s: PDB2.2.2 Labels: puppetdb Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title
Anton Fomenko updated an issue
PuppetDB / PDB-1124
PuppetDB high CPU usage
Change By:
Anton Fomenko
Greetings,WefacedintoissueswithPuppetDBPostgreSQLprocessesusingallcoresonourPuppetMasterserver(LA=100with32cores).Thisserverhavefollowingcomponentsinstalled:1.puppet-server3.7.3(httpdwithpassenger)2.PuppetDB2.2.2withPostgreSQL9.3Thisismasterseverfrommaster-slavePostgreSQLreplicationsetupusingPuppetDBdatabaseandread-databasesettings.Issueswassolvedbyfollowingthisinstruction:https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.htmlonallPuppetDBnodesandrepeatedonemoretimeinapproximatelyaweek.topwasshowingalotofDELETEPostgreSQLqueries.FollowingquerieswereinblockedstateinPostgreSQL:{noformat}-[RECORD1]--+blocked_pid|17367blocked_user|puppetdbblocking_pid|14736blocking_user|puppetdbblocked_statement|UPDATEcertnamesSETdeactivated=$1WHEREname=$2AND(deactivated$3ORdeactivatedISNULL)blocking_statement|DELETEFROMfact_pathsfp|WHEREfp.idin(SELECTfp.id|FROMfact_pathsfp|innerjoinfact_valuesfvonfp.id=fv.path_id|innerjoinfactsfonfv.id=f.fact_value_id|WHEREfp.idin(selectfv.path_idfromfact_valuesfvwherefv.idin($1,$2,$3,$4,$5))|GROUPBYfp.id|HAVINGCOUNT(fv.id)=1)-[RECORD2]--+blocked_pid|19100blocked_user|puppetdbblocking_pid|11406blocking_user|puppetdbblocked_statement|UPDATEcertnamesSETdeactivated=$1WHEREname=$2AND(deactivated$3ORdeactivatedISNULL)blocking_statement|DELETEFROMfact_pathsfp|WHEREfp.idin(SELECTfp.id|FROMfact_pathsfp|innerjoinfact_valuesfvonfp.id=fv.path_id|innerjoinfactsfonfv.id=f.fact_value_id|WHEREfp.idin(selectfv.path_idfromfact_valuesfvwherefv.idin($1,$2,$3,$4))|GROUPBYfp.id{noformat}
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: ScreenShot2015-01-19at16.14.54.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko created an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Issue Type: Bug Assignee: Unassigned Attachments: Screen Shot 2015-01-19 at 12.12.26.png Created: 2015/01/19 1:26 AM Priority: Normal Reporter: Anton Fomenko Greetings, We faced into issues with PuppetDB PostgreSQL processes using all cores on our Puppet Master server (LA = 100 with 32 cores). This server have following components installed: 1. puppet-server 3.7.3 (httpd with passenger) 2. PuppetDB 2.2.2 with PostgreSQL 9.3 This is master sever from master-slave PostgreSQL replication setup using PuppetDB database and read-database settings. Issues was solved by following this instruction: https://docs.puppetlabs.com/puppetdb/latest/trouble_kahadb_corruption.html on all PuppetDB nodes and repeated one more time in approximately a week. top was showing a lot of DELETE PostgreSQL queries. Following queries were in blocked state in PostgreSQL: -[ RECORD 1
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko Attachment: ScreenShot2015-01-19at19.42.06.png Add Comment This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko updated an issue PuppetDB / PDB-1124 PuppetDB high CPU usage Change By: Anton Fomenko
