The Not working data have no fields. Your line protocol has a measurement name and a tag set and a timestamp, but no field set. That's not valid line protocol.
You must have at least one key value pair, separated from the measurement+tagset and the timestamp by whitespace. Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=2184, currentIndexSizeInGB=0.000977,series=summary 1466416763000 Has whitespace only between the end of the tagset and the timestamp. There is no field set. On Sat, Jun 25, 2016 at 1:46 PM, <[email protected]> wrote: > Hi Gentlemen, > > I have been trying my all day today to insert some data to influxdb using > a custom python script. My test data is getting inserted successfully but > not other use cases. > > Working : > ---------- > > [tsm1wal] 2016/06/25 19:10:02 tsm1 WAL starting with 10485760 segment size > [tsm1wal] 2016/06/25 19:10:02 tsm1 WAL writing to > /var/lib/influxdb/wal/splunk_db/default/16 > [shard] 2016/06/25 19:10:02 /var/lib/influxdb/data/splunk_db/default/16 > database index loaded in 2.069µs > [httpd] 2016/06/25 19:10:02 127.0.0.1 - - [25/Jun/2016:19:10:02 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 204 0 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 6b007ed9-3b08-11e6-826c-000000000000 394.430592ms > [httpd] 2016/06/25 19:10:02 write body received by handler: > Splunk_Index_Influx,host=sj1010005186243.myserver.com,series=_internal > ev=333.0,eps=10.743802,kbps=2.890245 1466881765002 > [httpd] 2016/06/25 19:10:02 127.0.0.1 - - [25/Jun/2016:19:10:02 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 204 0 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 6b3d343d-3b08-11e6-826d-000000000000 12.69874ms > [httpd] 2016/06/25 19:10:02 write body received by handler: > Splunk_Index_Influx,host=sj1010005186243.myserver.com,series=_audit > ev=733.0,eps=23.649269,kbps=6.810627 1466881765002 > [httpd] 2016/06/25 19:10:02 127.0.0.1 - - [25/Jun/2016:19:10:02 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 204 0 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 6b3f961d-3b08-11e6-826e-000000000000 13.576595ms > [httpd] 2016/06/25 19:10:02 write body received by handler: > Splunk_Index_Influx,host=sj1010005186243.myserver.com,series=_introspection > ev=46.0,eps=1.483899,kbps=0.686316 1466881796002 > [httpd] 2016/06/25 19:10:02 127.0.0.1 - - [25/Jun/2016:19:10:02 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 204 0 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 6b421268-3b08-11e6-826f-000000000000 8.940615ms > > Not working : > --------------- > > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=30,currentIndexSizeInGB=0.105469,series=_internal > 1466883470000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 184 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 54238bd2-3b0c-11e6-8341-000000000000 558.522µs > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=14,currentIndexSizeInGB=0.192383,series=_introspection > 1466883474000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 187 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 5423f62d-3b0c-11e6-8342-000000000000 577.384µs > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=28,currentIndexSizeInGB=0.000977,series=_thefishbucket > 1466416763000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 187 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 54245b37-3b0c-11e6-8343-000000000000 839.81µs > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=7,currentIndexSizeInGB=0.000977,series=history > 1466416763000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 182 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 5424c357-3b0c-11e6-8344-000000000000 2.054409ms > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=2184,currentIndexSizeInGB=0.000977,series=main > 1466416763000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 181 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 5425651a-3b0c-11e6-8345-000000000000 1.873808ms > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=2184,currentIndexSizeInGB=0,series=splunklogger > 1466883481000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 181 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 5425ff95-3b0c-11e6-8346-000000000000 31.485151ms > [httpd] 2016/06/25 19:38:01 write body received by handler: > Splunk_Index_Influx,MaxIndexSizeInGB=488.281250,RetentionPeriodInDays=2184,currentIndexSizeInGB=0.000977,series=summary > 1466416763000 > [httpd] 2016/06/25 19:38:01 127.0.0.1 - - [25/Jun/2016:19:38:01 +0000] > POST /write?db=splunk_db&p=%5BREDACTED%5D&precision=ms HTTP/1.1 400 183 - > python-requests/2.3.0 CPython/2.7.11 Linux/2.6.32-358.el6.x86_64 > 542b430e-3b0c-11e6-8347-000000000000 3.520169ms > > Can you please suggest on what is wrong here and why the server is > responding with 400 message ? A kind response on this would be highly > appreciated. > > thanks, > Aneesh > > -- > Remember to include the InfluxDB version number with all issue reports > --- > You received this message because you are subscribed to the Google Groups > "InfluxDB" 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/8b32115d-75ea-40ab-a2b5-53611f165a8c%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 InfluxDB version number with all issue reports --- You received this message because you are subscribed to the Google Groups "InfluxDB" 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/CALGqCvMkON5cpmqi%2B_sE%2B7xtnsKY-KFbvc7%3DK4hHsC83OWnSqA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
