system.uname on windows picks up outdated info

[herta]

Environment:
- zabbix server and client: 2.0.4
- client OS: Windows 2003 SP2 32-bit
- server OS: Ubuntu 12.04.1 LTS

Some of our Windows servers have been renamed one or more times.

For some reason, system.uname regularly picks up the old system info, resulting in false alarms for "Host information was changed on xxx" and possibly also for "xxx has just been restarted". (The system.uptime graphs are zigzags.)

Is there a way to force zabbix to ignore the old info?

Does anyone have an idea from where it picks up this old info? (I searched the registry, but there's nothing there.)

[tchjts1]

have you altered the stock polling interval for that item? By default it is set to 3600 seconds... so it updates hourly. or it should, anyway.

[herta]

No, I haven't changed the default polling interval. How would that influence its behaviour?

[tchjts1]

No, I haven't changed the default polling interval. How would that influence its behaviour?

Well, if it is set to 3600, then Zabbix is only checking it once per hour.

This is an exaggeration, but you can get my point: If you change you server name 4 times in that hour, Zabbix will miss 3 of those changes and pick up the 4th one when it checks again in 60 minutes.

[herta]

Ah, it looks like I explained poorly. These systems were renamed ages ago.

[herta]

resolved

Found it.

All of the servers are physical servers which have been cloned to virtual machines. The zabbix configuration file was not adjusted in the process.

As system.uname and system.uptime have been defined as items of type "Zabbix agent (active)", the clones kept sending their information to the zabbix server which happily logged the info as data for the original server.