[collectd] Collectd client data not written to Collectd Server

[xflou]

Hello,

I was able to resolve the issue.

Thank you!!

On Sat, May 25, 2019 at 8:04 PM xflou <xn9733 at gmail.com> wrote:

> Hello,
>
> I have two Ubuntu hosts. One acts as the collected Server and the other as
> a collectd client.
>
> The configuration seems to be fine on both. The collectd client traffic
> seems to be received at the collectd Server, but the data is not written to
> the "/var/lib/collected/rdd" directory. The Tcpdump below confirms this.
>
> On the collectd client side,  the tcp dump also indicates that the data is
> being sent to the collectd server on the correct IP and port.
>
> What I was expecting, is that the collected client data  received on the
> collected server would be written to the
> "/var/lib/collectd/rdd/clientMachineName" directory as a separate entry
> from the "/var/lib/collectd/rdd/serverMachinename" directory.
>
> Any ideas as to why this is not working as expected, would be appreciated.
>
>
> Below are the /etc/collectd/collectd.conf file entries for the collectd
> server and collectd client:
>
>
> ==============> Server config:
>
> LoadPlugin logfile
> LoadPlugin syslog
> #LoadPlugin log_logstash
>
> <Plugin logfile>
>         LogLevel "info"
>         File STDOUT
>         Timestamp true
>         PrintSeverity false
> </Plugin>
>
> <Plugin syslog>
>         LogLevel info
> </Plugin>
>
>
> LoadPlugin cpu
> LoadPlugin df
> LoadPlugin disk
> LoadPlugin entropy
> LoadPlugin interface
> LoadPlugin irq
> LoadPlugin load
> LoadPlugin memory
> LoadPlugin network
> LoadPlugin processes
> LoadPlugin rrdtool
> LoadPlugin swap
> LoadPlugin users
>
> <Plugin network>
> #       # client setup:
>         <Listen "0.0.0.0" "25826">
>         </Listen>
> </Plugin>
>
> ==> server netstat:
> udp    17408      0 0.0.0.0:25826           0.0.0.0:*
>       7223/collectd
>
> ===> server tcpcump
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens3, link-type EN10MB (Ethernet), capture size 1500 bytes
> 19:41:56.652796 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1321
> 19:41:56.655302 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1316
> 19:41:56.656320 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1328
> 19:41:56.659259 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1289
> 19:42:06.642940 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1343
>
>
> ========> Client config is the same except for the network section below:
>
> Plugin network>
> #       # client setup:
>         <Server "192.168.122.253" "25826">
>         </Server>
> </Plugin>
>
>
> ==> client netstat:
> udp        0      0 0.0.0.0:51442           0.0.0.0:*
>       7361/collectd
>
> ===> client tcpdump output below:
> tcpdump -i ens3 -p -n -s 1500 udp port 25826
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on ens3, link-type EN10MB (Ethernet), capture size 1500 bytes
> 19:40:46.658595 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1343
> 19:40:46.660715 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1331
> 19:40:46.662103 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1289
> 19:40:46.672435 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1341
> 19:40:56.656713 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1285
> 19:40:56.659586 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1344
> 19:40:56.660752 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1338
> 19:40:56.663490 IP 192.168.122.20.51442 > 192.168.122.253.25826: UDP,
> length 1323
>
>
>
> Thanks!!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.verplant.org/pipermail/collectd/attachments/20190525/d3a5d4d9/attachment.html>