Skip to content

xcp-ng logs flooded with "became not supported"/"became supported" errors #5

Description

@meekser

I have 2 issues found after implementing this template:

  1. zabbix_server.log is flooded with below "became not supported"/"became supported" errors.
    Zabbix seems like not report any problems but logs are full of these:
    2404683:20240524:024302.813 item ":citrix.xenserver.py["-m","{$XENMASTER}","-u","{$XENUSERNAME}","-p","{$XENPASSWORD}","-t","host","-H","{HOST.NAME}","-c","value","-f","pif_aggr_rx"]" became not supported: Value of type "string" is not suitable for value type "Numeric (float)". Value "Exception ignored in: <function Lock.del at 0x7f71f0f4ef20>
    2404683:20240524:024402.191 item ":citrix.xenserver.py["-m","{$XENMASTER}","-u","{$XENUSERNAME}","-p","{$XENPASSWORD}","-t","host","-H","{HOST.NAME}","-c","value","-f","pif_aggr_rx"]" became supported

  2. some externally mounted / shared storage is erroring with similar exceptions in zabbix itself this time:
    Value of type "string" is not suitable for value type "Numeric (float)". Value ""

Any tips on what might be the issue and/or how to debug it? Thanks.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions