Skip to main content

Hi 

I have had a problem with centreon updates for some time. My version is 24.10.8. The problem is in the vmware infrastructure monitoring plugin. Previously (based on the centreon_vmware.pm file) everything worked fine. After updates (from several versions within 24.10) the centreon_vmware service does not want to start. When I change the option to old in the /etc/default/centreon_vmware file and restore the centreon_vmware.pm file, everything returns to normal.

Here is the configuration and logs after updates (the last one to 24.10.8), which do not work well.

My instance: Centreon 24.10.8, Debian 12.

 

$ ls -l
razem 44
-rw-rw---- 1 www-data www-data 1287 2018-10-17 centreon.conf.php
-rw-r----- 1 centreon centreon 390 06-24 08:25 centreontrapd.pm
-rw-rw-r-- 1 centreon centreon 390 2024-05-16 centreontrapd.pm.dpkg-dist
-rw-rw---- 1 centreon-gorgone centreon 626 06-24 08:24 centreon_vmware.json
-rw-r--r-- 1 centreon centreon 812 03-28 09:37 centreon_vmware.pm.deprecated
drwxrwxr-x 2 centreon centreon 4096 2024-05-15 config.d
-rw------- 1 root root 103 04-18 15:14 config.yaml
-rw-rw---- 1 centreon centreon 779 06-24 08:25 conf.pm
-rw-rw-r-- 1 centreon centreon 0 2024-05-16 conf.pm.dpkg-dist
-rw-rw-r-- 1 centreon centreon 0 2020-02-14 conf.pm.rpmnew
-rw-rw-r-- 1 centreon centreon 590 06-18 09:16 instCentPlugins.conf
-rw-rw-r-- 1 centreon centreon 909 06-18 09:16 instCentWeb.conf
drwxrwxr-x 2 centreon centreon 4096 2023-06-05 license.d

 

$ sudo cat centreon_vmware.json
{
"vsphere_server" :
{
"url" : "https://vcenter02-drc.xxx/sdk",
"name" : "drc",
"password" : "xxx",
"username" : "centreon@vsphere.local"
},
{
"url" : "https://vcenter01-pdc.xxx/sdk",
"password" : "xxx",
"name" : "pdc",
"username" : "centreon@vsphere.local"
}
],
"port" : 5700
}
sudo cat /etc/default/centreon_vmware
# centreon_vmware command line options
#OPTIONS="--logfile=/var/log/centreon_vmware.log --severity=error"
+OPTIONS="--config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=info"

 

I have entries in the logs

$ sudo tail -f /var/log/centreon/centreon_vmware.log 

r2025-03-28 09:09:40] 4error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
r2025-03-28 09:09:40] 4error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
r2025-03-28 09:09:41] 4error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.

 

Do you have any ideas what happened? As I wrote earlier, returning to the centreon_vmware.pm file solves the problem, but I still see these entries in the logs, but I can monitor the datastore

hello ​@centreon_s 
Thanks for reaching to us !

Could you share the anonymized version of the file centreon_vmware.pm and the logs when you execute the daemon with the old file ?

Can you also share the version you updated from for the centreon application and the plugins ?

 

Regards,


Hello ​@centreon_s, I came to the forum for a similar issue which I think is related to yours. Maybe we can help each other.

I’m also on the latest Centreon version and I realised that my centreon_vmware.pm config got deleted since one of the latest updates (don’t know which one exactly).

It seems that now the config must be managed from the Centreon UI according to the documentation:

https://docs.centreon.com/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration/

The problem is I cannot find the menu “Additional configuration” anywhere in my install.

Can anybody help? 


Hi  ​@pressor

Indeed, since 24.10.0, you must declare all vCenter/ESX configurations using the Configuration > Additional connector configurations page before deploying the configuration of the corresponding poller. 

 

which version are you using ? You should check the dedicated ACL Menu for Additional configuration : Configuration > Connectors > Additional Configurations (or Additional Connector Configuration, depending on your version) 

 

Tell me if it helps.


 

Hello ​@fmattes , thanks for your reply. As you can see I have no “Connector” menu under “Configuration” ?


Hello, 

Did you check the ACL Menu in Administration > ACL > Menu ?

Is Connector enabled for your profile ? 

Are you in Centreon onPrem or Cloud ? 


Hello ​@fmattes I created an ACL for the group ALL with all the checkmarks for every existing menu and I added all the profiles to the group. I still have no access to the menu.

The menu doesn’t even show up in the ACL Menu list.

It’s centreon onPrem that I installed using the OVF (Alma Linux).


@fmattes can you send me a screenshot of your web interface?


hello ​@centreon_s 
Thanks for reaching to us !

Could you share the anonymized version of the file centreon_vmware.pm and the logs when you execute the daemon with the old file ?

Can you also share the version you updated from for the centreon application and the plugins ?

 

Regards,

%centreon_vmware_config = (
vsphere_server => {
'pdc' => {'url' => 'https://vcenter01-pdc/sdk',
'username' => 'centreon@vsphere.local',
'password' => 'password'},
'drc' => {'url' => 'https://vcenter02-drc/sdk',
'username' => 'centreon@vsphere.local',
'password' => 'password'},
'hci' => {'url' => 'https://vcenter03-hci/sdk',
'username' => 'centreon@vsphere.local',
'password' => 'password'}
},
port => 5700
);

1;

My logs from the VMware Centeron daemon are currently empty. The last log is from 2025-03-28

 

$ systemctl status centreon_vmware.service 
● centreon_vmware.service - Centreon VMWare
Loaded: loaded (/lib/systemd/system/centreon_vmware.service; enabled; preset: enabled)
Active: active (running) since Mon 2025-07-14 11:11:20 CEST; 1 day 3h ago
Main PID: 4114413 (perl)
Tasks: 28 (limit: 7009)
Memory: 168.7M
CPU: 35min 51.172s
CGroup: /system.slice/centreon_vmware.service
├─4114413 /usr/bin/perl /usr/bin/centreon_vmware.pl --logfile=/var/log/centreon_vmware.log --severity=error
├─4114422 /usr/bin/perl /usr/bin/centreon_vmware.pl --logfile=/var/log/centreon_vmware.log --severity=error
├─4114429 /usr/bin/perl /usr/bin/centreon_vmware.pl --logfile=/var/log/centreon_vmware.log --severity=error
└─4114436 /usr/bin/perl /usr/bin/centreon_vmware.pl --logfile=/var/log/centreon_vmware.log --severity=error

 

 

$ sudo tail -f  /var/log/centreon/centreon_vmware.log.1 -n 200

.2025-03-28 04:29:33] error] 'pdc' SOAP request error - possibly a protocol issue: Status read failed: Connection reset by peer at /usr/share/perl5/Net/HTTP/Methods.pm line 288.
e2025-03-28 04:45:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 04:46:03] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 04:46:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:00:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:01:03] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:01:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:15:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:16:03] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:16:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:30:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:31:03] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:31:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:45:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:45:31] error] 'drc' SOAP request error - possibly a protocol issue: Status read failed: Connection reset by peer at /usr/share/perl5/Net/HTTP/Methods.pm line 288.
e2025-03-28 05:46:03] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 05:46:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:00:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:00:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:01:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:02:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:15:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:16:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:17:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:30:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:30:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:31:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:32:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:45:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:45:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:46:13] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 06:47:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:00:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:01:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:02:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:15:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:15:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:16:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:17:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:31:01] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:31:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:32:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:46:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:47:01] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 07:47:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:01:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:02:01] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:02:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:16:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:17:01] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:17:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:31:43] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:32:01] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:32:02] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:38:58] error] The given configuration file /var/lib/centreon/vault/vault.json does not exist. Passwords won't be retrieved from Centreonvault. Ignore this if you don't use Centreonvault.
2025-03-28 08:39:25] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:39:25] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:39:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:39:32] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:54:25] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:54:25] error] 'hci' SOAP request error - possibly a protocol issue: Status read failed: Connection reset by peer at /usr/share/perl5/Net/HTTP/Methods.pm line 288.
e2025-03-28 08:54:31] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 08:54:33] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 09:09:34] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 09:09:40] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 09:09:40] error] 'drc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.
e2025-03-28 09:09:41] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.

 


I don't have a connector defined in the GUI (configuration->connectors->additional configurations). I'm using vcenter8


Hello ​@centreon_s, I came to the forum for a similar issue which I think is related to yours. Maybe we can help each other.

I’m also on the latest Centreon version and I realised that my centreon_vmware.pm config got deleted since one of the latest updates (don’t know which one exactly).

It seems that now the config must be managed from the Centreon UI according to the documentation:

https://docs.centreon.com/pp/integrations/plugin-packs/getting-started/how-to-guides/additional-connector-configuration/

The problem is I cannot find the menu “Additional configuration” anywhere in my install.

Can anybody help? 

Hi,

Yes, during the update, the pm file is replaced with json. But I restore it again, i.e., I delete the json file and use the .pm file. I restart the daemon and everything is fine.


The problem is I cannot find the menu “Additional configuration” anywhere in my install.

Can anybody help? 

 

Configuration->Connectors->Additional Configuration 


@centreon_s Which is the page id?

192.xx/centreon/main.php?p=60901

For example this is the Pollers configuration page.


Hello, latest news:

  • I reset the password on the vSphere appliance
  • I checked the .json file which has been correctly migrated
  • I restarted the centreon_vmware.service

Now the services are working okay. It was something about the password which seems to expire after x days or months.

I still cannot find the new Configuration → Connector menu on my install, but I guess I don’t need it for the time being.

I have one last issue with the proc-gorgone and the proc-centreontrapd services which are reported to be down. This has something to do with vmware it seems. I’m currently troubleshooting the issue.


Hello ​@centreon_s 

 

 

I see in the .pm file the url is 'https://vcenter02-drc.xxx/sdk' and 'https://vcenter02-drc/sdk' in the json. I suppose it’s the same url but anonymized differently ?

 

could you update the systemd config to enable debug ?

On alma/redhat it the file /etc/sysconfig/centreon_vmware

on debian it the file /etc/default/centreon_vmware

 

In this file there should be a part `--severity=error` replace it with `--severity=debug`

Then restart centreon_vmware daemon.

You should have more log of what the daemon is doing.


Hello, latest news:

  • I reset the password on the vSphere appliance
  • I checked the .json file which has been correctly migrated
  • I restarted the centreon_vmware.service

Now the services are working okay. It was something about the password which seems to expire after x days or months.

I still cannot find the new Configuration → Connector menu on my install, but I guess I don’t need it for the time being.

I have one last issue with the proc-gorgone and the proc-centreontrapd services which are reported to be down. This has something to do with vmware it seems. I’m currently troubleshooting the issue.

 

Hello ​@pressor 

 

Can you enable debug for gorgoned and check if you can send maintenance and new configuration to your poller ?

 

To enable debug change the file 

On alma/redhat it the file /etc/sysconfig/gorgoned

on debian it the file /etc/default/gorgoned

 

replace  `--severity=error` with `--severity=debug`
Then restart the service

can you share the systemctl status gorgoned output, the logs and the files /etc/centreon-gorgone/config.d/* in a new thread so we can keep things organized  ?


@evanadam I restarted the server and the gorgone services went up without any change on my side.

 

Thanks a lot for your support.


Hi

Yes, the anonymization didn't work for me 🙂. I changed the logging level. I'm attaching the start of the centeron_vmware service.

 

sudo head /var/log/centreon/centreon_vmware.log -n 200
>2025-07-22 09:08:05] debug] Reading configuration from /etc/centreon/centreon_vmware.pm
>2025-07-22 09:08:05] info] No vault config file given. Applying default: /var/lib/centreon/vault/vault.json
>2025-07-22 09:08:05] debug] Vault config file /var/lib/centreon/vault/vault.json exists. Creating the vault object.
>2025-07-22 09:08:05] error] The given configuration file /var/lib/centreon/vault/vault.json does not exist. Passwords won't be retrieved from Centreonvault. Ignore this if you don't use Centreonvault.
>2025-07-22 09:08:05] info] Something happened during init() method that makes Centreonvault not usable. Ignore this if you don't use Centreonvault.
>2025-07-22 09:08:05] debug] Not using credstore.
>2025-07-22 09:08:05] debug] Retrieving secret: username
>2025-07-22 09:08:05] debug] Retrieving secret: password
>2025-07-22 09:08:05] debug] Retrieving secret: username
>2025-07-22 09:08:05] debug] Retrieving secret: password
>2025-07-22 09:08:05] debug] Retrieving secret: username
>2025-07-22 09:08:05] debug] Retrieving secret: password
>2025-07-22 09:08:05] info] Configuration file /etc/centreon/centreon_vmware.pm has been read correctly and has 3 entries.
>2025-07-22 09:08:05] debug] centreon_vmware launched....
>2025-07-22 09:08:05] debug] PID: 1866821
>2025-07-22 09:08:05] debug] Creating vSphere child for pdc
>2025-07-22 09:08:05] info] Create vsphere sub-process for 'pdc'
>2025-07-22 09:08:05] debug] Creating vSphere child for hci
>2025-07-22 09:08:05] info] Create vsphere sub-process for 'hci'
>2025-07-22 09:08:05] info] 'pdc' ZMQ init begin
>2025-07-22 09:08:05] debug] Creating vSphere child for drc
>2025-07-22 09:08:05] info] Create vsphere sub-process for 'drc'
>2025-07-22 09:08:05] info] 'pdc' init done
>2025-07-22 09:08:05] info] 'pdc' Vsphere connection in progress
>2025-07-22 09:08:05] info] 'hci' ZMQ init begin
>2025-07-22 09:08:05] info] 'hci' init done
>2025-07-22 09:08:05] info] 'hci' Vsphere connection in progress
>2025-07-22 09:08:05] info] Server accepting clients]
>2025-07-22 09:08:05] debug] Global loop starting...
>2025-07-22 09:08:05] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:05] info] 'drc' ZMQ init begin
>2025-07-22 09:08:05] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:05] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:05] info] 'drc' init done
>2025-07-22 09:08:05] info] 'drc' Vsphere connection in progress
>2025-07-22 09:08:05] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:06] info] 'drc' Vsphere connection ok
>2025-07-22 09:08:06] info] 'drc' Create perf counters cache in progress
>2025-07-22 09:08:06] info] 'hci' Vsphere connection ok
>2025-07-22 09:08:06] info] 'hci' Create perf counters cache in progress
>2025-07-22 09:08:06] info] 'pdc' Vsphere connection ok
>2025-07-22 09:08:06] info] 'pdc' Create perf counters cache in progress
>2025-07-22 09:08:06] info] 'drc' Create perf counters cache done
>2025-07-22 09:08:06] info] 'pdc' Create perf counters cache done
>2025-07-22 09:08:06] info] 'hci' Create perf counters cache done
>2025-07-22 09:08:10] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:15] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:17] info] connector 'pdc' Receiving order to stop...
>2025-07-22 09:08:17] info] 1866821 Receiving order to stop...
>2025-07-22 09:08:17] info] connector 'drc' Receiving order to stop...
>2025-07-22 09:08:17] info] Send -TERM signal to 'drc' process..
>2025-07-22 09:08:17] info] connector 'drc' Receiving order to stop...
>2025-07-22 09:08:17] info] Send -TERM signal to 'pdc' process..
>2025-07-22 09:08:17] info] Send -TERM signal to 'hci' process..
>2025-07-22 09:08:17] info] connector 'pdc' Receiving order to stop...
>2025-07-22 09:08:17] debug] 3 child(ren) found. Stop ? : 1
>2025-07-22 09:08:17] info] connector 'hci' Receiving order to stop...
>2025-07-22 09:08:17] info] Sub-process for 'hci' dead ???!!
>2025-07-22 09:08:17] debug] 2 child(ren) found. Stop ? : 1
>2025-07-22 09:08:17] info] Sub-process for 'pdc' dead ???!!
>2025-07-22 09:08:17] debug] 1 child(ren) found. Stop ? : 1
>2025-07-22 09:08:17] info] Sub-process for 'drc' dead ???!!
>2025-07-22 09:08:17] debug] 0 child(ren) found. Stop ? : 1
>2025-07-22 09:08:17] info] Quit main process
>2025-07-22 09:08:17] debug] Reading configuration from /etc/centreon/centreon_vmware.pm
>2025-07-22 09:08:17] info] No vault config file given. Applying default: /var/lib/centreon/vault/vault.json
>2025-07-22 09:08:17] debug] Vault config file /var/lib/centreon/vault/vault.json exists. Creating the vault object.
>2025-07-22 09:08:17] error] The given configuration file /var/lib/centreon/vault/vault.json does not exist. Passwords won't be retrieved from Centreonvault. Ignore this if you don't use Centreonvault.
>2025-07-22 09:08:17] info] Something happened during init() method that makes Centreonvault not usable. Ignore this if you don't use Centreonvault.
>2025-07-22 09:08:17] debug] Not using credstore.
>2025-07-22 09:08:17] debug] Retrieving secret: username
>2025-07-22 09:08:17] debug] Retrieving secret: password
>2025-07-22 09:08:17] debug] Retrieving secret: username
>2025-07-22 09:08:17] debug] Retrieving secret: password
>2025-07-22 09:08:17] debug] Retrieving secret: username
>2025-07-22 09:08:17] debug] Retrieving secret: password
>2025-07-22 09:08:17] info] Configuration file /etc/centreon/centreon_vmware.pm has been read correctly and has 3 entries.
>2025-07-22 09:08:17] debug] centreon_vmware launched....
>2025-07-22 09:08:17] debug] PID: 1866998
>2025-07-22 09:08:17] debug] Creating vSphere child for hci
>2025-07-22 09:08:17] info] Create vsphere sub-process for 'hci'
>2025-07-22 09:08:17] debug] Creating vSphere child for pdc
>2025-07-22 09:08:17] info] Create vsphere sub-process for 'pdc'
>2025-07-22 09:08:17] info] 'hci' ZMQ init begin
>2025-07-22 09:08:17] info] 'hci' init done
>2025-07-22 09:08:17] info] 'hci' Vsphere connection in progress
>2025-07-22 09:08:17] debug] Creating vSphere child for drc
>2025-07-22 09:08:17] info] Create vsphere sub-process for 'drc'
>2025-07-22 09:08:17] info] 'pdc' ZMQ init begin
>2025-07-22 09:08:17] info] 'pdc' init done
>2025-07-22 09:08:17] info] 'pdc' Vsphere connection in progress
>2025-07-22 09:08:17] info] Server accepting clients]
>2025-07-22 09:08:17] debug] Global loop starting...
>2025-07-22 09:08:17] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:17] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:17] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:17] info] 'drc' ZMQ init begin
>2025-07-22 09:08:17] info] 'drc' init done
>2025-07-22 09:08:17] info] 'drc' Vsphere connection in progress
>2025-07-22 09:08:17] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:17] info] 'pdc' Vsphere connection ok
>2025-07-22 09:08:17] info] 'pdc' Create perf counters cache in progress
>2025-07-22 09:08:17] info] 'drc' Vsphere connection ok
>2025-07-22 09:08:17] info] 'drc' Create perf counters cache in progress
>2025-07-22 09:08:17] info] 'hci' Vsphere connection ok
>2025-07-22 09:08:17] info] 'hci' Create perf counters cache in progress
>2025-07-22 09:08:17] info] 'drc' Create perf counters cache done
>2025-07-22 09:08:17] info] 'pdc' Create perf counters cache done
>2025-07-22 09:08:17] info] 'hci' Create perf counters cache done
>2025-07-22 09:08:18] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:18] info] vpshere 'drc' handler asking: {"warning-status":null,"filter_counters_block":null,"warning-usage":null,"warning-usage-prct":null,"timeout":null,"units":"","time_shift":0,"display_ok_counters":null,"container":"drc","connector_hostname":"localhost","vsphere_username":null,"identity":"client-e11d53cb365245ee87704de5c7eb9b54","free":null,"warning_connector_status":null,"case_insensitive":null,"critical-status":null,"critical-provisioned":null,"unknown-provisioned":null,"unknown-usage-free":null,"unknown_connector_status":null,"vsphere_address":null,"critical-usage-prct":"88","scope_datacenter":null,"filter_host":null,"datastore_name":"vault_fsa_archive_01","critical_connector_status":null,"warning-usage-free":null,"warning-provisioned":null,"critical-usage":null,"refresh":null,"vsphere_password":null,"unknown-usage":null,"unknown-usage-prct":null,"unknown-status":"$values->{accessible} !~ /^true|1$/i","filter":null,"critical-usage-free":null,"list_counters":null,"command":"datastoreusage","filter_counters":null,"connector_port":"5700","sampling_period":null}
>2025-07-22 09:08:18] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:19] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:19] info] vpshere 'pdc' handler asking: {"connector_hostname":"localhost","filter_counters":null,"case_insensitive":null,"container":"pdc","vsphere_username":null,"vsphere_address":null,"vsphere_password":null,"display_ok_counters":null,"cluster_name":null,"critical_connector_status":null,"identity":"client-132f629636c34719bdfe1e3ad4f85da4","time_shift":0,"command":"statuscluster","unknown_connector_status":null,"warning_connector_status":null,"filter_counters_block":null,"scope_datacenter":null,"connector_port":"5700","list_counters":null,"warning-status":"$values->{overall_status} =~ /yellow/i || $values->{vsan_status} =~ /yellow/i","timeout":null,"unknown-status":"$values->{overall_status} =~ /gray/i || $values->{vsan_status} =~ /gray/i","critical-status":"$values->{overall_status} =~ /red/i || $values->{vsan_status} =~ /red/i","filter":null,"sampling_period":null}
>2025-07-22 09:08:19] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:19] info] vpshere 'pdc' handler asking: {"critical-usage":null,"filter_host":null,"warning_connector_status":null,"critical-usage-free":null,"sampling_period":null,"refresh":null,"vsphere_password":null,"filter":null,"warning-usage-prct":null,"timeout":null,"connector_hostname":"localhost","container":"pdc","display_ok_counters":null,"unknown_connector_status":null,"identity":"client-26a9b5c62d4c4eeea0b9e7924b94cb7c","critical_connector_status":null,"unknown-usage-prct":null,"case_insensitive":null,"connector_port":"5700","unknown-usage":null,"filter_counters_block":null,"warning-usage-free":null,"free":null,"unknown-provisioned":null,"warning-usage":null,"unknown-usage-free":null,"command":"datastoreusage","warning-provisioned":null,"units":"","vsphere_username":null,"vsphere_address":null,"warning-status":null,"critical-status":null,"unknown-status":"$values->{accessible} !~ /^true|1$/i","list_counters":null,"scope_datacenter":null,"critical-usage-prct":"85","time_shift":0,"datastore_name":"VMware_PDC_FotoWare","critical-provisioned":null,"filter_counters":null}
>2025-07-22 09:08:19] error] 'pdc' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.


>2025-07-22 09:08:19] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:19] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:24] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:29] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:29] info] vpshere 'hci' handler asking: {"timeout":null,"vsphere_password":null,"list_counters":null,"command":"statuscluster","critical-status":"$values->{overall_status} =~ /red/i || $values->{vsan_status} =~ /red/i","vsphere_address":null,"container":"hci","filter":null,"cluster_name":null,"case_insensitive":null,"display_ok_counters":null,"warning-status":"$values->{overall_status} =~ /yellow/i || $values->{vsan_status} =~ /yellow/i","unknown_connector_status":null,"sampling_period":null,"time_shift":0,"filter_counters":null,"critical_connector_status":null,"scope_datacenter":null,"unknown-status":"$values->{overall_status} =~ /gray/i || $values->{vsan_status} =~ /gray/i","warning_connector_status":null,"identity":"client-32b1cdd54ca843cfb8bd826c3741b311","filter_counters_block":null,"connector_port":"5700","connector_hostname":"localhost","vsphere_username":null}
>2025-07-22 09:08:29] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:34] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:39] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:42] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:42] info] vpshere 'hci' handler asking: {"units":"","timeout":null,"filter_counters_block":null,"sampling_period":null,"unknown-status":"$values->{accessible} !~ /^true|1$/i","critical-usage":null,"critical-usage-free":null,"free":null,"warning-status":null,"vsphere_username":null,"warning-provisioned":null,"unknown-usage-prct":null,"time_shift":0,"critical-provisioned":null,"connector_hostname":"localhost","unknown-provisioned":null,"datastore_name":"DE600220657394-01-01-service-datastore1","vsphere_password":null,"warning-usage-prct":null,"display_ok_counters":null,"refresh":null,"unknown-usage":null,"vsphere_address":null,"connector_port":"5700","critical-status":null,"filter_counters":null,"critical_connector_status":null,"warning-usage":null,"list_counters":null,"filter":null,"critical-usage-prct":"80","command":"datastoreusage","container":"hci","unknown_connector_status":null,"warning-usage-free":null,"case_insensitive":null,"filter_host":null,"scope_datacenter":null,"identity":"client-121817e015164e069421d571b7d95e6b","unknown-usage-free":null,"warning_connector_status":null}
>2025-07-22 09:08:42] error] 'hci' SOAP request error - possibly a protocol issue: Server closed connection without sending any data back at /usr/share/perl5/Net/HTTP/Methods.pm line 397.


>2025-07-22 09:08:42] debug] 3 child(ren) found. Stop ? : 0
>2025-07-22 09:08:47] debug] 3 child(ren) found. Stop ? : 0

 


Hello, latest news:

  • I reset the password on the vSphere appliance
  • I checked the .json file which has been correctly migrated
  • I restarted the centreon_vmware.service

Now the services are working okay. It was something about the password which seems to expire after x days or months.

I still cannot find the new Configuration → Connector menu on my install, but I guess I don’t need it for the time being.

I have one last issue with the proc-gorgone and the proc-centreontrapd services which are reported to be down. This has something to do with vmware it seems. I’m currently troubleshooting the issue.

 

Hello ​@pressor 

 

Can you enable debug for gorgoned and check if you can send maintenance and new configuration to your poller ?

 

To enable debug change the file 

On alma/redhat it the file /etc/sysconfig/gorgoned

on debian it the file /etc/default/gorgoned

 

replace  `--severity=error` with `--severity=debug`
Then restart the service

can you share the systemctl status gorgoned output, the logs and the files /etc/centreon-gorgone/config.d/* in a new thread so we can keep things organized  ?

 

I am attaching the logs and file listings

 

$ sudo ls -ltr /etc/centreon-gorgone/config.d/
razem 40
-r-------- 1 centreon-gorgone centreon-gorgone 131 2024-04-30 41-autodiscovery.yaml
-rw-r----- 1 centreon-gorgone centreon-gorgone 115 2024-04-30 50-centreon-audit.yaml
-rw-r----- 1 centreon-gorgone centreon-gorgone 136 2024-04-30 30-centreon.yaml
-rw-rw---- 1 centreon-gorgone centreon-gorgone 255 2024-06-12 centreon-api.yaml.new
-rw-r----- 1 centreon-gorgone centreon-gorgone 255 2024-07-15 31-centreon-api.yaml.dpkg-dist
-rw-r--r-- 1 www-data www-data 2792 04-18 09:02 40-gorgoned.yaml
-rw-r----- 1 centreon-gorgone centreon-gorgone 247 04-18 09:03 31-centreon-api.yaml
-rw-r----- 1 centreon-gorgone centreon-gorgone 250 05-07 09:38 39-action.yaml
drwxrwx--- 2 centreon-gorgone centreon-gorgone 4096 06-24 08:24 whitelist.conf.d
drwxrwx--- 2 centreon-gorgone centreon-gorgone 4096 06-24 08:25 cron.d

 

$ sudo systemctl status gorgoned.service 
● gorgoned.service - Centreon Gorgone
Loaded: loaded (/lib/systemd/system/gorgoned.service; enabled; preset: enabled)
Active: active (running) since Thu 2025-06-26 11:21:31 CEST; 3 weeks 4 days ago
Main PID: 1611157 (perl)
Tasks: 48 (limit: 7009)
Memory: 192.8M
CPU: 30min 59.771s
CGroup: /system.slice/gorgoned.service
├─1611157 /usr/bin/perl /usr/bin/gorgoned --config=/etc/centreon-gorgone/config.yaml --logfile=/var/log/centreon-gorgone/gorgoned.log --severity=error
├─1611311 gorgone-cron
├─1611312 gorgone-dbcleaner
├─1611313 gorgone-autodiscovery
├─1611314 gorgone-httpserver
├─1611315 gorgone-proxy
├─1611316 gorgone-proxy
├─1611319 gorgone-proxy
├─1611322 gorgone-proxy
├─1611325 gorgone-proxy
├─1611334 gorgone-legacycmd
├─1611335 gorgone-statistics
├─1611336 gorgone-action
├─1611337 gorgone-nodes
├─1611338 gorgone-audit
└─1611339 gorgone-engine

lip 17 10:45:25 sudon3811259]: centreon-gorgone : PWD=/ ; USER=root ; COMMAND=/usr/sbin/service centengine reload
lip 17 10:45:25 sudoD3811259]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=993)
lip 17 10:45:25 sudod3811259]: pam_unix(sudo:session): session closed for user root
lip 17 10:45:25 sudo83811258]: pam_unix(sudo:session): session closed for user root
lip 17 10:46:20 sudo83812193]: centreon-gorgone : PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart centreon_vmware.service
lip 17 10:46:20 sudor3812193]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=993)
lip 17 10:46:20 sudod3812196]: centreon-gorgone : PWD=/ ; USER=root ; COMMAND=/usr/sbin/service centengine reload
lip 17 10:46:20 sudoD3812196]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=993)
lip 17 10:46:20 sudod3812196]: pam_unix(sudo:session): session closed for user root
lip 17 10:46:20 sudo83812193]: pam_unix(sudo:session): session closed for user root

 

 

$ sudo systemctl restart gorgoned.service && sudo tail -f /var/log/centreon-gorgone/gorgoned.log
2025-07-22 09:25:35 - DEBUG - ;legacycmd] Send TERM signal 1
2025-07-22 09:25:35 - DEBUG - -nodes] Send TERM signal 1611337
2025-07-22 09:25:35 - DEBUG - 2audit] Send TERM signal 1611338
2025-07-22 09:25:35 - DEBUG - 2core] Received SIGCLD signal (pid: 1611334)
2025-07-22 09:25:35 - DEBUG - core] Received SIGCLD signal (pid: 1611337)
2025-07-22 09:25:35 - DEBUG - core] Received SIGCLD signal (pid: 1611338)
2025-07-22 09:25:40 - INFO - -core] Module 'gorgone::modules::centreon::legacycmd::hooks' is unloaded
2025-07-22 09:25:40 - INFO - gcore] Module 'gorgone::modules::centreon::nodes::hooks' is unloaded
2025-07-22 09:25:40 - INFO - 'core] Module 'gorgone::modules::centreon::audit::hooks' is unloaded
2025-07-22 09:25:40 - INFO - 'core] Quit main process
2025-07-22 09:25:41 - ERROR - 2core] Package 'gorgone::modules::core::action::hooks' already loaded
2025-07-22 09:25:42 - DEBUG - gcore] Message received internal - kAUTODISCOVERYREADY] ] 2] {}
2025-07-22 09:25:42 - DEBUG - acore] Message received internal - ESETCOREID] ] ] {"id":1}
2025-07-22 09:25:42 - DEBUG - ecore] Message received internal - IREGISTERNODES] 1] b] {"nodes":-]}
2025-07-22 09:25:42 - DEBUG - enodes] Event: lACK] E14b941128c5c395bdb6ef584d5c9007be57b35ae1aa6cd1464f486f830338139d05e24e0b769a4d55c9a079e93a9dbbe1205e6e142a981eaf96db7b3ea5614fc] {"code":2,"data":{"message":"setcoreid unchanged, use config value","action":"setcoreid"}}
2025-07-22 09:25:42 - DEBUG - dcore] Message received internal - iSETMODULEKEY] "] <] {"key":"61105c799db5bfab47d5ededf39a4c517b967f57e60ce55ef7f767f7a5df7105"}
2025-07-22 09:25:42 - INFO - bcore] module key gorgone-httpserver changed
2025-07-22 09:25:42 - DEBUG - -core] Message received internal - hUNREGISTERNODES] <] ] {"nodes":2]}
2025-07-22 09:25:42 - DEBUG - enodes] Event: -ACK] E237f801aae0f5f01a54018239402fb74a0fca60ec6798926e3c62ded21db56ad2a15633ed8acc02433fd8eefc3aa709107b7767300fc697f5f75d4fd8cb362f6] {"code":0,"data":null}
2025-07-22 09:25:42 - DEBUG - 7core] Message received internal - dHTTPSERVERREADY] <] ] {}
2025-07-22 09:25:42 - DEBUG - enodes] Event: ACK] nbef637469f55b7ea625f8e7d9663cb78d3739e9d5d7324f1b86a5415d231bd80a03f93f92894e50af44dd70862674e764a9e9ba3d15fc8c3da77e75c6133d10f] {"code":0,"data":null}
2025-07-22 09:25:42 - DEBUG - ecore] Message received internal - dPUTLOG] t77bb7d92a4a5593d8a6a7123b7ee7ace0319cae1f6f4bc58cdfdf6ba4f593993bb2a3cd8eb297a30ebd7cad530c8a2c2862c1d3a98b236fcff24be61adc0bacd] 6] {"data":{"message":"action nodesresync finished"},"code":2,"instant":null,"etime":1753169142,"token":"77bb7d92a4a5593d8a6a7123b7ee7ace0319cae1f6f4bc58cdfdf6ba4f593993bb2a3cd8eb297a30ebd7cad530c8a2c2862c1d3a98b236fcff24be61adc0bacd"}
2025-07-22 09:25:42 - DEBUG - anodes] Event: aACK] 277bb7d92a4a5593d8a6a7123b7ee7ace0319cae1f6f4bc58cdfdf6ba4f593993bb2a3cd8eb297a30ebd7cad530c8a2c2862c1d3a98b236fcff24be61adc0bacd] {"data":{"message":"message inserted"},"code":0}
2025-07-22 09:25:42 - ERROR - aautodiscovery] -class- host discovery - cannot get host discovery jobs - request error code: '404'] ymessage: 'No route found for "GET http://127.0.0.1/centreon/api/latest/auto-discovery/scheduling/jobs"']
2025-07-22 09:25:43 - DEBUG - cnodes] Event: tACK] ufa99d5800d44671477accec57132869df40efe52b7e006761c4a7c1684bad4762bac58edd6076a5433029a49d026cb631a8ea603a09259d587812bd36dfbc9fc] {"data":null,"code":0}
2025-07-22 09:25:47 - DEBUG - eaudit] sampling starting
2025-07-22 09:26:42 - INFO - 0autodiscovery] -class- host discovery - sync started
2025-07-22 09:26:42 - DEBUG - == Info: Connection 0 seems to be dead
2025-07-22 09:26:42 - DEBUG - == Info: Closing connection 0
2025-07-22 09:26:42 - DEBUG - == Info: Hostname in DNS cache was stale, zapped
2025-07-22 09:26:42 - DEBUG - == Info:   Trying 127.0.0.1:80...
2025-07-22 09:26:42 - DEBUG - == Info: Connected to 127.0.0.1 (127.0.0.1) port 80 (#1)
2025-07-22 09:26:42 - DEBUG - => Send header: GET /centreon/api/latest/auto-discovery/scheduling/jobs?limit=10000&page=1 HTTP/1.1
Host: 127.0.0.1
Accept: */*
X-AUTH-TOKEN: TRludOxZQhRVfwOAkb0TEE3oe35+XATxJec5nN314lJahkFReL31wAC5Q9kwMk6l
Accept-Type: application/json; charset=utf-8
Content-Type: application/json; charset=utf-8
2025-07-22 09:26:42 - DEBUG - => Recv header: HTTP/1.1 404 Not Found
2025-07-22 09:26:42 - DEBUG - => Recv header: Date: Tue, 22 Jul 2025 07:26:42 GMT
2025-07-22 09:26:42 - DEBUG - => Recv header: Server: Apache
2025-07-22 09:26:42 - DEBUG - => Recv header: Cache-Control: no-cache, private
2025-07-22 09:26:42 - DEBUG - => Recv header: Api-Version: 24.10
2025-07-22 09:26:42 - DEBUG - => Recv header: X-Frame-Options: sameorigin
2025-07-22 09:26:42 - DEBUG - => Recv header: Transfer-Encoding: chunked
2025-07-22 09:26:42 - DEBUG - => Recv header: Content-Type: application/json
2025-07-22 09:26:42 - DEBUG - => Recv header: 
2025-07-22 09:26:42 - DEBUG - => Recv data: 7f
{"code":404,"message":"No route found for \"GET http:\/\/127.0.0.1\/centreon\/api\/latest\/auto-discovery\/scheduling\/jobs\""}
0
2025-07-22 09:26:42 - DEBUG - == Info: Connection #1 to host 127.0.0.1 left intact
2025-07-22 09:26:42 - ERROR - Gautodiscovery] -class- host discovery - cannot get host discovery jobs - request error Rcode: '404'] vmessage: 'No route found for "GET http://127.0.0.1/centreon/api/latest/auto-discovery/scheduling/jobs"']
2025-07-22 09:26:47 - DEBUG - .audit] sampling starting


Reply