# Beatfile doesn'f capture Docker's logs but others do, why? \[solved\]

**URL:** https://discuss.elastic.co/t/beatfile-doesnf-capture-dockers-logs-but-others-do-why-solved/63435
**Category:** Beats
**Tags:** filebeat
**Created:** [October 19, 2016, 7:37pm UTC](https://discuss.elastic.co/t/beatfile-doesnf-capture-dockers-logs-but-others-do-why-solved/63435 "2016-10-19T19:37:07Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![ndarkness](https://avatars.discourse-cdn.com/v4/letter/n/90db22/32.png) [@ndarkness](https://discuss.elastic.co/u/ndarkness)
#### Post date: [October 20, 2016, 2:03pm UTC](https://discuss.elastic.co/t/beatfile-doesnf-capture-dockers-logs-but-others-do-why-solved/63435/11 "2016-10-20T14:03:38Z")

</div>

I think this issue might be related to the starting of the filebeat in the client, I have hanged its initialization time in _rc.d_ with  
`sudo update-rc.d filebeat defaults 95 10`

I read that in [this post](http://www.mos-eisley.dk/display/it/Filebeat+troubleshooting), it does work!

```
2016-10-20T15:59:51+02:00 DBG Flushing spooler because of timeout. Events flushed: 3
    2016-10-20T15:59:51+02:00 DBG Publish: {
      "@timestamp": "2016-10-20T13:59:44.233Z",
      "beat": {
        "hostname": "VPSA",
        "name": "VPSA"
      },
      "count": 1,
      "fields": null,
      "input_type": "log",
 },
  "count": 1,
  "fields": null,
  "input_type": "log",
  "message": "Oct 20 15:59:39 artguard GW[1401]: message repeated 2 times: [#033[90m DEBUG#033[0m Handle PULL_DATA #033[90mGatewayID#033[0m=#033[90madapter#033[0m=gateway-semtech]",
  "offset": 17654,
  "source": "/var/log/syslog",
  "type": "syslog"
}
```

---

_[View the full topic](https://discuss.elastic.co/t/beatfile-doesnf-capture-dockers-logs-but-others-do-why-solved/63435)._