search

elastic / logstash-forwarder

An experiment to cut logs in preparation for processing elsewhere. Replaced by Filebeat: https://github.com/elastic/beats/tree/master/filebeat
Other
1.79k stars 413 forks source link

[rhel6.x ppc64] Logstash-forwarder cannot connect to logstash server, report "socket: function not implemented" #540

Open fenglixa opened 9 years ago

fenglixa commented 9 years ago

Built out logstash-forwarder for ppc64 by following steps of wiki: https://github.com/elastic/logstash-forwarder/blob/master/README.md But when I try to startup logstash-forwarder on RHEL6.4_ppc64 or RHEL6.5_ppc64 platform, there report errors of “socket: function not implemented”. as following:

[root@ppcrhel6d log]# uname -a Linux ppcrhel6d 2.6.32-358.el6.ppc64 #1 SMP Tue Jan 29 11:43:27 EST 2013 ppc64 ppc64 ppc64 GNU/Linux [root@ppc64test log]# 2015/10/11 23:17:42.640472 Connecting to [192.168.0.111]:5043 (ppc64test) 2015/10/11 23:17:42.640534 Failure connecting to 192.168.0.111: dial tcp 192.168.0.111:5043: socket: function not implemented 2015/10/11 23:17:43.640743 Connecting to [192.168.0.111]:5043 (ppc64test) 2015/10/11 23:17:43.640814 Failure connecting to 192.168.0.111: dial tcp 192.168.0.111:5043: socket: function not implemented 2015/10/11 23:17:44.641120 Connecting to [192.168.0.111]:5043 (ppc64test) 2015/10/11 23:17:44.641183 Failure connecting to 192.168.0.111: dial tcp 192.168.0.111:5043: socket: function not implemented 2015/10/11 23:17:45.641366 Connecting to [192.168.0.111]:5043 (ppc64test) 2015/10/11 23:17:45.641439 Failure connecting to 192.168.0.111: dial tcp 192.168.0.111:5043: socket: function not implemented 2015/10/11 23:17:46.641622 Connecting to [192.168.0.111]:5043 (ppc64test) 2015/10/11 23:17:46.641696 Failure connecting to 192.168.0.111: dial tcp 192.168.0.111:5043: socket: function not implemented 2015/10/11 23:17:47.641894 Connecting to [192.168.0.111]:5043 (ppc64test)

jordansissel commented 9 years ago

I don't know anything about the architecture (ppc64) you are running on, so I'm not sure how to help here.

fenglixa commented 9 years ago

Thanks @jordansissel. I am so glad you can pay attention on this, and I will provide more info timely once you needed. : ) ppc64 is the arch of IBM Power Server. I found the error was output by the function of "net.DialTimeout" in the file of "publisher1.go" ... ... tcpsocket, err := net.DialTimeout("tcp", addressport, config.timeout) if err != nil { emit("Failure connecting to %s: %s\n", address, err) time.Sleep(1 * time.Second) continue } ... ... I am wander some package/lib are missed in the environment, could you give some advise?

BTW, one question wish you could help answer: Which version of Go is used for building logstash-forwarder officially?

Thanks BR -Feng

driskell commented 9 years ago

@fenglixa My guess is Golang doesn't support that OS and is trying to do a syscall or library call that is not implemented.

It'll probably be painful to try trace it. Only thing that isn't strace or similar (which isn't guaranteed to show anything) is to change error to report with %v to see if it'll show more error info.

emit("Failure connecting to %s: %v\n", address, err)
fenglixa commented 9 years ago

@driskell, following is the output after changed error to report with %v:

... ... emit("Failure connectiing %s\n", timeoutt) tcpsocket, err := net.DialTimeout("tcp", addressport, timeoutt) if err != nil { emit("============Failure connecting to %s: %v\n", addressport, err) ... ...

2015/10/26 04:26:53 Failure connectiing 2m30s 2015/10/26 04:26:53 ============Failure connecting to [9.21.55.178]:5000: dial tcp 9.21.55.178:5000: socket: function not implemented 2015/10/26 04:26:54 Failure connectiing 2m30s 2015/10/26 04:26:54 ============Failure connecting to [9.21.55.178]:5000: dial tcp 9.21.55.178:5000: socket: function not implemented 2015/10/26 04:26:55 Failure connectiing 2m30s 2015/10/26 04:26:55 ============Failure connecting to [9.21.55.178]:5000: dial tcp 9.21.55.178:5000: socket: function not implemented

jordansissel commented 9 years ago

This sounds like a bug in Go, not logstash-forwarder.