Hello,
I’ve a new Centreon 23.04, my issue is when i export the configuration on my Central, it’s doesn’t work :
I need to reload the centengine service to apply the change :
#systemctl reload centengine.service
Anyone have faced same issue? Does somebody have an idea, please?
Thanks.
+13
ponchoh,
Thank's for your feedback.
The No such file or directory was fixed, by updated the Centreon web.
My issue is the export configuration isn't working. I need to reload the centengine to apply the changes.
Hello,
Issue was resolved. there are noexec restruction in sudoers file. Now i can export configuration by reload the centengine in GUI.
Thank’s
+1
Hello,
Issue was resolved. there are noexec restruction in sudoers file. Now i can export configuration by reload the centengine in GUI.
Thank’s
Hello
Thanks in advance,
+1
Hello all,
Can anyone help us with this issue?
Thanks in advance 🙂
Hello
Check you sudoers file, if the centengine user is autorized to run cmd as root user and check the owner of directory /etc/cent* , eg. /etc/centreon-broker owner by centreon-broker user
+1
Hello
Check you sudoers file, if the centengine user is autorized to run cmd as root user and check the owner of directory /etc/cent* , eg. /etc/centreon-broker owner by centreon-broker user
Hello
Are you sure that is it really necessary to do this?
In my case I’ve deployed a template with everyhing configured and directly from Centreon official website. It seems a bit strange to have to make these types of modifications in the “sudoers” file, it doesn't appear anywhere in the guide I've followed: https://docs.centreon.com/docs/installation/installation-of-a-central-server/using-virtual-machines/"
Thank you again 😊
Hello
In My case i've an internal rules to block user sudo. I've deploy manually my server.
What'is exactly your issue? If you make any change (adding new host or service) you should restart your poller to apply the change. The change is not take effet if you didn't restart the poller. It’s not an issue , it's normal behavior.
+1
Hello
In My case i've an internal rules to block user sudo. I've deploy manually my server.
What'is exactly your issue? If you make any change (adding new host or service) you should restart your poller to apply the change. The change is not take effet if you didn't restart the poller. It’s not an issue , it's normal behavior.
Hello
My exactly issue is that when I do any change (add new host, disable host, modify any services, etc) it won’t be applied/showed after exporting the poller configuration and reloading it or restarting it (tried both with no luck) if I don’t restart after manually the service “centengine” from the server, command line.
I’ve been working with Centreon for many years and this isn’t a normal behavior 😅
Thank my friend!
Check the owner and permission of those directory :
+1
Check the owner and permission of those directory :
Here you have the details
Thank you,
Ok, the directory permission is correct . Please, check the file owner and permission under the directory :
here an eg.
ls -l /etc/centreon-engine/
total 464
-rw-rw-r--. 1 apache centreon-engine 321 22 août 17:14 plugins.json
-rw-rw-r--. 1 apache centreon-engine 1,5K 22 août 17:14 connectors.cfg
-rw-rw-r--. 1 apache centreon-engine 18K 22 août 17:14 commands.cfg
-rw-rw-r--. 1 apache centreon-engine 4,5K 22 août 17:14 centengine.cfg
-rw-rw-r--. 1 apache centreon-engine 4,4K 22 août 17:14 contacts.cfg
apache user owns files owner
+1
Ok, the directory permission is correct . Please, check the file owner and permission under the directory :
here an eg.
ls -l /etc/centreon-engine/
total 464
-rw-rw-r--. 1 apache centreon-engine 321 22 août 17:14 plugins.json
-rw-rw-r--. 1 apache centreon-engine 1,5K 22 août 17:14 connectors.cfg
-rw-rw-r--. 1 apache centreon-engine 18K 22 août 17:14 commands.cfg
-rw-rw-r--. 1 apache centreon-engine 4,5K 22 août 17:14 centengine.cfg
-rw-rw-r--. 1 apache centreon-engine 4,4K 22 août 17:14 contacts.cfg
apache user owns files owner
-rw-rw-r--. 1 centreon-engine centreon-engine 4601 29 août 14:19 centengine.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 commands.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1521 29 août 14:19 connectors.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 contactgroups.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 contacts.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 dependencies.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 escalations.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 hostgroups.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 hosts.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 hostTemplates.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 meta_commands.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 meta_host.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 meta_services.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 meta_timeperiod.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 2 29 août 14:19 plugins.json
-rw-rw-r--. 1 centreon-engine centreon-engine 1167 29 août 14:19 resource.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 servicegroups.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 services.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 serviceTemplates.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 severities.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 tags.cfg
-rw-rw-r--. 1 centreon-engine centreon-engine 1088 29 août 14:19 timeperiods.cfg
Ok, apache isn’t owen’t owner of files.
Try to change the files ownership :
+1
Ok, apache isn’t owen’t owner of files.
Try to change the files ownership :
Maybe it’s related with this issue?
Because when I try to run this command I got this error:
[root@XXX~]# su - centreon-gorgone -s /bin/bash -c 'sudo systemctl restart centengine'
>>> /etc/sudoers.d/root: erreur de syntaxe near line 2 <<<
sudo: erreur d'analyse grammaticale dans /etc/sudoers.d/root aux environs de la ligne 2
sudo: aucune source sudoers valide n'a été trouvée, fin d'exécution
sudo: impossible d'initialiser le greffon de règles
But the file looks good (it’s by default):
password ALL = (ALL) NOPASSWD: ALL
Defaults:root \!requiretty
And the “sudo” tool/command is already installed...so I don’t know what else to try 🤔
Thanks a lot again for your efforts helping me.
Modify the file /etc/sudoers.d/root and remove \
password ALL = (ALL) NOPASSWD: ALL
Defaults:root \!requiretty
Its sould be :
password ALL = (ALL) NOPASSWD: ALL
Defaults:root !requiretty
+1
Modify the file /etc/sudoers.d/root and remove \
password ALL = (ALL) NOPASSWD: ALL
Defaults:root \!requiretty
Its sould be :
password ALL = (ALL) NOPASSWD: ALL
Defaults:root !requiretty
It worked like a charm
Thank you for your feedbak 😀
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
