Error Zbx_tcp_read Failed
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us get value from agent failed cannot connect to 4 interrupted system call Learn more about Stack Overflow the company Business Learn more about hiring developers zbx_tcp_read() failed: [104] connection reset by peer or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack
Zbx_tcp_read() Failed Interrupted System Call
Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up zabbix-agent active config: ZBX_TCP_READ() failed up vote
Get Value From Agent Failed Zbx_tcp_read() Failed 104 Connection Reset By Peer
1 down vote favorite 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 zabbix 4 interrupted system call 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. zabbix share|improve this question edited Oct 7 '14 at 8:34 asked Oct 7 '14 at 8:21 neo0 230413 add a comment| active oldest votes Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook. Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Browse other questions tagged zabbix or ask your own questio
instructions: Windows Mac Red Hat Linux Ubuntu Click URL instructions: Right-click on ad, choose "Copy Link", then paste here → (This may not be possible with some types of ads) More
Zabbix Cannot Connect To Interrupted System Call
information about our ad policies X You seem to have CSS turned off. zabbix connection reset by peer Please don't fill out this field. You seem to have CSS turned off. Please don't fill out this field. "active check configuration update from" "started to fail" Briefly describe the problem (required): Upload screenshot of ad (required): Select a file, or drag & drop file here. ✔ ✘ Please provide the ad click URL, if possible: Home Browse ZABBIX http://stackoverflow.com/questions/26231592/zabbix-agent-active-config-zbx-tcp-read-failed Mailing Lists ZABBIX Enterprise-class, distributed monitoring solution for networks & apps Brought to you by: apustovalov, hugetoad, tatjana-zabbix Summary Files Reviews Support Wiki Mailing Lists News zabbix-announce zabbix-developers zabbix-packagers zabbix-translators zabbix-users Re: [Zabbix-users] Status of Zabbix Agent Re: [Zabbix-users] Status of Zabbix Agent From: Umair Mehmood
I had just fired http://systemsoperations.blogspot.com/2013/07/get-value-from-agent-failed-zbxtcpread.html up. As I was investigating, I found that http://kakakikikeke.blogspot.com/2013/01/zabbixget-value-error-zbxtcpread-failed.html there was a hung connection to the primary resolver listed in /etc/resolv.conf. Turns out that network segment didn't have a firewall exclusion for the new caching name server I had installed interrupted system not too long ago. I added a firewall exclusion and a minute or so later the node was reporting data in my Zabbix web console. UPDATE: I've also experienced the same issue where the node had no issue contacting interrupted system call the resolver listed in /etc/resolv.conf. The fix was to add an entry in /etc/hosts for the Zabbix server. It's odd that it only affected one RHEL node. TLDR: This error message is related to some type of failure of the DNS subsystem on the target node. Posted by Laurent at 15:08 Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Zabbix No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Archive ► 2014 (2) ► October (1) ► April (1) ▼ 2013 (2) ▼ July (1) Get value from agent failed: ZBX_TCP_READ() failed... ► May (1) About Me Laurent View my complete profile Simple template. Powered by Blogger.
zabbix_agent.confの「Server=」の部分に記載されているIPによって そのzabbix-agentがプライベート通信するのかグローバル側で通信するのかが決定する つまり書かれているIPによって通信するNICが変わってることですね しらんかったぜよ ネットワーク系のエラーだったのFWかなーと思ったが・・・まさかでした 冷静になれば確かにと思うんですがね 投稿者 kaka kikikeke 時刻: 8:20 メールで送信BlogThis!Twitter で共有するFacebook で共有するPinterest に共有 ラベル: Zabbix, 技術 0 件のコメント: コメントを投稿 次の投稿 前の投稿 ホーム 登録: コメントの投稿 (Atom) 技術 AllJoyn (1) Android (19) AndroidStudio (3) Ant (7) Apache (14) Arduino (2) AWS (10) BLE (8) C (1) Capistrano (9) chef (21) Cloud (7) consul (1) Cygwin (8) docker (5) drone (1) Eclipse (20) ElasticSearch (5) elixir (1) emacs (33) embulk (2) Firefox (9) fluentd (6) git (24) go (1) gradle (2) graphviz (2) guideline (4) hadoop (3) Heroku (2) HTML (2) hubot (1) iOS (9) IoT (1) iTunes (1) Java (44) JavaScript (5) Jekyll (5) Jenkins (40) kafka (1) latex (1) Linux (79) LogStash (1) lua (2) Mac (9) Maven (17) memcached (1) MongoDB (15) mosquitto (1) Munin (1) MySQL (15) NewRelic (2) nfc (1) nginx (6) NiftyCloud (11) Nodejs (1) Office (2) Parse.com (5) Perl (7) PHP (16) Puppet (1) Python (7) RabbitMQ (8) RaspberryPi (25) Redis (13) Ruby (23) Selenium (8) serverspec (3) shellscript (24) Spring.io (11) struts (3) supervisor (1) tmux (6) Tomcat (5) Twitter (7) Vagrant (6) VMware (9) Vyatta (1) WebServ