Solving “connection refused” issues on Debian Sid
Some weeks ago I started to experiment some network issues on my debian sid:
- The selenium-remote-control was not running:
I could even try to do a: “telnet localhost 4444″, it just did not work.
- My Apache-Solr was not capable to subscribe to apache-activemq
When reading the log, I saw:
Could not connect to broker URL: tcp://localhost:61616. Reason: java.net.ConnectException: Connection refused
Suddenly I noticed something weird in my netstat:
tcp6 0 0 :::8983 :::* LISTEN 3865/solr-globocom
tcp6 0 0 :::8161 :::* LISTEN 3901/activemq-globo
tcp6 0 0 :::61616 :::* LISTEN 3901/activemq-globo
tcp6 0 0 127.0.0.1:41879 127.0.0.1:61616 ESTABLISHED 3865/solr-globocom
tcp6 0 0 127.0.0.1:61616 127.0.0.1:41879 ESTABLISHED 3901/activemq-globo
Suddenly I noticed something weird in my netstat:
tcp6 0 0 :::8983 :::* LISTEN 3865/solr-globocom
tcp6 0 0 :::8161 :::* LISTEN 3901/activemq-globo
tcp6 0 0 :::61616 :::* LISTEN 3901/activemq-globo
tcp6 0 0 127.0.0.1:41879 127.0.0.1:61616 ESTABLISHED 3865/solr-globocom
tcp6 0 0 127.0.0.1:61616 127.0.0.1:41879 ESTABLISHED 3901/activemq-globo
Everything is being bound as IPv6… humm, that doesn’t have a good smell….
Looking for solutions I’ve found this file:
/etc/sysctl.d/bindv6only.conf
interesting, huh?!?
Openning up that file, I saw a full description of it, then I just needed to change its property from this:
net.ipv6.bindv6only = 1
to this:
net.ipv6.bindv6only = 0
Well, if you have the same problem, jsut change that, restart your PC, and be happy!