nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OD Rcvr: Port already in use: 9173

djhalliday

Environment:

TeamSite 6.5 SP1
OpenDeploy 6.0.2 (with DD enabled)
Windows 2003 EE

Scenario / Problem:

I'm data deploying to a number of different database servers - each of which requires a properly configured open deploy receiver.
I've had no trouble doing this until the current server, which is failing to start-up with an error remarkably similar to that in this post .

Here is the output and od.log from the latest attempt to start the receiver:

Command-Line Output
(btp01db) OpenDeployNG > /etc/init.d/iwod60 stop
iwod60:20051005:0527: Stopping OpenDeploy server and its RMI registry.
iwod60:20051005:0527: OpenDeploy server home is /apps/OpenDeployNG
iwod60:20051005:0527: OpenDeploy instance name is initial
OpenDeploy server is stopping, please wait ...
OpenDeploy server and its RMI registry stopped.
(btp01db) OpenDeployNG > /etc/init.d/iwod60 start
iwod60:20051005:0529: Starting OpenDeploy server and its RMI registry.
iwod60:20051005:0529: OpenDeploy server home is /apps/OpenDeployNG
iwod60:20051005:0529: OpenDeploy instance name is initial
Starting OpenDeploy server.
It may take a few moments. Please wait....
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
WARNING: The OpenDeploy server is still not responding.
WARNING: Please check the OpenDeploy server log.
WARNING: OpenDeploy might have failed during start up or
it might still be in the process of starting up.
Make sure OpenDeploy server successfully
started up before doing deployments.

From the od.log
iwod60:20051005:0527: Stopping OpenDeploy server and its RMI registry.
iwod60:20051005:0527: OpenDeploy server home is /apps/OpenDeployNG
iwod60:20051005:0527: OpenDeploy instance name is initial
OpenDeploy server is stopping, please wait ...
OpenDeploy server host: localhost, RMI registry port: 9173
shutdownDate: Wed Oct 05 05:27:49 UTC 2005
OpenDeploy server and its RMI registry stopped.

iwod60:20051005:0529: Starting OpenDeploy server and its RMI registry.
iwod60:20051005:0529: OpenDeploy server home is /apps/OpenDeployNG
iwod60:20051005:0529: OpenDeploy instance name is initial
Starting OpenDeploy server.
processod: OpenDeploy home = /apps/OpenDeployNG
processod: RMI registry port = 9173
processod: OpenDeploy instance name = initial
DEPLOYAPI_AGENT_CMD "/apps/OpenDeployNG/jre/bin/java" -Xss2m -Xms32m -Xmx256m -classpath "/apps/OpenDeployNG/lib/odcomboint.jar:/apps/OpenDeployNG/lib/ddcombo.jar:/apps/OpenDeployNG/lib/odapi_svr100.jar:/apps/OpenDeployNG/lib/odapi_cl100.jar:/apps/OpenDeployNG/lib/odng.jar:/apps/OpenDeployNG/lib/version.jar:/apps/OpenDeployNG/drivers/classes12.zip:/apps/OpenDeployNG/jre/lib/sparc:/apps/OpenDeployNG/lib/odcombo.jar:/apps/OpenDeployNG/websvc/lib/wasp_combo.jar" -Djava.library.path="/apps/OpenDeployNG/lib:/apps/OpenDeployNG/jre/lib/sparc:/usr/lib" -Djava.rmi.server.codebase="file:///apps/OpenDeployNG/lib/odapi_cl100.jar file:///apps/OpenDeployNG/openjms/lib/openjms-client-0.7.6.1.jar" -Djava.rmi.server.useCodebaseOnly=true -Djava.security.manager -Djava.security.policy="/apps/OpenDeployNG/lib/deployapi.policy" -Dod.home="/apps/OpenDeployNG" -Dod.inst.name=initial com.interwoven.deploy.cdmain.IWCDBoot "/apps/OpenDeployNG/etc/deploy.cfg"
START OD AGENT
It may take a few moments. Please wait....
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Begin initialization of OpenDeploy server.
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Version: 6.0.2.0.0 Build 46963 Interwoven 20050402
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using time zone: Coordinated Universal Time
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using locale: en_US
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using file encoding: UTF-8
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using OpenDeploy home directory: /apps/OpenDeployNG
SVR: 2005-10-05 05:29:44 UTC GMT+00:00
--License info--
License Information
Product Type : receiver
Trial Period (days) : 0

-----------------
No license expiration date
FileNotFoundException: /apps/OpenDeployNG/install/odlic_datadeploy (No such file or directory)
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 DataDeploy License not found
FileNotFoundException: /apps/OpenDeployNG/install/odlic_intelligentdelivery (No such file or directory)
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Intelligent Delivery License not found
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Got arguments: /apps/OpenDeployNG/etc/deploy.cfg
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Reading configuration file: /apps/OpenDeployNG/etc/deploy.cfg
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 RMI server binding hostname/IP address not requested in deploy.cfg file.
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Will use default which is the local hostname.
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 RMI server binding hostname/IP address in Java property is null.
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using server config file specified in deploy.cfg: /apps/OpenDeployNG/etc/odrcvr.xml
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using server nodes config file specified in deploy.cfg: /apps/OpenDeployNG/etc/odnodes.xml
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using server log directory /apps/OpenDeployNG/log specified in server config file.
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using OpenDeploy Server log file: /apps/OpenDeployNG/log/btp01db_odrcvr.log
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Using Reporting log file: /apps/OpenDeployNG/log/btp01db_eventReporting.log
SVR: 2005-10-05 05:29:44 UTC GMT+00:00 Start logging to OpenDeploy server log.
java.rmi.server.ExportException: Port already in use: 9173; nested exception is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:283)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:218)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:400)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:134)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:163)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:110)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:96)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:189)
at com.interwoven.deploy.cdmain.IWCDMain.main(IWCDMain.java:1622)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.interwoven.deploy.cdmain.IWCDBoot.run(IWCDBoot.java:255)
at java.lang.Thread.run(Thread.java:567)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:357)
at java.net.ServerSocket.bind(ServerSocket.java:341)
at java.net.ServerSocket.<init>(ServerSocket.java:208)
at java.net.ServerSocket.<init>(ServerSocket.java:120)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:45)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:349)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:633)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:271)
... 15 more
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
OpenDeploy server and its RMI registry started.
WARNING: The OpenDeploy server is still not responding.
WARNING: Please check the OpenDeploy server log.
WARNING: OpenDeploy might have failed during start up or
it might still be in the process of starting up.
Make sure OpenDeploy server successfully
started up before doing deployments.

Following the advice from the aforementioned post., I did a 'netstat -anp' to get a list of any active connections to port 9173.
According to netstat help, the -p flag should also map these connections to PIDs,
which is appears to be doing.

Here is only relevant line from the output that references this port:

Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:9173 0.0.0.0:* LISTEN -

The problem is, there doesn't seem to be a PID associated with the process listening on 9173. Any suggestions on this one??
Is there a way to unbind ports without knowing the PID to kill? I'm stumped.

Thanks,
Derek

Find more posts tagged with

Comments

djhalliday

Looks like the issue is lack of permissions on the database server - I'm currently not permitted to view the relevant PID in order to kill it. Hopefully once I get the correct permissions I'll be able to resolve this.