Solaris 10 Cannot login
Hello World:
Those of you who are from the "old school" will get the salutation! In any case, I am have a problem with my Solaris 10 system. Recently, I ran patchadd for those patches that were downloaded by the Sun patch manager into /var/sadm/spool. After doing this, I rebooted my system and now I am receiving the following error message and cannot login except in single user mode:
ld.so.1: Login: fatal relocation error: File /usr/lib/passwdutil.so.1: symbol_nsl_fgetspent_r: Referenced symbol not found.
Also, when I login with single user mode and run the passwd command, I get the same error message.
I would greatly appreciate any help as I am under a deadline to get this system back up.
Respectfully,
Mark K.
[765 byte] By [
rambo51a] at [2007-11-26 19:42:35]

# 1
Hi,I ran into same issue. Could you ever resolve that issue. Please post your solution here. thanks in advance.-SMG
# 2
Same issue here:
Loaded Solaris 10 11/06 on SB1500 - no problem.
When I tried to patch up to the latest & greatest -- crash
I get the following:
ld.sol.1: login: fatal: relocation error: file /usr/lib/passwdutil.sol1: symbol _nsl_fgetspent_r: referenced symbol not found
pathing issue?
Only solution for me was to reload back to a 11/06 baseline.
# 3
I had the same problem, and have gotten around it. I will lay out what I did, and maybe that will eliminate some options that you will not have to try yourself:
Fourth installation was a charm on this one:
-installed new, full + oem without any custom packages
upon reboot, I logged in using Java Desktop and cancelled the registration pop-up, then immediately logged out. Went to command-line and did a reboot -- -s
-When machine rebooted into single-user mode, I put jumbo patch into /tmp and did a SAVE option -- normally, I would do: ./install_cluster -q -nosave
But, the patch instructions said you have to run the patch TWICE for the newest patches to take affect.
So, I did a cd /tmp/10_Recommended
then ./install_cluster
In my previous attempts, I had copied in my .cshrc, changed configuration files etc..like I have always done, but three attempts at installing, and getting that "ld.so.1...referenced sy mbol not found", caused me to just ignore the temptation to tweak the installation before completing the patches.
-When the patching finished, I did another reboot -- -s
-Again, I added patches to /tmp and re-ran using:
./install_cluster
I noticed that SEVERAL patches (20+) applied, as opposed to just one when
I had installed three times earlier.
-did a reboot
--was able to login at the splash screen no problem.
-uname -a came out: 125100-07
I cannot figure out which, if any of my previous actions caused the issue
of not being able to log in, but here are some of the things I had done on
non-successful installations:
- modified /etc/passwd (before patching & between first & second patching)
- modified /var/svc/profile/generic.xml before patching
-chose "no" to the installer's question about remote hosts being allowed access
- installed patches WITH the quiet (-q) and No Save option (-nosave)
-installed patches after bringing system down to single-user mode, instaed of up to single-user mode (no reboot)
-had setup Java desktop system (registration, icons, menus, etc. prior to patching)
-Installed Sun Studio 11 prior to patching
Hope that helps you eliminate some possibilities.
# 4
Hello Everyone,
I think i've got a serious problem with my system. I just installed Solaris 10 on my laptop, i followed the instructions on this site. During the installation, i was asked to create a host name, root name and password but after i've finished the installation and it came to Login in I couldn't because it kept telling me wrong user name and password and when i clicked on the HELP, it stated that if i've not created any User name, I should put "root" which I did and the password of the root host i created when installing the OS but it still didn't work and now i'm stuck. I need help guys
# 5
Since I do not know your skill level, I will write this rather lengthy - please do not take offense.
My experience with PC's is rare, as I am assuming you have an X86 laptop versus a Tadpole or some other SPARC-based laptop.
If possible, re-introduce an installation DVD/CD.
On a Sun workstation or server, you simply do a "boot cdrom -s" at the Open Boot Prom (OBP), but there is no such thing on the X86 boxen.
If you can boot up off of the DVD/CD, and get to a command line or terminal without affecting your previous installation, you can do the following:
<1> make a temporary directory like /a/tmp (or wherever you can)
<2> mount the internal disk to the new temporary directory. (mount /dev/dsk/c0t0d0s0 /a/tmp or something along those lines) If you made separate partitions on your disk(s) for /etc, /usr, /opt (c0t0d0s1 c0t1d0s3 etc.) use the one with /etc, as that is where the passwd & shadow files are located.
<3> once you have successfully mounted the file system that has the passwd and shadow files on it, you can now simply use the vi editor, or whatever you have available to you, to edit the shadow entry.
replace the string that should look something like:
root:0123456789abc:13654::::::
with an entry that has a "null" string, or has a string with a password
value that you already know. (i.e. copy the entry from a Solaris box where
you know the password)
something like
root:pvjnfRJYgLbUA:13654::::::
(which on my test box was a null passwd)
If that doesn't work, a longer option would be to re-install using the
"upgrade" option.
It should ask for the root password again.
Option three & four - try it with caps lock on, and then try it with your hands shifted one key to the left, and then one key to the right -- that works on the rare occasion that you were a bit rushed and didn't notice hand placement.
There may be a simpler way, (and there should be after 15+ years of doing it the hard way) but I presented some of the ways that have worked for me.
If you didn't add any additional software to the installation, it wouldn't be unheard of to just re-install from scratch. If you are new to Solaris, it is good practice for you until later when you set up a jumpstart server to do all the work for you.
# 6
try this:ok b -s# mount /dev/dsk/c0t3d0s0 /a# cd /a/etc# TERM=vt100# export TERM# vi shadow(Remove root抯 encrypted password string )# cd /# umount /a# init 6