# Logstash 7.9.1 have issues in ARM

**URL:** <https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596>\
**Category:** Logstash\
**Created:** [September 23, 2020, 1:04am UTC](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596 "2020-09-23T01:04:00Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [September 24, 2020, 5:04pm UTC](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596/7 "2020-09-24T17:04:19Z")

</div>

> [@goutham968](#):
>
> ```auto
> Stack: org/jruby/RubyFile.java:675:in `chown'
> 
> /aarch64/Logstash-agent/Logstash-agent-6624.0-0/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-input-file-4.2.1/lib/filewatch/helper.rb:41:in `write_atomically'
> 
> ```

This feels like a bug to me. Only privileged processes can change the ownership of a file. Calling chown makes no sense to me. I could understand trying to chgrp (and ignoring a failure) but not chown.

If you have some systems where it works and some where it does not then I would guess the ones where it works are [choosing](https://github.com/logstash-plugins/logstash-input-file/blob/be18de77292f0aafb667debbdef8fe7297065fe3/lib/filewatch/sincedb_collection.rb#L20) to use the non-atomic write function.

The non-atomic write is used on Windows, or if the sincedb\_path points to something that is neither a character nor a block device. Frankly I cannot think of a circumstance where that would occur, but you seem to have hit it.

---

_[View the full topic](https://discuss.elastic.co/t/logstash-7-9-1-have-issues-in-arm/249596)._