# Filbeat integrating with redis

**URL:** <https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [June 1, 2016, 4:27pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590 "2016-06-01T16:27:27Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Atul\_Patel](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Atul\_Patel](https://discuss.elastic.co/u/Atul_Patel)\
**Post date:** [June 1, 2016, 4:27pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/1 "2016-06-01T16:27:27Z")

</div>

Hi All,

We are working with filebeat integrating with redis cache.

When i start the filebeat it is not at all starting.

after i issued the yml file with -configtest it is hanged.How to see whether it is sucess or failure

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [June 2, 2016, 7:06am UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/2 "2016-06-02T07:06:51Z")

</div>

Can you share some more details? Filbeat version? Config file? Can you run it with `-e -d "*"` options and share the output?

---

<div class="post-metadata">

**Author:** ![Atul\_Patel](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Atul\_Patel](https://discuss.elastic.co/u/Atul_Patel)\
**Post date:** [June 2, 2016, 10:00am UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/3 "2016-06-02T10:00:55Z")

</div>

sudo /etc/init.d/filebeat status  
â filebeat.service - LSB: Sends log files to Logstash or directly to Elasticsearch.  
Loaded: loaded (/etc/rc.d/init.d/filebeat)  
Active: active (running) since Thu 2016-06-02 10:54:23 BST; 4min 46s ago  
Docs: man:systemd-sysv-generator(8)  
Process: 19916 ExecStop=/etc/rc.d/init.d/filebeat stop (code=exited, status=0/SUCCESS)  
Process: 21690 ExecStart=/etc/rc.d/init.d/filebeat start (code=exited, status=0/SUCCESS)  
CGroup: /system.slice/filebeat.service  
ââ21704 filebeat-god -r / -n -p /var/run/filebeat.pid -- /usr/bin/filebeat -c /etc/filebeat/filebeat.yml  
ââ21705 /usr/bin/filebeat -c /etc/filebeat/filebeat.yml

Jun 02 10:58:16 HOSTANME /usr/bin/filebeat[21705]: filebeat.go:134: Events sent: 40  
Jun 02 10:58:16 HOSTANME /usr/bin/filebeat[21705]: registrar.go:157: Registry file updated. 2236 states w...en.  
Jun 02 10:58:21 HOSTANME /usr/bin/filebeat[21705]: filebeat.go:134: Events sent: 10  
Jun 02 10:58:21 HOSTANME /usr/bin/filebeat[21705]: registrar.go:157: Registry file updated. 2236 states w...en.  
Jun 02 10:58:28 HOSTANME /usr/bin/filebeat[21705]: filebeat.go:134: Events sent: 17  
Jun 02 10:58:28 HOSTANME /usr/bin/filebeat[21705]: registrar.go:157: Registry file updated. 2236 states w...en.  
Jun 02 10:58:56 HOSTANME /usr/bin/filebeat[21705]: filebeat.go:134: Events sent: 66  
Jun 02 10:58:56 HOSTANME /usr/bin/filebeat[21705]: registrar.go:157: Registry file updated. 2236 states w...en.  
Jun 02 10:59:03 HOSTANME /usr/bin/filebeat[21705]: filebeat.go:134: Events sent: 125  
Jun 02 10:59:03 HOSTANME /usr/bin/filebeat[21705]: registrar.go:157: Registry file up

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [June 6, 2016, 10:06am UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/4 "2016-06-06T10:06:56Z")

</div>

please run filebeat in foreground from command line (don't use `/etc/init.d/filebeat`) via `filebeat -c /etc/filebeat/filebeat.yml -v -d '*'`.

---

<div class="post-metadata">

**Author:** ![Atul\_Patel](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Atul\_Patel](https://discuss.elastic.co/u/Atul_Patel)\
**Post date:** [June 8, 2016, 12:19pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/5 "2016-06-08T12:19:59Z")

</div>

After we start the filebeat like this (version is 1.2) the service is not coming to active

sudo service filebeat status  
â filebeat.service - filebeat  
Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled)  
Active: inactive (dead) since Wed 2016-06-08 13:12:01 BST; 4s ago  
Docs: [https://www.elastic.co/guide/en/beats/filebeat/current/index.html](https://www.elastic.co/guide/en/beats/filebeat/current/index.html)  
Process: 13066 ExecStop=/etc/init.d/filebeat stop (code=exited, status=0/SUCCESS)  
Process: 13044 ExecStart=/etc/init.d/filebeat start (code=exited, status=0/SUCCESS)  
Main PID: 13044 (code=exited, status=0/SUCCESS)

Jun 08 13:12:01 HOSTANME filebeat[13044]: [OK]  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: logp.go:130: Disable stderr logging  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: beat.go:135: Initializing output plugins  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: geolite.go:24: GeoIP disabled: No paths were set under...ths  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: client.go:297: ES Ping(url=http://localhost:9200, time...0s)  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: client.go:302: Ping request failed with: Head [http://l](http://l)...sed  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: outputs.go:126: Activated elasticsearch as output plugin.  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: logstash.go:106: Max Retries set to: 3  
Jun 08 13:12:01 HOSTANME /usr/bin/filebeat[13061]: client.go:100: connect  
Jun 08 13:12:01 HOSTANME filebeat[13066]: Stopping filebeat: [OK]  
Hint: Some lines were ellipsized, use -l to show in full.

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [June 8, 2016, 12:35pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/6 "2016-06-08T12:35:12Z")

</div>

what are you trying to do? Title states you want to connect to redis (not recommended for filebeat 1.x releases, but 5.x is ok), but logs print errors about writing to Elasticsearch + logstash output seems to be configured too. No redis in log.

what you mean by:

> After we start the filebeat like this (version is 1.2) the service is not coming to active

Sample output given by you is definitely not from filebeat running in foreground as requested.

---

<div class="post-metadata">

**Author:** ![Atul\_Patel](https://avatars.discourse-cdn.com/v4/letter/a/48db29/32.png) [@Atul\_Patel](https://discuss.elastic.co/u/Atul_Patel)\
**Post date:** [June 8, 2016, 1:00pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/7 "2016-06-08T13:00:32Z")

</div>

Sorry stefan wrong paste.I wanted to create a new ticket

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [June 22, 2016, 4:27pm UTC](https://discuss.elastic.co/t/filbeat-integrating-with-redis/51590/8 "2016-06-22T16:27:30Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.
