-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to chmod & close file /var/log/sudosh/ Bad file descriptor #12
Comments
Can you post your sudosh.conf and verify that you are on the current HEAD? |
Hi Thanks for considering my request. I have uploaded my sudosh.conf file. Thanks |
Thanks. I don't see anything odd there, but I am not able to reproduce in my testing on centos 6.6 + current HEAD of sudosh2 inside a container. Are you using selinux in enforcing mode? if so I will need to set up an actual VM to test properly. Any other details you think might be pertinent? |
sestatus | grep -i modeCurrent mode: permissive My default umask is 0077. I'm using RHEL 6.7 integrated with Active Directory using SSSD and I am not seeing this issue for AD accounts but only for the local accounts I am facing this issue. Do you need any specific information? |
Hi.. Any luck on this request? |
I'm working to get a SSSD system set up to test with this. I don't currently have such an environment, and it appears the issue is related. |
Thanks a lot for your help. I’ll be happy to hear from you. Best Regards E V Devarajulu tel +91 44 24407480 From: squash [mailto:[email protected]] I'm working to get a SSSD system set up to test with this. I don't currently have such an environment, and it appears the issue is related. — |
Hi Any luck on this? Best Regards E V Devarajulu tel +91 44 24407480 From: squash [mailto:[email protected]] I'm working to get a SSSD system set up to test with this. I don't currently have such an environment, and it appears the issue is related. — |
Bump. Seems to only happen with long lived sessions. |
Cool Is there any plans to fix this issue? Thanks Best Regards E V Devarajulu tel +91 44 24407480tel:+91%2044%2024407480 On 25-Aug-2016, at 12:00 AM, rfifarek <[email protected]mailto:[email protected]> wrote: Bump. Seems to only happen with long lived sessions. � |
Were their updates to this? |
I was not able to get an SSSD system to test on or reproduce the problem outside of that environment. I see that since then they have created a basic containerized sssd setup which might be useful for diagnosing in a smaller environment. https://github.com/SSSD/sssd-ci-containers My guess is that we're running into an expired token or credential and SSSD is dropping our rights to new operations on these files, but that is pure speculation. |
I installed sudosh2 on RHEL 6.6 OS and whenever I logout from sudo session, I get below message. When I check the log files showing the error, I observe the permission is set to 600 instead of 440.
Unable to chmod file /var/log/sudosh/aduxacm-sys1-time-1444075745-AiTiXTtJvJsKenFa: Bad file descriptor
Unable to close file /var/log/sudosh/aduxacm-sys1-time-1444075745-AiTiXTtJvJsKenFa: Bad file descriptor
Please let me know if you need more details to identify the issue
The text was updated successfully, but these errors were encountered: