proc.num issues

[Stephan2]

Hi there,

just upgraded to 5.0 on Ubuntu 20.04. I've got an issue with the proc.num check.

Checking for fail2ban to be up and running, I use a simple template with one check:

proc.num[fail2ban-server]

The check runs fine on Ubuntu 18.04 boxes:

root# ps wax |grep fail2ban
774 ? Ssl 0:55 /usr/bin/python3 /usr/bin/fail2ban-server -xf start
19715 pts/1 S+ 0:00 grep --color=auto fail2ban
root# zabbix_agentd -t proc.num[fail2ban-server]
proc.num[fail2ban-server] [u|1]

The same check on Ubuntu 20.04 returns

root# ps wax |grep fail2ban
413773 pts/0 S+ 0:00 grep --color=auto fail2ban
3446386 ? Ssl 71:26 /usr/bin/python3 /usr/bin/fail2ban-server -xf start
root# zabbix_agentd -t proc.num[fail2ban-server]
zabbix_agentd [413840]: Warning: EnableRemoteCommands parameter is deprecated, use AllowKey=system.run[*] or DenyKey=system.run[*] instead
proc.num[fail2ban-server] [u|0]

I cannot see any difference in the output of ps, on both boxes fail2ban is up with an identical command line.

Any idea what goes wrong and how to fix this?

Thanks & best,
Stephan

[tim.mooney]

I cannot see any difference in the output of ps, on both boxes fail2ban is up with an identical command line.

Just a guess, but I wonder if proc.num assumes MAX_PID will be 5 digits and it's having trouble because of the larger PID range? I haven't checked, but it max be necessary to look at the source code to see.

[Stephan2]

Filed a bug report for it: https://support.zabbix.com/browse/ZBX-17880