Zabbix agent on is unreachable for 5 minutes - zabbix

I used zabbix 2.4 and it worked perfectly. I decided to upgrade server and all agents to 3.0 LTS. I did not change any settings in agents and server conf-files and did not change any settings wia web.
But now I receive messages
Zabbix agent %servername% on is unreachable for 5 minutes
This agent works on the same machine with zabbix-server. More strange that I receive other messages from this agent. So I can see that agent works and server can communicate with it.
After I started to receive this error message I tried to change IP of agent. First it was 127.0.0.1, after I changed address to network's IP: 192.168.x.x. Nothing changed. I receive unreachable message every 6-7 minutes with the other messages from this agent. And also this agent is green via web-interface.
zabbix_get -s 127.0.0.1 -k agent.ping
also returns 1.
How to fix problem?

I increased Timeout and error has gone

take zabbix server restart and it will work.

You can check also zabbix_agentd.conf and replace valid IP and name

Related

Zabbix agent Interrupted system call

Recently, there is a host which indicates me the error message :
Get value from agent failed: cannot connect to [] interrupted system call
I do not understand what happens to it, this host uses an agent zabbix on the port 10050.
Except that on my 10 other hosts which are also with a zabbix agent there is no problem, it's really only on one that I have this problem.
I've tried to search on the web but nothing works.
Could it be a problem with the agent installed on the host?

Zabbix Mattermost notification integrations - Timeout exceeded while connecting to 'localhost' when testing Mattermost Media Type

I am trying to intergrate our mattermost with zabbix to receive notifications on alerts. I've followed up the instructions on this link. We are using Zabbix 4.4 with MM 5.19.
After enabling the integration, No alerts are being posted on Mattermost. I tried testing the Media type on Administration > Media Types > Mattermost > Test.
I've added the following as the parameters, but it throws the error : Connection timeout of 3 seconds exceeded when connecting to Zabbix server "localhost".
bot_token : {Token generated for the Bot in Mattemost}
mattermost_url : {https://mattermost.our-company.com}
send_mode : alarm
Tried changing {ZABBIX_URL} to both http://127.0.0.1 and http://zabbix.our-company.com (The DNS is resolved only internally, but our mattermost is available on public network) but none of them work.
I checked the logs inside /var/log/zabbix but no error or anything. I even tried putting the zabbix logs to Debug mode but no luck in any case, the only Debug log I've got is the following :
2063:20200216:090224.146 trapper got '{"request":"alert.send","sid":"74095b240dd6783618571516f029187a","data":{"parameters":{"zabbix_url":"{$ZABBIX.URL}","send_mode":"alarm","send_to":"{ALERT.SENDTO}","event_tags":"{EVENT.TAGS}","event_name":"{EVENT.NAME}","event_nseverity":"{EVENT.NSEVERITY}","event_ack_status":"{EVENT.ACK.STATUS}","event_value":"{EVENT.VALUE}","event_update_status":"{EVENT.UPDATE.STATUS}","event_date":"{EVENT.DATE}","event_time":"{EVENT.TIME}","event_severity":"{EVENT.SEVERITY}","event_opdata":"{EVENT.OPDATA}","event_id":"{EVENT.ID}","event_update_message":"{EVENT.UPDATE.MESSAGE}","trigger_id":"{TRIGGER.ID}","trigger_description":"{TRIGGER.DESCRIPTION}","host_name":"{HOST.NAME}","host_ip":"{HOST.IP}","event_update_date":"{EVENT.UPDATE.DATE}","event_update_time":"{EVENT.UPDATE.TIME}","event_recovery_date":"{EVENT.RECOVERY.DATE}","event_recovery_time":"{EVENT.RECOVERY.TIME}","bot_token":"qs3rkqdappy6i8gs3a8871phxc","mattermost_url":"https:\/\/mattermost.our-company.com"},"mediatypeid":"7"}}'
What can be the issue? Is there a way to "debug" and find the root cause of this error? Any help is appreciated! Note that right now we have integrated Slack with Zabbix and it's working fine, but we are moving to Mattermost and therefore, we need to migrate the integrations as well.
We found out the issue with our Network Admin. The problem was that our Zabbix server was trying to resolve Mattermost name from local network route (i.e. 192.168.x.x) and it kept failing, therefore, no SSL connection could be initiated.
It seems that Zabbix integration tests' error messages are quite generic and sometimes, misleading. Thorough investigation is needed for finding out the root cause.

Exception occurred while flushing email queue on Ionos virtual cloud server

I have a Symfony 4 application running on 1und1 on a package called "1&1 Unlimited Plus". The SMTP config looks like this:
MAILER_URL=smtp://smtp.1and1.com?username=****&password=******
and it works fine. I also have a development copy of this application on my local dev server with same config. This dev copy can send emails, too.
Since the databases on "1&1 Unlimited Plus" are limited to 1GB, I ordered another cloud server from Ionos. With the same config I am not able to send emails. I got this error in dev.log:
Exception occurred while flushing email queue: Connection could not be established with host smtp.1and1.com [Connection timed out #110]
Ping on smtp.1and1.com works, it reveals the same IP like if I ping on my dev server. On this cloud server I have running:
Plesk Onyx
Ubuntu 18.04.2 LTS‬
DNS turned off. I have just an A-record on the origin server to the IP of cloud server. NO MX-records set.
I checked the firewall rules. No outgoing limits found, just incoming. I added TCP 25 to incoming rules but I dont know if it is necessary.
I tried another ports but then I got this:
Exception occurred while flushing email queue: Expected response code 220 but got an empty response []
More config:
swiftmailer:
url: '%env(MAILER_URL)%'
spool: { type: 'memory' }
Any idea whats wrong?
I found the solution. Ionos closes the outgoing port 25 per default. This is nothing I can find or change in admin area, only technical support can open this port.

IDAS not connecting to the ContextBroker

i'm having a problem sending the mesurements to the contextBroker.
I have the ContextBroker running on a CentOS virtual machine. On another CentOS virtual machine i'm setting the figway config.ini file with the host=/ContextBroker Virtual Machine Host IP/ and Port=1026. When i send mesurements to my ContextBroker:
python2.7 SendObservation.py Bus1 't|1'
it simply doesn't stick the values to the entity. It gives me a code:200 but the response is just blank.
What am i doing wrong?
UPDATE:
Even when i do from one VM to another (to the one where the contextBroker is running) the command:
GET *ip*:1026/version
, it returns nothing.
UPDATE:
Running
GET localhost:1026/version
works. Returns what's supose to return.
The problem could be similar to the one described in the answer to this question. The most probable causes of Orion connection problems are:
Something in the Orion host (e.g a firewall or security group) is blocking the incoming connection
Something in the client host (e.g a firewall) is blocking the outcoming connection
There is some other network issue is causing the connection problem.

zabbix-agent active config: ZBX_TCP_READ() failed

I'm using Zabbix 2.2.6 for both server and clients and trying to configure zabbix-agent works only for active mode. Basically I set on /etc/zabbix/zabbix_agentd.conf
ServerActive=zabbix_server_ip
StartAgents=0
I clone 2 templetes in zabbix server web GUI Template App Zabbix Agent Active and change all item type to Zabbix agent active mode. Then add the client and link to that template.
I also open firewall on Zabbix server port 10050 and 10051 for client. On client I can telnet and check that connection is okay for those 2 ports. But I still got this error:
active check configuration update from [zabbix_server_ip:10051] started to fail (ZBX_TCP_READ() failed: [104] Connection reset by peer)
On passive mode everything work fine except sometimes it returns the anyoing error:
Zabbix agent on MY_CLIENT_NODE is unreachable for 5 minutes
I think switch to active mode can solve this problem since I update the server to latest version of 2.2.x.
Please give me suggest about this case.