z670193
asked on
solaris 8 upgrade issue..
Hi,
We went with the upgrade from solaris 32-bit to solaris 64-bit today. We have to say that the upgrade process went smoothly. But, after the upgrade, the X-session failed to start. When it was time for a login screen, I was handed with the following message:
The X-server can not be started on display: 0…
We also found the following error message when the system was coming up.
Jun 23 12:27:10 dbservt login: open_module: stat (/usr/lib/security/pam_uni x_session. so.1) failed: no such file or directory
After the X-server failed to start, the screen was asking for the server login. After attempting to login either with root or username, the following message appeared and was prompted to login again. After entering the username, the system is not asking for the password. The same process would be repeated if tried to login.
Jun 23 12:27:10 dbservt login: open_module: stat (/usr/lib/security/pam_aut htok_get.s o.1) failed: no such file or directory
Jun 23 12:27:10 dbservt login: load_module: stat (/usr/lib/security/pam_aut htok_get.s o.1) failed: no such file or directory
So, I am now wondering what is going to be next proper step for us.
Regards,
We went with the upgrade from solaris 32-bit to solaris 64-bit today. We have to say that the upgrade process went smoothly. But, after the upgrade, the X-session failed to start. When it was time for a login screen, I was handed with the following message:
The X-server can not be started on display: 0…
We also found the following error message when the system was coming up.
Jun 23 12:27:10 dbservt login: open_module: stat (/usr/lib/security/pam_uni
After the X-server failed to start, the screen was asking for the server login. After attempting to login either with root or username, the following message appeared and was prompted to login again. After entering the username, the system is not asking for the password. The same process would be repeated if tried to login.
Jun 23 12:27:10 dbservt login: open_module: stat (/usr/lib/security/pam_aut
Jun 23 12:27:10 dbservt login: load_module: stat (/usr/lib/security/pam_aut
So, I am now wondering what is going to be next proper step for us.
Regards,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You will find that there is probably a file such as:
/usr/lib/security/pam_auth tok_get.so .2
You may be able to get away with making a symbolic link from the newer file to /usr/lib/security/pam_auth tok_get.so .1 using ln -s, but ideally you need the original /usr/lib/security/pam_auth tok_get.so .1
( (()
(`-' _\
'' ''
/usr/lib/security/pam_auth
You may be able to get away with making a symbolic link from the newer file to /usr/lib/security/pam_auth
( (()
(`-' _\
'' ''
ASKER
OS: Solaris 8 release 2/02
platform: E4500
Please let me know if you need any further information.