Host uptime (in sec) value incorrect

[disgruntleddutch]

I am currently monitoring 4 systems (planning to roll this out to all 50 servers in the next few months).

In any case I seem to be having a problem getting Zabbix to monitor the correct value for host uptime (system.uptime).

System 1 - 3 are running debian 3.1 with 2.4.18 as kernel
System 4 is running fedora core 2 with 2.6.9 as kernel

actual uptime (checked via 'uptime' in bash) on
system 1: up 113 days, 23:00
system 2: up 144 days, 5:36
system 3: up 269 days, 3:37
system 4: up 145 days, 21:04

here is what zabbix is returning:
system 1: 3m23d23h1m5s
system 2: 4m24d5h33m50s
system 3: 8m29d3h34m16s
system 4: 4m25d21h5m29s

I have tried changing the multiplier to 0.01 or 0.1. Units is s. I have tried m and h.

Anyone have any clue to what I am doing wrong.

All 4 machines were setup using the unix template. system 1 - 3 are using the precompiled agent found on this website at version 1.1, system 4 (the fedora core system) is using 1.1.2.

[James Wells]

Greetings,

I haven't pulled out a calculator, but they all appear to be fairly close.

[disgruntleddutch]

So its normal for Zabbix to display
3m23d23h1m5s as up 113 days, 23:00

Why doesn't it display as
up 113 days, 23:00?

[Alexei]

So its normal for Zabbix to display
3m23d23h1m5s as up 113 days, 23:00

Why doesn't it display as
up 113 days, 23:00?

Well, I guess you are right. The "113 days, 23:00" is much more readable. I'm changing this in 1.1.3 to somethis like "113 days, 23:00:32" (32 - seconds). Any objections?

[dantheman]

I'm sure this will be more complicated to implement, but could we choose a setting somewhere how we want the dates to display?

[peter_field]

I dont mind the existing format

I dont mind the existing format, don't really know what the big deal is all about.

[peter_field]

Time in actions

While we are talking about time formats, the uptime shows like this in actions:

Trigger key: system.uptime
Value: 155.20 Ks

The action that generated this is:
Trigger key: {TRIGGER.KEY}
Value: {{HOSTNAME}:{TRIGGER.KEY}.last(0)}

I don't know about you, but I can't do that sort of math in my head.