Skip to main content

Bonjour,

 

En mettant en place la supervision pour nos serveurs d‘Exchange en utilisant le plugin-pack dédié, tous les checks fonctionnent sauf celui de Queues. En fait, avec le mode debug, j’ai le message d’erreur suivant :

UNKNOWN: Cannot decode json response: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "#< CLIXML ;{"nextho...") at C:\Windows\TEMP\par-4844564d5347333824\cache-3b5388704b9e4d63032f19c5b7e4f211de0db869\inc\lib/apps/microsoft/exchange/local/mode/queues.pm line 136.

Est-ce que quelqu’un a des idées sur l’origine du problème ?

En vous remerciant par avance.

 

Zequan

 

Hi @huangzequan, Please ask your problem in English. This will help all other non-french speaking users who have the same issue to benefit from the solutions that will be proposed. Thank you for your understanding


Hello @huangzequan 

Coul you provide the --ps-exec-only result (it’s a new option to add to your command) ?


Hi @Fabrix,

So here is my problem in English :

When i was trying earlier to supervise my Exchange server with the corresponded plugin-pack, all checks works out fine except the check for exchange queues. In fact, by using the debug option i get the following error message :

UNKNOWN: Cannot decode json response: malformed JSON string, neither tag, array, object, number, string or atom, at character offset 0 (before "#< CLIXML [{"nextho...") at C:\Windows\TEMP\par-4844564d5347333824\cache-3b5388704b9e4d63032f19c5b7e4f211de0db869\inc\lib/apps/microsoft/exchange/local/mode/queues.pm line 136.

So i wonder if anyone has any idea of what could be the origine of the problem.


Hello @Kriko,

Here is the error message returned with the extraoption “--ps-exec-only” :

UNKNOWN: Cannot decode json response: malformed UTF-8 character in JSON string, at character offset 1041 (before "\x{fffd}0080\\u009Ap...") at /usr/lib/centreon/plugins//centreon_nsclient_restapi.pl line 162.

For me it’s the same message with the extraoption “--verbose”.


Hello,

I just dicovered that by lauching the command directly on the centreon server i get a “403 forbidden”.

And for other checks which work already on the centreon web interface, i also get the same result “403 forbidden” by lauching the corresponded commands...


Sorry, concerning 403 fobidden i just forgot to change the password which is *** when i copied the command.

And by accidently deleting the “--verbose” option from the extraoption, it works ! I added it to get more info but apparently it blocked centreon to decode correctly the json response.

But when i do a --help for the command i see that --verbose is supported.


Reply