logstash i snot listening 5044 port

[kalavathiy]

Logstash information:

Please include the following information:

1. Logstash version (e.g. bin/logstash --version)
2. Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker)
3. How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes)

Plugins installed: (bin/logstash-plugin list --verbose)

JVM (e.g. java -version):

If the affected version of Logstash is 7.9 (or earlier), or if it is NOT using the bundled JDK or using the 'no-jdk' version in 7.10 (or higher), please provide the following information:

1. JVM version (java -version)
2. JVM installation source (e.g. from the Operating System's package manager, from source, etc).
3. Value of the LS_JAVA_HOME environment variable if set.

OS version (uname -a if on a Unix-like system):

Description of the problem including expected versus actual behavior:

Steps to reproduce:

Please include a minimal but complete recreation of the problem, including (e.g.) pipeline definition(s), settings, locale, etc. The easier you make for us to reproduce it, the more likely that somebody will take the time to look at it.

Provide logs (if relevant):

[yaauie]

Would you mind following up with details? How are your pipelines defined? Do the logs indicate that the pipelines are being started as expected, or do they point to an issue preventing them from starting up?

By default, Logstash isn't expected to bind to TCP/5044, but by convention the Beats Input plugin is often configured to bind to TCP/5044 (but can only be done so for one pipeline at a time). This leads me to believe that you have defined a pipeline, configured Logstash to use that pipeline's definition, and are expecting the pipeline to listen on TCP/5044 for inbound events. The logs should give a pretty clear indication if your pipeline's definition has an issue.