Unable to start Logstash service on Linux Ubuntu 20.04

Dung Do Tien Mar 14 2022 32

Hello Guys. I installed Logstash on my server Ubuntu 20.04. I got a problem I can not start Logstash service after stop it. 

After running command:

sudo systemctl stop logstash.service

And then check status, it's result:

● logstash.service - logstash
   Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm) since Sun 2022-03-13 04:20:41 UTC; 3h 11min ago
 Main PID: 2055 (java)
    Tasks: 24 (limit: 4915)
   CGroup: /system.slice/logstash.service
           └─2055 /usr/share/logstash/jdk/bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancy
Mar 12 10:00:19 instance-3 logstash[2055]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecat
Mar 12 10:00:39 instance-3 logstash[2055]: Sending Logstash logs to /var/log/logstash which is now configured via l
Mar 12 10:00:39 instance-3 logstash[2055]: [2022-03-12T10:00:39,699][INFO ][logstash.runner          ] Log4j config
Mar 12 10:00:39 instance-3 logstash[2055]: [2022-03-12T10:00:39,712][INFO ][logstash.runner          ] Starting Log
Mar 12 10:00:39 instance-3 logstash[2055]: [2022-03-12T10:00:39,715][INFO ][logstash.runner          ] JVM bootstra
Mar 12 10:00:41 instance-3 logstash[2055]: [2022-03-12T10:00:41,532][INFO ][logstash.agent           ] Successfully
Mar 12 10:00:41 instance-3 logstash[2055]: [2022-03-12T10:00:41,582][INFO ][logstash.config.source.local.configpath
Mar 12 10:00:41 instance-3 logstash[2055]: [2022-03-12T10:00:41,595][ERROR][logstash.config.sourceloader] No config
Mar 13 04:20:41 instance-3 systemd[1]: Stopping logstash...
Mar 13 04:20:42 instance-3 logstash[2055]: [2022-03-13T04:20:42,008][WARN ][logstash.runner  

And now I want to active it again, I ran command:

sudo systemctl start logstash.service

But it's still not active for me. It's still deactivating. How can I active Logstash service?

Thanks for any suggestions.

Have 1 answer(s) found.
  • Đ

    Đặng Thanh Tuấn Mar 14 2022

    You need to kill the process of Logstash first. To kill you can run the command:

    kill -9 [Main PID] 

    About Main PID, you can see when checking the status of Logstash. Your Main PID is 2055. After running the command above, LogStash will auto-start for you.

Related Q&A May You Like

  1. logstash: command not found in Ubuntu installed ELK stack
  2. Your settings are invalid. Reason: Path "/usr/share/logstash/data" must be a writable directory. It is not writable.
  3. Index management requested but the Elasticsearch output is not configured/enabled
  4. Package 'python-certbot-nginx' has no installation candidate in Ubuntu
  5. How to renew SSL certificate let's encrypt in ubuntu 20.04?
  6. Type '“deb' is not known on line 1 in source list /etc/apt/sources.list.d/elastic-7.x.list in Ubuntu 20.04
  7. E: unable to locate package openjdk-8-jdk in ubuntu 20.04
  8. How to delete unused docker images and docker containers?
  9. How to set and get REDIS maximum memory size in Ubuntu?
  10. How to open txt file in console Terminal or Portainer Docker
  11. What is Redis command to get all available keys in Ubuntu?
  12. Could not connect to Redis at 127.0.0.1:6379: Connection refused in Docker container
  13. How to mount a file in Docker to the server's hard drive
  14. Got permission denied while trying to connect to the Docker daemon socket
  15. How to install Sudo inside a docker container in Linux?
Leave An Answer
* NOTE: You need Login before leave an answer

* Type maximum 2000 characters.

* All comments have to wait approved before display.

* Please polite comment and respect questions and answers of others.

Most Quizs Popular

Start Test

Javascript - Functions
Start Test

Asp.Net Core - Exam test 01
Start Test

Asp.Net Core - Exam test 02
Start Test

C# - Level Beginner

Popular Tips

This site uses cookies so that we can remember you and understand how you interact with our website. This allows us to improve and customize your browsing experience. See our Cookies Policy.
X Close