This discussion is archived
5 Replies Latest reply: Mar 26, 2012 6:15 AM by 923604 RSS

Can not deploy  a remote storage node

923604 Newbie
Currently Being Moderated
Hello,

I have started successfully two SNA at two node, because we can ping to each other. But when I use admin console to to deploy the first remote storage node, it always shows the error "Connection refused to host: localhost". I use the command line to deploy a remote storage node. There is the same problem.
Dose some one know how to solve it? Thank you advanced.

Here is the error log:

in createPlan: Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is: java.net.ConnectException: Connection refused

caused by:
oracle.kv.impl.admin.AdminFaultException
Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
Oracle NoSQL DB 11gR2.1.2.123 oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused oracle.kv.impl.fault.OperationFaultException: Plan 16[Plan-16] finished in state ERROR. Problem during plan execution: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:601)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:198)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:110)
     at java.rmi.server.RemoteObjectInvocationHandler.invokeRemoteMethod(RemoteObjectInvocationHandler.java:178)
     at java.rmi.server.RemoteObjectInvocationHandler.invoke(RemoteObjectInvocationHandler.java:132)
     at $Proxy8.getSerialVersion(Unknown Source)
     at oracle.kv.impl.util.registry.RemoteAPI.(RemoteAPI.java:32)
     at oracle.kv.impl.sna.StorageNodeAgentAPI.(StorageNodeAgentAPI.java:51)
     at oracle.kv.impl.sna.StorageNodeAgentAPI.wrap(StorageNodeAgentAPI.java:58)
     at oracle.kv.impl.util.registry.RegistryUtils.getStorageNodeAgent(RegistryUtils.java:243)
     at oracle.kv.impl.admin.plan.task.DeploySN.call(DeploySN.java:94)
     at oracle.kv.impl.admin.plan.task.DeploySN.call(DeploySN.java:35)
     at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
     at java.util.concurrent.FutureTask.run(FutureTask.java:138)
     at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
     at java.lang.Thread.run(Thread.java:662)
Caused by: java.rmi.ConnectException: Connection refused to host: localhost; nested exception is:
     java.net.ConnectException: Connection refused
     ... 18 more
Caused by: java.net.ConnectException: Connection refused
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:351)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:213)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:200)
     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
     at java.net.Socket.connect(Socket.java:529)
     at java.net.Socket.connect(Socket.java:478)
     at java.net.Socket.(Socket.java:375)
     at java.net.Socket.(Socket.java:189)
     at sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:22)
     at sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:128)
     at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:595)
     ... 17 more

     at oracle.kv.impl.admin.AdminServiceFaultHandler.getThrowException(AdminServiceFaultHandler.java:84)
     at oracle.kv.impl.fault.ProcessFaultHandler.rethrow(ProcessFaultHandler.java:205)
     at oracle.kv.impl.fault.ProcessFaultHandler.execute(ProcessFaultHandler.java:144)
     at oracle.kv.impl.admin.CommandServiceImpl.executePlan(CommandServiceImpl.java:234)
     at oracle.kv.impl.admin.CommandServiceAPI.executePlan(CommandServiceAPI.java:162)
     at oracle.kv.impl.admin.webapp.server.AdminUIServiceImpl.createPlan(AdminUIServiceImpl.java:554)
     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:597)
     at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:569)
     at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:208)
     at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:248)
     at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:538)
     at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:476)
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119)
     at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:517)
     at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:225)
     at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:934)
     at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:404)
     at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:183)
     at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:869)
     at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
     at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:114)
     at org.eclipse.jetty.server.Server.handle(Server.java:341)
     at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:589)
     at org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1065)
     at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:823)
     at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:220)
     at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:515)
     at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:40)
     at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:529)
     at java.lang.Thread.run(Thread.java:662)
(from Plans.PlanCallback)
  • 1. Re: Can not deploy  a remote storage node
    Charles Lamb Pro
    Currently Being Moderated
    If I had to guess, I would bet that you used "localhost" in your configuration. Start from scratch and don't use localhost. That will probably help.

    Charles Lamb
  • 2. Re: Can not deploy  a remote storage node
    923604 Newbie
    Currently Being Moderated
    Thanks, Charles. I use network host name or network host IP address instead of localhost and it well resolved my former problem. I can deploy the remote SN. But there is a new problem when I deploy the store. It looks like that these Replication Node at different SN can not communicate with each other, because of mis-match IP address format.

    Note that the node "community01/10.193.128.223" is the first deployed node who holds the administration process, "mi-desktop/127.0.1.1:5011" is another node. I don't understand why the second node uses its loopback adress. Can you help me to find out the solution?

    Here is the original error log.
    "mi-desktop/127.0.1.1:5011 the address associated with this node, is a loopback address. It conflicts with an existing use, by a different node of the address:community01/10.193.128.223:5011 which is not a loopback address. Such mixing of addresses within a group is not allowed, since the nodes will not be able to communicate with each other."
  • 3. Re: Can not deploy  a remote storage node
    Charles Lamb Pro
    Currently Being Moderated
    920601 wrote:
    Thanks, Charles. I use network host name or network host IP address instead of localhost and it well resolved my former problem. I can deploy the remote SN. But there is a new problem when I deploy the store. It looks like that these Replication Node at different SN can not communicate with each other, because of mis-match IP address format.

    Note that the node "community01/10.193.128.223" is the first deployed node who holds the administration process, "mi-desktop/127.0.1.1:5011" is another node. I don't understand why the second node uses its loopback adress. Can you help me to find out the solution?

    Here is the original error log.
    "mi-desktop/127.0.1.1:5011 the address associated with this node, is a loopback address. It conflicts with an existing use, by a different node of the address:community01/10.193.128.223:5011 which is not a loopback address. Such mixing of addresses within a group is not allowed, since the nodes will not be able to communicate with each other."
    I'm not sure I have any good advice, but I would check your /etc/hosts to see if mi-desktop maps to the loopback address (127.0.0.1). If it does, then you need to use a name that does not map to the loopback.

    Charles Lamb
  • 4. Re: Can not deploy  a remote storage node
    923604 Newbie
    Currently Being Moderated
    Hi Charles,

    I use the real IP address as the the node name. These two node can ping to each other. But the preblem is still like that. Can you give me a standard configuration in the /etc/hosts for the Oracle Nosql data base installation? Thank you very much for your help.

    Best regards,

    Kun
  • 5. Re: Can not deploy  a remote storage node
    923604 Newbie
    Currently Being Moderated
    Hello,

    I want to share my solution for those problems in my former messages. That is just because of locking of clock synchronisation in multiple physical nodes. Setting a NTP server is a simple and good solution. It is noted in the installation guide, but I ignored it.(see: http://docs.oracle.com/cd/NOSQL/html/AdminGuide/installation.html#install-prereqs)

    Best regards,

    Kun

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points