Skip to main content
Solved

Centreon 25.10 / RHEL 9.7 – Disk discovery issue with Windows NSClient05 RestAPI connector – call to missing script centreon_windows_local.pl

  • Apr 7, 2026 4:10 PM UTC
  • 3 replies
  • 40 views
Forum|alt.badge.img+5

Hello,

I am facing an issue on a fresh installation of Centreon 25.10 running on Red Hat Enterprise Linux 9.7.

Context

  • Centreon installation: fresh install / from scratch

  • OS: RHEL 9.7

  • Connector in use: Windows NSClient05 RestAPI

  • License: IT-100

  • Plugin Pack installed online from the web interface

  • Goal: use Windows disk discovery

Issue observed

When I open the discovery rule:

OS-Windows-NSClient05-Restapi-Disk-Name

I get the following error in the Centreon web interface:

Command execution issue: status code '127'
(command: /usr/lib/centreon/plugins//centreon_windows_local.pl --plugin=os::windows::local::plugin --mode=list-storages --hostname=127.0.0.1 --disco-format)

Checks already performed

The script called by the rule does not exist on the server:

ls /usr/lib/centreon/plugins/centreon_windows_local.pl
# ls: cannot access '/usr/lib/centreon/plugins/centreon_windows_local.pl': No such file or directory

The following plugin package is already installed:

dnf install centreon-plugin-Operatingsystems-Windows-Restapi
# Package centreon-plugin-Operatingsystems-Windows-Restapi-20260300-1.el9.noarch is already installed.

How can I download the script file ?

Best answer by Philippe

Hello, the Centreon Nsclient agent is deployed on remote Windows server.
It works fine. The problem is on discovery service.

For example, when I try to discover disk on remote Windows server I have a message :

 

 

View original

3 replies

Alexandre Belhomme
Forum|alt.badge.img+13

Hello, just to confirm, the connector you used is made for the NSClient++ Rest API, did you install the regular nsclient++ software on your windows host or specifically the one asked by Centreon precised at https://docs.centreon.com/fr/pp/integrations/plugin-packs/getting-started/how-to-guides/centreon-nsclient-tutorial/ ?

The exit code 127 is indeed related to command not found (i believe it’s the bash exit code for that). But not normal that it tried to call the centreon_windows_local.pm from your centreon poller, it should do it from within the nsclient++.

If you can share us details about that please.

Forum|alt.badge.img+5
  • Philippe
  • Author
  • Steward **
  • Answer
  • Apr 14, 2026 3:04 PM UTC

Hello, the Centreon Nsclient agent is deployed on remote Windows server.
It works fine. The problem is on discovery service.

For example, when I try to discover disk on remote Windows server I have a message :

 

 

Alexandre Belhomme
Forum|alt.badge.img+13

I’m not very familiar with the discovery module, here i’m unsure if the 403 is returned by centreon or from the NSClient REST API. 

Can you look manually if the api is reachable ?

Terms & ConditionsAccessibility statement