I followed the directions for creating a core file that you passed onto me, however one is not being created. Am I supposed to replace the collectd pkg with the collectd-dbg package or is it just an addon to get the debug symbols?
Ray Florian Forster wrote: > Hi Raymond, > > On Fri, May 21, 2010 at 12:19:51PM -0400, Raymond Flanery wrote: > >> […] The only plugins I have turned on are syslog, gmond and csv. if I >> start collectd the records in syslog look like the following: >> >> collectd[18878]: Initialization complete, entering read-loop. >> collectdmon[18852]: Warning: collectd terminated with exit status 127 >> collectdmon[18852]: Warning: restarting collectd >> > > That sounds like collectd is crashing, likely due to a bug in the gmond > plugin. Since that plugin is probably not the most widely used one, even > obvious bugs in that plugin are possible :( > > It looks like you're using a Debian package. Could you please install > the "collectd-dbg" package (which provides the debugging symbols) and > enable the creation of "core dumps" by setting > ENABLE_COREFILES=1 > in /etc/default/collectd. When collectd crashes after an > /etc/init.d/collectd restart > it should create a core dump in the working directory of the daemon, > usually > /var/lib/collectd > > If you're using either x86 or x86_64, it's enough if you could provide > that core file to me. If you use another architecture, a stack backtrace > would be very useful. > > I've just created a wiki page, "Core file" [0], which describes the > debugging process in some more detail. It'd be great if you would follow > that, provide that core file or stack backtrace and tell me if the > instructions are understandable. :) > > Regards, > —octo > > [0] <http://collectd.org/wiki/index.php/Core_file> > -- Raymond E. Flanery, Jr. GIST Group, ORNL 865.574.0630 _______________________________________________ collectd mailing list [email protected] http://mailman.verplant.org/listinfo/collectd
