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)
Starting Open Deploy Errors
Lynchy
Trying to start Open deploy On A Receiver And receiving some weird error messages. Any help greatly appreciated as my eyes are bugging from crawling logs and config files:
From ServerName_odrcvr.log:
ENG: 2003-03-13 13:07:30 EST ***ERROR - Exception: CONFIG_FILE.
message: CONFIG_FILE.
Details: File not found
at com.interwoven.deploy.adapters.od.TNewToOldRx.convert(TNewToOldRx.java:93)
at com.interwoven.deploy.adapters.od.TNewToOldRx.convert(TNewToOldRx.java:58)
at com.interwoven.deploy.engine.TMacroDeployReceiver.start(TMacroDeployReceiver.java:121)
at com.interwoven.deploy.engine.TDeploySvrEngine.start(TDeploySvrEngine.java:692)
at com.interwoven.deployapi.deploy.IWDeployServiceRemoterImpl.<init>(IWDeployServiceRemoterImpl.java:662)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.interwoven.deployapi.service.IWODServiceServer.startService(IWODServiceServer.java:373)
at com.interwoven.deployapi.service.IWODServiceServer.startServiceList(IWODServiceServer.java:296)
at com.interwoven.deployapi.service.IWODServiceServer.server(IWODServiceServer.java:158)
at com.interwoven.deployapi.service.IWODServiceServer.main(IWODServiceServer.java:169)
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.a([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
API: 2003-03-13 13:07:30 EST *** ERROR: OpenDeploy server encountered error.
Bring up of OpenDeploy server FAILED.
message: AGENT_RECEIVER_FAILED
Details: Failed to start OpenDeploy receiver.error caught:
CONFIG_FILE.
at com.interwoven.deploy.engine.TMacroDeployReceiver.start(TMacroDeployReceiver.java:145)
at com.interwoven.deploy.engine.TDeploySvrEngine.start(TDeploySvrEngine.java:692)
at com.interwoven.deployapi.deploy.IWDeployServiceRemoterImpl.<init>(IWDeployServiceRemoterImpl.java:662)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.interwoven.deployapi.service.IWODServiceServer.startService(IWODServiceServer.java:373)
at com.interwoven.deployapi.service.IWODServiceServer.startServiceList(IWODServiceServer.java:296)
at com.interwoven.deployapi.service.IWODServiceServer.server(IWODServiceServer.java:158)
at com.interwoven.deployapi.service.IWODServiceServer.main(IWODServiceServer.java:169)
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.a([DashoPro-V1.2-120198])
at com.zerog.lax.LAX.main([DashoPro-V1.2-120198])
FROM opendeploy.log:
Parsing command line.
Reading configuration:
File "/zline/iw-home/opendeploy/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: 2003-03-13 13:07:30 EST Using OpenDeploy home directory: /zline/iw-home/opendeploy/OpenDeployNG
API: 2003-03-13 13:07:30 EST Using server config file specified in deploy.cfg: /zline/iw-home/opendeploy/OpenDeployNG/etc/new
.xml
API: 2003-03-13 13:07:30 EST Using server nodes config file specified in deploy.cfg: /zline/iw-home/opendeploy/OpenDeployNG/e
tc/odnodes.xml
API: 2003-03-13 13:07:30 EST Using server log directory /zline/iw-home/opendeploy/OpenDeployNG/log specified in server config
file.
API: 2003-03-13 13:07:30 EST Using OD Server log file /zline/iw-home/opendeploy/OpenDeployNG/log/tpascr02_odrcvr.log.
API: 2003-03-13 13:07:30 EST Start logging to server log.
ERROR: File not found
~
~
FROM od.log:
iwod:20030313:1251: Starting iwdeploy server
OpenDeploy server host: localhost, RMI registry port: 9173
Connection could not be established to 'IWDeployService'
iwod:20030313:1307: Starting iwdeploy server
Again Any help greatly appreciated. All files are in the places they should be after triple checks but still getting these errors.
Find more posts tagged with
Comments
Lynchy
Turned out to be permissions issues where some files were owned by root. I would have expected more precise error messages but OH Well.