Error when attempting to log onto console

[steven Burgess_2]

Hi

Our test/training box for some reason keeled over the other day. Messages from console show /dev/root no space etc

when log in prompt, attempt to log in and get the message

/usr/lib/dld.sl
can't open shared library
/usr/lib/libsec.l

/usr/lib/dld.sl : no such file or directory

The easiest way to get round it would be to boot from my last ignite.

What is the message refering to, is it possible to fix without booting from tape

Thanks in advance

Steve

[Robin Wakefield]

Hi Steve,

If this machine is on the network, try logging on remotely, but use the following command:

remsh yourhostname ksh -i

The -i switch tells ksh to ignore certain signals and should keep the session active. From there, determine what's filling up your root filesystem and you should then be able to remove the offending file(s).

Rgds, Robin.

[steven Burgess_2]

Hi robin

Thanks for the reply

message received when attempting to log on via remsh is the same as the message received when attempting to log on via the console

/usr/lib/dld.sl: Can't open shared library

[harry d brown jr]

Steve,

The actual error is not in dld.sl, but the missing library /usr/lib/libsec.l.

Below are a few links that references libsec, and what I'm wondering is has something changed?

Did you recently do a patch or software install that might have modified some system routines?

Did you just recently change your system over to a trusted system? Something changed, because a library just doesn't start to fail....

http://devresource.hp.com/STK/impacts/i564.html
http://www.ecn.purdue.edu/ECN/FAQ/unix/hp/hp_librout

What OS are you running?

Although you are receiving the error, are you able to login?

You might want to think about applying the latest patch sets (providing it wasn't the cause of this error).

live free or die
harry

[Michael Tully]

Hi,

One thing to note about the error message is that it reports /dev/root instead of /dev/vg00/lvol3.
This will also need to be fixed. Do a 'bdf'
to confirm before doing the below:

# mv /etc/mnttab to /etc/mnttab.old
# mount -a

This can be caused by entering LVM maintenance
mode or even a not completely successful reboot.

HTH
-Michael

[steven Burgess_2]

Thanks for the replies

will check these out when i'm back in work on Wednesday