Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
segmentation fault in OD
rangan
Hi,
While trying to start Open Deploy in my local solaris box , I followed the below steps :
# cd /etc/init.d
# ./iwtcboot start
# ./iwod start
But only the process /apps/iw-home/OpenDeployNG/jre/bin/../bin/sparc/native_threads/rmiregistry 9173 has started . The other process i.e /bin/sh /apps/iw-home/OpenDeployNG/startod is not starting up. When I tried starting this process explicitly from the command line , I get the below chain of messages :
OD HOME is: /apps/iw-home/OpenDeployNG
RMI registry port: 9173
DEPLOYAPI_AGENT_CMD /apps/iw-home/OpenDeployNG/jre/bin/java -Xss2m -classpath /apps/iw-home/OpenDeployNG/lib/odapi_svr100.jar:/apps/iw-home/OpenDeployNG/lib/odapi_cl100.jar:/apps/iw-home/OpenDeployNG/lib/odng.jar:/apps/iw-home/OpenDeployNG/lib/od_fo.jar:/apps/iw-home/OpenDeployNG/lib/od_se.jar:/apps/iw-home/OpenDeployNG/lib/cfg2xml.jar:/apps/iw-home/OpenDeployNG/jre/lib/sparc:/apps/iw-home/OpenDeployNG/lib/odcombo.jar:/apps/iw-home/OpenDeployNG/jre/lib/dt.jar -Djava.library.path=/apps/iw-home/OpenDeployNG/lib:/apps/iw-home/OpenDeployNG/jre/lib/sparc:/usr/lib -Djava.rmi.server.codebase=file:/apps/iw-home/OpenDeployNG/lib/odapi_cl100.jar -Djava.security.policy=/apps/iw-home/OpenDeployNG/lib/deployapi.policy -Dinterwoven.deployapi.locator=9173 -Dod.home=/apps/iw-home/OpenDeployNG com.interwoven.deployapi.service.IWODServiceServer /apps/iw-home/OpenDeployNG/etc/deploy.cfg
START OD AGENT
Parsing command line.
Reading configuration:
File "/apps/iw-home/OpenDeployNG/etc/deploy.cfg".
Getting locator.
Starting services:
Starting service "Deploy":
Creating service "Deploy". [Interface version: "-0.0"]
Registering service "Deploy" as "IWDeployService".
OpenDeploy server host: localhost, RMI registry port: 9173
API: 2004-09-15 06:42:16 BST GMT+01:00 Using time zone: Greenwich Mean Time
API: 2004-09-15 06:42:16 BST GMT+01:00 Using locale: en_US
API: 2004-09-15 06:42:16 BST GMT+01:00 Using file encoding: UTF-8
API: 2004-09-15 06:42:16 BST GMT+01:00 Using OpenDeploy home directory: /apps/iw-home/OpenDeployNG
API: 2004-09-15 06:42:16 BST GMT+01:00 Using server config file specified in deploy.cfg: /apps/iw-home/OpenDeployNG/etc/odbase.xml
API: 2004-09-15 06:42:16 BST GMT+01:00 Using server nodes config file specified in deploy.cfg: /apps/iw-home/OpenDeployNG/etc/odnodes.xml
API: 2004-09-15 06:42:17 BST GMT+01:00 Using server log directory /apps/iw-home/OpenDeployNG/log specified in server config file.
API: 2004-09-15 06:42:17 BST GMT+01:00 Using OpenDeploy Server log file /apps/iw-home/OpenDeployNG/log/delmhicom-testscjp-intrwvn_odbase.log.
API: 2004-09-15 06:42:17 BST GMT+01:00 Start logging to server log.
Segmentation Fault - core dumped
Can anybody please tell me the cause of this segmentation fault which is occuring ?
Thanks,
RG
Find more posts tagged with
Comments
Adam Stoller
Do you know if your server has been appropriately patched with all the latest Solaris Java/JDK patches - as documented as being required in the installation manual?
If not - you could very well be running into a problem with the java code that might be causing a segmentation violation when attempting to start up.
If you believe you *have* correctly patched your server's OS - then I suggest you open up a case with Interwoven Support so that they can work with you on resolving the situation.
--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com
bodo
This is what we got as an answer in Jan 2003 by support
OpenDeploy 5.5.1 Solaris Fails When Executed From an External Task
Knowledge Base Article: 49799
Type: Tech Note
Author: Sajid Islam
Synopsis
OpenDeploy 5.5.1 Solaris may fail/core dump, when executed from an external task.
Details
The cause of this failure is due to two (2) known bugs at the time of publishing this article.
Bug #1 is a Teamsite bug, where not all file descriptors in a forked process are being closed.
Bug #2 is a Sun bug 4821957 in ksh where it cores when too many files are open.At present, there are 2 workarounds:1) Change all the JDK/jre distributions's .java_wrapper script topline from /usr/bin/ksh to /usr/dt/bin/dtksh So, in OD's case, the change would be in /jre/bin/.java_wrapperOR2)# mv /usr/bin/ksh /usr/bin/ksh.orig# cp -p /usr/dt/bin/dtksh /usr/bin/ksh
Cheers,
bodo
Migrateduser
That problem (#1) was addressed in a TeamSite service pack. (May have been TS 5.5.2 SP3, but I'm going from memory here.)
There were some discussion threads on this topic.
Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e:
tscallan@interwoven.com
Edited by tscallan on 09/15/04 08:11 AM (server time).