"SU" command fails with an error "could not open session"

Solution Verified - Updated -

Issue

  • "SU" command fails with an error "could not open session"

  • It throws below error messages in /var/log/messages

Jun 29 12:30:39 hostname su: PAM [dlerror: /lib64/security/pam_vas3.so: cannot open shared object file: No such file or directory]
Jun 29 12:30:39 hostname su: PAM adding faulty module: /lib64/security/pam_vas3.so

Environment

  • Red Hat Enterprise Linux 4
  • VAS

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content