lpinsivy
commented
4 years ago Updating my platform to 19.10.0 I din't have this error.
From which version you start your update? or maybe it's a fresh install?
Open wilvh opened 4 years ago
lpinsivy
commented
4 years ago Updating my platform to 19.10.0 I din't have this error.
From which version you start your update? or maybe it's a fresh install?
lpinsivy
commented
4 years ago OK this is a simple notice message.
Can you check that 'centcore' process is running?
wilvh
commented
4 years ago Updating my platform to 19.10.0 I din't have this error.
From which version you start your update? or maybe it's a fresh install?
If I remember correctly, the original version was 18.10. I updated in 19.04 then 19.10 ( and several minor updates in 19.10). This problem has been present since at least 19.04.
OK this is a simple notice message.
Can you check that 'centcore' process is running?
After verification, the centcore process is not started. Even after restarting the server, the process does not start. I've tried to enable the service at startup with "systemctl enable centcore" but the process does not start until I type "systemctl start centcore". Once the process is started, the "move export file" and "restart monitoring engine" are working and new host is visible.
There are messages in /var/log/centreon/centcore.log but they were generated before I make some tests :
Job for centengine.service failed because start of the service was attempted too often. See "systemctl status centengine.service" and "journalctl -xe" for details. To force a start use "systemctl reset-failed centengine.service" followed by "systemctl start centengine.service" again. Job for centengine.service failed because start of the service was attempted too often. See "systemctl status centengine.service" and "journalctl -xe" for details. To force a start use "systemctl reset-failed centengine.service" followed by "systemctl start centengine.service" again. Job for centengine.service invalid. Job for centengine.service failed because start of the service was attempted too often. See "systemctl status centengine.service" and "journalctl -xe" for details. To force a start use "systemctl reset-failed centengine.service" followed by "systemctl start centengine.service" again. Job for centengine.service invalid. Job for centengine.service invalid. 2020-04-24 08:59:08 - ERROR - Could not write into pipe file /var/lib/centreon-engine/rw/centengine.cmd on poller 1
I've tied this https://github.com/centreon/centreon/issues/5589#issuecomment-385559738 but it doest not work better
lpinsivy
commented
4 years ago Hi @wilvh those errors in /var/log/centreon/centcore.log are unusual.
Can you try to restart centengine then centcore?
wilvh
commented
4 years ago Hi @lpinsivy , I've deleted the log and restarted centengine and centcore and there is no content in /var/log/centreon/centcore.log file. I've updated Centreon to 19.10.10 and after a reboot of the server, the Centcore service was not running (and nothing in /var/log/centreon/centcore.log).
systemctl status centcore
● centcore.service - Centreon Core
Loaded: loaded (/usr/lib/systemd/system/centcore.service; enabled; vendor preset: disabled)
Active: inactive (dead)A manual start of the service is working perfectly (and without anything in /var/log/centreon/centcore.log).
systemctl status centcore -l
● centcore.service - Centreon Core
Loaded: loaded (/usr/lib/systemd/system/centcore.service; enabled; vendor preset: disabled)
Active: active (running) since mer. 2020-05-13 11:46:31 CEST; 5min ago
Main PID: 11714 (centcore)
CGroup: /system.slice/centcore.service
└─11714 /usr/bin/perl /usr/share/centreon/bin/centcore --logfile=/var/log/centreon/centcore.log --severity=error --config=/etc/centreon/conf.pm
mai 13 11:46:31 myserver systemd[1]: Started Centreon Core.
mai 13 11:46:31 myserver sudo[11715]: centreon : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl reload centengineTo summarize : everything seems to be working perfectly if I start manually centcore service after a server reboot but I don't understand why the service does not start automatically.
Thank you
Versions
Operating System
CentOS Linux release 7.7.1908 (Core)
Browser used
Version: 75
Additional environment details (AWS, VirtualBox, physical, etc.): VM on vSphere
Description
When I add a host and export configuration with restart or reload, the new host does not appear. I must restart centengine from SSH for the new host to be added.
Steps to Reproduce
Please describe precisely the steps to reproduce the encountered issue.
Describe the received result
No errors from export step but no new host added
Describe the expected result
No errors from export step but new host added
Logs
PHP error logs
centreon-engine logs (if needed)
centreon-broker logs (if needed)
centcore logs (if needed)
Additional relevant information (e.g. frequency, ...)
Everytime I add a host or a service and reload/restart the poller from the web interface, the new service/host does not appear. I've checked centreon sudoers file and everything seems ok. When I execute "sudo systemctl reload centengine" from SSH with centreon user, the new host/service appears. On "poller Configuration" I've changed start/stop/restart/reload commands which started with "service..." for the newer "Systemctl" but it is not better.