RHEL 6.2 on server and proxy

most likely the agent has not been updated - lld protocol was changed in ZBX-4725 thus you must use at least 2.0.0rc1 agents as well

Please investigate this further. The server, proxy and agents involved are all running 2.0.0rc1, this was happening in 1.9.9 as well.

I'm happy to collect more information to figure this out.

reopening then. when you do zabbix_get for that key, what exactly is the answer ?

output from zabbix_get -s dr1lin028 -k vfs.fs.discovery run from proxy

LLD rule and error

heh. looks like discovery json is trimmed
...ok, it's not, formatting got me

just to be sure, proxy database is a fresh one from the same version, right ?

Yes, I blew it away and it recreated it from scratch.

It's only affecting vfs.fs.discovery, on the same host I'm using net.if.discovery with no issues

Also it affects every host on this proxy (35) both linux and solaris agents

sasha suggested that this might be because of the length of the discovery response

That would explain why it doesn't happen on another proxy (those hosts don't have a thousand+ autofs maps) but itdoesn't explain why it works fine without a proxy. Is there some limit on the proxy that could be increased?

there might be some proxy specific limit, but nobody has investigated it more yet

It appeared to be the limit we have (64 kB) of what we put to history_text table. The response in this case is 96 kB. The reason it works on the server side is that server processes the response without storing it in the DB so basically there is no limit in that case. Removing that limit should fix that for SQLite and PostgreSQL (proxy). For MySQL we will change the db schema. There will be no fix for Oracle and IBM DB2 (we doubt anybody would use that for proxy anyways).

For the record, which DB are you using for proxy?

The docs will need to be updated and it should be mentioned that there will be limit for what lld returns to proxy in case of Oracle and IBM DB2.

Ah, great work figuring that out We use SQLite for our proxies.

Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBX-4780

Successfully tested! Please review my changes in r26563.

Fixed in pre-2.0.0 r26576.

Hi,

I upgraded my proxy with the issue to pre-2.0.0rc3 r26725 and I still have the problem. (proxy uses SQLite DB)

Do I also need to upgrade my server? If so, do I also need to apply the r26576 database patch? (server uses mysql DB)

ALTER TABLE proxy_history
MODIFY value longtext NOT NULL;

No, proxy db does not need to be patched. I have just tried it with your setup (proxy with SQLite, server using MySQL), got JSON error before r26576, then upgraded to the latest trunk and rebuild everything (didn't touch the databases), restarted everything and the error was gone. Can you confirm that after upgrade discovery rule gives exactly the same error ("Value should be a JSON object")?

Yes exact same error. I only upgraded my proxy. Do I need to upgrade the server as well?

Yep, the change affects the limit on both the server and proxy. You need to rebuild the server with MySQL support too.

Okay I'll update the server as well. Do I need to apply the schema update to the proxy_history table as well?

Nope. That would've been needed only if you'd run proxy with MySQL.

nope, server doesn't use that table. for consistency you can apply the schema change, but it's not required.
dimir will correct me if that's not right

damn you. i was slower.

That'll teach you to interrupt a conversation like that! :-D

Updated the server this morning and it's working fine now. Thanks