There is nothing in the logs as previously noted. It simply crashed quietly.
This is the same for when I'm running it in the foreground with --debug or
when it's a daemon. It simply quietly crashes.
--
013-01-09 18:00:15,841 DEBUG [command-proc-89]
[bonecp.PreparedStatementHandle] SELECT timestamp FROM certname_catalogs
WHERE certname='typhoon.xxx.com' ORDER BY timestamp DESC LIMIT 1
2013-01-09 18:00:16,185 DEBUG [command-proc-89]
[bonecp.PreparedStatementHandle] SELECT 1 FROM catalogs WHERE
hash='b9915aef874b1a291e32f1b7cbe0efa9848fb923' LIMIT 1
2013-01-09 18:00:16,185 DEBUG [command-proc-89] [bonecp.StatementHandle]
UPDATE catalogs SET api_version=1, catalog_version='1357754062' WHERE
hash='b9915aef874b1a291e32f1b7cbe0efa9848fb923'
2013-01-09 18:00:16,185 DEBUG [command-proc-89] [bonecp.StatementHandle]
DELETE FROM certname_catalogs WHERE certname='typhoon.xxx.com'
2013-01-09 18:00:16,186 DEBUG [command-proc-89]
[bonecp.PreparedStatementHandle] INSERT INTO certname_catalogs
(certname,catalog,timestamp) VALUES
('typhoon.xxx.com','b9915aef874b1a291e32f1b7cbe0efa9848fb923',2013-01-09
18:00:15.815)
2013-01-09 18:00:16,186 INFO [command-proc-89] [puppetdb.command]
[7779017b-5be2-415d-afd6-264d6d4d789e] [replace catalog] typhoon.xxx.com
sh-4.1#
--
I'll attempt to attach a strace to it however it's so remarkably verbose
it's always a treat to sift through it. Is there an easy way to increase
the verbosity of puppetDB perhaps?
-Cody
On Wednesday, January 9, 2013 6:11:19 AM UTC-5, Matthew Burgess wrote:
>
> On Wed, Jan 9, 2013 at 1:37 AM, Cody Robertson
> <codyha...@gmail.com<javascript:>>
> wrote:
> > Hello! How is everyone this splendid evening?
> >
> > I've recently migrated to the latest Puppet and PuppetDB (using the
> build in
> > database) however I'm noticing PuppetDB keeps crashing without any
> errors
> > that I can find in the logs. I've ran it in the foreground using the
> > puppetdb-foreground command however it simply exits after awhile. The
> only
> > thing I can consistently do is see it crash - I can't get any useful
> debug
> > information beyond that.
> >
> > Can anyone shed some light on how I should go about this? Thank you!
>
> What does /var/log/messages say. Just a stab in the dark, but if your
> server is short of memory, then the kernel's oom killer may be
> targetting the puppetdb process; that would certainly be evident in
> your /var/log/messages output.
>
> If that's not the culprit, then attaching 'strace' to the puppetdb
> process might be informative (strace -p <pid>).
>
> Regards,
>
> Matt.
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/vADEbpPDw7IJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
