[ZBX-10750] Get value from agent failed: cannot connect to [[141.170.130.96]:10050]: [4] Interrupted system call Created: 2016 May 04  Updated: 2017 May 30  Resolved: 2016 May 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: None
Affects Version/s: 2.2.11
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Adrian Bardossy Assignee: Unassigned
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Hello

my name is Adrian Bardossy and I was setting up zabbix for server monitoring.

I was setting up Passive agent. I set up Server on zabbix server IP and Hostname, on web interface I set up hostname in upper part and IP address, and after reloading zabbix service on OS centos 6 I see this error message: Get value from agent failed: cannot connect to [[141.170.130.96]:10050]: [4] Interrupted system call.

In /var/log/zabbix log file is:
28278:20160504:153213.964 Starting Zabbix Agent [seco.mujhelpdesk.cz]. Zabbix 2.2.11 (revision 56693).
28278:20160504:153213.964 using configuration file: /etc/zabbix_agentd.conf
28279:20160504:153213.964 agent #0 started [collector]
28280:20160504:153213.965 agent #1 started listener #1
28281:20160504:153213.965 agent #2 started listener #2
28282:20160504:153213.965 agent #3 started listener #3
28283:20160504:153213.965 agent #4 started listener #4
28284:20160504:153213.966 agent #5 started listener #5

Do you know how to carry on? Ping is succesfull. Every other server is set up like this one the same configuration but in this case it does not work.

Thanks for your response,
Best regards,
Adrian Bardossy



 Comments   
Comment by Aleksandrs Saveljevs [ 2016 May 05 ]

This tracker is for bug reports only. For troubleshooting and community support, please refer to https://www.zabbix.org/wiki/Getting_help .

If, however, you have purchased commercial support from Zabbix LLC, please move this issue to the appropriate project.

Generated at Sun May 18 07:55:29 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.