The value is not stored in database.

[rbmf]

I'm using zabbix 1.3.5. I'm unable to get any items I'm monitoring to update. In /tmp/zabbix_server.log I'm finding errors like this:

2695:20070417:144934 Getting value of [vfs.file.cksum[/etc/passwd]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [sensor[temp3]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [vfs.fs.size[/var,pfree]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [net.if.out[eth1,bytes]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [vfs.fs.size[/home,free]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [vfs.fs.inode[/,free]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [system.cpu.load[,avg5]] from host [zabbix] failed
  2695:20070417:144934 The value is not stored in database.
  2695:20070417:144934 Getting value of [vm.memory.size[free]] from host [zabbix] failed
  2696:20070417:144934 The value is not stored in database.

What am I missing?

[NOB]

Hi,

the same happened to me - until I updated ALL agents to version 1.3.5, too.

I hope that this is not "normal" behaviour.
It would not be funny to update more than 1000 servers or
build a second environment just for a minor version change.

Regards,

Norbert.

[Farzad FARID]

Hi,

the same happened to me - until I updated ALL agents to version 1.3.5, too.
[...]

Norbert.

Hi,

Same problem here, but both my test server and test agent are already at version 1.3.5. So I'm not sure that upgrading the agents to version 1.3.5 is a real cure for this issue.

Personnaly, I had to restart the Zabbix server to get rid of this blocking bug. I also restarted the agent, so I don't know which of them is really the cause of the bug.

[rbmf]

still not working...

We are using the latest agentd. We have restarted the zabbix server and agents. Still nothing is being updated.

[NOB]

Hi,

for all my test agents (1.3.4) the server did report these errors.
It ceased as soon as the agent was updated.
It went away with the update of the last agent.

I use a mix of FreeBSD 6.1, Linux RedHat, Solaris 8 and
Windows agents for testing - not just the BETA but the
other functionality, too.

Of course, I had to restart the server and the agents
several times.

Norbert.

[Alexei]

Fixed in pre 1.3.6.

[Farzad FARID]

Fixed in pre 1.3.6.

Hi, thanks for the prompt fix. Does is also fix the error I reported here (http://www.zabbix.com/forum/showthread.php?t=5842) regarding the very high CPU load?

I guess so but I wanted to be sure.

Regards