These two days have been plagued by the following mistakes:
Ap13:lb-m Ccmscell uptime ld.so.1:uname:fatal:/usr/lib/secure/0@0.so.1:open failed:no file or directory such 6]: 4412 killed ld.so.1:uptime:fatal:/usr/lib/secure/0@0.so.1:open failed:no such file or directory
LB is a script that invokes Rsh, Ccmscell is a server pool,uname is invoked in lb.
Careful study of n-time related scripts, Google the N-Times related error messages, did not find a valuable clue. She later asked an IT colleague who said she had met a similar problem before, but her solution proved ineffective.
It turns out that not all of the servers are having problems executing this command, and some of them can be executed. In contrast, it turns out that if the/usr/lib/secure/0@0.so.1 group is set to Bin,owner as root, the above problem does not occur. The/usr/lib/secure/0@0.so.1 group on the problem server is other.
Further investigations revealed that/usr/lib/secure/0@0.so.1 was set to ld_preload_32 on Solaris 5.8 Because many programs were called by Setuid+chroot Pseudo root. The above error occurs only if the above command is executed by the pseudo root.
Luckily, Solaris 5.8 has begun to walk into the grave, even in a place that is lagging behind our company.
"update2011-06-23":
The root cause was found today not because of the/usr/lib/secure/0@0.so.1 group, but because there is no/usr/lib/on the remote server (such as the server in Pool Ccmscell) secure/0@0.so.1--executes the rsh command login is the setuid+chroot implementation of pseudo root, so remote server will need/usr/lib/secure/0@0.so.1.
"Update 2012-03-12"
today, you have encountered an error on Solaris 9:
Ld.so.1:pt_chmod:warning:/lib/0@0.so.1:open failed:illegal insecure pathname
It took a long time to remember that it could have been caused by/usr/lib/secure/0@0.so.1. A check /usr/lib/secure/0@0.so.1, and sure enough does not exist.
On a working server,
Ap31:echo $LD _preload_32
/usr/lib/secure/0@0.so.1
On a server that is not working,
Ap13:echo $LD _preload_32
/lib/0@0.so.1
--just upgraded a software and then lost the library, some comrades, alas ...