Hello @Benoit,
You can fix this error by editing the file /etc/centreon-gorgone/config.d/31-centreon-api.yaml with the credential of the admin user and restarting gorgoned but we recommend that you set up a dedicated technical account for this fiile. That account is the one that will execute the discovery jobs in the background. More information here: https://docs.centreon.com/21.04/en/monitoring/discovery/installation.html#setting-up-a-dedicated-autodiscovery-account.
Ok thanks you very much for this tips.
But i don’t use auto discovery function.
Can i safely stop gorgoned service ? Is there an impact to other functionality ?
Hi @Benoit, you should definitely NOT stop the gorgoned service as it in charges of several mechanisms in the Centreon system (configuration export, poller management, acknowledgement of alarms etc...).
If you don’t want to configure the service account as advised by @itoussies (but you should give it a try someday ! 
) , then you can manually disable the autodiscovery feature in the gorgone configuration by editing this file on the Centreon Central server:
/etc/centreon-gorgone/config.d/41-autodiscovery.yaml
set the `enable` option to `false`, then restart the gorgoned process
systemctl restart gorgoned
Yes, thanks you i found this website which give me the solution also :
https://www.sugarbug.fr/atelier/techniques/centreon-gorgone/les%20bases/
File 31-centreon-api.yaml can be renamed also it seem, it’s correct and safe ?
In my honest opinion, it would be cleaner and safer to disable the feature rather than deleting (or renaming) the files it uses. Furthermore the files could be created again when updating the platform, causing the issue again…
so it’s up to you :)
ok you have right, i set enabled to false in : 41-autodiscovery.yaml and it’s working fine
Thanks you to all for your help. Topic can be closed :)
