Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[logstash] Invalid ports in headless service
See original GitHub issueChart version: 7.8.1
Kubernetes version: 1.18
Helm Version: 3.3.0-rc.2
Logstash headless service uses container ports from .Values.extraPorts which are incompatible with the service spec.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:7
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Logstash not starting; error reason : Your settings are invalid
I am using the command "logstash --config.test_and_exit -f test1.conf" to ... -XX:+UseCMSInitiatingOccupancyOnly, -Djava.awt.headless=true, ...
Read more >Logstash unable to start and collect logs - Elastic Discuss
Hi I have configure Elasticsearch, kibana & logstash on same machine. Want to receive firewall logs in logstash but facing below error.
Read more >Logstash did not listen to port 5044 after startup - Elastic Discuss
Hello, I would like to ask what is wrong with my logstash configuration. I configured the port to listen to 5044 in the...
Read more >Error while connecting logstash to elasticsearch
... Name or service not known"} [2022-05-13T12:02:16,412][ERROR][logstash. ... httpPort: 9600 # Custom ports to add to logstash extraPorts: ...
Read more >Logstash start up issues - Elastic Discuss
The two most common reasons for Logstash not starting from systemctl are probably permissions, and improper indentation in the logstash.yml file ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
What is the problem exactly? service supports multi-ports.
The non-headless service uses
.Values.service.ports, which is what the headless service also needs to use.