Networking: port listening but nc fails
0
I have set up a docker-compose stack on a server.
One of its services is jaeger collector and is configured as follows:
collector:
image: jaegertracing/jaeger-collector:1.8
environment:
- SPAN_STORAGE_TYPE=elasticsearch
- ES_SERVER_URLS=http://some-elk-address:9200
ports:
- "14269"
- "14268:14268"
- "14267"
- "14250"
- "9411:9411"
From my machine:
$ nc -zv -w 2 server-hostname 9411
nc: connect to server-hostname port 9411 (tcp) failed: Connection refused
However, from within that server:
# ss -tula | grep 9411
tcp LISTEN 0 128 :::9411 :::*
networking nc port ss
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
add a comment |
0
I have set up a docker-compose stack on a server.
One of its services is jaeger collector and is configured as follows:
collector:
image: jaegertracing/jaeger-collector:1.8
environment:
- SPAN_STORAGE_TYPE=elasticsearch
- ES_SERVER_URLS=http://some-elk-address:9200
ports:
- "14269"
- "14268:14268"
- "14267"
- "14250"
- "9411:9411"
From my machine:
$ nc -zv -w 2 server-hostname 9411
nc: connect to server-hostname port 9411 (tcp) failed: Connection refused
However, from within that server:
# ss -tula | grep 9411
tcp LISTEN 0 128 :::9411 :::*
networking nc port ss
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
I think that should this was a firewall issue, I would get a time out, rather than aConnection refused
– pkaramol
Dec 27 '18 at 12:07
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
you are right; it is just a fresh ubuntu 16.04 installation with no messing ofiptableswhatsoever
– pkaramol
Dec 27 '18 at 12:19
add a comment |
0
0
0
I have set up a docker-compose stack on a server.
One of its services is jaeger collector and is configured as follows:
collector:
image: jaegertracing/jaeger-collector:1.8
environment:
- SPAN_STORAGE_TYPE=elasticsearch
- ES_SERVER_URLS=http://some-elk-address:9200
ports:
- "14269"
- "14268:14268"
- "14267"
- "14250"
- "9411:9411"
From my machine:
$ nc -zv -w 2 server-hostname 9411
nc: connect to server-hostname port 9411 (tcp) failed: Connection refused
However, from within that server:
# ss -tula | grep 9411
tcp LISTEN 0 128 :::9411 :::*
networking nc port ss
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
I have set up a docker-compose stack on a server.
One of its services is jaeger collector and is configured as follows:
collector:
image: jaegertracing/jaeger-collector:1.8
environment:
- SPAN_STORAGE_TYPE=elasticsearch
- ES_SERVER_URLS=http://some-elk-address:9200
ports:
- "14269"
- "14268:14268"
- "14267"
- "14250"
- "9411:9411"
From my machine:
$ nc -zv -w 2 server-hostname 9411
nc: connect to server-hostname port 9411 (tcp) failed: Connection refused
However, from within that server:
# ss -tula | grep 9411
tcp LISTEN 0 128 :::9411 :::*
networking nc port ss
networking nc port ss
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
asked Dec 27 '18 at 11:59
pkaramolpkaramol
464216
464216
I think that should this was a firewall issue, I would get a time out, rather than aConnection refused
– pkaramol
Dec 27 '18 at 12:07
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
you are right; it is just a fresh ubuntu 16.04 installation with no messing ofiptableswhatsoever
– pkaramol
Dec 27 '18 at 12:19
add a comment |
I think that should this was a firewall issue, I would get a time out, rather than aConnection refused
– pkaramol
Dec 27 '18 at 12:07
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
you are right; it is just a fresh ubuntu 16.04 installation with no messing ofiptableswhatsoever
– pkaramol
Dec 27 '18 at 12:19
I think that should this was a firewall issue, I would get a time out, rather than a
Connection refused– pkaramol
Dec 27 '18 at 12:07
I think that should this was a firewall issue, I would get a time out, rather than a
Connection refused– pkaramol
Dec 27 '18 at 12:07
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
you are right; it is just a fresh ubuntu 16.04 installation with no messing of
iptables whatsoever– pkaramol
Dec 27 '18 at 12:19
you are right; it is just a fresh ubuntu 16.04 installation with no messing of
iptables whatsoever– pkaramol
Dec 27 '18 at 12:19
add a comment |
1 Answer
1
active
oldest
votes
1
The problem is most likely related to (as the ss output above clearly hints) that the service is only listening for IPv6 connections
root@server-hostname:~/# ss -tula -4 | grep 9411
root@server-hostname:~/# ss -tula -6 | grep 9411
tcp LISTEN 0 128 :::9411 :::*
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491113%2fnetworking-port-listening-but-nc-fails%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
The problem is most likely related to (as the ss output above clearly hints) that the service is only listening for IPv6 connections
root@server-hostname:~/# ss -tula -4 | grep 9411
root@server-hostname:~/# ss -tula -6 | grep 9411
tcp LISTEN 0 128 :::9411 :::*
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
add a comment |
1
The problem is most likely related to (as the ss output above clearly hints) that the service is only listening for IPv6 connections
root@server-hostname:~/# ss -tula -4 | grep 9411
root@server-hostname:~/# ss -tula -6 | grep 9411
tcp LISTEN 0 128 :::9411 :::*
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
add a comment |
1
1
1
The problem is most likely related to (as the ss output above clearly hints) that the service is only listening for IPv6 connections
root@server-hostname:~/# ss -tula -4 | grep 9411
root@server-hostname:~/# ss -tula -6 | grep 9411
tcp LISTEN 0 128 :::9411 :::*
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
The problem is most likely related to (as the ss output above clearly hints) that the service is only listening for IPv6 connections
root@server-hostname:~/# ss -tula -4 | grep 9411
root@server-hostname:~/# ss -tula -6 | grep 9411
tcp LISTEN 0 128 :::9411 :::*
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
answered Dec 27 '18 at 12:09
pkaramolpkaramol
464216
464216
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f491113%2fnetworking-port-listening-but-nc-fails%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think that should this was a firewall issue, I would get a time out, rather than a
Connection refused– pkaramol
Dec 27 '18 at 12:07
Iptables can do either, depending on the rules in place and the policies of the sysadmin.
– stolenmoment
Dec 27 '18 at 12:12
you are right; it is just a fresh ubuntu 16.04 installation with no messing of
iptableswhatsoever– pkaramol
Dec 27 '18 at 12:19