Comment 8 for bug 1531509

I'm getting the same issue at the moment on my deployment.

Also on MOS 7 and LMA 0.8.0.

A bit more concerning is the fact that on this controller (which is the current vip__management/vip__vrouter_pub/vip__vrouter), getting the same error messages, trying to kill everything related off to start things off "fresh", but the error just seems to be coming back.

- kill -9 collectd (because trying to kill it nicely just does not work)

- crm resource stop lma_collector (make sure hekad has really stopped, as it sometimes takes a minute or two)

- crm resource start lma_collector

At this point, everything seems fine, lma is running, no particular error messages, even after letting it run for 2 minutes.

- /etc/init.d/collectd start

And in /var/log/lma_collector.log, I'll start seeing this:

2016/02/23 21:34:41 Decoder 'collectd_httplisten-collectd_decoder' error: FATAL: process_message() /usr/share/lma_collector/decoders/collectd.lua:35: bad argument #1 to 'gsub' (string expected, got nil)
2016/02/23 21:34:41 Shutdown initiated.

Hekad proceeds to shutdown. Pacemaker proceeds to start it back up.

But again, that error message comes back:

2016/02/23 21:36:20 Decoder 'collectd_httplisten-collectd_decoder' error: FATAL: process_message() /usr/share/lma_collector/decoders/collectd.lua:35: bad argument #1 to 'gsub' (string expected, got nil)
2016/02/23 21:36:20 Shutdown initiated.

And the loop keeps going...

Of course, in /var/log/collectd.log, at this point, I'm going to start seeing:

[2016-02-23 21:41:27] write_http plugin: curl_easy_perform failed with status 7: Failed to connect to 127.0.0.1 port 8325: Connection refused