"error":"partial write:\nunable to parse

[Akira74]

Hi, in my nagflux log I see high amount of "partial write:\nunable to parse" errors. The NRPE Command output format of the check itself looks fine for me:

OK: All drives within bounds.|'C:\ %'=74%;92;95 'C:'=8.90799G;11.04;11.4;0;12

The line looks like this: [35m2017-01-13 02:02:42 Warn: Influx status: 400 Bad Request - {"error":"partial write:\nunable to parse 'metrics,host=109_TOC,service=HardDrives,command=check_nrpe,performanceLabel=C:\\,warn-fill=none,crit-fill=none,unit=G value=8.90499,warn=11.04,crit=11.4,min=0.0,max=12.0 1484262144000': invalid tag format\nunable to parse 'metrics,host=103_1_VR,service=HardDrives,command=check_nrpe,performanceLabel=C:\\,warn-fill=none,crit-fill=none,unit=G value=9.179,warn=27.6,crit=28.5,min=0.0,max=30.0 1484262144000':.....

in Thruk the value is shown but the performance graph not for the second value. I see, that after the "unit=G" value there is no "," inserted... is this the issue ?

Using version v0.2.7 together with OMD Any Idea? best regards Martin

[Griesbacher]

Hi Martin, the problem is the trailing backslash in your Performancelabel "performanceLabel=C:\". You are probably using nsclient, which could produce this kind of data. In this case you could change the behaviour as far as I know.

For more info have a look at the issue at InfluxDB: https://github.com/influxdata/influxdb/issues/6008

Greetings, Philip

[u238]

Hi, we have the same problem here. It's a InfluxDB problem. I think a workaround can be inserting a space if the Performancelabel has a trailing backslash.

[Griesbacher]

Hi, yes that's true and that's why there are these config parameters:

    NastyString = ""
    NastyStringToReplace = ""

So you could search and replace in all the labels/fields. But there is currently no hardcoded workaround for this problem, because I thought they will fix it...

[u238]

thank you very much for your response, this solved my problem!