Hi Evgenii,

  Issue has been resolved ..Thank you for   your suggetions

Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

________________________________
From: Evgenii Zhuravlev <e.zhuravlev...@gmail.com>
Sent: Thursday, May 21, 2020 7:12:11 PM
To: user <user@ignite.apache.org>
Subject: Re: Unable to deploy Ignite Web Console in local

"External email. Open with Caution"
I suggest checking the logs from the cluster nodes - there should be messages 
that node is using this IP and that it was bound to 8080 port.

Also, it makes sense to check the connection between these machines, there is a 
chance that you have a firewall or ports are blocked.

Evgenii

чт, 21 мая 2020 г. в 01:57, BEELA GAYATRI 
<beela.gaya...@tcs.com<mailto:beela.gaya...@tcs.com>>:

Hi Evgenii,



  Thanks for the update. When I run  in my local machine every thing works 
fine. However when I run the same in centOS Linux server web-console-agent.sh 
is not  able to communicate with node URI. Below is the log. Here my queries are



  1.  What should be the node uri to be given? Here I have given 
http://serverIp:8080
  2.  ignite-rest-http module is also in  Ignite_home libs folder.please 
suggest what could be the issue



WARNING: All illegal access operations will be denied in a future release

[2020-05-21T03:58:32,604][INFO ][main][AgentLauncher]

[2020-05-21T03:58:32,604][INFO ][main][AgentLauncher] Web Console Agent 
configuration :

[2020-05-21T03:58:32,950][INFO ][main][AgentLauncher] User's security tokens    
         : ********************************7066

[2020-05-21T03:58:32,951][INFO ][main][AgentLauncher] URI to Ignite node REST 
server     : http://xx.xxx.xxx.xxx:8080

[2020-05-21T03:58:32,952][INFO ][main][AgentLauncher] Login to Ignite node REST 
server   : ignite

[2020-05-21T03:58:32,952][INFO ][main][AgentLauncher] Password to Ignite node 
REST server: ******

[2020-05-21T03:58:32,953][INFO ][main][AgentLauncher] URI to GridGain Web 
Console        : http://xx.xxx.xxx.xxx:8008

[2020-05-21T03:58:32,953][INFO ][main][AgentLauncher] Path to properties file   
         : default.properties

[2020-05-21T03:58:32,954][INFO ][main][AgentLauncher] Path to JDBC drivers 
folder        : /***/*****/gridgain-web-console-agent-2020.03.01/./jdbc-drivers

[2020-05-21T03:58:32,954][INFO ][main][AgentLauncher] Demo mode                 
         : enabled

[2020-05-21T03:58:32,955][INFO ][main][AgentLauncher]

[2020-05-21T03:58:33,117][INFO ][main][WebSocketRouter] Starting Web Console 
Agent...

[2020-05-21T03:58:33,148][INFO ][Connect thread][WebSocketRouter] Connecting to 
server: ws://xx.xxx.xxx.xxx:8008

[2020-05-21T03:58:34,381][INFO ][http-client-16][WebSocketRouter] Successfully 
completes handshake with server

[2020-05-21T03:58:34,440][WARN ][pool-2-thread-1][ClusterHandler] Failed to 
connect to cluster.

[2020-05-21T03:58:34,440][WARN ][pool-2-thread-1][ClusterHandler] Check that 
'--node-uri' configured correctly.

[2020-05-21T03:58:34,441][WARN ][pool-2-thread-1][ClusterHandler] Ensure that 
cluster nodes have [ignite-rest-http] module in classpath (was copied from 
libs/optional to libs folder).

[2020-05-21T03:58:34,446][INFO ][pool-2-thread-1][ClustersWatcher] Failed to 
establish connection to node

^C[2020-05-21T04:00:03,722][INFO ][Thread-9][WebSocketRouter] Websocket 
connection closed with code: 1006

[2020-05-21T04:00:03,724][INFO ][Connect thread][ClustersWatcher] Topology 
watch process was suspended

[2020-05-21T04:00:03,729][INFO ][main][WebSocketRouter] Stopping Web Console 
Agent...



Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10



From: Evgenii Zhuravlev<mailto:e.zhuravlev...@gmail.com>
Sent: Wednesday, May 20, 2020 11:43 PM
To: user<mailto:user@ignite.apache.org>
Subject: Re: Unable to deploy Ignite Web Console in local



"External email. Open with Caution"

Hi,



The community is stopping maintenance for Ignite WebConsole: 
http://apache-ignite-developers.2346864.n4.nabble.com/RESULT-VOTE-Stop-Maintenance-of-Ignite-Web-Console-td47548.html.
 I recommend using GridGain Webconsole instead: 
https://www.gridgain.com/resources/download#webconsole. There is no need to 
build it, binaries are available.



Best Regards,

Evgenii



ср, 20 мая 2020 г. в 02:32, BEELA GAYATRI 
<beela.gaya...@tcs.com<mailto:beela.gaya...@tcs.com>>:

Hi,





   I am trying to deploy Ignite Web Console in my local machine and installed 
Mongo Dbversion 4.2 and NodeJs 14.0 versions, Ignite version used is  
apache-ignite-2.7.0.

However am unable to find paths($IGNITE_HOME/modules/web-console/backend and 
$IGNITE_HOME/modules/web-console/frontend)  in Ignite_home  and  unable to  
create ignite-web-agent-x.x.x.zip



I am getting below error while running below Command. Please suggest how to 
proceed further.

mvn clean package -pl :ignite-web-agent -am -P web-console -DskipTests=true



[cid:172334700d870ff2ace1]





https://apacheignite-tools.readme.io/docs/build-and-deploy





In order to deploy Ignite Web Console locally, you should install:

*         MongoDB (version >=3.2.x <=3.4.15) follow instructions from site 
http://docs.mongodb.org/manual/installation

*         NodeJS (version >=8.0.0) using installer from site 
https://nodejs.org/en/download/current for your OS.

Download the following dependencies:

*         For backend:
cd $IGNITE_HOME/modules/web-console/backend
npm install --no-optional

*         For frontend:
cd $IGNITE_HOME/modules/web-console/frontend
npm install --no-optional

Building Ignite Web Agent

To build Ignite Web 
Agent<https://apacheignite-tools.readme.io/docs/getting-started#section-ignite-web-agent>
 from sources, run the following command from the $IGNITE_HOME folder:
mvn clean package -pl :ignite-web-agent -am -P web-console -DskipTests=true

Once the build process is over, you can find ignite-web-agent-x.x.x.zip in:
$IGNITE_HOME/modules/web-console/web-agent/target





Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10



=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you


Reply via email to