Zabbix agent availability issues on Ubuntu 22.04 typically stem from firewall blocks, misconfigured Zabbix server addresses, or systemd service failures. Verify the agent is running with
systemctl status zabbix-agent, ensure port 10050 is open in UFW, and confirm the
Server directive in
/etc/zabbix/zabbix_agentd.conf matches your Zabbix server IP.
Verifying Service Status
The first step in troubleshooting any availability issue is confirming that the software process is actually active. On Ubuntu 22.04, the Zabbix agent is managed by systemd. You should check its status using the following command:
systemctl status zabbix-agent
If the service is inactive or failed, systemd will provide a brief reason in the output. Look for lines indicating "Active: inactive (dead)" or "Active: failed." If the service is not enabled to start at boot, you can enable it with:
sudo systemctl enable zabbix-agent
Restarting the service after configuration changes is also critical:
sudo systemctl restart zabbix-agent
If the service fails to start, check the journal logs for specific error messages:
journalctl -u zabbix-agent -f
Common errors include permission denied issues when reading configuration files or network binding failures. Ensure the configuration file has correct ownership:
sudo chown zabbix:zabbix /etc/zabbix/zabbix_agentd.conf
Checking Firewall Configuration
Ubuntu 22.04 ships with UFW (Uncomplicated Firewall) enabled by default. The Zabbix agent listens on TCP port 10050 for incoming connections from the Zabbix server. If this port is blocked, the server cannot reach the agent, resulting in an "Unavailable" status.
Check the current firewall status:
sudo ufw status
If the status shows "active," verify if port 10050 is allowed. To allow traffic, run:
sudo ufw allow from /32 to any port 10050 proto tcp
Replace
<your-zabbix-server-ip> with the actual IP address of your Zabbix server. This rule restricts access to only the trusted server, enhancing security. After adding the rule, reload the firewall:
sudo ufw reload
Test connectivity from the Zabbix server using telnet or nc:
nc -zv 10050
A successful connection confirms the firewall is no longer blocking communication.
Validating Agent Configuration
The most common cause of availability issues is incorrect configuration in
/etc/zabbix/zabbix_agentd.conf. Two directives are critical:
Server and
ServerActive.
-
Server: Defines the IP addresses of Zabbix servers that can connect to the agent. These servers can actively poll data.
-
ServerActive: Defines the IP address of the Zabbix server to which the agent sends active checks.
Ensure the
Server directive includes the correct IP address of your Zabbix server:
Server=192.168.1.100
You can specify multiple IPs separated by commas. Also, verify that
Hostname matches exactly what is configured in the Zabbix web interface under Hosts > Agents. Mismatches here prevent the server from recognizing the agent.
After editing, test the configuration syntax:
zabbix_agentd -t system.uname
This command attempts to retrieve system information. If it returns a value like
Linux hostname 5.15.0..., the configuration is valid. An error indicates a syntax problem in the config file.
Testing Connectivity and Logs
If the service is running, the firewall allows traffic, and the configuration appears correct, check the agent logs for detailed insights. The primary log location is
/var/log/zabbix/zabbix_agentd.log.
Review recent entries:
sudo tail -n 50 /var/log/zabbix/zabbix_agentd.log
Look for messages such as "cannot connect to [server_ip]:10051" which indicate the agent cannot reach the server, or "connection refused" which suggests the server is down or unreachable.
On the Zabbix server side, verify that the host is correctly defined in the web interface. Go to Configuration > Hosts and check the "Availability" column. Icons indicate network connectivity (green line), item availability (green circle), and trapper status (green square). A red icon signifies a problem.
If the network icon is red, the server cannot reach the agent. Double-check routing, DNS resolution, and firewall rules. If the item icon is red but the network icon is green, the issue lies with specific items or permissions.
SELinux and AppArmor Considerations
While Ubuntu uses AppArmor rather than SELinux, AppArmor profiles can sometimes restrict Zabbix agent behavior. Check if AppArmor is enforcing restrictions:
sudo aa-status
If AppArmor is active, ensure the Zabbix profile is in enforce mode and not complain mode causing unexpected blocks. Usually, the default profile allows necessary operations. However, custom modifications might require reloading the profile:
sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.zabbix_agentd
In rare cases, disabling AppArmor temporarily for testing can help isolate whether it is the cause:
sudo aa-disable /etc/apparmor.d/usr.sbin.zabbix_agentd
Remember to re-enable it after testing for security reasons.
Frequently Asked Questions
Why does my Zabbix agent show as unavailable even though the service is running?
This usually indicates a network or configuration mismatch. Verify that the Zabbix server's IP is listed in the
Server directive of the agent's config file. Also, ensure the firewall on the agent machine allows inbound TCP connections on port 10050 from the server's IP address.
How do I find the Zabbix agent log file on Ubuntu 22.04?
The default log file is located at
/var/log/zabbix/zabbix_agentd.log. You can view the last few lines using
tail -n 50 /var/log/zabbix/zabbix_agentd.log. Ensure you have read permissions, which may require using
sudo.
What if I changed the Zabbix server IP address? Do I need to reinstall the agent?
No, you do not need to reinstall. Simply edit
/etc/zabbix/zabbix_agentd.conf and update the
Server and
ServerActive directives with the new IP address. Then restart the service using
sudo systemctl restart zabbix-agent.
Can I use DNS names instead of IP addresses in the Zabbix agent configuration?
Yes, you can use DNS names in the
Server and
ServerActive directives. However, ensure that the agent machine can resolve the DNS name correctly. Using IP addresses is generally more reliable for avoiding resolution delays or failures during startup.
How do I check if the Zabbix agent is listening on the correct port?
Use the
ss or
netstat command to check listening ports. Run
sudo ss -tulnp | grep zabbix to see if the agent is listening on port 10050. The output should show
LISTEN state for the local address and port 10050.