Lua SDK - probe.config() spams the output logs with error "can't determine source encoding"
search cancel

Lua SDK - probe.config() spams the output logs with error "can't determine source encoding"

book

Article ID: 277676

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

In the Lua SDK there is a probe.config() function to parse probe configuration files.

When a Lua script calls probe.config() the nimCharsetAutoConvert message is reported once per line of the specified configuration file:

 

C:\Program Files (x86)\Nimsoft\probes\service\nas\scripts\test>..\..\..\..\..\sdk\nsa\nsa.exe test_probe_config
registered debug token init_mib, 1
Jul 27 14:31:44:827 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:827 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:843 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:843 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:858 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:858 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:874 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:874 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:889 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:905 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:921 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:983 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding
Jul 27 14:31:44:999 0 nsa: nimCharsetAutoConvert() -- can't determine source encoding

Is this meaningful?

Can it be disabled?

Resolution

This error message is not meaningful; it is related to a function which attempts to read the source encoding of a file to ensure it is in UTF-8 format.  The failure of this function does not cause any problems.

It cannot be disabled, but in NSA 20.60 it will be suppressed automatically.

Currently we do not have any specific ETA for NSA 20.60 but as of this writing (January 4 2024) it is expected within the next quarter.