setroubleshoot user checking out Flexlm license
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
My user are experiencing an issue with the setroubleshoot user checking out a network license from the Flexlm license manager. When a user checks out a network license the setroubleshoot user also grabs a user from the Flexlm server. I suspect setroubleshoot is trying to monitor network traffic on a non-standard port causing it to ping the license server causing a license checkout. Has anyone else experienced this behavior or know if my estimation is incorrect?
My solution to this point has been to disable selinux, setroubleshoot, and remove the setroubleshoot user. I am currently investigating a more secure solution to allow selinux but not block user licenses with setroubleshoot to Flexlm servers.
selinux
asked Aug 15 at 13:28
Dr.Zenzic
11
add a comment |Â
up vote
0
down vote
favorite
My user are experiencing an issue with the setroubleshoot user checking out a network license from the Flexlm license manager. When a user checks out a network license the setroubleshoot user also grabs a user from the Flexlm server. I suspect setroubleshoot is trying to monitor network traffic on a non-standard port causing it to ping the license server causing a license checkout. Has anyone else experienced this behavior or know if my estimation is incorrect?
My solution to this point has been to disable selinux, setroubleshoot, and remove the setroubleshoot user. I am currently investigating a more secure solution to allow selinux but not block user licenses with setroubleshoot to Flexlm servers.
selinux
asked Aug 15 at 13:28
Dr.Zenzic
11
1
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
My user are experiencing an issue with the setroubleshoot user checking out a network license from the Flexlm license manager. When a user checks out a network license the setroubleshoot user also grabs a user from the Flexlm server. I suspect setroubleshoot is trying to monitor network traffic on a non-standard port causing it to ping the license server causing a license checkout. Has anyone else experienced this behavior or know if my estimation is incorrect?
My solution to this point has been to disable selinux, setroubleshoot, and remove the setroubleshoot user. I am currently investigating a more secure solution to allow selinux but not block user licenses with setroubleshoot to Flexlm servers.
selinux
asked Aug 15 at 13:28
Dr.Zenzic
11
My user are experiencing an issue with the setroubleshoot user checking out a network license from the Flexlm license manager. When a user checks out a network license the setroubleshoot user also grabs a user from the Flexlm server. I suspect setroubleshoot is trying to monitor network traffic on a non-standard port causing it to ping the license server causing a license checkout. Has anyone else experienced this behavior or know if my estimation is incorrect?
My solution to this point has been to disable selinux, setroubleshoot, and remove the setroubleshoot user. I am currently investigating a more secure solution to allow selinux but not block user licenses with setroubleshoot to Flexlm servers.
selinux
selinux
asked Aug 15 at 13:28
Dr.Zenzic
11
asked Aug 15 at 13:28
Dr.Zenzic
11
asked Aug 15 at 13:28
Dr.Zenzic
11
asked Aug 15 at 13:28
Dr.Zenzic
11
asked Aug 15 at 13:28
Dr.Zenzic
11
11
1
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35
add a comment |Â
1
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35
1
1
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f462751%2fsetroubleshoot-user-checking-out-flexlm-license%23new-answer', 'question_page');
);
Post as a guest
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
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
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
1
I always wonder why people using commercial products do not involve their vendors. You are also being overly broad in the question, our main focus is not end-user hard core helpdesk i.e. you have got to do your end of the job and provide useful diagnostics on your own for we to be able to help you.
– Rui F Ribeiro
Aug 15 at 13:32
On second thought my original reply was very unhelpful I apologize. I am contacting redhat regarding this issue but wanted to see if the community has experienced similar behavior for future admins and to gain a more specific understanding so I could ask a better question.
– Dr.Zenzic
Aug 15 at 13:50
Flexlm is a generic licensing system used with many kinds of software. As far as I know, a client program must send a well-formed request for a license to a license server: just pinging the license server won't do it. That implies one of two things: either the setroubleshoot user is running some licensed software (why would that happen?), or the licensed software attempts to detect the number of users on a system and does not correctly identify setroubleshoot as one of normal system accounts. The latter is clearly an issue within the licensed software, whatever it may be.
– telcoM
Aug 15 at 14:35