My Oracle Support Banner

An Application Reporting "ld.so.1: <binary> : fatal: relocation error" (Doc ID 1363879.1)

Last updated on MARCH 20, 2018

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 and later
Information in this document applies to any platform.
Checked for relevance on 12-oct-2016

Symptoms

This issue is likely to occur for every application present the OCNCC suite, in the example that will be followed through the course of this article, it will be a sample issue with Session Control Agent (SCA) that will be covered.

This article aims to explain about the cause that can lead an application reporting about:
-"ld.so.1: <binary> : fatal: relocation error"


The message mentioning the relocation error will only appear in the application's log file, usually located in /IN/service_packages/<APPLICATION>/tmp/<APPLICATION>.log:

ld.so.1: sca: fatal: relocation error: file /IN/service_packages/SCA/lib/libesctxn.so: symbol _ZN3esc10SipRequest12getViaBranchEv: referenced symbol not found

 

This relocation error message will result in the application generating a core file. The message signaling the application core will be seen in the system log (/var/adm/messages):

Sep 29 11:31:05 slc-01 genunix: [ID 603404 kern.notice] NOTICE: core_log: sca_11705162_1[14305] core dumped: /var/crash/core-slc-01-14305-sca_11705162_1




Changes

The present phenomenon will occur if:

-One or more libraries have been changed recently, causing an incompatibility with the concerned application.
-The application binary has been changed recently, causing an incompatibility with the installed libraries.

This will most of the time happen after the installation of an incompatible Emergency Binary, that can either be the application binary or, one or more libraries.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
 1. A recently installed patch.
 2. Lack of maintenance of the affected environment.
Solution
 1. A recently installed patch.
 2. Lack of maintenance of the affected environment.


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.