ll /etc/centreon/centreon_vmware.json
-rw-rw---- 1 centreon centreon 2 Dec 30 04:40 /etc/centreon/centreon_vmware.json

file rights?

No, it was:

-rw-r----- 1 centreon centreon 440 Dec 30 17:05 /etc/centreon/centreon_vmware.json

then I did

chmod g+w centreon_vmware.json

and now it is:

-rw-rw---- 1 centreon centreon 2 Jan  8 12:00 /etc/centreon/centreon_vmware.json

but the content changed this way:

cat /etc/centreon/centreon_vmware.json
{}

On /var/log/centreon-gorgone/gorgoned.log a row was written:

2025-01-08 12:00:10 - ERROR - -action] Copy processing - can't change permission of file /etc/centreon/centreon_vmware.json: Operation not permitted

By the way, I can restore the json file from the backup

This is the actual behaviour:

1. When I export the configuration to the pollers, /etc/centreon/centreon_vmware.json file on pollers is overwritten with {}
2. On the central server, on /var/log/centreon-gorgone/gorgoned.log for each poller configuration’s export is added a row with the message: “2025-01-08 17:15:15 - ERROR - Rlegacycmd] Cannot process message type 'SENDCBCFGthrowing it away.”
3. On the pollers, /var/log/centreon-gorgone/gorgoned.log says: “2025-01-08 17:15:15 - ERROR - Eaction] Copy processing - can't change permission of file /etc/centreon/centreon_vmware.json: Operation not permitted”. The previous messages don’t appear anymore

Can someone help me?

Egidio

Today I found this:

I configured the additional connectors and now /etc/centreon/centreon_vmware.json is not overwritten anymore.

Errors 2 and 3 are still there

I resolved errors 2 and 3 editing this file:

/etc/centreon-gorgone/config.d/40-gorgoned.yaml

by disabling legacycmd module (set enable:false)

    - name: legacycmd
      package: "gorgone::modules::centreon::legacycmd::hooks"
      enable: false
      cmd_dir: "/var/lib/centreon/centcore/"
      cmd_file: "/var/lib/centreon/centcore.cmd"
      cache_dir: "/var/cache/centreon/"
      cache_dir_trap: "/etc/snmp/centreon_traps"
      remote_dir: "/var/cache/centreon//config/remote-data/"

Now, when I export the configuration and restart the pollers, I don’t get errors anymore on file /var/log/centreon-gorgone/gorgoned.log neither for central server nor for distant pollers

I just realized that disabling legacycmd module newly inserted hosts (from the Web interface) aren’t inserted anymore into the database.

So I had to re-enable the module and got the errors back

Hello.

I’ve stumbled into the same error when I updated to 24.10.3 from 24.04.9

After searching left and right, I’ve noticed that the file /etc/centreon/centreon_vmware.json was owned by the user centreon. But the gorgone has another centreon-gorgone user, so I’ve deleted the centreon_vmware.json file, and when I restarted the poller, the new file was created by the user centreon-gorgone, and now all it’s working as it should.

Now the file is almost all the time empty, with only {} inside.

Give it a try, maybe it will work for you aswell.

Hi ​@astalush 

The file /etc/centreon/centreon_vmware.json contains the configurations of the connectors inserted in Configuration > Additional Connector Configurations and I don’t think it should be empty if you configured a connector for that poller. Maybe you haven’t any connector configured?

By the way, I made a try:

- I deleted the file /etc/centreon/centreon_vmware.json owned by user centreon

- I exported the poller’s configuration and restarted the monitoring engine (Reload), then I saw that the file was re-generated with owner centreon-gorgone

-rw-r--r-- 1 centreon-gorgone centreon 257 Jan 29 17:42 centreon_vmware.json

The file content is unchanged.

So, thank you! i finally got rid of the error 3: action] Copy processing - can't change permission of file /etc/centreon/centreon_vmware.json: Operation not permitted

Only error 2 “ylegacycmd] Cannot process message type 'SENDCBCFGthrowing it away.” on central server centreon-gorgone’s logs persists.

Bye

Hey ​@PerBacco, I’m glad it works for you.

Indeed it’s empty because I don’t have any connectors configured. That error for me blocked all new services via that poller, it was a bit problematic.

For your other error I didn’t found anything in our logs, sorry.