Zabbix Proxy: Difference between revisions

From DWIKI
Line 35: Line 35:


  [Service]
  [Service]
  Environment="CONFFILE=/usr/local/etc/zabbix/zabbix_proxy.conf"
  Environment="CONFFILE=/usr/local/etc/zabbix_proxy.conf"
  EnvironmentFile=-/etc/sysconfig/zabbix-proxy
  EnvironmentFile=-/etc/sysconfig/zabbix-proxy
  User=zabbix
  User=zabbix
Line 50: Line 50:
  [Install]
  [Install]
  WantedBy=multi-user.target
  WantedBy=multi-user.target


====zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted====
====zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted====

Revision as of 13:04, 14 August 2024

Documentation

HOWTO

Building zabbix proxy on Ubuntu

requirements

apt-get install gcc make libsqlite3-dev zlib1g-dev libevent-dev libpcre3-dev libsnmp-dev libopenipmi-dev libgnutls28-dev libcurl4-gnutls-dev snmp-mibs-downloader libxml2-dev pkg-config

On Ubuntu-22.04 i did:

Get the source

Configure

./configure --enable-agent --enable-proxy --with-sqlite3 --with-openipmi --with-net-snmp --with-gnutls --with-libcurl --with-libxml2


Error messages

Zabbix proxy was compiled without VMware support

 apt install libxml2-dev

and

--with-libxml2

configure: error: LIBXML2 library not found

apt install pkg-config

You might want a systemd service file

So create /etc/systemd/system/zabbix-proxy.service

[Unit]
Description=Zabbix Proxy
After=syslog.target
After=network.target
[Service]
Environment="CONFFILE=/usr/local/etc/zabbix_proxy.conf"
EnvironmentFile=-/etc/sysconfig/zabbix-proxy
User=zabbix
Group=zabbix
Type=forking
Restart=on-failure
PIDFile=/run/zabbix/zabbix_proxy.pid
KillMode=control-group
ExecStart=/usr/local/sbin/zabbix_proxy -c $CONFFILE
ExecStop=/bin/kill -SIGTERM $MAINPID
RestartSec=10s
TimeoutSec=0
[Install]
WantedBy=multi-user.target

zabbix-proxy.service: Can't open PID file /run/zabbix/zabbix_proxy.pid (yet?) after start: Operation not permitted

make sure PIDFile in system config matches PidFile in zabbix_proxy.conf


Zabbix proxy with PSK

openssl rand -hex 32 > /etc/zabbix/proxy.psk  

Config:

DBName=/var/lib/zabbix/db/zabbix_proxy.db
TLSConnect=psk
TLSPSKIdentity=proxy-nss
TLSPSKFile=/etc/zabbix/proxy.psk

FAQ

zabbix proxy messages

Zabbix proxy poller processes more than 75% busy

A passive proxy went away?

Zabbix does not support SQLite3 database upgrade.

Stop the proxy and (re)move the .db file

Cannot find module (IF-MIB): At line 1 in (none)

Check /etc/snmp/snmp.conf for

mibs +ALL

and make sure to comment out

mibs: 

And

apt-get install snmp-mibs-downloader

cannot send list of active checks

See Zabbix#cannot_send_list_of_active_checks

cannot accept connection from proxy

If you see this in server log, check:

Administration->Proxies->Your proxy->Proxy addresses

Cannot parse heartbeat from active proxy

TBD, probably name issue


Troubleshoot high queue on proxy

cannot send heartbeat message

Proxy wrong version?


Nodata and proxy

https://www.zabbix.com/documentation/5.0/en/manual/introduction/whatsnew500#no-data-triggers-sensitive-to-proxy-availability



Zabbix unreachable poller processes more than 75% busy

??


Zabbix poller processes more than 75% busy

I've seen this happen when a proxy gets monitored via another proxy.

[Z3002] cannot create database 'zabbix_proxy': [0] unable to open database file

fix DBName


cannot initialize database: cannot open database

Probably fresh install, in case of sqlite: In proxy config:

DBName=/var/lib/zabbix/zabbix_proxy

and restart zabbix-proxy


Zabbix proxy and PSK

TLS read fatal alert "unknown PSK identity"

Could mean you forgot

TLSAccept=psk

in proxy config

The SRP/PSK username is missing or not known

SSL alert number 115: TLS read fatal alert "unknown PSK identity"

poller data processes

StartPollers

cannot obtain data from proxy "proxybox": ZBX_TCP_READ() failed: [104] Connection reset by peer

Could be a proxy configured passive, and it's unreachable

force "sending configuration data to proxy"

zabbix_proxy -R config_cache_reload