Added a new input and nothing was coming in.
looking tcpdump, tcpdump port 2060, yes there is traffic
looking logstash logs, nothing wrong
looking netstat
root@ip-10-247-0-158:/home/ubuntu# netstat -an | grep 2060
tcp6 0 0 :::2060 :::* LISTEN
There is it, the new port bound to the ipv6 port only
Select 'configure' from the main menu. This line is in blue in the main window.
This one only shows the 'tcp' connections after I removed the ipv6.
But that ipv6 was a sneaky thing.
Logstash is currently collecting locally on: 10.247.0.158 tcp: 2060, 3515, 2056, 5544, 2057udp: 5544
Double check:
root@ip-10-247-0-158:/home/ubuntu# netstat -an | grep 2060
tcp 0 0 0.0.0.0:2060 0.0.0.0:* LISTEN
All good.
Watch for the ipv6 in new deployments.
Cheers
ipv6 on AWS
Re: ipv6 on AWS
I spoke to fast.
I forgot to disbale ipv6 on reboot
But I caught the 'configure' screen
Logstash is currently collecting locally on: 10.247.0.158 tcp6: 3515, 2056, 5544, 2057, 2060udp6: 5544
I forgot to disbale ipv6 on reboot
But I caught the 'configure' screen
Logstash is currently collecting locally on: 10.247.0.158 tcp6: 3515, 2056, 5544, 2057, 2060udp6: 5544
Re: ipv6 on AWS
So it sounds like you've got everything working. Or were you trying to get the server to listen on both IPv4 and IPv6?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!