# Sincedb write error despite proper permissions

**URL:** <https://discuss.elastic.co/t/sincedb-write-error-despite-proper-permissions/112259>\
**Category:** Logstash\
**Created:** [December 18, 2017, 3:00pm UTC](https://discuss.elastic.co/t/sincedb-write-error-despite-proper-permissions/112259 "2017-12-18T15:00:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![makibroshett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/makibroshett/32/106322_2.png) [@makibroshett](https://discuss.elastic.co/u/makibroshett)\
**Post date:** [December 18, 2017, 3:00pm UTC](https://discuss.elastic.co/t/sincedb-write-error-despite-proper-permissions/112259/1 "2017-12-18T15:00:03Z")

</div>

Hi,

I installed LS 6.0 on Linux (2.6.18, centos). I have an error logged whenever LS attempts to write to a sincedb (not in the default folder), could you please help me finding out what is wrong ?

All kind of help is appreciated !

Olivier (config and debug logs follow)

Here is my pipeline configuration:

```
input
{
        file {
                path => "/home/logstash/gzfiles/file01.txt"
                sincedb_path =>"/data_bkp/logstash/test_sincedb/sincedb_file01"
        }
}

filter
{
}

output {
        stdout {codec => rubydebug}
}

```

On startup the sincedb file is created as expected (I have checked that LS is running as user logstash and group logstash):

> [2017-12-18T14:34:36,967][DEBUG][logstash.inputs.file] \_globbed\_files: /home/logstash/gzfiles/file01.txt: glob is: ["/home/logstash/gzfiles/file01.txt"]  
> [2017-12-18T14:34:36,968][DEBUG][logstash.inputs.file] \_discover\_file: /home/logstash/gzfiles/file01.txt: new: /home/logstash/gzfiles/file01.txt (exclude is )  
> [2017-12-18T14:34:36,975][DEBUG][logstash.inputs.file] \_open\_file: /home/logstash/gzfiles/file01.txt: opening  
> [2017-12-18T14:34:36,976][DEBUG][logstash.inputs.file] /home/logstash/gzfiles/file01.txt: initial create, no sincedb, seeking to end 312

Then I add a line to the input file, the data is indeed received and processed but I get the following message:

> [2017-12-18T14:34:47,207][DEBUG][logstash.inputs.file] \_sincedb\_write: error: /data\_bkp/logstash/test\_sincedb/sincedb\_file01: Permission denied - No message available  
> [2017-12-18T14:34:51,233][DEBUG][logstash.inputs.file] \_globbed\_files: /home/logstash/gzfiles/file01.txt: glob is: ["/home/logstash/gzfiles/file01.txt"]  
> [2017-12-18T14:34:51,989][DEBUG][logstash.pipeline] Pushing flush onto pipeline {:pipeline\_id=\>"gztest1", :thread=\>"#\<Thread:0x1c9d0ca@/opt/logstash-6.0.1/logstash-core/lib/logstash/pipeline.rb:290 sleep\>"}

Since the file is created w/o problem, I don't understand where the permission problem comes from. I double checked that it is ok (all above directories have r and x bit set for 'others'):

> [logstash@gsrecs01 gzfiles]$ ls -al /data\_bkp/logstash/test\_sincedb/  
> drwxrwxr-x 2 logstash logstash 64 Dec 18 14:34 .  
> drwxr-xr-x 2 logstash logstash 64 Dec 18 13:46 ..  
> -rw-rw-r-- 1 logstash logstash 19 Dec 18 14:34 sincedb\_file01

---

<div class="post-metadata">

**Author:** ![makibroshett](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/makibroshett/32/106322_2.png) [@makibroshett](https://discuss.elastic.co/u/makibroshett)\
**Post date:** [December 21, 2017, 2:47pm UTC](https://discuss.elastic.co/t/sincedb-write-error-despite-proper-permissions/112259/2 "2017-12-21T14:47:28Z")

</div>

I finally found out why: my sincedb file is created on a network drive, and the file input is not guaranteed/designed to work on non-local network volumes as specified in the doc...

Hope this helps not only me 🙂

---

<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:** [January 18, 2018, 2:47pm UTC](https://discuss.elastic.co/t/sincedb-write-error-despite-proper-permissions/112259/3 "2018-01-18T14:47:56Z")

</div>

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