search

aldenso / prtgZFSSAmetrics

PRTG Python Advanced script to get metrics from analytics datasets using ZFSSA Rest api
BSD 2-Clause "Simplified" License
1 stars 0 forks source link

The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231) #1

Open liv3010m opened 6 years ago

liv3010m commented 6 years ago

Hi, thanks for making this script and the other one (prtgZFSSAhealth).

We have a problem with both of them. We get the following result when running any of these: "XML: Structural error in xml file, 1 open items. -- JSON: The returned JSON does not match the expected structure (Invalid JSON.). (code: PE231)"

We are using PRTG version 17.3, should it work it?

Thank you!

aldenso commented 6 years ago

Hi, try enabling "Write result to disk" in the sensor's settings to see the returned message, the result should be located in a directory like this "C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)". Most usual errors are caused when people use the wrong sensor, maybe bad credentials, setting a frequency too low or using a non privileged user to retrieve the desired data.

liv3010m commented 6 years ago

Hi, thanks for the fast reply! I already tried that but the log file is not being created. Sensor type is set to advanced python, credentials were double checked and are provided in the additional parameters field (with the root user), the checking interval is set to every 60 seconds, and the sensor is of course applied to an ZFS appliance. Any other idea? Thanks in advance.

aldenso commented 6 years ago

It's complicated to know the reason without the log, you need to try to enable the option and get the log, you should check the OS logs and audits, maybe the user doesn't have enough privileges or something like that, but the log for this sensor must be available to debug.

liv3010m commented 6 years ago

Thanks Aldo, I will try tomorrow and report back!

leonliGit commented 3 years ago

Hi, @liv3010m :

I guess this issue has been solved. However, I'd like to share my experience because I've encountered the same issue.

My solution is very simple. Just clone the other well-worked sensor to replace the original one with the problem.

Hope this can help who has faced the same issue.