Self Monitoring failures on new VM install upgraded to latest version
Hi all,
I recently did an install of the free edition of Centreon. All I’ve done was install the VM and update everything to the latest versions and now I’m receiving a few errors in the services section and a bunch if unknowns.
The first is for proc-postfix and is CRITICAL: Number of current processes running: 0. I suspect this might just because postfix isn't running and probably isn't a big issue.
The other is for Connection-Time and is CRITICAL: Cannot connect: Access denied for user 'centreon-engine'@'localhost' (using password: YES). I also see this in a large number of the unknown issues.
Would anyone be kind enough to point me in the right direction on how to fix this?
Thanks
Page 1 / 1
hello
how did you deploy your centreon setup? if you used an ova/ovf from centreon or the “installation from package” (a script that will configure centreon with a nice unattended script)
for the postfix problem : postfix is not installed by default, as this is only needed if you want to do mail notification, you need to install and enable that on your machine (yum install postfix, or apt install something, depends on you linux os)
if you don’t need mail notification, simply disable that check-process “proc-postfix” from the list of services in the configuration
for the second issue is a mysql problem, ‘connection-time’ is a mysql check that needs a login/password
this is setup in the “host” configuration of the machine you want to monitor
the host with mysql should have a template that creates a few macro you need to setup for each host
macro like
or
(these macro are created in the host automatically if your host has a “mysql” template, or the “app-monitoring-centreon-database-custom” template for example
you do not need to create a macro, but you need to input the correct value on the right)
for the self-check of centreon the login you should input is “centreon”, and the password you generated during the setup of the platform for the DB,
most check will need something to be setup to work, be it a snmp community, a login/password for the thing you want to monitor.
if you don’t specify the correct values for your host, or leave things empty, it will try to use the user running the check on the poller, and that user is “centreon-engine”