All Apps and Add-ons

Could not find plugin "write_http" in /usr/lib64/collectd

sloshburch
Splunk Employee
Splunk Employee

Following the instructions from http://docs.splunk.com/Documentation/AddOns/released/Linux/Configure, I set up my config by uncommenting the LoadPlugin write_http, and creating my Node:

<Plugin write_http>
        <Node "burch">
                URL "https://<myhost>:8088/services/collector/raw?channel=<mytoken>"
                Header "Authorization: Splunk <mytoken>"
                Format "JSON"
                Metrics true
                StoreRates true
                BufferSize 1
        </Node>
</Plugin write_http>

Yet, I see collectd failing with the following in its log:

[2017-08-02 10:36:36] plugin_load: plugin "logfile" successfully loaded.
[2017-08-02 10:36:36] logfile: invalid loglevel [debug] defaulting to 'info'
[2017-08-02 10:36:36] plugin_load: plugin "cpu" successfully loaded.
[2017-08-02 10:36:36] plugin_load: plugin "interface" successfully loaded.
[2017-08-02 10:36:36] plugin_load: plugin "load" successfully loaded.
[2017-08-02 10:36:36] plugin_load: plugin "memory" successfully loaded.
[2017-08-02 10:36:36] plugin_load: Could not find plugin "write_http" in /usr/lib64/collectd
[2017-08-02 10:36:36] There is a `Node' block within the configuration for the write_http plugin. The plugin either only expects "simple" configuration statements or wasn't loaded using `LoadPlugin'. Please check your configuration.

When I check out the /usr/lib64/collectd directory, the plugins seem all there EXCEPT FOR write_http. I see:
-rwxr-xr-x 1 root root 27968 May 25 15:11 aggregation.so
-rwxr-xr-x 1 root root 11000 May 25 15:11 apcups.so
-rwxr-xr-x 1 root root 12880 May 25 15:11 battery.so
-rwxr-xr-x 1 root root 13456 May 25 15:11 cgroups.so
-rwxr-xr-x 1 root root 5848 May 25 15:11 conntrack.so
-rwxr-xr-x 1 root root 5968 May 25 15:11 contextswitch.so
-rwxr-xr-x 1 root root 5976 May 25 15:11 cpufreq.so
-rwxr-xr-x 1 root root 5264 May 25 15:11 cpusleep.so
-rwxr-xr-x 1 root root 11120 May 25 15:11 cpu.so
-rwxr-xr-x 1 root root 12512 May 25 15:11 csv.so
-rwxr-xr-x 1 root root 15272 May 25 15:11 df.so
-rwxr-xr-x 1 root root 5152 May 25 15:11 entropy.so
-rwxr-xr-x 1 root root 10936 May 25 15:11 ethstat.so
-rwxr-xr-x 1 root root 60736 May 25 15:11 exec.so
-rwxr-xr-x 1 root root 7056 May 25 15:11 fhcount.so
-rwxr-xr-x 1 root root 11480 May 25 15:11 filecount.so
-rwxr-xr-x 1 root root 6720 May 25 15:11 fscache.so
-rwxr-xr-x 1 root root 8848 May 25 15:11 hddtemp.so
-rwxr-xr-x 1 root root 7720 May 25 15:11 interface.so
-rwxr-xr-x 1 root root 6896 May 25 15:11 ipc.so
-rwxr-xr-x 1 root root 7360 May 25 15:11 irq.so
-rwxr-xr-x 1 root root 6784 May 25 15:11 load.so
-rwxr-xr-x 1 root root 9072 May 25 15:11 logfile.so
-rwxr-xr-x 1 root root 26200 May 25 15:11 madwifi.so
-rwxr-xr-x 1 root root 4776 May 25 15:11 match_empty_counter.so
-rwxr-xr-x 1 root root 6672 May 25 15:11 match_hashed.so
-rwxr-xr-x 1 root root 9800 May 25 15:11 match_regex.so
-rwxr-xr-x 1 root root 5744 May 25 15:11 match_timediff.so
-rwxr-xr-x 1 root root 8048 May 25 15:11 match_value.so
-rwxr-xr-x 1 root root 8168 May 25 15:11 mbmon.so
-rwxr-xr-x 1 root root 8328 May 25 15:11 md.so
-rwxr-xr-x 1 root root 15088 May 25 15:11 memcached.so
-rwxr-xr-x 1 root root 8104 May 25 15:11 memory.so
-rwxr-xr-x 1 root root 8472 May 25 15:11 multimeter.so
-rwxr-xr-x 1 root root 44896 May 25 15:11 network.so
-rwxr-xr-x 1 root root 13248 May 25 15:11 nfs.so
-rwxr-xr-x 1 root root 7096 May 25 15:11 notify_nagios.so
-rwxr-xr-x 1 root root 15536 May 25 15:11 ntpd.so
-rwxr-xr-x 1 root root 6984 May 25 15:11 numa.so
-rwxr-xr-x 1 root root 12984 May 25 15:11 olsrd.so
-rwxr-xr-x 1 root root 13248 May 25 15:11 openvpn.so
-rwxr-xr-x 1 root root 29760 May 25 15:11 powerdns.so
-rwxr-xr-x 1 root root 17712 May 25 15:11 processes.so
-rwxr-xr-x 1 root root 8624 May 25 15:11 protocols.so
-rwxr-xr-x 1 root root 6720 May 25 15:11 serial.so
-rwxr-xr-x 1 root root 41632 May 25 15:11 statsd.so
-rwxr-xr-x 1 root root 10128 May 25 15:11 swap.so
-rwxr-xr-x 1 root root 7104 May 25 15:11 syslog.so
-rwxr-xr-x 1 root root 13648 May 25 15:11 table.so
-rwxr-xr-x 1 root root 15064 May 25 15:11 tail_csv.so
-rwxr-xr-x 1 root root 44368 May 25 15:11 tail.so
-rwxr-xr-x 1 root root 8272 May 25 15:11 target_notification.so
-rwxr-xr-x 1 root root 11944 May 25 15:11 target_replace.so
-rwxr-xr-x 1 root root 10992 May 25 15:11 target_scale.so
-rwxr-xr-x 1 root root 10880 May 25 15:11 target_set.so
-rwxr-xr-x 1 root root 9728 May 25 15:11 target_v5upgrade.so
-rwxr-xr-x 1 root root 11984 May 25 15:11 tcpconns.so
-rwxr-xr-x 1 root root 15160 May 25 15:11 teamspeak2.so
-rwxr-xr-x 1 root root 8880 May 25 15:11 ted.so
-rwxr-xr-x 1 root root 8824 May 25 15:11 thermal.so
-rwxr-xr-x 1 root root 17296 May 25 15:11 threshold.so
-rwxr-xr-x 1 root root 56688 May 25 15:11 unixsock.so
-rwxr-xr-x 1 root root 6720 May 25 15:11 uptime.so
-rwxr-xr-x 1 root root 5080 May 25 15:11 users.so
-rwxr-xr-x 1 root root 7056 May 25 15:11 uuid.so
-rwxr-xr-x 1 root root 8400 May 25 15:11 vmem.so
-rwxr-xr-x 1 root root 9048 May 25 15:11 vserver.so
-rwxr-xr-x 1 root root 6776 May 25 15:11 wireless.so
-rwxr-xr-x 1 root root 19272 May 25 15:11 write_graphite.so
-rwxr-xr-x 1 root root 19192 May 25 15:11 write_log.so

I installed collectd with yum. This is an EC2 instance. Is there another step? Perhaps something obvious I don't know (since collectd is new to me) or something extra required for AWS EC2 instances?

1 Solution

sloshburch
Splunk Employee
Splunk Employee

Appears that with yum, you need to install another component: collectd-write_http.x86_64

So the full install should be: yum -y install collectd collectd-write_http.x86_64

View solution in original post

sloshburch
Splunk Employee
Splunk Employee

Appears that with yum, you need to install another component: collectd-write_http.x86_64

So the full install should be: yum -y install collectd collectd-write_http.x86_64

sloshburch
Splunk Employee
Splunk Employee

For disk stuff, I also needed collectd-disk.x86_64

0 Karma
Get Updates on the Splunk Community!

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...

Get the T-shirt to Prove You Survived Splunk University Bootcamp

As if Splunk University, in Las Vegas, in-person, with three days of bootcamps and labs weren’t enough, now ...

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...