# Error writing snapshot: compaction in progress: open /var/lib/influxdb/data/\_internal/monitor/2/000000181-000000001.tsm.tmp: no such file or directory engine=tsm1

**URL:** <https://community.influxdata.com/t/error-writing-snapshot-compaction-in-progress-open-var-lib-influxdb-data-internal-monitor-2-000000181-000000001-tsm-tmp-no-such-file-or-directory-engine-tsm1/3851>\
**Category:** Systems\
**Tags:** influxdb\
**Created:** [February 1, 2018, 7:49am UTC](https://community.influxdata.com/t/error-writing-snapshot-compaction-in-progress-open-var-lib-influxdb-data-internal-monitor-2-000000181-000000001-tsm-tmp-no-such-file-or-directory-engine-tsm1/3851 "2018-02-01T07:49:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![f1outsourcing](https://avatars.discourse-cdn.com/v4/letter/f/a183cd/32.png) [@f1outsourcing](https://community.influxdata.com/u/f1outsourcing)\
**Post date:** [February 1, 2018, 7:49am UTC](https://community.influxdata.com/t/error-writing-snapshot-compaction-in-progress-open-var-lib-influxdb-data-internal-monitor-2-000000181-000000001-tsm-tmp-no-such-file-or-directory-engine-tsm1/3851/1 "2018-02-01T07:49:35Z")

</div>

error writing snapshot: compaction in progress: open /var/lib/influxdb/data/\_internal/monitor/2/000000181-000000001.tsm.tmp: no such file or directory engine=tsm1

Directory 2 is indeed not there, is there something that can be concluded from this?

---

<div class="post-metadata">

**Author:** ![tim.hall](https://sea1.discourse-cdn.com/flex023/user_avatar/community.influxdata.com/tim.hall/32/39_2.png) [@tim.hall](https://community.influxdata.com/u/tim.hall)\
**Post date:** [February 1, 2018, 11:33pm UTC](https://community.influxdata.com/t/error-writing-snapshot-compaction-in-progress-open-var-lib-influxdb-data-internal-monitor-2-000000181-000000001-tsm-tmp-no-such-file-or-directory-engine-tsm1/3851/2 "2018-02-01T23:33:28Z")

</div>

what version of InfluxDB is this? When compactions run, tsm.tmp files are compacted into larger .tsm files. This kind of error may indicate a race condition between some activities the database is running. The database itself is logging the error, but should recover from this. I’m curious to know which version you are running as there were some improvements made in the 1.4 release to address an issue like this. It is possible we didn’t catch all of the possible situations where this might occur – so, a little more information would be useful. Thanks!

---

<div class="post-metadata">

**Author:** ![f1outsourcing](https://avatars.discourse-cdn.com/v4/letter/f/a183cd/32.png) [@f1outsourcing](https://community.influxdata.com/u/f1outsourcing)\
**Post date:** [February 26, 2018, 12:48pm UTC](https://community.influxdata.com/t/error-writing-snapshot-compaction-in-progress-open-var-lib-influxdb-data-internal-monitor-2-000000181-000000001-tsm-tmp-no-such-file-or-directory-engine-tsm1/3851/3 "2018-02-26T12:48:43Z")

</div>

Now I am running influxdb-1.4.2-1.x86\_64 on CentOS7. I am not sure if this is still occuring since I sort of disabled logging by influxdb because of this issue

> [@Stop logging NaN possible?](https://community.influxdata.com/t/stop-logging-nan-possible/3721):
>
> Is there a way to prevent this logging being send to the syslog server (not filtering at the syslog server) influxd: [I] 2018-01-19T21:23:56Z Dropping point ceph\_value: NaN is an unsupported value for field value service=collectd influxd: [I] 2018-01-19T21:23:56Z Dropping point ceph\_value: NaN is an unsupported value for field value service=collectd influxd: last message repeated 156 times