Jira (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Close it... I appreciate all your help! El 18 ago. 2016 4:52 PM, "Wyatt Alt (JIRA)" < 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 (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Good morning! I appreciate all your help! Just one last question, for puppetdb 2.3.8 postgres 9.5 works? Thanks 2016-08-10 17:52 GMT-06:00 Wyatt Alt (JIRA) < – Ing.Priscilla Piedra Hidalgo Software Developer 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 (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 One last question, do you know if there is like an official documentation that talks about postgresDB in relation w puppetDB? What I want to know is if puppetDB server RAM and cpu capacity should be reflected in postgres server, like in a 1-1 way, an example: My puppetdb server has 4 cpu and 16RAM (and I have 7 of them) My postgres server has 10 cpu and 32RAM Thanks again! 2016-08-10 16:31 GMT-06:00 Wyatt Alt (JIRA) < – Ing.Priscilla Piedra Hidalgo Software Developer 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 (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra commented on PDB-2941 Re: PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Hi! Thanks for answer me! Just a qq.. We have puppetdb working on each puppetaMaster (which are more than 1) and they are behind a load balancer... what we are thinking is: does puppetdb support more that 1 instance? Maybe this is the reason why we have problems with duplicate keys and UTF8 on DB. Should we have just 1 puppetdb instance isolated from puppetMasters? and just this instance will be the one tanling w DB. I appreciate all your help! 2016-08-08 22:51 GMT-06:00 Wyatt Alt (JIRA) < – Ing.Priscilla Piedra Hidalgo Software Developer 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 (PDB-2941) PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1
Title: Message Title Priscilla Piedra created an issue PuppetDB / PDB-2941 PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 on puppetdb 2.3.8-1puppetlabs1 Issue Type: Bug Assignee: Unassigned Components: PuppetDB Created: 2016/08/08 2:11 PM Environment: Running puppet 3.8.7-1puppetlabs1 on masters, puppetdb 2.3.8-1puppetlabs1 and postgres database 9.5, apache passenger on masters as web server Priority: Normal Reporter: Priscilla Piedra I'm having this issue on puppetdb and is concurrent to see it [replace facts] Retrying after attempt 7, due to: org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 org.postgresql.util.PSQLException: ERROR: invalid byte sequence for encoding "UTF8": 0x00 at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2157) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1886) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:255) ~[puppetdb.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:555) ~[puppetdb.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:417) ~[puppetdb.jar:na] at
Jira (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt, Just wondering if there is a stablish max for facts, (eg. max of 500 characters) or objects in case of a structure fact, or can I store information with not limit? Will set max_stack_depth setting to 6MB or higher would cost any performace issues on db? is there a guideline for it? Thanks 2016-04-18 11:10 GMT-06:00 Wyatt Alt (JIRA) < – Ing.Priscilla Piedra Hidalgo Software Developer 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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt I have applied this config on DB and I haven't seen the error... seems like it worked! Thanks for your help 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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt Do you know what is a good value to set max_stack_depth? My current value is 2MB 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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt ! Thanks for your help! To answer your questions: 1) have you been on 2.3.8 for a long time or have you recently upgraded: We have like two months using 2.3.8 version, before we had 2.2.2 2) did this start occurring suddenly or has it been going on for a while This problem appeared suddenly... like two weeks ago. 3) if suddenly, do any of the fact names I listed above correspond in an obvious way to recent changes? No, the facts are the same, there is no a recent change on them. 4) Do you use a single PDB + postgres/single master or is your PDB/postgres setup more complicated than that? We use a single postgres master, but for each PM we have puppetdb installed (we have 10 pms) 5) (unlikely) does anyone ever perform manual deletions on this database? Manual deletions no, but it is configured on each PDB report-ttl = 14d I sent to your email the output of the log. Thanks again!! 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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt Alt !! Thanks for helping me with this! I sent you the output of this query to your email wy...@puppetlabs.com (is a big output) 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 (PDB-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Priscilla Piedra commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi, It is suposed that this bug was fixed in version 2.3.4 but I'm having this issue on PDB 2.3.8 java.sql.BatchUpdateException: Batch entry 0 DELETE FROM fact_values fv WHERE fv.id in (131215,132501,132501,175,129002) AND NOT EXISTS (SELECT 1 FROM facts f WHERE f.fact_value_id in (131215,132501,132501,175,129002)AND f.fact_value_id = fv.id AND (f.factset_id, f.fact_path_id, f.fact_value_id) NOT in ((5790,111587,131215),(5790,118579,132501),(5790,110159,132501),(5790,120871,175),(5790,111511,129002))) 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.processResults(QueryExecutorImpl.java:1887) ~[puppetdb.jar:na] at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:405) ~[puppetdb.jar:na] at org.postgresql.jdbc2.AbstractJdbc2Statement.executeBatch(AbstractJdbc2Statement.java:2893) ~[puppetdb.jar:na] at com.jolbox.bonecp.StatementHandle.executeBatch(StatementHandle.java:469) ~[puppetdb.jar:na] at clojure.java.jdbc.internal$do_prepared_STAR_$fn__5845.invoke(internal.clj:356) ~[na:na] at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:223) ~[na:na] at clojure.java.jdbc.internal$do_prepared_STAR_.doInvoke(internal.clj:356) ~[na:na] at clojure.lang.RestFn.applyTo(RestFn.java:139) ~[puppetdb.jar:na] at clojure.core$apply.invoke(core.clj:626) ~[puppetdb.jar:na] at clojure.java.jdbc$do_prepared.doInvoke(jdbc.clj:206) ~[na:na] at clojure.lang.RestFn.invoke(RestFn.java:423) ~[puppetdb.jar:na] at com.puppetlabs.puppetdb.scf.storage$eval9406$delete_pending_value_id_orphans_BANG__9407$fn9408$fn_9409.invoke(storage.clj:813) ~[na:na] at clojure.lang.AFn.applyToHelper(AFn.java:165) ~[puppetdb.jar:na] at clojure.lang.AFn.applyTo(AFn.java:144) ~[puppetdb.jar:na] at clojure.core$apply.invoke(core.clj:624) ~[puppetdb.jar:na] at clojure.core$map$fn__4260.invoke(core.clj:2578) ~[puppetdb.jar:na] at clojure.core$map$fn__4245.invoke(core.clj:2559) ~[puppetdb.jar:na] at clojure.lang.LazySeq.sval(LazySeq.java:40) ~[puppetdb.jar:na] at clojure.lang.LazySeq.seq(LazySeq.java:49) ~[puppetdb.jar:na] at clojure.lang.RT.seq(RT.java:484) ~[puppetdb.jar:na] at clojure.core$seq.invoke(core.clj:133) ~[puppetdb.jar:na] at clojure.core$dorun.invoke(core.clj:2855) ~[puppetdb.jar:na] at com.puppetlabs.puppetdb.scf.storage$eval9406$delete_pending_value_id_orphans_BANG__9407$fn_9408.invoke(storage.clj:801) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9406$delete_pending_value_id_orphans_BANG___9407.invoke(storage.clj:787) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9585$update_facts_BANG__9586$fn9590$fn_9592.invoke(storage.clj:1013) ~[na:na] at clojure.java.jdbc.internal$transaction_STAR_.invoke(internal.clj:223) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9585$update_facts_BANG__9586$fn_9590.invoke(storage.clj:976) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9585$update_facts_BANG___9586.invoke(storage.clj:969) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9789$replace_facts_BANG__9790$fn9794$fn_9796.invoke(storage.clj:1235) ~[na:na] at com.puppetlabs.puppetdb.scf.storage.proxy$java.lang.Object$Callable$7da976d4.call(Unknown Source) ~[na:na] at com.yammer.metrics.core.Timer.time(Timer.java:91) ~[puppetdb.jar:na] at com.puppetlabs.puppetdb.scf.storage$eval9789$replace_facts_BANG__9790$fn_9794.invoke(storage.clj:1232) ~[na:na] at com.puppetlabs.puppetdb.scf.storage$eval9789$replace_facts_BANG___9790.invoke(storage.clj:1225) ~[na:na] at
