I have zabbix agentd w/ 1.1.8beta set for active alerts and the next check time goes to 12.31.1969 16:00. If I set it to passive tests it works.
This happens for multiple ones including built in functions like
system.cpu.load[all,avg1]
and ones I create myself:
UserParameter=read.hda,vmstat -d | grep ^hda | awk '{print $2}'
Any clues would be appreciated.
Cheers.
Upon further investigation it seems this happens when the type of information is set to Numeric Integer (64 bit) I've tried this on several different installs -- including clean ones and it's pretty consistently broken.
Create this check:
vm.memory.size[free]
set type of info to:
Numeric integer (64 bit)
Go to Monitor, the Queues and detail view you'll see the next check set to 12.31.1969.
Setting it to Numeric float seems to fix it, at least in the two I've tried so far...
This happens for multiple ones including built in functions like
system.cpu.load[all,avg1]
and ones I create myself:
UserParameter=read.hda,vmstat -d | grep ^hda | awk '{print $2}'
Any clues would be appreciated.
Cheers.
Upon further investigation it seems this happens when the type of information is set to Numeric Integer (64 bit) I've tried this on several different installs -- including clean ones and it's pretty consistently broken.
Create this check:
vm.memory.size[free]
set type of info to:
Numeric integer (64 bit)
Go to Monitor, the Queues and detail view you'll see the next check set to 12.31.1969.
Setting it to Numeric float seems to fix it, at least in the two I've tried so far...
Comment