Troubleshooting

Symptom: No data reaches Zabbix

Run:

./util.sh integrations zabbix doctor

If trapper reachability fails, check firewall/routing/security groups to server_bridge_zabbix_host:server_bridge_zabbix_port.

Symptom: LLD rules exist but no hosts discovered

Check LLD endpoints directly:

curl -fsS "http://<main-server>:8088/lld/gateways" | jq .
curl -fsS "http://<main-server>:8088/lld/beacons" | jq .

Then run:

./util.sh integrations zabbix verify --url "http://<zabbix>/api_jsonrpc.php" --user Admin

If verify fails on server host lookup, use the printed host candidates and retry with:

./util.sh integrations zabbix verify --url "http://<zabbix>/api_jsonrpc.php" --user Admin --zabbix-host "<exact host name>"

Symptom: unexpected parameter \"auth\" from Zabbix API

This indicates a version/auth-transport mismatch. New SafeCall builds automatically use modern bearer-token auth for newer Zabbix and fallback for legacy versions.

If you still see this error, update SafeCall CLI/scripts to the latest build and retry verify or setup.

Symptom: Bridge receives MQTT but drops messages

Enable bridge debug config:

• server_bridge_debug_enabled: true
• optional server_bridge_debug_sample_rate
• optional server_bridge_debug_snapshot_interval

Look for:

• beacon_unmapped or gateway_unmapped events
• high throttled counters
• cache refresh failures

Symptom: Zabbix setup partially broken after manual edits

Run:

./util.sh integrations zabbix setup --url "http://<zabbix>/api_jsonrpc.php" --user Admin

The setup command is idempotent and can recreate missing objects.

Fast Isolation Checklist

1. doctor passes on bridge machine.
2. /lld/* returns valid JSON on main machine.
3. verify passes against Zabbix API.
4. bridge debug snapshot shows increasing bridge_zabbix_send_success.