Skip to main content

 

Mon Discovery ne se lance jamais, je ne comprend pas pourquoi.

si quelqu'un connais la solution 

cdt

Hi @vraica ,

Thank you for your interest in Centreon.

My first attempt in troubleshooting your issue would be to make sure this prerequisite is met: https://docs.centreon.com/docs/monitoring/discovery/installation/#setting-up-a-dedicated-autodiscovery-account

I hope his helps!

Regards


hi, this is the same 

 


sorry misstake

 


And have you restarted Gorgone (`systemctl restart gorgoned`) and tried creating a new host discovery job since you have created this account and configured your credentials?

 

PS: you can lower the job’s SNMP timeout to 0.1 or 0.2 seconds to make it spend less time on unused IP addresses.


And have you restarted Gorgone (`systemctl restart gorgoned`) and tried creating a new host discovery job since you have created this account and configured your credentials?

 

PS: you can lower the job’s SNMP timeout to 0.1 or 0.2 seconds to make it spend less time on unused IP addresses.

yes i have restart a create, new user, config centreon-api.yaml


restart gorgone, create user, config .yaml and restart

create a new discovery, push pooler , and restart gorgone

 

ans not working, it the same


Hello @vraica 

What did you get in your /var/log/centreon-gorgoned/gorgoned.log when adding a new discovery job ?

 


hey, this is my gorgoned.log 

 


Which version of centreon do you have ?


my version of centreon is 21.10

 


Could you change the base_url in /etc/centreon-gorgone/config.d/31-centreon-api.yaml  file by this one:

base_url: "http://127.0.0.1/centreon/api/latest/"

Then restart gorgoned and recreating a discovery job ?


I have change the line base_url with your, restart gorgoned and this is the same 

never run

 

 


But we move on :D

The error messsage changed ^^

Your user defined in /etc/centreon-gorgone/config.d/31-centreon-api.yaml has the access to the APIs and it’s an admin user:

 


i have change, buuuut 😭😭 the same … dont run 

log:

 


Last try:
could you change edit the file /etc/syconfig/gorgoned and changed the flag --severity=’info’ by --severity=’debug’.

Then restart gorgoned and try again (with the logs) ?


ok^^ ,so ty for your help 

 


Saw it!

Typo in the base_url, it was lastet and not latest.

Everything is cool now B-)


Reply