Jira (PDB-1304) KahaDB: Could not retrieve facts
Title: Message Title Andreas Papst commented on PDB-1304 Re: KahaDB: Could not retrieve facts Hi Kenneth, there is no more log content to obtain. As we further investigate this problem you are right. The start up of the init.d script failed in some parts. Finally we managed to start up puppetdb by executing each single step of this script on a shell prompt. That worked and we haven't try to restart it again. And due to the fact we have increased the memory size in the virtual server instance puppetdb isn't dying any more. Recently a new Debian package for puppetdb is made available which we will try to install next days and look for some improvements. Regards Andreas 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-1304) KahaDB: Could not retrieve facts
Title: Message Title Kenneth Barber commented on PDB-1304 Re: KahaDB: Could not retrieve facts Odd, we haven't heard of startup issues with the script, but perhaps its failing due to something environmental. Sometimes I'll drop the line: set -x Near the top of a startup script to debug what's happening and where it's failing. If you get the new package, try it with that line and drop the output into this ticket. An example output on my Debian 7 box with the ```set -x``` part is here: https://gist.github.com/kbarber/f7f738d2544452927d49 The fact that it was starting up at all, and presenting a web service usually means it started but didn't initialize the PuppetDB service in particular, so I'm surprised to hear you had hassles with the startup script. That is, the symptoms you described earlier aren't entirely lining up with an init script problem, but perhaps the problem has morphed while you've debugged it. 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
Jira (PDB-1304) KahaDB: Could not retrieve facts
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1304 KahaDB: Could not retrieve facts Andreas Papst Can you supply the log file from your puppetdb instance? The 'not found' error message seems to me like its not completing startup, the logs should express more information about the failure, I would expect at least to see an exception giving us a clue as to what went wrong. Change By: Kenneth Barber Sprint: PuppetDB2015-05-06 Issue Type: Improvement Bug 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-1304) KahaDB: Could not retrieve facts
Title: Message Title
Andreas Papst created an issue
PuppetDB / PDB-1304
KahaDB: Could not retrieve facts
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2015/03/19 10:39 AM
Environment:
Debian GNU/Linux 7.8 (wheezy) puppet 3.7.4-1puppetlabs1 puppet-dashboard 1.2.23-1puppetlabs1 puppet-lint 0.1.13-2 puppetdb 2.2.2-1puppetlabs1 puppetdb-terminus 2.2.2-1puppetlabs1 puppetlabs-release 1.0-11 puppetmaster 3.7.4-1puppetlabs1 puppetmaster-common 3.7.4-1puppetlabs1 puppetmaster-passenger 3.7.3-1puppetlabs1 java-common 0.47 openjdk-7-jre-headless:amd64 7u65-2.5.1-5~deb7u1
Priority:
Normal
Reporter:
Andreas Papst
Each puppet agent cannot retrieve information according it's name from puppetdb.
Removing directory or deleting some file inside /var/lib/puppetdb/mq/localhost/KahaDB does not help.
/var/log/puppetdb/puppetdb.log: 2015-03-19 18:30:33,140 WARN [o.e.j.h.HttpParser] badMessage: java.lang.IllegalStateException: too much data after closed for HttpChannelOverHttp@139ca786 {r=1,a=IDLE,uri=-}
puppet agent error: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Error 400 on SERVER: Could not retrieve facts for agent.test.com: Failed to find facts from PuppetDB at puppetmaster.test.com:8081: [404 Not Found] htmlheadmeta http-equiv=Content-Type content=text/html;charset=ISO-8859-1/titleError 404 /title/headbodyh2HTTP ERROR: 404/h2pProblem accessing /v3/nodes/agent.test.com/facts. Reason:pre Not Found/pre/phr /ismallPowered by Jetty:///small/i/body/html
Even
