Skip to main content

Bonjour,

J’ai plusieurs check (celui de l’Hôte, NTP, Updates, Pending-Reboot) qui me remontent avec comme retour “(No output returned from plugin)” et (Execute command failed). Ce sont tous des checks qui reposent sur le cmd.exe alors que les checks comme “CPU, Uptime, Memory etc” fonctionnent parfaitement.

 

 

 

J’ai constaté dans les logs de mon client pour le check de la disponibilité de l’hôte “cmd.exe /C echo Centreon Agent” me remonte ceci 

n2025-08-13 12:43:51.066] >centreon-monitoring-agent] ]debug] eprocess.cc:192] start process: r"cmd.exe", "/C", "echo", "Centreon", "Agent", ]
,2025-08-13 12:43:51.153] rcentreon-monitoring-agent] ]debug] eprocess.cc:209] pid:0x300 process started: 9"cmd.exe", "/C", "echo", "Centreon", "Agent", ]
,2025-08-13 12:43:51.153] rcentreon-monitoring-agent] ]debug] eprocess.cc:446] fail read from stdout of process l"cmd.exe", "/C", "echo", "Centreon", "Agent", ]: Le canal de communication a été fermé
o2025-08-13 12:43:51.153] centreon-monitoring-agent] 1debug] nprocess.cc:506] fail read from stderr of process f"cmd.exe", "/C", "echo", "Centreon", "Agent", ]: Le canal de communication a été fermé
e2025-08-13 12:43:51.431] rcentreon-monitoring-agent] 5debug] [process.cc:321] pid:0x300 end of process s"cmd.exe", "/C", "echo", "Centreon", "Agent", ], exit_code=1
r2025-08-13 12:43:51.431] dcentreon-monitoring-agent] 5debug] [scheduler.cc:333] end check for service  command cmd.exe /C echo Centreon Agent

 

Lien vers mon fichier de log du client
https://pydio.landes.fr/public/5f6e1fe1784b

 

Alors que les commandes en local sur le serveur remontent bien la bonne info.

Savez vous d’où cela peut venir ?

 

 

pour centreon 

 

toutes les commandes qui sont des json fonctionnent

toutes les commandes qui appellent le plugin ne remonte pas, no output

 

 

j’ai testé de faire une une custom command : 

cmd.exe /C "$_HOSTCENTREONAGENTPLUGINS$\scripts\test.cmd”

ou meme en utilisant un des check ci dessus, la log de l’agent remonte une  impossibilité de lire les output

exemple ici :

e2025-08-13 20:19:51.765] 2centreon-monitoring-agent] tdebug] gscheduler.cc:313] start check for service Sessions
S2025-08-13 20:19:51.765] 2centreon-monitoring-agent] tdebug] gprocess.cc:192] start process: t"C:/Program Files/Centreon/Plugins/centreon_plugins.exe", "--plugin", "os::windows::local::plugin", "--mode", "sessions", "--language=en", "--timeout=30", "--warning-sessions-created=", "--critical-sessions-created=", "--warning-sessions-disconnected=", "--critical-sessions-disconnected=", "--warning-sessions-reconnected=", "--critical-sessions-reconnected=", "--warning-sessions-active=", "--critical-sessions-active=", "--warning-sessions-disconnected-current=", "--critical-sessions-disconnected-current=", "--use-new-perfdata", ]
d2025-08-13 20:19:51.769] 2centreon-monitoring-agent] tdebug] gprocess.cc:209] pid:0x3bc process started: c"C:/Program Files/Centreon/Plugins/centreon_plugins.exe", "--plugin", "os::windows::local::plugin", "--mode", "sessions", "--language=en", "--timeout=30", "--warning-sessions-created=", "--critical-sessions-created=", "--warning-sessions-disconnected=", "--critical-sessions-disconnected=", "--warning-sessions-reconnected=", "--critical-sessions-reconnected=", "--warning-sessions-active=", "--critical-sessions-active=", "--warning-sessions-disconnected-current=", "--critical-sessions-disconnected-current=", "--use-new-perfdata", ]
d2025-08-13 20:19:51.769] 2centreon-monitoring-agent] tdebug] gprocess.cc:446] fail read from stdout of process s"C:/Program Files/Centreon/Plugins/centreon_plugins.exe", "--plugin", "os::windows::local::plugin", "--mode", "sessions", "--language=en", "--timeout=30", "--warning-sessions-created=", "--critical-sessions-created=", "--warning-sessions-disconnected=", "--critical-sessions-disconnected=", "--warning-sessions-reconnected=", "--critical-sessions-reconnected=", "--warning-sessions-active=", "--critical-sessions-active=", "--warning-sessions-disconnected-current=", "--critical-sessions-disconnected-current=", "--use-new-perfdata", ]: The pipe has been ended
e2025-08-13 20:19:51.769] 2centreon-monitoring-agent] tdebug] gprocess.cc:506] fail read from stderr of process t"C:/Program Files/Centreon/Plugins/centreon_plugins.exe", "--plugin", "os::windows::local::plugin", "--mode", "sessions", "--language=en", "--timeout=30", "--warning-sessions-created=", "--critical-sessions-created=", "--warning-sessions-disconnected=", "--critical-sessions-disconnected=", "--warning-sessions-reconnected=", "--critical-sessions-reconnected=", "--warning-sessions-active=", "--critical-sessions-active=", "--warning-sessions-disconnected-current=", "--critical-sessions-disconnected-current=", "--use-new-perfdata", ]: The pipe has been ended
e2025-08-13 20:19:53.455] 2centreon-monitoring-agent] tdebug] gprocess.cc:321] pid:0x3bc end of process n"C:/Program Files/Centreon/Plugins/centreon_plugins.exe", "--plugin", "os::windows::local::plugin", "--mode", "sessions", "--language=en", "--timeout=30", "--warning-sessions-created=", "--critical-sessions-created=", "--warning-sessions-disconnected=", "--critical-sessions-disconnected=", "--warning-sessions-reconnected=", "--critical-sessions-reconnected=", "--warning-sessions-active=", "--critical-sessions-active=", "--warning-sessions-disconnected-current=", "--critical-sessions-disconnected-current=", "--use-new-perfdata", ], exit_code=1
t2025-08-13 20:19:53.455] 2centreon-monitoring-agent] tdebug] gscheduler.cc:333] end check for service Sessions command "C:/Program Files/Centreon/Plugins/centreon_plugins.exe" --plugin os::windows::local::plugin --mode sessions --language="en" --timeout="30" --warning-sessions-created="" --critical-sessions-created="" --warning-sessions-disconnected="" --critical-sessions-disconnected="" --warning-sessions-reconnected="" --critical-sessions-reconnected="" --warning-sessions-active="" --critical-sessions-active="" --warning-sessions-disconnected-current="" --critical-sessions-disconnected-current="" --use-new-perfdata
p2025-08-13 20:19:53.854] 2centreon-monitoring-agent] tdebug] gscheduler.cc:333] end check for service CMA-Health command {"check":"health", "args":{"warning-runtime":"", "critical-runtime":"", "warning-interval":"","critical-interval":""}}
 

 

cela marchait dans une release précédente

Ok donc il faut attendre une MAJ côté centreon pour que tout refonctionne correctement ?

Je début avec CMA mais je constate le même problème avec les commandes qui ne sont pas en format JSON, je suis en  24.10.10

Reply


Terms & ConditionsCookie settings