Unit logstash.service entered failed state

Hi!
OS Centos 7, java -version openjdk version "1.8.0_252"
Updated the version of logstash to 7.16.2, now at startup I get the following
systemctl status logstash:

Dec 24 01:27:08 elk systemd[1]: Unit logstash.service entered failed state.
Dec 24 01:27:08 elk systemd[1]: logstash.service failed.
Dec 24 01:27:08 elk systemd[1]: logstash.service holdoff time over, scheduling restart.
Dec 24 01:27:08 elk systemd[1]: Stopped logstash.
Dec 24 01:27:08 elk systemd[1]: start request repeated too quickly for logstash.service
Dec 24 01:27:08 elk systemd[1]: Failed to start logstash.
Dec 24 01:27:08 elk systemd[1]: Unit logstash.service entered failed state.
Dec 24 01:27:08 elk systemd[1]: logstash.service failed.

Executing the command:

/usr/share/logstash/bin/system-install /etc/logstash/startup.options systemd

did not give the result.

Manually starts without errors:

/usr/share/logstash/bin/logstash
Using bundled JDK: /usr/share/logstash/jdk
OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
Sending Logstash logs to /var/log/logstash which is now configured via log4j2.properties
[2021-12-24T01:01:11,737][INFO ][logstash.runner          ] Log4j configuration path used is: /usr/share/logstash/config/log4j2.properties
[2021-12-24T01:01:11,778][INFO ][logstash.runner          ] Starting Logstash {"logstash.version"=>"7.16.2", "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-24T01:01:14,170][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600, :ssl_enabled=>false}

Why doesn't it want to run as a service?

Run with parameters:

/usr/share/logstash/bin/logstash --path.settings /etc/logstash

Gives an error message:

[FATAL] 2021-12-24 02:05:16.675 [main] Logstash - Logstash stopped processing because of an error: (NameError) cannot link Java class org.apache.http.conn.ssl.SSLConnectionSocketFactory, probable missing dependency: 'boolean org.apache.logging.log4j.spi.LoggerContextFactory.isClassLoaderDependent()'

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