So one of the more challanging issues with Siteminder Web Agents on UNIX / LINUX is the way that shared objects are handled. I call the three general ways this can cause issues the Three P’s:
whenever a webagent is patched you run the risk of mucking up the shared objects. Always backup everything before you start, never manually copy things in, and making sure that your environment scripts are correct is the easiest way to avoid this.
Historically, the .so libraries have been stored in the WebAgentHome/lib directory, but things have been moving to /bin for some time. bringing up the LLAWP webagent process with error -LLAWP: error while loading shared libraries: libsmi18n.so: cannot open shared object file: No such file or directory.
Making sure that the PATH, LD_LIBRARY_PATH, and other environment settings are set correctly for the user, the users profile, and various start scripts is well documented on the CA support site and is always a good first place to start.
Definitely the hardest thing to troubleshoot–changes to the file system ownership is generally the root cause–someone doing chown -g dave or something so that the group permissions get all messed up can cause error while loading shared libraries: libsmi18n.so: cannot open shared object file: No such file or directory type errors at startup which do not make much sense and are hard to find.
Make sure stuff like:
LLAWP /path/to/webagent.conf -APACHEversion
work is a good place to start. Comparing closely with a working server is likely the only way to find these–be sure to pay attention to sym link permission.