# Filebeat does not read new lines

**URL:** <https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 19, 2018, 2:13pm UTC](https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140 "2018-09-19T14:13:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![kater](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@kater](https://discuss.elastic.co/u/kater)\
**Post date:** [September 19, 2018, 2:13pm UTC](https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140/1 "2018-09-19T14:13:39Z")

</div>

Hello.  
I'm currently using a 6.4 ELK stack and 6.4 Filebeat on a other server.

A squid is running and the access.log get new lines but Filebeat is not able to read it.  
I even tried to "echo \>\>" the file but Filebeat just read nothing.

here is the filebeat conf

```
filebeat.inputs:
- type: log
  enabled: true
  paths:
    – /var/log/squid/access.log
output.logstash:
  hosts: ["10.137.200.18:5044"]
logging.level: debug

```

Filebeat load the input correctly

```
2018-09-19T15:31:01.031+0200 INFO instance/beat.go:273 Setup Beat: filebeat; Version: 6.4.0
2018-09-19T15:31:01.031+0200 DEBUG [beat] instance/beat.go:290 Initializing output plugins
2018-09-19T15:31:01.031+0200 DEBUG [processors] processors/processor.go:66 Processors:
2018-09-19T15:31:01.034+0200 DEBUG [publish] pipeline/consumer.go:137 start pipeline event consumer
2018-09-19T15:31:01.034+0200 INFO pipeline/module.go:98 Beat name: squid
2018-09-19T15:31:01.035+0200 INFO instance/beat.go:367 filebeat start running.
2018-09-19T15:31:01.035+0200 DEBUG [registrar] registrar/registrar.go:114 Registry file set to: /var/lib/filebeat/registry
2018-09-19T15:31:01.036+0200 INFO registrar/registrar.go:134 Loading registrar data from /var/lib/filebeat/registry
2018-09-19T15:31:01.036+0200 INFO registrar/registrar.go:141 States Loaded from registrar: 0
2018-09-19T15:31:01.036+0200 WARN beater/filebeat.go:371 Filebeat is unable to load the Ingest Node pipelines for the configured modules because the Elasticsearch output is not configured/enabled. If you have already loaded the Ingest Node pipelines or are using Logstash pipelines, you can ignore this warning.
2018-09-19T15:31:01.036+0200 INFO crawler/crawler.go:72 Loading Inputs: 1
2018-09-19T15:31:01.036+0200 DEBUG [processors] processors/processor.go:66 Processors:
2018-09-19T15:31:01.037+0200 DEBUG [input] log/config.go:201 recursive glob enabled
2018-09-19T15:31:01.037+0200 DEBUG [input] log/input.go:147 exclude_files: []. Number of stats: 0
2018-09-19T15:31:01.037+0200 DEBUG [input] log/input.go:168 input with previous states loaded: 0
**2018-09-19T15:31:01.037+0200 INFO log/input.go:138 Configured paths: [/– /var/log/squid/access.log]**
2018-09-19T15:31:01.037+0200 INFO input/input.go:114 Starting input of type: log; ID: 1805975221398277003
2018-09-19T15:31:01.037+0200 INFO crawler/crawler.go:106 Loading and starting Inputs completed. Enabled inputs: 1
2018-09-19T15:31:01.038+0200 INFO [monitoring] log/log.go:114 Starting metrics logging every 30s
2018-09-19T15:31:01.038+0200 DEBUG [registrar] registrar/registrar.go:267 Starting Registrar
2018-09-19T15:31:01.038+0200 DEBUG [input] log/input.go:174 Start next scan

```

But even if i add line to the file, filebeat does not seems to see something 🙂

```
2018-09-19T15:31:01.038+0200 DEBUG [input] log/input.go:174 Start next scan
2018-09-19T15:31:01.039+0200 DEBUG [input] log/input.go:195 input states cleaned up. Before: 0, After: 0, Pending: 0
2018-09-19T15:31:11.040+0200 DEBUG [input] input/input.go:152 Run input
2018-09-19T15:31:11.040+0200 DEBUG [input] log/input.go:174 Start next scan
2018-09-19T15:31:11.040+0200 DEBUG [input] log/input.go:195 input states cleaned up. Before: 0, After: 0, Pending: 0
2018-09-19T15:31:21.042+0200 DEBUG [input] input/input.go:152 Run input
2018-09-19T15:31:21.043+0200 DEBUG [input] log/input.go:174 Start next scan
2018-09-19T15:31:21.043+0200 DEBUG [input] log/input.go:195 input states cleaned up. Before: 0, After: 0, Pending: 0

```

Am i missing something ?  
Thank in advance.

---

<div class="post-metadata">

**Author:** ![jsoriano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jsoriano/32/27920_2.png) [@jsoriano](https://discuss.elastic.co/u/jsoriano)\
**Post date:** [September 19, 2018, 4:19pm UTC](https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140/2 "2018-09-19T16:19:30Z")

</div>

Hi @kater and welcome 🙂

It looks like your configuration contains a symbol that looks like a hyphen but it is not. In the log you can see that this is taking this symbol as part of the path (`Configured paths: [/– /var/log/squid/access.log]**`).  
Could you try to replace the hyphen before the path to be a normal hyphen (like the one on `- type: log`)?

---

<div class="post-metadata">

**Author:** ![kater](https://avatars.discourse-cdn.com/v4/letter/k/eb9ed0/32.png) [@kater](https://discuss.elastic.co/u/kater)\
**Post date:** [September 20, 2018, 7:22am UTC](https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140/3 "2018-09-20T07:22:27Z")

</div>

Thank you @jsoriano, it works ! I was sure this log line was weird looking

On vi theses hyphen are pretty similar :  
 ![image](https://us1.discourse-cdn.com/elastic/original/3X/4/7/47b9d420cd5fb817a5bfe2d812b94df035ce395d.png)

---

<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:** [October 18, 2018, 7:22am UTC](https://discuss.elastic.co/t/filebeat-does-not-read-new-lines/149140/4 "2018-10-18T07:22:27Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.