Proc-centengine service, return values > 1

Hi @Benjamin_b, you should have only one centengine process.

May be an issue with an old version of centengine

Well I’ll wait until I update to last version to see if it correct the issue(s). if I manage to do the update without errors hehe

Thank you Laurent

Hi @Benjamin_b 
 

Can you test to query the OIDs used by this plugin to know if a process is running or not?

First, can you query the list of processes and get the index value?

snmpwalk -v2c -c public 127.0.0.1 .1.3.6.1.2.1.25.4.2.1.2 | grep -i centengine
HOST-RESOURCES-MIB::hrSWRunName.22867 = STRING: "centengine"

Here the index is 22867.

Now, can you query the status replacing the index value?

snmpwalk -v2c -c public 127.0.0.1 .1.3.6.1.2.1.25.4.2.1.7.22867
HOST-RESOURCES-MIB::hrSWRunStatus.22867 = INTEGER: runnable(2)

Hi, thank for your answer @sduret 

Here is the status :

HOST-RESOURCES-MIB::hrSWRunStatus.21900 = INTEGER: runnable(2)

(at this moment plugin says 8 running process)

@Benjamin_b 
Is it possible to send me this snmpalk output? Maybe it’s possible to specify on the path and arguments to filter on the good process

snmpwalk -v2c -c public 127.0.0.1 .1.3.6.1.2.1.25.4.2.1 > /tmp/walk-process.txt

If it’s not possible to send the file, can you send the output of this command?

snmpwalk -v2c -c public 127.0.0.1 .1.3.6.1.2.1.25.4.2.1 | grep -i engine

@sduret 

Here is the result of

snmpwalk -v2c -c XYZ 127.0.0.1 .1.3.6.1.2.1.25.4.2.1 |grep -i engine > /tmp/walk-process.txt
cat /tmp/walk-process.txt

HOST-RESOURCES-MIB::hrSWRunName.21900 = STRING: "centengine"
HOST-RESOURCES-MIB::hrSWRunPath.21900 = STRING: "/usr/sbin/centengine"
HOST-RESOURCES-MIB::hrSWRunParameters.21900 = STRING: "/etc/centreon-engine/centengine.cfg"

Thx

@Benjamin_b It’s weird because you’ve only one centengine process.
Maybe it’s the same PID…

Can you execute these two commands and send the result?

/usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='public' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug

/usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='public' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug --process-status='running|runnable'

@sduret 

There the results :

OK: Number of current processes running: 1 | 'nbproc'=1;;1:1;0;
Process '21900' [status: runnable] [name: centengine]

OK: Number of current processes running: 1 | 'nbproc'=1;;1:1;0;
Process '21900' [status: runnable] [name: centengine]

At this moment the plugin says :

CRITICAL: Number of current processes running: 9

Most likely, your service definition doesn’t include proper macro configuration. Compare the command provided by @sduret with the one displayed here:

 

Thanks for your answer @sims24 

Here is my macro configuration for this service :

I see no real differences between his command, mine and yours. (except for the --debug and --process-status)

Could you try to add --process-status='running|runnable' in the EXTRAOPTIONS macro please?

It very weird, no reasons to get such difference between UI and CLI execution. What about the CLI in the UI, looks line the one on my screenshot?

/usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='xyz'
    --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1'

Here is the command as shown in the UI.

[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XTZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1'
OK: Number of current processes running: 1 | 'nbproc'=1;;1:1;0;
[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XYZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug --process-status='running|runnable'
OK: Number of current processes running: 1 | 'nbproc'=1;;1:1;0;
Process '21900' [status: runnable] [name: centengine]
[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XYZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug
OK: Number of current processes running: 1 | 'nbproc'=1;;1:1;0;
Process '21900' [status: runnable] [name: centengine]
[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XYZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug
CRITICAL: Number of current processes running: 8 | 'nbproc'=8;;1:1;0;
Process '5679' [status: running] [name: centengine]
Process '5684' [status: running] [name: centengine]
Process '5675' [status: running] [name: centengine]
Process '21900' [status: runnable] [name: centengine]
Process '5686' [status: running] [name: centengine]
Process '5685' [status: running] [name: centengine]
Process '5683' [status: running] [name: centengine]
Process '5687' [status: running] [name: centengine]
[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XYZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1' --debug --process-status='running|runnable'
CRITICAL: Number of current processes running: 8 | 'nbproc'=8;;1:1;0;
Process '5679' [status: running] [name: centengine]
Process '5684' [status: running] [name: centengine]
Process '5675' [status: running] [name: centengine]
Process '21900' [status: runnable] [name: centengine]
Process '5686' [status: running] [name: centengine]
Process '5685' [status: running] [name: centengine]
Process '5683' [status: running] [name: centengine]
Process '5687' [status: running] [name: centengine]
[root@s-sup ~]# /usr/lib/centreon/plugins/centreon_linux_snmp.pl --plugin=os::linux::snmp::plugin --mode=processcount --hostname=127.0.0.1 --snmp-version='2c' --snmp-community='XYZ' --process-name='centengine' --process-path='' --process-args='' --regexp-name --regexp-path --regexp-args --warning='' --critical='1:1'
CRITICAL: Number of current processes running: 8 | 'nbproc'=8;;1:1;0;
[root@s-sup ~]#

I typed his two commands and mine with 5 minutes delay

Ok, an idea came to my mind during the weekend. Do you monitor centengine on Pollers from this server? 

I guess that while the command is running, other centengine process checks are running as well and are erroneously checked as an engine process. 

Using --process-path='/usr/sbin/' will avoid this. You can use the PROCESSPATH macro to set the value ‘/usr/sbin/’

Sims24, I’m not sure to fully understand your question.

I have only one server, no remote pollers.

I’ll update the command with your suggestion.

Thx

I wanted to click on Like and I clicked on ‘Best answer’. Woopsie ^^

Anyway I did the change when I answered you and until now no more errors :)

Well, no errors in 24h since the change.

I think it‘s time to say : Issue resolved.

Thank you @sims24 

Now, time to move to another challenge > updating my 2.8.32 Centreon hehe

@Benjamin_b happy to hear that! We will set this value as a default in the template, so thank you for confirming that it works as expected. 

Oh, I will probably write a post soon about Centreon experts best practices to upgrade old centreon platforms. But, I’m not sure it will be ready before christmas;