if a database query fails, server shouldn't send incomplete configuration data to the proxy.

for example, if a query fails like this :

5384:20120218:065603.077 [Z3005] query failed: [126] Incorrect key file for table '/var/tmp/mysql.CerISn/#sql_ee7_0.MYI'; try to repair it [select t.itemid,t.type,t.snmp_community,t.snmp_oid,t.snmp_port,t.hostid,t.key_,t.delay,t.status,t.value_type,t.trapper_hosts,t.units,t.multiplier,t.delta,t.snmpv3_securityname,t.snmpv3_securitylevel,t.snmpv3_authpassphrase,t.snmpv3_privpassphrase,t.formula,t.logtimefmt,t.templateid,t.valuemapid,t.delay_flex,t.params,t.ipmi_sensor,t.data_type,t.authtype,t.username,t.password,t.publickey,t.privatekey from items t,hosts r where t.hostid=r.hostid and r.proxy_hostid=5002 and r.status in (0,1) and t.status in (0,1,3) and t.type in (0,7,1,4,6,12,2,3,9,10,11,13,14) order by t.itemid]

proxy gets host information, but without any items.

if any of the queries for proxy configuration dataset fail, server should either retry them, or, if not successful, refuse to send config data to the proxy.

this has happened twice in a test setup during a few hours for different reasons.