http://docs.influxdata.com/influxdb/v1.1/administration/logs/ describes how logs are configured.
On Wed, Nov 16, 2016 at 11:43 AM, <[email protected]> wrote: > On Wednesday, 16 November 2016 13:27:21 UTC-5, Sean Beckett wrote: > > What's in the InfluxDB logs for those write attempts? > > > > > > On Wed, Nov 16, 2016 at 11:04 AM, ThisUser <[email protected]> wrote: > > I've got influxdb running on my internal network and it works fine for > my internal clients. But I am unable to get data from my external clients > on AWS EC2. I can see with tcpdump that the packets are being received by > the influxdb server, but the data doesn't load into the database. I do see > some "bad udp cksum" errors in tcpdump. I've tried some suggestions from > the internets and I can't get rid of those errors, and some sources say > they may not be an issue. In the following output 10.0.0.10 is my external > client, 192.168.0.211 is my internal client, 192.168.0.217 is my influxdb > server (ip addresses are not real). > > > > > > > > tcpdump: listening on any, link-type LINUX_SLL (Linux cooked), capture > size 65535 bytes > > > > 13:00:54.104685 IP (tos 0x0, ttl 44, id 59067, offset 0, flags [DF], > proto UDP (17), length 1366) > > > > 10.0.0.10.45154 > 192.143.74.217.25826: UDP, length 1338 > > > > 13:00:54.105499 IP (tos 0x0, ttl 44, id 59068, offset 0, flags [DF], > proto UDP (17), length 1366) > > > > 10.0.0.10.45154 > 192.143.74.217.25826: UDP, length 1338 > > > > 13:00:56.681054 IP6 (hlim 64, next-header UDP (17) payload length: 1343) > ::1.33092 > ::1.25826: [bad udp cksum 0x0552 -> 0xaf26!] UDP, length 1335 > > > > 13:00:56.683873 IP6 (hlim 64, next-header UDP (17) payload length: 1314) > ::1.33092 > ::1.25826: [bad udp cksum 0x0535 -> 0x607b!] UDP, length 1306 > > > > 13:01:00.451326 IP (tos 0x0, ttl 64, id 28105, offset 0, flags [DF], > proto UDP (17), length 1328) > > > > 192.168.0.211.52913 > 192.168.0.217.25826: UDP, length 1300 > > > > 13:01:00.456388 IP (tos 0x0, ttl 64, id 28106, offset 0, flags [DF], > proto UDP (17), length 1369) > > > > 192.168.0.211.52913 > 192.168.0.217.25826: UDP, length 1341 > > > > 13:01:00.456420 IP (tos 0x0, ttl 64, id 28107, offset 0, flags [DF], > proto UDP (17), length 1327) > > > > 192.168.0.211.52913 > 192.168.0.217.25826: UDP, length 1299 > > > > 13:01:00.457079 IP (tos 0x0, ttl 64, id 28108, offset 0, flags [DF], > proto UDP (17), length 1345) > > > > 192.168.0.211.52913 > 192.168.0.217.25826: UDP, length 1317 > > > > 13:01:04.104660 IP (tos 0x0, ttl 44, id 59069, offset 0, flags [DF], > proto UDP (17), length 1353) > > > > 10.0.0.10.45154 > 192.143.74.217.25826: UDP, length 1325 > > > > 13:01:04.105118 IP (tos 0x0, ttl 44, id 59070, offset 0, flags [DF], > proto UDP (17), length 1353) > > > > 10.0.0.10.45154 > 192.143.74.217.25826: UDP, length 1325 > > > > 13:01:06.680680 IP6 (hlim 64, next-header UDP (17) payload length: 1353) > ::1.33092 > ::1.25826: [bad udp cksum 0x055c -> 0x4f6a!] UDP, length 1345 > > > > 13:01:06.682883 IP6 (hlim 64, next-header UDP (17) payload length: 1336) > ::1.33092 > ::1.25826: [bad udp cksum 0x054b -> 0x107a!] UDP, length 1328 > > > > > > > > -- > > > > Remember to include the version number! > > > > --- > > > > You received this message because you are subscribed to the Google > Groups "InfluxData" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > Visit this group at https://groups.google.com/group/influxdb. > > > > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/fe4c0b5a-6e28-4e2c-8a14-d2ceb37c86e4%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > -- > > > > > > Sean Beckett > > Director of Support and Professional Services > > InfluxDB > > I'm running InfluxDB 1.0.2 on CentOS 7 and I don't see anything logged to > /var/log/messages beyond messages during startup. Is there some additional > logging I can enable to see more about what's happening with the incoming > collectd data? I set these to true, but the only additional logging I see > is when I run queries in the database (select, etc): > > trace-logging-enabled > query-log-enabled > > -- > Remember to include the version number! > --- > You received this message because you are subscribed to the Google Groups > "InfluxData" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/influxdb. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/influxdb/f9e0f90a-bb0b-4b10-9334-84c6c6d11985%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Sean Beckett Director of Support and Professional Services InfluxDB -- Remember to include the version number! --- You received this message because you are subscribed to the Google Groups "InfluxData" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/influxdb. To view this discussion on the web visit https://groups.google.com/d/msgid/influxdb/CALGqCvPWM8piYGrRTah3j7MKhxt0HrdasdF1_BaQiQEadYOv7A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
