Unit logstash.service entered failed state

Elastic Stack Logstash
1

I am trying to start logstash via sudo service logstash start

Redirecting to /bin/systemctl status logstash.service
● logstash.service - logstash
Loaded: loaded (/etc/systemd/system/logstash.service; disabled; vendor preset: disabled)
Active: active (running) since Thu 2019-01-03 11:49:52 UTC; 22min ago
Main PID: 11405 (java)
CGroup: /system.slice/logstash.service
└─11405 /bin/java -Xms1g -Xmx1g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.aw...

Jan 03 11:49:52 ip-172-31-40-86.us-west-2.compute.internal systemd[1]: logstash.service: main process exited, code=exited, status=143/n/a
Jan 03 11:49:52 ip-172-31-40-86.us-west-2.compute.internal systemd[1]: Unit logstash.service entered failed state.
Jan 03 11:49:52 ip-172-31-40-86.us-west-2.compute.internal systemd[1]: logstash.service failed.
Jan 03 11:49:52 ip-172-31-40-86.us-west-2.compute.internal systemd[1]: Started logstash.
Jan 03 11:49:52 ip-172-31-40-86.us-west-2.compute.internal systemd[1]: Starting logstash...

It seems to succeed (service status now is active ), however nothing gets written in logstash 's own logs, under /var/log/logstash/logstash-plain.log

Until a few minutes ago, starting / stopping the logstash service did produce output in the above log.

2

Check /var/log/logstash-stderr.log and /var/log/logstash-stdout.log if they exist. If not, try starting logstash manually (without systemd) to see if anything gets written to your console.

3

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