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 6.0.2 Port already in use: 9173

boskovuk

I am having a lots of problems with restarting OD 6.0.2 daemon process on our Solaris 9. I don't think I am be able to do that at all.

My latest attempts include:
/etc/init.d//iwod60 stop
/etc/init.d//iwod60 start

This is the outcome:
bash-2.05$ ./iwod60 stop
iwod60:20050805:1143: Stopping OpenDeploy server and its RMI registry.
iwod60:20050805:1143: OpenDeploy server home is /opt/Interwoven/OpenDeployNG
iwod60:20050805:1143: OpenDeploy instance name is initial
OpenDeploy server is stopping, please wait ...
OpenDeploy server and its RMI registry stopped.
bash-2.05$ ./iwod60 start
iwod60:20050805:1144: Starting OpenDeploy server and its RMI registry.
iwod60:20050805:1144: OpenDeploy server home is /opt/Interwoven/OpenDeployNG
iwod60:20050805:1144: 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.
bash-2.05$

This is coming from od.log:
START OD AGENT
SVR: 2005-08-05 11:44:50 EDT GMT+01:00 Begin initialization of OpenDeploy server.
SVR: 2005-08-05 11:44:50 EDT GMT-04:00 Version: 6.0.2.0.0 Build 46963 Interwoven 20050402
SVR: 2005-08-05 11:44:50 EDT GMT-04:00 Using time zone: Eastern Daylight Time
SVR: 2005-08-05 11:44:50 EDT GMT-04:00 Using locale: en_CA
SVR: 2005-08-05 11:44:50 EDT GMT-04:00 Using file encoding: ISO8859-1
SVR: 2005-08-05 11:44:50 EDT GMT-04:00 Using OpenDeploy home directory: /opt/Interwoven/OpenDeployNG
SVR: 2005-08-05 11:44:51 EDT GMT-04:00
--License info--
License Information
Product Type : full
Trial Period (days) : 0

-----------------
No license expiration date
SVR: 2005-08-05 11:44:51 EDT GMT-04:00
--DataDeploy License info--
License Information
Product Type : datadeploy
Trial Period (days) : 0

-----------------
No license expiration date
FileNotFoundException: /opt/Interwoven/OpenDeployNG/install/odlic_intelligentdelivery (No such file or directory)
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Intelligent Delivery License not found
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Got arguments: /opt/Interwoven/OpenDeployNG/etc/deploy.cfg
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Reading configuration file: /opt/Interwoven/OpenDeployNG/etc/deploy.cfg
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 RMI server binding hostname/IP address not requested in deploy.cfg file.
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Will use default which is the local hostname.
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 RMI server binding hostname/IP address in Java property is null.
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Using server config file specified in deploy.cfg: /opt/Interwoven/OpenDeployNG
/etc/odbase.xml
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Using server nodes config file specified in deploy.cfg: /opt/Interwoven/OpenDe
ployNG/etc/odnodes.xml
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Using server log directory /opt/Interwoven/OpenDeployNG/log specified in serve
r config file.
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Using OpenDeploy Server log file: /opt/Interwoven/OpenDeployNG/log/irc-ce_odba
se.log
SVR: 2005-08-05 11:44:51 EDT GMT-04:00 Using Reporting log file: /opt/Interwoven/OpenDeployNG/log/irc-ce_eventReporti
ng.log
SVR: 2005-08-05 11:44:51 EDT GMT-04: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:243)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:178)
at sun.rmi.transport.tcp.TCPEndpoint.exportObject(TCPEndpoint.java:382)
at sun.rmi.transport.LiveRef.exportObject(LiveRef.java:116)
at sun.rmi.server.UnicastServerRef.exportObject(UnicastServerRef.java:145)
at sun.rmi.registry.RegistryImpl.setup(RegistryImpl.java:92)
at sun.rmi.registry.RegistryImpl.<init>(RegistryImpl.java:78)
at java.rmi.registry.LocateRegistry.createRegistry(LocateRegistry.java:164)
at com.interwoven.deploy.cdmain.IWCDMain.main(IWCDMain.java:1623)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.interwoven.deploy.cdmain.IWCDBoot.run(IWCDBoot.java:255)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:331)
at java.net.ServerSocket.bind(ServerSocket.java:318)
at java.net.ServerSocket.<init>(ServerSocket.java:185)
at java.net.ServerSocket.<init>(ServerSocket.java:97)
at sun.rmi.transport.proxy.RMIDirectSocketFactory.createServerSocket(RMIDirectSocketFactory.java:27)
at sun.rmi.transport.proxy.RMIMasterSocketFactory.createServerSocket(RMIMasterSocketFactory.java:333)
at sun.rmi.transport.tcp.TCPEndpoint.newServerSocket(TCPEndpoint.java:615)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:231)
... 14 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.
bash-2.05$

Would this 'Port already in use: 9173' message mean that previous shutdown didn't complete successfully?

TS Server Version: 6.1.0
Service Pack 2 (Build Number: 41240)
Platform: Solaris 5.9

Find more posts tagged with

Comments

Migrateduser

Sounds like a safe bet. Or something else is bound to port 9173.

Do a netstat -an to see if something is in fact bound to 9173. I think Solaris's version of netstat doesn't include an option to see what PID is bound to a port. You can grab a package for lsof from sunfreeware.com to get that info and you could track back from there. I would also be curious, after you have executed your shutdown, to see a ps -eaf and to see if the
<OD-HOME>/db/.odrunning file and the <OD-HOME>/db/.opendeploy.pid file still exist (they shouldn't)

MyProject.rptdesign

gsundeep

Do you have any other version of OpenDeploy ( for e.g OD 5.6 ) running simultaneously on this system along with the OD 6.0.2.
If this the case, please check that the legacy version should not be using the RMI Port 9173 .

Thanks

boskovuk

robhuffstedtler,
you were right. Port 9173 was used by one of OpenDeploy processes. As you said, Solaris doesn't help with mapping port numbers to the processes that are holding them.

What we did here was to:
ps -ef | grep java and
ps -ef | grep Open

First one (grep java) gave us all 'java' processes. Second one (grep Open) gave us the one OpenDeploy (java) process that was not shutdown properly.

After killing hanging OD java process, things worked.

Solaris 5.9 - TS 6.5 sp1 - OD 6.0.2; DD enabled
Solaris 5.9 - TS 6.1 sp1 - OD 5.6; DD 5.6