Help on error message: libumem.so

Paris Heng · 03-09-2009, 02:46 AM

I get the following error message in my terminal after I invoked the terminal on the Solaris:

Code:

$ld.so.1: utmp_update: warning: libumem.so: open failed: No such file in secure directories

Please someone assist, it look very annoying, seem something error in the system.

bathory · 03-09-2009, 05:02 AM

I don't know why utmp_update complains, but you can add a symlink for that lib to the trusted libraries directory and see if the warning goes away. Depending of the architecture (32 or 64 bits) do:

Code:

ln -s /lib/libumem.so* /lib/secure
or
ln -s /lib/libumem.so* /lib/secure/64

Paris Heng · 03-09-2009, 05:34 AM

Thanks! How to check whether the Solaris is 32bit or 64bits? I have installed some application, then this error come out. What normally causing this kind of complain?

bathory · 03-09-2009, 06:03 AM

Quote:

How to check whether the Solaris is 32bit or 64bits?

To check arch run:

Code:

isainfo -b

Quote:

I have installed some application, then this error come out. What normally causing this kind of complain?

Dunno. Maybe the applications you have installed are trying to use utmpx to log information in a way that is not correct.

Paris Heng · 03-09-2009, 06:16 AM

But did it means that my application do have error during the installation? I will try the symlink command later on, will post up the result here, thanks alot.

Paris Heng · 03-09-2009, 06:20 AM

Example if I get both 64 and 32 bits, did I need to key in both of the symlink command? How my going to do?

Code:

example% isainfo -v
64-bit sparcv9 applications
32-bit sparc applications

bathory · 03-09-2009, 06:58 AM

You should know if your application is 32 or 64 bits, or the application should be able to add the path to its libs in the appropriate trusted libraries directory. For example I have installed Sunone Calendar and Messaging Server (32 and 64 bits apps respectively) and I have in the trusted directories:

Quote:

#crle

Configuration file [version 4]: /var/ld/ld.config
Default Library Path (ELF): /lib:/usr/lib (system default)
Trusted Directories (ELF): /usr/lib/secure:/sunone/calendar/SUNWics5/cal/lib

Command line:
crle -c /var/ld/ld.config -s /usr/lib/secure:/sunone/calendar/SUNWics5/cal/lib

# crle -64

Configuration file [version 4]: /var/ld/64/ld.config
Default Library Path (ELF): /lib/64:/usr/lib/64 (system default)
Trusted Directories (ELF): /usr/lib/secure/64:/sunone/messaging64/lib

Command line:
crle -64 -c /var/ld/64/ld.config -s /usr/lib/secure/64:/sunone/messaging64/lib

As you see calendar has added the path to its libs in the 32bt crle and messaging in 64bit crle

Paris Heng · 03-09-2009, 10:35 AM

Quote:

Originally Posted by bathory

I don't know why utmp_update complains, but you can add a symlink for that lib to the trusted libraries directory and see if the warning goes away. Depending of the architecture (32 or 64 bits) do:

Code:

ln -s /lib/libumem.so* /lib/secure
or
ln -s /lib/libumem.so* /lib/secure/64

If any rollback works needed, what should I configured to remove the the ln between these two files and directory?

Paris Heng · 03-09-2009, 11:29 AM

Get it

Code:

rm /lib/secure
rm /lib/secure/64

bathory · 03-09-2009, 12:37 PM

Quote:

Originally Posted by Paris Heng

Get it

Code:

rm /lib/secure
rm /lib/secure/64

Better use:

Code:

rm /lib/secure/libumem.so*
rm /lib/secure/64/libumem.so*

in case the directories are not empty.

Paris Heng · 03-10-2009, 08:06 AM

problem solved, thanks alot!