tail -f (your service)/log/error.log
[20/Oct/2012:14:38:26][1360.1929070336][-main-] Notice: modload: loading '/usr/lib/aolserver4/bin/nssha1.so'
[20/Oct/2012:14:38:26][1360.1929070336][-main-] Warning: modload: could not find Ns_ModuleInit in /usr/lib/aolserver4/bin/nssha1.so
[20/Oct/2012:14:38:26][1360.1929070336][-main-] Fatal: modload: failed to load module '/usr/lib/aolserver4/bin/nssha1.so'
I verified the file nssha1.so exists. I don't know how to proceed. Thanks for the help.
I vaguely remember a similar situation where modules were built strangely (and Ns_ModuleInit was involved iirc) when aolserver 4.5 first came out; this link issue was solved in aolserver 4.5.1. It had something to do with building from each module, a nsX.so -and- a libnsX.so; I never found out why a lib was built for each module.
the only other thing I can offer, is that while I never used naviserv either before it was renamed to aolserver or after it was forked from aolserver, I'm presently trying to find out where the actice development is taking place. I may or may not switch to naviserv on that basis or on the basis of building and testing it.
I was running out of time so in the end, rightly or wrongly, I renamed the bin/nssha1.so and symlinked lib/libnssha1.so to bin/nssha1.so and it appears to have worked. This was just for a demo on a laptop so not a critical test but it appeared OK.