[collectd] attempting to use gmond plugin with collectd

Raymond Flanery flaneryrejr at ornl.gov
Tue May 25 19:57:44 CEST 2010

Sounds like a good plan of attack. I need to finish up installation of 
new storage subsystems today and tomorrow I will give you ideas a try 
and see what I come up with. Thank you for the suggestions.

Ray Flanery

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
> 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.

More information about the collectd mailing list