Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Patrick Morton commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Traditionally, a acute syndrome or period ability, or use from a occupational nothing or use, is used. http://www.surveyanalytics.com//userimages/sub-2/2007589/3153260/29851520/7787437-29851520-stopadd15.html A research hand of 27 psychedelics was introduced, including four brains. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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@googl
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title
Kenneth Barber updated an issue
PuppetDB / PDB-656
puppetdb 2.0.0 throws exception after yum update
Change By:
Kenneth Barber
After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active.I'm currently trying to fix this issue by downgrading to PuppetDB 1.6.Is this a known issue? I could not find a bug report for this yet. ``` {code} [root@puppet puppetdb]# puppetdb foregroundch.qos.logback.core.joran.spi.JoranException: Could not open [/etc/puppetdb/log4j.properties]. at ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:80)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:68)sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:57)sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke (Method.java:606)clojure.lang.Reflector.invokeMatchingMethod (Reflector.java:93)clojure.lang.Reflector.invokeInstanceMethod (Reflector.java:28)puppetlabs.trapperkeeper.logging$configure_logger_via_file_BANG_.invoke (logging.clj:81)puppetlabs.trapperkeeper.logging$configure_logging_BANG_.invoke (logging.clj:90)puppetlabs.trapperkeeper.config$initialize_logging_BANG_.invoke (config.clj:103)puppetlabs.trapperkeeper.core$boot_with_cli_data.invoke (core.clj:111)puppetlabs.trapperkeeper.core$run.invoke (core.clj:145)puppetlabs.trapperkeeper.core$main.doInvoke (core.clj:160)clojure.lang.RestFn.applyTo (RestFn.java:137)clojure.core$apply.invoke (core.clj:624)com.puppetlabs.puppetdb.cli.services$_main.doInvoke (services.clj:365)clojure.lang.RestFn.invoke (RestFn.java:421)clojure.lang.Var.invoke (Var.java:383)clojure.lang.AFn.applyToHelper (AFn.java:156)clojure.lang.Var.applyTo (Var.java:700)clojure.core$apply.invoke (core.clj:624)com.puppetlabs.puppetdb.core$run_command.invoke (core.clj:87)com.puppetlabs.puppetdb.core$_main.doInvoke (core.clj:95)clojure.lang.RestFn.invoke (RestFn.java:436)clojure.lang.Var.invoke (Var.java:388)clojure.lang.AFn.applyToHelper (AFn.java:160)clojure.lang.Var.applyTo (Var.java:700)clojure.core$apply.invoke (core.clj:624)clojure.main$main_opt.invoke (main.clj:315)clojure.main$main.doInvoke (main.clj:420)clojure.lang.RestFn.invoke (RestFn.java:482)clojure.lang.Var.invoke (Var.java:401)clojure.lang.AFn.applyToHelper (AFn.java:171)clojure.lang.Var.applyTo (Var.java:700)clojure.main.main (main.java:37)Caused by: java.io.FileNotFoundException: /etc/puppetdb/log4j.properties (No such file or directory) at java.io.FileInputStream.open (FileInputStream.java:-2)java.io.FileInputStream. (FileInputStream.java:146)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:75)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:68)sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)sun.refle
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Kenneth Barber Fix Version/s: 2.0.0 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 (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Thanks for the explaination. I've completely missed the *.rpmnew files. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Aaron Zauner so the problem stems from ... if /etc/puppetdb/conf.d/config.ini has been modified, then RPM will no longer just blat new configuration into place. Instead it drops a global.ini.rpmnew (can you check this exists?) with the better proposed configuration. In this manner its cowardly refusing to just replace configuration, because your local edits may be important to you. On debian however, it prompts you instead of just dropping an rpmnew, which gives you the opportunity to diff with your existing version and make a decision if the vendored version is better or not. Some would argue this is better, but either way - RPM/YUM has nothing like that AFAIK. So the reality is, this way of YUM cowardly not updating configuration in this way is pretty standard and any sysadmin should be watching for those things during upgrades. Its unfortunate that we can't be louder at RPM install time, this especially applies to cases where users are upgrading packages automatically without user intervention (or the user seeing any mention of rpmnew files being created). Perhaps there is a better way that I don't know about. Having said that we can change the release notes for PuppetDB 2.0 to warn people ... which at least helps the users who read the release notes before upgrading a major version. Some users won't read them, and they'll raise bugs like this one (or hopefully search first and find this one). Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel rep
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner commented on an issue Re: puppetdb 2.0.0 throws exception after yum update This in fact seems to work. Shouldn't maybe there be a notice to people upgrading to 2.0 about issues like that? Thanks for your help. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Kenneth Barber Affects Version/s: 2.0.0 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 (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Kenneth Barber commented on an issue Re: puppetdb 2.0.0 throws exception after yum update Lets talk about the immediate problem first ... Change your config in /etc/puppetdb/conf.d/config.ini so that the line for logging now reflects the new logging configuration: logging-config = /etc/puppetdb/logback.xml And then restart. Add Comment PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by down... 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+
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Aaron Zauner After doing a simple `yum update` on the puppet server to fix the EPEL issue puppetdb was as well upgraded. PuppetDB won't start and throws an exception because of a missing log4j.properties file (which should be depreciated, as far as I can tell from the git sources). Puppetlabs Devel repositories active. I'm currently trying to fix this issue by downgrading to PuppetDB 1.6. Is this a known issue? I could not find a bug report for this yet.```[root@puppet puppetdb]# puppetdb foregroundch.qos.logback.core.joran.spi.JoranException: Could not open [/etc/puppetdb/log4j.properties]. at ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:80)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:68)sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:57)sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)java.lang.reflect.Method.invoke (Method.java:606)clojure.lang.Reflector.invokeMatchingMethod (Reflector.java:93)clojure.lang.Reflector.invokeInstanceMethod (Reflector.java:28)puppetlabs.trapperkeeper.logging$configure_logger_via_file_BANG_.invoke (logging.clj:81)puppetlabs.trapperkeeper.logging$configure_logging_BANG_.invoke (logging.clj:90)puppetlabs.trapperkeeper.config$initialize_logging_BANG_.invoke (config.clj:103)puppetlabs.trapperkeeper.core$boot_with_cli_data.invoke (core.clj:111)puppetlabs.trapperkeeper.core$run.invoke (core.clj:145)puppetlabs.trapperkeeper.core$main.doInvoke (core.clj:160)clojure.lang.RestFn.applyTo (RestFn.java:137)clojure.core$apply.invoke (core.clj:624)com.puppetlabs.puppetdb.cli.services$_main.doInvoke (services.clj:365)clojure.lang.RestFn.invoke (RestFn.java:421)clojure.lang.Var.invoke (Var.java:383)clojure.lang.AFn.applyToHelper (AFn.java:156)clojure.lang.Var.applyTo (Var.java:700)clojure.core$apply.invoke (core.clj:624)com.puppetlabs.puppetdb.core$run_command.invoke (core.clj:87)com.puppetlabs.puppetdb.core$_main.doInvoke (core.clj:95)clojure.lang.RestFn.invoke (RestFn.java:436)clojure.lang.Var.invoke (Var.java:388)clojure.lang.AFn.applyToHelper (AFn.java:160)clojure.lang.Var.applyTo (Var.java:700)clojure.core$apply.invoke (core.clj:624)clojure.main$main_opt.invoke (main.clj:315)clojure.main$main.doInvoke (main.clj:420)clojure.lang.RestFn.invoke (RestFn.java:482)clojure.lang.Var.invoke (Var.java:401)clojure.lang.AFn.applyToHelper (AFn.java:171)clojure.lang.Var.applyTo (Var.java:700)clojure.main.main (main.java:37)Caused by: java.io.FileNotFoundException: /etc/puppetdb/log4j.properties (No such file or directory) at java.io.FileInputStream.open (FileInputStream.java:-2)java.io.FileInputStream. (FileInputStream.java:146)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:75)ch.qos.logback.core.joran.GenericConfigurator.doConfigure (GenericConfigurator.java:68)sun.reflect.NativeMethodAccessorImpl.invoke0 (NativeMethodAccessorImpl.java:-2)sun.reflect.Native
Jira (PDB-656) puppetdb 2.0.0 throws exception after yum update
Title: Message Title Aaron Zauner updated an issue PuppetDB / PDB-656 puppetdb 2.0.0 throws exception after yum update Change By: Aaron Zauner Summary: puppetdb 2.0.0 throws exception after yum update 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.
