Jira (PUP-7185) Danish UTF-8 chars kills Puppet in v2.7.2 (not in 2.5.0)
Title: Message Title
Klavs Klavsen commented on PUP-7185
Re: Danish UTF-8 chars kills Puppet in v2.7.2 (not in 2.5.0)
It was late - so I wrote the puppetserver version in the subject.. googleing couldn't give me a hit showing which puppet version that is I did restart puppetserver (twice to be sure).
I just looked a bit further, and that exact array, is not loaded via autoloading, but loaded using: $users = hiera_hash('eit_users', {})
so its the hiera_hash function most likely.
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 (PUP-7185) Danish UTF-8 chars kills Puppet in v2.7.2 (not in 2.5.0)
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-7185 Danish UTF-8 chars kills Puppet in v2.7.2 (not in 2.5.0) Issue Type: Bug Affects Versions: PUP 4.9.2 Assignee: Unassigned Created: 2017/02/07 1:21 PM Priority: Normal Reporter: Klavs Klavsen This content in my hieradata/common.yaml eit_users: lisbeth: realname: "Lisbeth Ammitzbøll Hansen" uid: '3004' Kills puppet (after I upgraded from 2.5.0 who had no issues with it) to 2.7.2 - with this error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Resource Statement, Lookup of key 'common::system::enable_selinux' failed: DataBinding 'hiera': ""\xC3"" on US-ASCII Add Comment
Jira (PUP-7105) Remount mounts with "bad file descriptor" errors
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-7105 Remount mounts with "bad file descriptor" errors Issue Type: New Feature Assignee: Unassigned Created: 2017/01/16 11:46 PM Priority: Normal Reporter: Klavs Klavsen Feature request (which I also saw some talked about back in 2.6 days Just this morning, 20 of our servers had an nfs mount with stale file handles - and had to be manually umounted and mounted again Puppet handles the mounts, but errors out with: Bad file descriptor so it knows somethings wrong, and IMHO it would be a nice feature, if it (when it knows its an nfs mount) atleast just tried once - to umount and remount to see if that resolved the issue (especially since the system reports the mount as being mounted). Add Comment
Jira (FACT-453) selinux fact fails on centos/lxc
Title: Message Title Klavs Klavsen commented on FACT-453 Re: selinux fact fails on centos/lxc it is resolved in facter 3 - with latest puppet-agent atleast 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 (PUP-6835) Puppet does not check for revoked cert against puppetdb connection
Title: Message Title Klavs Klavsen commented on PUP-6835 Re: Puppet does not check for revoked cert against puppetdb connection We have restarted the puppetmaster several times.. (it does not always handle updating functions etc. when we change them the cert on puppetdb was updated several months ago - only issue we ever saw, was the puppet node deactivate issue. 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 (PUP-6835) Puppet does not check for revoked cert against puppetdb connection
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-6835 Puppet does not check for revoked cert against puppetdb connection Issue Type: Bug Assignee: Unassigned Components: Puppet Server, PuppetDB Created: 2016/10/20 5:19 AM Priority: Normal Reporter: Klavs Klavsen We accidently revoked our puppetdb hosts puppet cert, and we just issued a new one so puppet agent worked again. But we had a weird issue with puppet node deactivate complaining that our puppetdb nodes cert was revoked - and yet our exported resources etc. worked just fine. I found out that since puppetdb SSL setup - is done by getting a copy of the puppet agent certs - it indeed had the old certs - which were revoked.. so it seems puppet does not do CRL checking in its communications with puppetdb. (except for puppet node stuff atleast Add Comment
Jira (PUP-6777) incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-6777 incompatible character encodings: UTF-8 and ASCII-8BIT Issue Type: Bug Affects Versions: PUP 4.6.1 Assignee: Unassigned Created: 2016/10/04 12:21 PM Priority: Normal Reporter: Klavs Klavsen This bug - seemingly fixed in https://github.com/puppetlabs/puppet/pull/3977#issuecomment-251466761 seems to have cropped up again: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782494 This bug has cropped up again in puppet-4.6.1 (puppet-agent 1.6.1) - since we upgraded from puppet-3.7.1 on an agent. it only happens when we run puppet in cron - and the workaround LANG=en_US.utf8 in front of puppet agent -t - works. Add Comment
Jira (PUP-2793) Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Klavs Klavsen commented on PUP-2793 Re: Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT To us it only happens, when we run puppet in cron. not when run in our login shell. It seems to be the same bug as PUP-4633 - and running puppet with: LANG=en_US.utf8 puppet agent -t works around it. 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 (PUP-2793) Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT
Title: Message Title Klavs Klavsen commented on PUP-2793 Re: Failed to apply catalog: incompatible character encodings: UTF-8 and ASCII-8BIT We got this problem for the first time on a specific server at Sep 13 12:43:23 (because a user has an Ø in "real name" - used by user type in puppet). Which fits perfectly with when we went from puppet-3.7.1 to puppet-agent-1.6.1 - from yum.log (on a centos 6 btw.) Sep 13 12:18:32 Installed: puppet-agent-1.6.1-1.el7.x86_64 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 (PUP-6565) Optional[integer] is accepted to mean Optional[String]
Title: Message Title
Klavs Klavsen created an issue
Puppet / PUP-6565
Optional[integer] is accepted to mean Optional[String]
Issue Type:
Bug
Assignee:
Unassigned
Created:
2016/07/29 9:13 AM
Priority:
Minor
Reporter:
Klavs Klavsen
class whaterver ( Optional[integer] $var1 = undef, ) { }
makes puppet think it should be a String.
If integer is written as Integer - it works as it should.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-29) Notification hooks
Title: Message Title Klavs Klavsen commented on PDB-29 Re: Notification hooks One use-case IMHO - would be to collect data from runs. We currently trigger this collection from puppetdb, by way of our clients running puppet agent - curl'ing to a REST service (once agent run has send in report), which then pulls the latest report numbers (and hence lets puppetdb do the report parsing) - so we can save successes, failure etc. numbers - and do alerting and graphing of the state of our servers. It actually allowed us to produce great graphs - highlighting servers that have "continous changes".. alert on massive failure (10+ servers within certain timeframe) in icinga/nagios etc. 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 (PUP-4422) Catalog fallback on failure
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-4422 Catalog fallback on failure Issue Type: New Feature Assignee: Unassigned Created: 2015/04/16 5:48 AM Priority: Normal Reporter: Klavs Klavsen Currently, when I make a mistake (f.ex. add an apache vhost which uses SSL features but forget to enable ssl module), then the service dies.. and previously working vhosts stops working What I would think would be a great feature, would be for puppet to be able to revert to last known good catalog (configurable).. so if the agent simply saves last catalog that worked.. and on failure (if so configured - or perhaps only for failures on Service types) it tries to run last known good catalog instaed.. hoping the service then works.. That would lessen the impact of mistakes on production environment a great deal.. Add Comment
Jira (HI-286) hiera array hierachy resolving
Title: Message Title Klavs Klavsen created an issue Hiera / HI-286 hiera array hierachy resolving Issue Type: Bug Assignee: Unassigned Created: 13/Aug/14 2:19 AM Priority: Normal Reporter: Klavs Klavsen I'd like you to reconsider: https://github.com/puppetlabs/hiera/pull/48 (ticket being: http://projects.puppetlabs.com/issues/14369 ) this feature I definetely think has great value in some respects.. and could be configurable (defaulting to disabled) - by having f.ex. hierachy_array_concat: setting default to true. For me this would be VERY useful (and I've heard this from others as well). I use netgroups to group hosts which does not necessarily have the same role.. currently I would like to model a list of connection checks on doing hiera array lookup. so I can get a collective list of things to check is there by doing a hiera_hash lookup. so when the host is in group1 and group3 - and on primarynetwork X, I'd like to get all checks needed for group1, group3, primarynetwork X and what's in common.yaml. and I'd also like to use it on hosts where I use facts to autodiscover (I have hosts where puppet isn't allowed to actually do anything) - so I would get an array fact - listing everything facts have detected - which I can then use as an array, to get all relevant for the host). I hope you'll consider merging this, as a configurable option.
Jira (PUP-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen commented on an issue Re: puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec As stated in subject, they are running Red Hat (RH) 6 (aka. EL6). Add Comment Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec I just updated all my hosts to puppet 3.5.1 (from 3.4.2) after having tested on a few. Unfortunately puppet run now fails on 50% of my hosts, with this failure: # puppet agent -t /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load -- json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 fro... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen assigned an issue to Charlie Sharpsteen I guess it goes to you, ? when I've answered Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec Change By: Klavs Klavsen Assignee: KlavsKlavsen CharlieSharpsteen Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen commented on an issue Re: puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec ahh. I just had a look at our source for rubygem-json.. and its a package we build a year ago.. so didn't get the EPEL version.. and for some faulty reason our package does not depend on rubygems, which it should.. most hosts had rubygems already - so it worked there. I'm guessing you mean as of 3.5.0? the hosts which only had rubygem-json and NOT rubygems - were working before (and I do believe puppet started with version 2.6.. coming directly from v0.25 I was using yum update btw. Add Comment Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec I just updated all my hosts to puppet 3.5.1 (from 3.4.2) after having tested on a few. Unfortunately puppet run now fails on 50% of my hosts, with this failure: # puppet agent -t /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load -- json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 fro... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
Jira (PUP-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen commented on an issue Re: puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec Fair enough - I'll fix our rubygem-json.. or perhaps let it be replaced by your puppetlabs-dependencies package. Sorry for the bogus error report Add Comment Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec I just updated all my hosts to puppet 3.5.1 (from 3.4.2) after having tested on a few. Unfortunately puppet run now fails on 50% of my hosts, with this failure: # puppet agent -t /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load -- json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 fro... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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
Jira (PUP-2507) puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-2507 puppet 3.5.1 needs rubygems on (RH) EL6 - but does not require it in spec Issue Type: Bug Affects Versions: 3.5.1 Assignee: Unassigned Created: 07/May/14 1:31 AM Priority: Normal Reporter: Klavs Klavsen I just updated all my hosts to puppet 3.5.1 (from 3.4.2) after having tested on a few. Unfortunately puppet run now fails on 50% of my hosts, with this failure: puppet agent -t /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3:in `require': no such file to load – json (LoadError) from /usr/lib/ruby/site_ruby/1.8/puppet/module.rb:3 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb:1 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb:6 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/methods.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/method_call.rb:2 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb:115 from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11:in `require' from /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb:11 from /usr/lib/ruby/site_ruby/1.8/puppet/parser.rb:4:in `require' from
Jira (PUP-2456) environment is not reset in user crontabs
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-2456 environment is not reset in user crontabs Issue Type: Bug Assignee: Unassigned Created: 05/May/14 1:54 AM Priority: Normal Reporter: Klavs Klavsen if I define a cronjob, with an environment setting for PATH, MAILTO etc. - then depending on WHERE in the users crontab it is inserted - this environment setting also affects every entry after this - and there is AFAIK no way to control in which order they are inserted into crontab - so other cronjobs could easily be unwillingly affected My suggestion, would be to reset the environment settings, right after.. So if the environment has MAILTO=.. set.. then set it to what it originally was before this (if no MAILTO is set in the file.. then MAILTO=$username ) It's definetely not perfect though. Add Comment
Jira (FACT-453) selinux fact fails on centos/lxc
Title: Message Title Klavs Klavsen created an issue Facter / FACT-453 selinux fact fails on centos/lxc Issue Type: Bug Affects Versions: 2.0.1 Assignee: Eric Sorenson Created: 03/Apr/14 2:03 PM Priority: Normal Reporter: Klavs Klavsen facter v2.0.1 spits out this on CentOS 6.5 in lxc. Could not retrieve fact='selinux', resolution='anonymous': Invalid argument - /proc/self/attr/current This was not a problem with the latest version of facter, before 2.0. Add Comment This
Jira (FACT-377) Does not detect LXC virtualization
Title: Message Title Klavs Klavsen commented on an issue Re: Does not detect LXC virtualization This has been contributed here.. https://github.com/puppetlabs/facter/pull/630 Add Comment Facter / FACT-377 Does not detect LXC virtualization Facter does not detect when run in an LXC virtual environment. It reports is_virtual = false and virtual = physical. This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen created an issue PuppetDB / PDB-501 kahadb has 1.1GB log files Issue Type: Bug Assignee: Unassigned Created: 06/Mar/14 7:42 AM Priority: Normal Reporter: Klavs Klavsen rw-r r -. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 rw-r r -. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 rw-r r - 1 puppetdb 29K May 19 2013 db.redo-1369122060204 rw-r r - 1 puppetdb 32K May 21 2013 db.data-1369122060204 rw-r r - 1 puppetdb 32M Mar 6 04:12 db-11955.log rw-r r
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files seems to be caused by https://tickets.puppetlabs.com/browse/PUP-1524 - I've upgraded to puppet 3.4.3 - now I just need to figure out how to clear the queue Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files I spoke too soon. the issue cleared itself up, after upgrading to 3.4.3 on the puppetmaster and restarting it. Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files the puppetdb.log was full of: 2014-03-06 16:48:14,273 ERROR [command-proc-65] [puppetdb.command] [bb57eeb6-6026-4ad4-ae13-01878327a47f] [store report] Retrying after attempt 7, due to: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint constraint_resource_events_unique org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint constraint_resource_events_unique at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:363) at com.jolbox.bonecp.PreparedStatementHandle.executeUpdate(PreparedStatementHandle.java:203) at clojure.java.jdbc.internal$do_prepared_return_keys_STAR_$fn__2133.invoke(internal.clj:337) at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:223) at clojure.java.jdbc.internal$do_prepared_return_keys_STAR_.invoke(internal.clj:337) at clojure.lang.AFn.applyToHelper(AFn.java:163) Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11...
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files hmm. can't close it as invalid.. which would seem to be the correct status Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files yup. caused by the other issue and luckily upgrading puppet cleared the queue right up Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PDB-501) kahadb has 1.1GB log files
Title: Message Title Klavs Klavsen commented on an issue Re: kahadb has 1.1GB log files I was on puppet 3.4.2 (that's what the issue I linked to regards..). Add Comment PuppetDB / PDB-501 kahadb has 1.1GB log files -rw-r--r--. 1 puppetdb 45K Apr 9 2013 db.redo-1365504151237 -rw-r--r--. 1 puppetdb 212K Apr 9 2013 db.data-1365504151237 -rw-r--r-- 1 puppetdb 29K May 19 2013 db.redo-1369122060204 -rw-r--r-- 1 puppetdb 32K May 21 2013 db.data-1369122060204 -rw-r--r-- 1 puppetdb 32M Mar 6 04:12 db-11955.log -rw-r--r-- 1 puppetdb 33M Mar 6 04:38 db-11... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- 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/groups/opt_out.
Jira (PUP-1480) put puppet ruby libs in ruby version neutral folder
Title: Message Title Klavs Klavsen created an issue Puppet / PUP-1480 put puppet ruby libs in ruby version neutral folder Issue Type: New Feature Assignee: Eric Sorenson Created: 21/Jan/14 7:41 AM Priority: Normal Reporter: Klavs Klavsen since puppet 3.4.2 should work fine with ruby 1.9 - should libs be put in version neutral folder.. so the few poor slobs, who happen to have a CentOS (or other el6) server that must have /usr/bin/ruby point to ruby 1.9.. can still have a functioning puppet.. in my setup - that would be: /usr/lib64/ruby/site_ruby (vendor_ruby isn't in el6's default search path). Add Comment This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)
