sm-notify: bindresvport on RPC socket failed: Cannot assign requested address
Can't figure out how to make sm-notify work.
I've added hostname entry with related IPv4 to /etc/hosts
$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# ...
172.21.10.1 vast10_vip1
But still sm-notify failing due to "EADDRNOTAVAIL" error
$ sudo sm-notify -f -d -v 172.21.10.1 -m 1
sm-notify: Version 1.3.0 starting
sm-notify: Canonical name for my_name '172.21.10.1': vast10_vip1
sm-notify: Added host 172.21.10.7 to notify list
sm-notify: Added host 172.21.10.2 to notify list
sm-notify: Added host 172.21.10.10 to notify list
sm-notify: Added host 172.21.10.8 to notify list
sm-notify: Added host 172.21.10.14 to notify list
sm-notify: Added host 172.21.10.4 to notify list
sm-notify: Added host 172.21.10.6 to notify list
sm-notify: Added host 172.21.10.5 to notify list
sm-notify: Added host 172.21.10.12 to notify list
sm-notify: Added host 172.21.10.15 to notify list
sm-notify: Added host 172.21.10.9 to notify list
sm-notify: Added host 172.21.10.11 to notify list
sm-notify: Added host 172.21.10.3 to notify list
sm-notify: Added host 172.21.10.1 to notify list
sm-notify: Added host 172.21.10.13 to notify list
sm-notify: bindresvport on RPC socket failed: Cannot assign requested address
Pasting here strace
output for more details:
103494 [00007f77fbd73027] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000014>
103494 [00007f77fbd72b97] bind(3, {sa_family=AF_INET6, sin6_port=htons(638), inet_pton(AF_INET6, "::ffff:172.21.10.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EADDRNOTAVAIL (Cannot assign requested address) <0.000014>
103494 [00007f77fbd62fd0] write(2, "bindresvport on RPC socket failed: Cannot assign requested address", 66) = 66 <0.000019>
Could be that sm-notify attempting to bind via IPv6 address instead of IPv4?
Thanks for help
linux ip hosts
add a comment |
Can't figure out how to make sm-notify work.
I've added hostname entry with related IPv4 to /etc/hosts
$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# ...
172.21.10.1 vast10_vip1
But still sm-notify failing due to "EADDRNOTAVAIL" error
$ sudo sm-notify -f -d -v 172.21.10.1 -m 1
sm-notify: Version 1.3.0 starting
sm-notify: Canonical name for my_name '172.21.10.1': vast10_vip1
sm-notify: Added host 172.21.10.7 to notify list
sm-notify: Added host 172.21.10.2 to notify list
sm-notify: Added host 172.21.10.10 to notify list
sm-notify: Added host 172.21.10.8 to notify list
sm-notify: Added host 172.21.10.14 to notify list
sm-notify: Added host 172.21.10.4 to notify list
sm-notify: Added host 172.21.10.6 to notify list
sm-notify: Added host 172.21.10.5 to notify list
sm-notify: Added host 172.21.10.12 to notify list
sm-notify: Added host 172.21.10.15 to notify list
sm-notify: Added host 172.21.10.9 to notify list
sm-notify: Added host 172.21.10.11 to notify list
sm-notify: Added host 172.21.10.3 to notify list
sm-notify: Added host 172.21.10.1 to notify list
sm-notify: Added host 172.21.10.13 to notify list
sm-notify: bindresvport on RPC socket failed: Cannot assign requested address
Pasting here strace
output for more details:
103494 [00007f77fbd73027] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000014>
103494 [00007f77fbd72b97] bind(3, {sa_family=AF_INET6, sin6_port=htons(638), inet_pton(AF_INET6, "::ffff:172.21.10.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EADDRNOTAVAIL (Cannot assign requested address) <0.000014>
103494 [00007f77fbd62fd0] write(2, "bindresvport on RPC socket failed: Cannot assign requested address", 66) = 66 <0.000019>
Could be that sm-notify attempting to bind via IPv6 address instead of IPv4?
Thanks for help
linux ip hosts
add a comment |
Can't figure out how to make sm-notify work.
I've added hostname entry with related IPv4 to /etc/hosts
$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# ...
172.21.10.1 vast10_vip1
But still sm-notify failing due to "EADDRNOTAVAIL" error
$ sudo sm-notify -f -d -v 172.21.10.1 -m 1
sm-notify: Version 1.3.0 starting
sm-notify: Canonical name for my_name '172.21.10.1': vast10_vip1
sm-notify: Added host 172.21.10.7 to notify list
sm-notify: Added host 172.21.10.2 to notify list
sm-notify: Added host 172.21.10.10 to notify list
sm-notify: Added host 172.21.10.8 to notify list
sm-notify: Added host 172.21.10.14 to notify list
sm-notify: Added host 172.21.10.4 to notify list
sm-notify: Added host 172.21.10.6 to notify list
sm-notify: Added host 172.21.10.5 to notify list
sm-notify: Added host 172.21.10.12 to notify list
sm-notify: Added host 172.21.10.15 to notify list
sm-notify: Added host 172.21.10.9 to notify list
sm-notify: Added host 172.21.10.11 to notify list
sm-notify: Added host 172.21.10.3 to notify list
sm-notify: Added host 172.21.10.1 to notify list
sm-notify: Added host 172.21.10.13 to notify list
sm-notify: bindresvport on RPC socket failed: Cannot assign requested address
Pasting here strace
output for more details:
103494 [00007f77fbd73027] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000014>
103494 [00007f77fbd72b97] bind(3, {sa_family=AF_INET6, sin6_port=htons(638), inet_pton(AF_INET6, "::ffff:172.21.10.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EADDRNOTAVAIL (Cannot assign requested address) <0.000014>
103494 [00007f77fbd62fd0] write(2, "bindresvport on RPC socket failed: Cannot assign requested address", 66) = 66 <0.000019>
Could be that sm-notify attempting to bind via IPv6 address instead of IPv4?
Thanks for help
linux ip hosts
Can't figure out how to make sm-notify work.
I've added hostname entry with related IPv4 to /etc/hosts
$ cat /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
# ...
172.21.10.1 vast10_vip1
But still sm-notify failing due to "EADDRNOTAVAIL" error
$ sudo sm-notify -f -d -v 172.21.10.1 -m 1
sm-notify: Version 1.3.0 starting
sm-notify: Canonical name for my_name '172.21.10.1': vast10_vip1
sm-notify: Added host 172.21.10.7 to notify list
sm-notify: Added host 172.21.10.2 to notify list
sm-notify: Added host 172.21.10.10 to notify list
sm-notify: Added host 172.21.10.8 to notify list
sm-notify: Added host 172.21.10.14 to notify list
sm-notify: Added host 172.21.10.4 to notify list
sm-notify: Added host 172.21.10.6 to notify list
sm-notify: Added host 172.21.10.5 to notify list
sm-notify: Added host 172.21.10.12 to notify list
sm-notify: Added host 172.21.10.15 to notify list
sm-notify: Added host 172.21.10.9 to notify list
sm-notify: Added host 172.21.10.11 to notify list
sm-notify: Added host 172.21.10.3 to notify list
sm-notify: Added host 172.21.10.1 to notify list
sm-notify: Added host 172.21.10.13 to notify list
sm-notify: bindresvport on RPC socket failed: Cannot assign requested address
Pasting here strace
output for more details:
103494 [00007f77fbd73027] socket(AF_INET6, SOCK_DGRAM, IPPROTO_IP) = 3 <0.000014>
103494 [00007f77fbd72b97] bind(3, {sa_family=AF_INET6, sin6_port=htons(638), inet_pton(AF_INET6, "::ffff:172.21.10.1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1
EADDRNOTAVAIL (Cannot assign requested address) <0.000014>
103494 [00007f77fbd62fd0] write(2, "bindresvport on RPC socket failed: Cannot assign requested address", 66) = 66 <0.000019>
Could be that sm-notify attempting to bind via IPv6 address instead of IPv4?
Thanks for help
linux ip hosts
linux ip hosts
asked 3 mins ago
SamuelSamuel
12316
12316
add a comment |
add a comment |
0
active
oldest
votes
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
});
}
});
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%2f510002%2fsm-notify-bindresvport-on-rpc-socket-failed-cannot-assign-requested-address%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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.
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%2f510002%2fsm-notify-bindresvport-on-rpc-socket-failed-cannot-assign-requested-address%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