# Logstash stopped processing because of an error: (SystemExit) exit

**URL:** <https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997>\
**Category:** Logstash\
**Created:** [December 15, 2021, 2:39pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997 "2021-12-15T14:39:31Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sama.sowjanya](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@sama.sowjanya](https://discuss.elastic.co/u/sama.sowjanya)\
**Post date:** [December 15, 2021, 2:39pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/1 "2021-12-15T14:39:31Z")

</div>

Hi

I am getting the error when I run the config file through 'systemctl start logstash'

log----  
[2021-12-15T13:49:55,003][INFO][logstash.runner] Log4j configuration path used is: /etc/logstash/log4j2.properties  
[2021-12-15T13:49:55,016][INFO][logstash.runner] Starting Logstash {"logstash.version"=\>"7.16.1", "jruby.version"=\>"jruby 9.  
2.20.1 (2.5.8) 2021-11-30 2a2962fbd1 OpenJDK 64-Bit Server VM 11.0.13+8 on 11.0.13+8 +indy +jit [linux-x86\_64]"}  
[2021-12-15T13:49:55,450][FATAL][org.logstash.Logstash] Logstash stopped processing because of an error: (SystemExit) exit  
org.jruby.exceptions.SystemExit: (SystemExit) exit  
at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:747) ~[jruby-complete-9.2.20.1.jar:?]  
at org.jruby.RubyKernel.exit(org/jruby/RubyKernel.java:710) ~[jruby-complete-9.2.20.1.jar:?]  
at usr.share.logstash.lib.bootstrap.environment.(/usr/share/logstash/lib/bootstrap/environment.rb:94) ~[?:?]

I have found that "uuid" file is not present in /var/lib/logstash/ path  
and also I am not able to delete ".lock" file, it says file not found. (tried this as work around as suggested for another case.)

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/f/5/f54e65d4910b7d700a15fd56236d1b5a29c67524.png)

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [December 15, 2021, 8:44pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/2 "2021-12-15T20:44:23Z")

</div>

Is this the result of upgrading an existing installation?

A change in permissions on `/usr/share/logstash` from `logstash` to `root` took place in `7.13.0`. Can you check the permissions on the data folder under `/usr/share/logstash` , which I suspect may have been changed to `root` during the upgrade.

To get the up and running again, we should be able to change the permissions of the `data` path under `/usr/share/logstash/` to the `logstash` user, rather than `root` .

---

<div class="post-metadata">

**Author:** ![sama.sowjanya](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@sama.sowjanya](https://discuss.elastic.co/u/sama.sowjanya)\
**Post date:** [December 16, 2021, 9:23am UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/3 "2021-12-16T09:23:55Z")

</div>

Is this the result of upgrading an existing installation? -- not sure. I did not run this logstash before upgradation.

I have changed the he permissions of the `data` path under `/usr/share/logstash/` to the `logstash` user but I cannot see any difference. I am still getting the same error.

---

<div class="post-metadata">

**Author:** ![sama.sowjanya](https://avatars.discourse-cdn.com/v4/letter/s/c2a13f/32.png) [@sama.sowjanya](https://discuss.elastic.co/u/sama.sowjanya)\
**Post date:** [December 16, 2021, 12:10pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/5 "2021-12-16T12:10:55Z")

</div>

Thank you @yaauie

Issue is resolved.

I have changed the permission of all the files under '/etc/logstash/' and '/usr/share/logsash' to logstash from root.  
chwon logstash: \*

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [December 16, 2021, 3:10pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/6 "2021-12-16T15:10:49Z")

</div>

From a security standpoint, the Logstash user should  
not have ownership of the Logstash installation. It should only have read permission on its installation, and write permission on only its data directory.

---

<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 13, 2022, 3:10pm UTC](https://discuss.elastic.co/t/logstash-stopped-processing-because-of-an-error-systemexit-exit/291997/7 "2022-01-13T15:10:50Z")

</div>

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