# Runtime panic error using Apache2 module **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [September 11, 2017, 10:02am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028 "2017-09-11T10:02:09Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![cuttlefishjones](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@cuttlefishjones](https://discuss.elastic.co/u/cuttlefishjones)\ **Post date:** [September 11, 2017, 10:02am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028/1 "2017-09-11T10:02:09Z")
Hi, I've been having no luck importing customised Apache2 logs into ES via logstash; my GROK always timeouts or give message too large errors which no one can seem to fix, so before ditching logstash and filebeat completely (in favour of Fluentd which seems to work out of the box) I thought I'd give the Apache2 module a go. I have a basic yml file: ```auto output.elasticsearch: hosts: ["xx.xx.xx.xx:9200"] ``` and am trying to test the module via the command line: `./filebeat -e -modules=apache2 -setup -c /etc/filebeat/filebeat_apache.yml` and I get the following response: ```auto 2017/09/11 09:19:34.150716 beat.go:285: INFO Home path: [/usr/share/filebeat/bin] Config path: [/usr/share/filebeat/bin] Data path: [/usr/share/filebeat/bin/data] Logs path: [/usr/share/filebeat/bin/logs] 2017/09/11 09:19:34.150736 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.1 2017/09/11 09:19:34.150784 metrics.go:23: INFO Metrics logging every 30s 2017/09/11 09:19:34.150789 output.go:258: INFO Loading template enabled. Reading template file: /usr/share/filebeat/bin/filebeat.template.json 2017/09/11 09:19:34.151335 output.go:269: INFO Loading template enabled for Elasticsearch 2.x. Reading template file: /usr/share/filebeat/bin/filebeat.template-es2x.json 2017/09/11 09:19:34.151986 output.go:281: INFO Loading template enabled for Elasticsearch 6.x. Reading template file: /usr/share/filebeat/bin/filebeat.template-es6x.json 2017/09/11 09:19:34.152599 client.go:128: INFO Elasticsearch url: http://xx.xx.xx.xx:9200 2017/09/11 09:19:34.152615 outputs.go:108: INFO Activated elasticsearch as output plugin. 2017/09/11 09:19:34.152652 publish.go:295: INFO Publisher name: standalone47 2017/09/11 09:19:34.152757 async.go:63: INFO Flush Interval set to: 1s 2017/09/11 09:19:34.152768 async.go:64: INFO Max Bulk Size set to: 50 2017/09/11 09:19:34.153439 client.go:128: INFO Elasticsearch url: http://xx.xx.xx.xx:9200 panic: runtime error: index out of range goroutine 1 [running]: panic(0x937580, 0xc42000e1d0) /usr/local/go/src/runtime/panic.go:500 +0x1a1 net/http.useProxy(0xc4202b2f07, 0xa, 0xf) /usr/local/go/src/net/http/transport.go:1124 +0x48d net/http.ProxyFromEnvironment(0xc4201a0960, 0xc4202b2f07, 0xf, 0xc4202b30a0) /usr/local/go/src/net/http/transport.go:261 +0x91 net/http.(*Transport).connectMethodForRequest(0xc4201a0780, 0xc4202b30a0, 0x0, 0xc4202b2f00, 0x4, 0xc4202b2f07, 0xf, 0xc41ffea67b, 0xc4201d7350) /usr/local/go/src/net/http/transport.go:563 +0xc6 net/http.(*Transport).RoundTrip(0xc4201a0780, 0xc4201a0960, 0xc4201a0780, 0xed1484c80, 0x925891e) /usr/local/go/src/net/http/transport.go:357 +0x26d net/http.send(0xc4201a0870, 0xc7d600, 0xc4201a0780, 0xed1484c80, 0x925891e, 0xd455e0, 0x8, 0xc4201d7648, 0xc420172368) /usr/local/go/src/net/http/client.go:256 +0x15f net/http.(*Client).send(0xc4202c23c0, 0xc4201a0870, 0xed1484c80, 0x925891e, 0xd455e0, 0xc420172368, 0x0, 0x1) /usr/local/go/src/net/http/client.go:146 +0x102 net/http.(*Client).doFollowingRedirects(0xc4202c23c0, 0xc4201a0870, 0xa2d2d8, 0x3, 0x625c01, 0xc4202c23f0) /usr/local/go/src/net/http/client.go:528 +0x5e5 net/http.(*Client).Do(0xc4202c23c0, 0xc4201a0870, 0xc4201d7870, 0x9e5acc, 0x10) /usr/local/go/src/net/http/client.go:184 +0x1ea github.com/elastic/beats/libbeat/outputs/elasticsearch.(*Connection).execHTTPRequest(0xc42018a780, 0xc4201a0870, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0) /go/src/github.com/elastic/beats/libbeat/outputs/elasticsearch/client.go:715 +0x1d2 github.com/elastic/beats/libbeat/outputs/elasticsearch.(*Connection).execRequest(0xc42018a780, 0x9db221, 0x3, 0xc4202b2f00, 0x16, 0x0, 0x0, 0x27, 0x0, 0x0, ...) /go/src/github.com/elastic/beats/libbeat/outputs/elasticsearch/client.go:702 +0xe7 github.com/elastic/beats/libbeat/outputs/elasticsearch.(*Connection).Ping(0xc42018a780, 0x14f46b0400, 0x0, 0x0, 0x0, 0xc4201d7ac8) /go/src/github.com/elastic/beats/libbeat/outputs/elasticsearch/client.go:640 +0x18c github.com/elastic/beats/libbeat/outputs/elasticsearch.(*Connection).Connect(0xc42018a780, 0x14f46b0400, 0x1, 0x1) /go/src/github.com/elastic/beats/libbeat/outputs/elasticsearch/client.go:623 +0x39 github.com/elastic/beats/libbeat/outputs/elasticsearch.NewConnectedClient(0xc42016d140, 0xc42016d501, 0x9e3c77, 0xd) /go/src/github.com/elastic/beats/libbeat/outputs/elasticsearch/output.go:86 +0x11a github.com/elastic/beats/libbeat/beat.(*Beat).loadDashboards(0xc420192000, 0x0, 0x0) /go/src/github.com/elastic/beats/libbeat/beat/beat.go:314 +0x1ee github.com/elastic/beats/libbeat/beat.(*Beat).launch(0xc420192000, 0xa2c8e8, 0x0, 0x0) /go/src/github.com/elastic/beats/libbeat/beat/beat.go:216 +0x517 github.com/elastic/beats/libbeat/beat.Run(0x9dfd86, 0x8, 0x0, 0x0, 0xa2c8e8, 0xc420176364, 0xc4200001a0) /go/src/github.com/elastic/beats/libbeat/beat/beat.go:141 +0x65 main.main() /go/src/github.com/elastic/beats/filebeat/main.go:22 +0x57 ``` I'm guessing with it being an index out of range that something screwey is happening when it trying to push the ES details out of the setup array. I've also tried with it all being in the YML file: ```auto filebeat.modules: - module: apache2 access: var.paths: ["/xxx/xxx/xxx/apache_logs/*.log"] error: var.paths: ["/xxx/xxx/xxx/apache_logs/*.log"] output.elasticsearch: hosts: ["xx.xx.xx.xx:9200"] ``` Is there something obviously wrong with this? I've only got one more day to show that Logstash and filebeat are stable and dependable enough to be used by the organisation before we write them off. ---
**Author:** ![cuttlefishjones](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@cuttlefishjones](https://discuss.elastic.co/u/cuttlefishjones)\ **Post date:** [September 22, 2017, 9:26am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028/2 "2017-09-22T09:26:14Z")
I've fixed this as well. ---
**Author:** ![exekias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/exekias/32/28718_2.png) [@exekias](https://discuss.elastic.co/u/exekias)\ **Post date:** [September 22, 2017, 9:51am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028/3 "2017-09-22T09:51:30Z")
Hi @cuttlefishjones, sorry for the late reply, did you fix this issue? How did yo do it? ---
**Author:** ![cuttlefishjones](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@cuttlefishjones](https://discuss.elastic.co/u/cuttlefishjones)\ **Post date:** [September 26, 2017, 10:38am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028/4 "2017-09-26T10:38:55Z")
Fluentd! ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 24, 2017, 10:39am UTC](https://discuss.elastic.co/t/runtime-panic-error-using-apache2-module/100028/5 "2017-10-24T10:39:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.