Operating System - HP-UX
1826446 Members
4108 Online
109692 Solutions
New Discussion

Re: /usr/lib/dld.sl: Unresolved symbol

 
Raj_Ranjan
Frequent Advisor

/usr/lib/dld.sl: Unresolved symbol

Hi All,

From last few day whenever we are starting the webserver in our HP UX server getting the error message as fllow:

root@butldr [/webserver/https-butldr.example.com] > ./start
iPlanet-WebServer-Enterprise/6.0SP5 B10/31/2002 17:01
/usr/lib/dld.sl: Unresolved symbol: parse__9SAXParserFPCcb (code) from /webserver/bin/https/lib/libns-httpd40.sl

Syslog error : Oct 16 09:11:59 butldr uxwdog[2508]: server initialization failed (Interrupted system call)

Server info:
Model: N4000
OS : HP UX 11.1


Please help me in solving this problem. Its very urgent.

Thanks in advance.
5 REPLIES 5
James R. Ferguson
Acclaimed Contributor

Re: /usr/lib/dld.sl: Unresolved symbol

Hi:

Begin by asking yourself "what has recently changed?". The error suggests that '/webserver/bin/https/lib/libns-httpd40.sl' may have changed.

Regards!

...JRF...
Raj_Ranjan
Frequent Advisor

Re: /usr/lib/dld.sl: Unresolved symbol

Dear James,

No changes were done on the system...And after all it is a library file.

James R. Ferguson
Acclaimed Contributor

Re: /usr/lib/dld.sl: Unresolved symbol

Hi (again) Raj:

> No changes were done on the system...And after all it is a library file.

And my point is that do you *know* that the version of the library hasn't changed?

Regards!

...JRF...
Raj_Ranjan
Frequent Advisor

Re: /usr/lib/dld.sl: Unresolved symbol

Hi James,

I am not sure, please guide how to check for it and do the needful for it to work.

Thanks for being promp.
Dennis Handly
Acclaimed Contributor

Re: /usr/lib/dld.sl: Unresolved symbol

The demangled name of the symbol is:
SAXParser::parse(char const *, bool)

Do you know which shlib has the definition?
Did SHLIB_PATH change?

>No changes were done on the system.

If nothing really changed, it is possible to get unsats because of different execution paths in the application. The default is -B deferred. By using "chatr -B immediate executable" it is possible to see if there are are even more of them.

>please guide how to check for it

Well, the simplest would be to do "ll" on all shlibs in the application.
$ ll -L $(ldd executable | awk '{print $NF}')