Hi Naveen! There are a few problems with your command. Try this one: *$ ./control.sh --host 10.144.96.142 --port 11211 --activate*
Port should be equal to the connector port, not discovery. The same thing can be achieved, using Visor CLI, by executing *top -activate* command. Denis вт, 2 янв. 2018 г. в 16:15, Naveen <[email protected]>: > Hi > > Am using 2.3, was trying to activate the cluster with the below command > > [tibusr@JMNGD1BAO50D00 bin]$ ./control.sh --10.144.96.142 --port 47500 > --activate > Something fail during activation, exception message: Latest topology update > failed. > > Here is the cluster config entries > > <property name="addresses"> > <list> > > <value>10.144.96.142:47500..47502</value> > <value>10.144.96.144:47500..47502</value> > <value>10.144.96.145:47500..47502</value> > </list> > </property> > > This is what I could see from the logs > > [18:43:37,412][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery accepted incoming connection [rmtAddr=/127.0.0.1, rmtPort=42958] > [18:43:37,412][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery spawning a new thread for connection [rmtAddr=/127.0.0.1, > rmtPort=42958] > [18:43:37,412][INFO][tcp-disco-sock-reader-#14%IgnitePOC%][TcpDiscoverySpi] > Started serving remote node connection [rmtAddr=/127.0.0.1:42958, > rmtPort=42958] > > [18:43:37,432][WARNING][tcp-disco-sock-reader-#14%IgnitePOC%][TcpDiscoverySpi] > Unknown connection detected (is some other software connecting to this > Ignite port? missing SSL configuration on remote node?) [rmtAddr=/ > 127.0.0.1] > [18:43:37,432][INFO][tcp-disco-sock-reader-#14%IgnitePOC%][TcpDiscoverySpi] > Finished serving remote node connection [rmtAddr=/127.0.0.1:42958, > rmtPort=42958 > [18:43:38,461][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery accepted incoming connection [rmtAddr=/127.0.0.1, rmtPort=42960] > [18:43:38,461][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery spawning a new thread for connection [rmtAddr=/127.0.0.1, > rmtPort=42960] > [18:43:38,462][INFO][tcp-disco-sock-reader-#15%IgnitePOC%][TcpDiscoverySpi] > Started serving remote node connection [rmtAddr=/127.0.0.1:42960, > rmtPort=42960] > [18:43:38,463][INFO][tcp-disco-sock-reader-#15%IgnitePOC%][TcpDiscoverySpi] > Finished serving remote node connection [rmtAddr=/127.0.0.1:42960, > rmtPort=42960 > [18:43:39,464][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery accepted incoming connection [rmtAddr=/127.0.0.1, rmtPort=42962] > [18:43:39,464][INFO][tcp-disco-srvr-#2%IgnitePOC%][TcpDiscoverySpi] TCP > discovery spawning a new thread for connection [rmtAddr=/127.0.0.1, > rmtPort=42962] > [18:43:39,465][INFO][tcp-disco-sock-reader-#16%IgnitePOC%][TcpDiscoverySpi] > Started serving remote node connection [rmtAddr=/127.0.0.1:42962, > rmtPort=42962] > [18:43:39,465][INFO][tcp-disco-sock-reader-#16%IgnitePOC%][TcpDiscoverySpi] > Finished serving remote node connection [rmtAddr=/127.0.0.1:42962, > rmtPort=42962 > > I could activate the cluster code thru code. > Whats wrong with this command, how can I activate cluster thru command port > Thanks > Naveen > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
