Content Server Crashes Shortly After Starting Up - Java stack shows error in libzip.so
(Doc ID 1616395.1)
Last updated on DECEMBER 15, 2017
Applies to:Oracle WebCenter Content - Version 10.1.3.5.0 to 22.214.171.124.0 [Release 10gR3 to 11g]
Information in this document applies to any platform.
When starting either of the two nodes in the cluster, they go down within 5 minutes. Can also happen in a non-clustered environment.
The web interface only displays the following message: The Server is unavailable. Unable to connect to address. Error code is 111.
The normal server logs do not have anything after logging the standard start up output.
Getting a java stack error :
# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x00002abeac88f1f0, pid=17144, tid=46998571075904
# JRE version: 6.0_45-b06
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.45-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libzip.so+0xb1f0] __int128+0x60
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