Steps to reproduce:

1. I do have such a trigger {HOST:proc.num[,,run,ruby].last(#1)}<1
2. when running locally it gives me expected result

   XXX$ zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf -t proc.num[,,run,ruby]
   
   proc.num[,,run,ruby]                          [u|1]
   

1. But both in logs and from server it gives me 0

   zabbix-server:~$ zabbix_get -s HOST -k"proc.num[,,run,ruby]"
   
   0
   

    32502:20190603:232704.927 Requested [proc.num[,,run,ruby]]
   
   32502:20190603:232704.929 Sending back [0]
   

1. If I run it under zabbix user I do receive normal result

   zabbix@XXX:$ zabbix_agentd -c /etc/zabbix/zabbix_agentd.conf -t proc.num[,,run,ruby]
   
   proc.num[,,run,ruby]                          [u|1]
   

Expected:
I receive 1 in all cases.

Also:

The same result with proc.num[,,run,nginx]