Zabbix server exception or troubleshooting method, zabbix exception

Zabbix server exception or troubleshooting method, zabbix exception

When an exception or fault occurs on the server monitored by zabbix, you can send an alarm via email to automatically remind the O & M personnel to handle the problem.

Environment

192.168.2.117 zabbixserver
192.168.2.119 zabbixagent
The curl version of server 117 must be 7.20 with the postfix service.

Set alert media type

Click the email button to go to the settings page and configure relevant parameters.

The smtp server writes smtp.139.com.
The default port number of the smt server is 25.
Smtp Email refers to the sender's email address.
Select normal password for authentication
The user name is the account of the mailbox
The password is the mailbox password. The account password here must actually exist. If the password does not exist or is written incorrectly, the system will prompt login denied when an error is reported.
Click Enable and then click Update.

Set User Information

Click admin to go to the setting page, click media, click add, and set the account information and receipt time of the email recipient.

Set action to add trigger conditions

A: Action Settings

B: Operation settings

Set the sender information and content after the trigger is triggered (generally a fault occurs. Here, step 1-3 indicates sending three times, with an interval of 60 s. Note: to add the information, click the add button.

C: Restore settings

Set the content/user information sent after fault recovery

Click Add to complete the Action Settings.

Test email alert

Manually stop the 119 agent service, as shown below:

Enable the agent to receive an email alert.

Because the default mail content is used, you can modify the mail content or directly configure the content in the Chinese format.

Set the web interface font to a Chinese font, and then reset the mail content
The email alert content is as follows:

The default title is: Fault {TRIGGER. STATUS}, server: {HOSTNAME1}, error: {TRIGGER. NAME! The default information is as follows: Alert HOST: {HOSTNAME1} alert time: {EVENT. DATE} {EVENT. TIME} alert level: {TRIGGER. SEVERITY} alert information: {TRIGGER. NAME} alert item: {TRIGGER. KEY1} problem details: {ITEM. NAME }:{ ITEM. VALUE} Current status: {TRIGGER. STATUS }:{ ITEM. VALUE1} event id: {EVENT. ID}

The email recovery content is as follows:

The restored title is set to {TRIGGER. STATUS}, and the server: {HOSTNAME1 }:{ TRIGGER. NAME} has been restored! The recovered information is: Alert HOST: {HOSTNAME1} alert time: {EVENT. DATE} {EVENT. TIME} alert level: {TRIGGER. SEVERITY} alert information: {TRIGGER. NAME} alert item: {TRIGGER. KEY1} problem details: {ITEM. NAME }:{ ITEM. VALUE} Current status: {TRIGGER. STATUS }:{ ITEM. VALUE1} event id: {EVENT. ID}

Then, manually stop the 119 agent service, and you can see the alarm email sending content.

Note:
1) when viewing the action information, if the prompt "Support for SMTP authentication was not compiled in" is displayed

Indicates that the curl version needs to be upgraded to version 7.20 or above, and the current version is 7.19

Solution:
Download curl. do not compile and install it. Use yum to install it.

cd /root/zabbixtestwget https://mirror.city-fan.org/ftp/contrib/yum-repo/city-fan.org-release-1-13.rhel6.noarch.rpmrpm  -ivh   city-fan.org-release-1-13.rhel6.noarch.rpmyum  upgrade  libcurl libcurl libcurl-devel -y

Restart the server and you can see that the curl version is 7.20.
Recompile zabbix

cd /root/zabbixtest/zabbix-3.2.7makemake install

Restart zabbix_server.