Hide Forgot
Description of problem: Ldap users are not able to execute #lshal. It produces below error:- Version-Release number of selected component (if applicable): hal-0.5.14-14.el6.x86_64 dbus-1.2.24-8.el6_6.x86_64 openldap-clients-2.4.40-12.el6.x86_64 How reproducible: ?? Steps to Reproduce: 1.Login as ldap user 2.execute #lshal 3. Actual results: #lshal gives below error:- ~~~ error: dbus_bus_get: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken ~~~ Expected results: #lshal should print output without any error. Additional info: Workaround:- 1} #getent passwd <username> >> /etc/passwd 2} #getent shadow <username> >> /etc/shadow
uname -a 2.6.32-642.6.2.el6.x86_64 #1 SMP Mon Oct 24 10:22:33 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux rpm -q --queryformat '%{RELEASE}' redhat-release-server 6.8.0.5.el6 <= Not working rpm -q --queryformat '%{VERSION}' redhat-release-server 6Server ################################################################################ uname -a 2.6.32-642.4.2.el6.x86_64 #1 SMP Mon Aug 15 02:06:41 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux rpm -q --queryformat '%{RELEASE}' redhat-release-server 6.4.0.4.el6 <= Working rpm -q --queryformat '%{VERSION}' redhat-release-server 6Server There's a minor release difference between the two Kernels. The suggested workaround is not feasible for our environment. Is there any plans of correcting this in the next revision of the kernel?
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available. The official life cycle policy can be reviewed here: http://redhat.com/rhel/lifecycle This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com