“semanage port” command does not work
Clash Royale CLAN TAG#URR8PPP
So, I was tasked to chagen SSH port in a CentOS server. As I did in the configuration file, the service failed to start, so after a little research I found that I should make some changes in selinux, so it would allow the default port to be changed.
So all I'd have to do is to run the commmand:
semanage port -a -t ssh_port_t -p tcp <port>
But when I do, I get the following error:
Invalid protocol
Bad portcon declaration at /etc/selinux/targeted/tmp/modules/100/base/cil:669
OSError: Error
When I try to run the command
semanage port -l
I get the following error:
`libsepol.ipproto2sepol: invalid protocol 132 found in policy (No such file or directory).
libsepol.port_to_record: could not convert port range 1 - 511 (???) to record (No such file or directory).
libsepol.sepol_port_iterate: could not iterate over ports (No such file or directory).
libsemanage.dbase_policydb_list: list handler could not extract record (No such file or directory).
libsemanage.dbase_policydb_list: could not list records (No such file or directory).
OSError: No such file or directory`
I've download all the necessary packages in order for this to work.
centos ssh selinux
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
add a comment |
So, I was tasked to chagen SSH port in a CentOS server. As I did in the configuration file, the service failed to start, so after a little research I found that I should make some changes in selinux, so it would allow the default port to be changed.
So all I'd have to do is to run the commmand:
semanage port -a -t ssh_port_t -p tcp <port>
But when I do, I get the following error:
Invalid protocol
Bad portcon declaration at /etc/selinux/targeted/tmp/modules/100/base/cil:669
OSError: Error
When I try to run the command
semanage port -l
I get the following error:
`libsepol.ipproto2sepol: invalid protocol 132 found in policy (No such file or directory).
libsepol.port_to_record: could not convert port range 1 - 511 (???) to record (No such file or directory).
libsepol.sepol_port_iterate: could not iterate over ports (No such file or directory).
libsemanage.dbase_policydb_list: list handler could not extract record (No such file or directory).
libsemanage.dbase_policydb_list: could not list records (No such file or directory).
OSError: No such file or directory`
I've download all the necessary packages in order for this to work.
centos ssh selinux
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40
add a comment |
So, I was tasked to chagen SSH port in a CentOS server. As I did in the configuration file, the service failed to start, so after a little research I found that I should make some changes in selinux, so it would allow the default port to be changed.
So all I'd have to do is to run the commmand:
semanage port -a -t ssh_port_t -p tcp <port>
But when I do, I get the following error:
Invalid protocol
Bad portcon declaration at /etc/selinux/targeted/tmp/modules/100/base/cil:669
OSError: Error
When I try to run the command
semanage port -l
I get the following error:
`libsepol.ipproto2sepol: invalid protocol 132 found in policy (No such file or directory).
libsepol.port_to_record: could not convert port range 1 - 511 (???) to record (No such file or directory).
libsepol.sepol_port_iterate: could not iterate over ports (No such file or directory).
libsemanage.dbase_policydb_list: list handler could not extract record (No such file or directory).
libsemanage.dbase_policydb_list: could not list records (No such file or directory).
OSError: No such file or directory`
I've download all the necessary packages in order for this to work.
centos ssh selinux
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
So, I was tasked to chagen SSH port in a CentOS server. As I did in the configuration file, the service failed to start, so after a little research I found that I should make some changes in selinux, so it would allow the default port to be changed.
So all I'd have to do is to run the commmand:
semanage port -a -t ssh_port_t -p tcp <port>
But when I do, I get the following error:
Invalid protocol
Bad portcon declaration at /etc/selinux/targeted/tmp/modules/100/base/cil:669
OSError: Error
When I try to run the command
semanage port -l
I get the following error:
`libsepol.ipproto2sepol: invalid protocol 132 found in policy (No such file or directory).
libsepol.port_to_record: could not convert port range 1 - 511 (???) to record (No such file or directory).
libsepol.sepol_port_iterate: could not iterate over ports (No such file or directory).
libsemanage.dbase_policydb_list: list handler could not extract record (No such file or directory).
libsemanage.dbase_policydb_list: could not list records (No such file or directory).
OSError: No such file or directory`
I've download all the necessary packages in order for this to work.
centos ssh selinux
centos ssh selinux
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
edited Jan 29 at 20:41
Msalvatori
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
asked Jan 28 at 20:39
MsalvatoriMsalvatori
136
136
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40
add a comment |
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40
add a comment |
0
active
oldest
votes
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
);
);
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%2f497290%2fsemanage-port-command-does-not-work%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%2f497290%2fsemanage-port-command-does-not-work%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
Does unix.stackexchange.com/a/242717/117549 help?
– Jeff Schaller
Jan 28 at 21:02
No. This is exactly what I tried and is returning the error.
– Msalvatori
Jan 28 at 21:45
I didn't see the -m flag in your version...?
– Jeff Schaller
Jan 28 at 22:01
The problem is not with the flag, but with the command itself.
– Msalvatori
Jan 29 at 20:40