[code lang=”js”]
Starting Zabbix agent: zabbix_agentd [10808]: user zabbix does not exist
zabbix_agentd [10808]: cannot run as root![/code]
[code lang=”js”]groupadd zabbix[/code]
<p style="text-align: justify;"> <p> [code lang=”js”]chown zabbix:zabbix /var/run/zabbix/[/code] </p> <p style="text-align: justify;"> <p> [code lang=”js”]rm -f /var/log/zabbix/*[/code] </p> <p style="text-align: justify;"> <p> [code lang=”js”]rm -f /var/run/zabbix/*[/code] </p> <p style="text-align: justify;"> <p> [code lang=”js”]service zabbix-agent restart[/code] </p> <p style="text-align: justify;"> <p> [code lang=”js”]chkconfig zabbix-agent on[/code] </p> <p style="text-align: justify;"> This should fix the agent start-up problem.
[code language=”js”]# service zabbix-server restart[/code]
I love zabbix a lot because of its ease of use and the simplicity of the configuration when it comes to monitoring anything. I recently added a monitor to check the fragmentation level of volumes on a machine once a week and set it to trigger an alert when the fragmentation level reaches the set threshold.
I wrote a simple command line statement that would run the defrag check and output just the value.
DNS Port monitoring
_ – More zabbix alert configurations_
_ – Triggers and alerting via email or sms_
_ – Setup and use of graphs_
[code lang=”js”]
vi /etc/sysconfig/iptables
-A INPUT -m state –state NEW -m tcp -p tcp –dport 80 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 10050 -j ACCEPT
-A INPUT -m state –state NEW -m tcp -p tcp –dport 10051 -j ACCEPT
[/code]
[code lang=”js”]service iptables restart[/code]