Question Admin server not starting up

[Anish T S]

Hello,

I am newbie to progress and from unix admin background. When my client starts the admin server after a server crash following error coming.

Exception at Mon Nov 25 04:07:13 IST 2013: java.rmi.server.ExportException
Message (throw): RegistryManager: Could not start RMI Registry
Message (excp): Port already in use: 20931; nested exception is:
java.net.BindException: Address already in use
Stack Trace:
java.rmi.server.ExportException: Port already in use: 20931; nested exception is:
java.net.BindException: Address already in use
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:249)
at sun.rmi.transport.tcp.TCPTransport.exportObject(TCPTransport.java:184)
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:180)
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:186)
at com.progress.common.rmiregistry.PrimaryRegistryManager.startRMIRegistry(PrimaryRegistryManager.java:188)
at com.progress.common.rmiregistry.PrimaryRegistryManager.register(PrimaryRegistryManager.java:73)
at com.progress.chimera.adminserver.AdminServer.setupRMI(AdminServer.java:644)
at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:312)
at com.progress.chimera.adminserver.AdminServer.<init>(AdminServer.java:166)
at com.progress.chimera.adminserver.NonNTAdminServer.<init>(NonNTAdminServer.java:10)
at com.progress.chimera.adminserver.NonNTAdminServer.main(NonNTAdminServer.java:29)
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:585)
at com.progress.chimera.adminserver.AdminServerStarter.<init>(AdminServerStarter.java:74)
at com.progress.chimera.adminserver.AdminServerStarter.main(AdminServerStarter.java:88)
Caused by: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:359)
at java.net.ServerSocket.bind(ServerSocket.java:319)
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:622)
at sun.rmi.transport.tcp.TCPTransport.listen(TCPTransport.java:237)
... 20 more

The port is not used by any other programs.

while doing a netstat during admin server start up I am seeing below

proadsv -start;netstat -an|grep 20931
OpenEdge Release 10.0B03 as of Wed Sep 7 10:19:30 EDT 2005
tcp 1 0 ::ffff:127.0.0.1:44433 ::ffff:127.0.0.1:20931 CLOSE_WAIT
tcp 0 0 ::ffff:127.0.0.1:20931 ::ffff:127.0.0.1:44433 FIN_WAIT2

Could you please help me out ?

 

[Cringer]

Progress version might be of use to tracking this down, as might OS and version please.

 

[Anish T S]

Hi Cringer,

Thanks for replying.

Is this the progress version:-
OpenEdge Release 10.0B03 as of Wed Sep 7 10:19:30 EDT 2005

Os:-
Linux myhost01 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007 i686 i686 i386 GNU/Linux

 

[Rob Fitzpatrick]

What do you see in netstat prior to starting the admin server?

 

[Anish T S]

nothing in netstat o/p

[root@myhost01 ~]# lsof -i :20931
[root@myhost01 ~]# telnet localhost 20931
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host: Connection refused
[root@myhost01 ~]#
[root@myhost01 ~]# netstat -an | grep 20931
[root@myhost01 ~]#

 

[RealHeavyDude]

OE 10.0B is a very old release and uses a very, very, very old version of Java.

Nevertheless, sometimes the Admin Server or some other involved Java process are in limbo and you are not able to stop it with the command provided by Progress. The only solution I've found to work for me is to kill the process on the OS level. ps and a grep for Java and the OpenEdge installation directory should give you a list of such Java process.

I know it is not a good solution, but you might spend a lot of time and effort into finding out why, in the end you will most likely wind up killing the offending process anyway.

Heavy Regards, RealHeavyDude.

 

[Anish T S]

Thanks RealHeavyDude,

But my issue is that the server was rebooted and when trying to start the admin server the error is coming. Anyway app team is trying to reinstall. I will update you the progress. It will take 2-3 days.

 

[RealHeavyDude]

I would check whether the Admin Server is auto-started when the machine is rebooted. I am aware of several machines where shutdown and starts are included in the system shutdown/startup - alhtough I have to admit that I am not a big fan of such automatic behavior that is not transparent.

Heavy Regards, RealHeavyDude.

 

[Anish T S]

Hi RealHeavyDude,

Thank you for your reply. Application team fixed the issue. It seems that java paths are not correct in some files and once they updated it with correct java path admin server started successfully. I don't have much idea what all are the files they edited.

Thank you all for your support.

 

[cj_brandt]

You can check the timestamp on the properties files in $DLC/properties, they were probably updated. There is also $DLC/bin/java_env.