vmlinuz checksum unsupported

[ahahum]

I recently updated to 2.2 and prior to that I updated the server and other packages. This trigger fired for the vmlinuz checksum changing, but it never resolved. Now, the server is saying that it is not supported.

I can get the checksum correctly on the zabbix server by running zabbix_agentd -t vfs.file.cksum[/vmlinuz] so I don't understand why Zabbix thinks it is not supported.

This is the default template that's always been used.

The item is listed as:
Zabbix Agent
vfs.file.cksum[/vmlinuz]
numeric (unsigned)
Decimal

Everything else on the item looks standard to me - nothing stands out.

Any reason for this being "not supported"?

[steveboyson]

https://www.zabbix.com/documentation/2.0/manual/config/items/itemtypes/zabbix_agent

May be:

vfs.file.cksum[file]
The file size limit depends on large file support.

[ahahum]

https://www.zabbix.com/documentation...s/zabbix_agent

May be:

vfs.file.cksum[file]
The file size limit depends on large file support.

Thanks for the info - is this something that would've changed between update from 2.0 to 2.2?

How can I check for LFS?

[steveboyson]

I don't suspect /vmlinuz to break the file size but this could be a mismatch of the options, either 32bit zabix on 64bit OS or something similar?

To check if a filesystem supports the LFS standard, the getconf program should be used

$ getconf FILESIZEBITS /some/path

http://people.redhat.com/berrange/notes/largefile.html

[ahahum]

I don't suspect /vmlinuz to break the file size but this could be a mismatch of the options, either 32bit zabix on 64bit OS or something similar?

To check if a filesystem supports the LFS standard, the getconf program should be used

$ getconf FILESIZEBITS /some/path
http://people.redhat.com/berrange/notes/largefile.html

That returns:
getconf FILESIZEBITS /vmlinuz
64