Power

 View Only

  • 1.  nextract Plus partial write to influx

    Posted Fri March 24, 2023 09:32 AM

    Hi,

    my env is on linux; nextract_plus version 41, python 3.6, influx 1.8.9 (didn't found v1.9 for linux), grafana 9.4.7.

    Script finishes with partial writes to influx, resulting 3 out of 4 servers been inserted correctly.

    nextract_plus.err log output:

    Traceback (most recent call last):
      File "/home/lpar2rrd/nextractplus_v41/nextract_plus.py", line 609, in <module>
        client.write_points(entry)
      File "/usr/local/lib/python3.6/site-packages/influxdb/client.py", line 599, in write_points
        consistency=consistency)
      File "/usr/local/lib/python3.6/site-packages/influxdb/client.py", line 676, in _write_points
        protocol=protocol
      File "/usr/local/lib/python3.6/site-packages/influxdb/client.py", line 410, in write
        headers=headers
      File "/usr/local/lib/python3.6/site-packages/influxdb/client.py", line 369, in request
        raise InfluxDBClientError(err_msg, response.status_code)
    influxdb.exceptions.InfluxDBClientError: 400: {"error":"partial write: field type conflict: input field \"physicalLocation\" on measurement \"vios_storage_physical\" is type float, already exists as type string dropped=478"}

    I tried inserting to new database, still getting same error.

    Is this because of 1.8.9 influx version or something else?



    ------------------------------
    Ivan Tuda
    ------------------------------



  • 2.  RE: nextract Plus partial write to influx

    Posted Mon March 27, 2023 09:23 AM

    Ivan,

     

    You are in wrong community. You need to find right IBM community. You need to post in Linux community.




    Original Message


  • 3.  RE: nextract Plus partial write to influx

    Posted Tue March 28, 2023 04:09 AM

    Hi,

    Better to contact Nigel Griffiths (me) via email and stated on the njmon webpage https://nmon.sourceforge.net/pmwiki.php?n=Site.Njmon

    • nigel ar griffiths at hot mail dot com (remove the spaces and replace at and dot with the characters.

    You tried the right thing. for some reason, the HMC REST API returned a number first and then a string.

    I hope to get to fix this is a couple of days. Sorry for the delay.
    Look for version 42.

    Cheers,



    ------------------------------
    Nigel Griffiths
    ------------------------------

    Original Message