/usr/dld.sl error (325 Views)
Reply
Frequent Advisor
Vincenzo Capasso
Posts: 101
Registered: ‎02-12-2003
Message 1 of 9 (325 Views)

/usr/dld.sl error

Hi all,

I have a problem with vp390 agent with OVO 8.10 on hp-ux 11.11 environment.
When I try to manage the "vp390sv" command, I have the following error in output:

------ Domain test1pt ------
Starting vp390mms (Master Message Server)...
/usr/lib/dld.sl: Unresolved symbol: $RECOVER_START (data) from /usr/lib/libcl.2
/usr/lib/dld.sl: Unresolved symbol: $RECOVER_END (data) from /usr/lib/libcl.2
/usr/lib/dld.sl: Unresolved module for symbol: U_get_previous_frame_x (code) from /usr/lib/libCsup.2
Starting vp390cs (Command Server)...
/usr/lib/dld.sl: Unresolved symbol: $RECOVER_START (data) from /usr/lib/libcl.2
/usr/lib/dld.sl: Unresolved symbol: $RECOVER_END (data) from /usr/lib/libcl.2
/usr/lib/dld.sl: Unresolved module for symbol: U_get_previous_frame_x (code) from /usr/lib/libCsup.2
Starting vp390alertsv (Alert Server)...
Starting vp390statman (Status Manager)...
root@suxdb01[/usr/lib]# eEVOSOK001 Alert Server failed calling read(), reason: I/O error
EVOSOK080 Alert Server failed reading HCI socket, reason: I/O error
EVOEXE102 Alert Server process of domain test1pt has exited.

I don't know how to solve this problem..

have u some idea??

Thanks in advance,
Vinc.
Exalted Contributor
Steven E. Protter
Posts: 33,806
Registered: ‎08-15-2002
Message 2 of 9 (325 Views)

Re: /usr/dld.sl error

1) check that SHLIB_PATH=/usr/lib ... echo $SHLIB_PATH

2) Check that the binary is installed correctly
swlist -a state | grep -i binary name

or swconfigure \*

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Occasional Visitor
100035354
Posts: 2
Registered: ‎04-11-2005
Message 3 of 9 (325 Views)

Re: /usr/dld.sl error

Hello Vincenzo,

I just have the same problem. Any clue on how you resolved it ??

thanks in advance.
Honored Contributor
Laurent Menase
Posts: 1,079
Registered: ‎11-06-2003
Message 4 of 9 (325 Views)

Re: /usr/dld.sl error

$RECOVER_START $RECOVER_END
are symbols added to structures used to stack unwind.

didn't you strip your executable?
Else what options did you compile and link with?
Honored Contributor
Naveej.K.A
Posts: 820
Registered: ‎06-11-2003
Message 5 of 9 (325 Views)

Re: /usr/dld.sl error

Hi,

Is the /lib and /usr/lib soft linked??

If not you have to create /lib linked to /usr/lib.

Regards,
Naveej
practice makes a man perfect!!!
Occasional Visitor
100035354
Posts: 2
Registered: ‎04-11-2005
Message 6 of 9 (325 Views)

Re: /usr/dld.sl error

I have already checked that /lib is linked to /usr/lib, so the problem persists.
Any other clue ?

I guess it's got to be with some kind of system patch, but which one ...??

Thanks in advance.
Rgds.
Honored Contributor
Laurent Menase
Posts: 1,079
Registered: ‎11-06-2003
Message 7 of 9 (325 Views)

Re: /usr/dld.sl error

The message is clear; the symbole $RECOVER_... are not available in your code.
you should check on your executable doing a
nm .... |grep RECOVER
if those 2 symboles are not defined you are probably stripped.
Else there is no problem whith path because it is in libcl which we encounter the problem.
U_get_previous_frame_x() is not loaded because RECOVER* are not available in the program.
Honored Contributor
Kent Ostby
Posts: 1,836
Registered: ‎09-26-2000
Message 8 of 9 (325 Views)

Re: /usr/dld.sl error

Seems like I saw this once before and it was resolved in a later version of OVO
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
Acclaimed Contributor
Dennis Handly
Posts: 25,089
Registered: ‎03-06-2006
Message 9 of 9 (318 Views)

Re: dld.sl unsat errors

[ Edited ]

>the symbols $RECOVER_... are not available in your code.
>you should check on your executable doing a
>nm .... | grep RECOVER

 

If these symbols aren't exported, it will also fail.  FOr PA32, check with:

odump -slexport ... | grep RECOVER

 

This could happen if the executable is now run against a new shlib version that now requires the aC++ runtime.

Or possibly use of an exported LD_PRELOAD for the whole session.

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.