You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Roman Guseinov <ro...@gromtech.ru> on 2018/06/01 04:28:43 UTC

Re: Agent not able to connect

Hi Humphrey,

1. I checked the details about ports. It was required to expose 3001 port
when back-end and front-end path were split into different docker images.
3001 was used on the back-end. Currently, we don't need to expose it [1].

2. Did you specify all env variables (they shouldn't be empty)? I don't see
that in your logs.

3. Is ignite node accessible inside docker container by
http://localhost:8080? I am not sure.

Could you try to connect web-agent container and check that Ignite node REST
URL is correct?

$ wget -qO- ${NODE_URI}/ignite?cmd=version

Best Regards,
Roman

[1] https://apacheignite-tools.readme.io/v2.5/docs/docker-deployment



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Agent not able to connect

Posted by Roman Guseinov <ro...@gromtech.ru>.
Hi Humphrey, 

Currently, front-end is included into back-end container as static files
(html, js). This way we don't have to open two ports. 80 is fully enough.
3001 isn't used now.

Regarding documentation, we don't have that one for web agent docker image
because it isn't public yet. I hope it will be published soon.

According to your logs, now the agent is able to connect to web console and
Ignite node as well.

Best Regards,
Roman



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Agent not able to connect

Posted by Humphrey <hm...@gmail.com>.
Hi Roman, I do understand the front-end part, I think that is the UI we get
when we connect to the web console when we go to http://webconsole and we
get the login page.

What I don't understand is the backend part, what does it do? I thought that
was where the agent is suppose to connect to (poort 3000 or 3001).

I didn't specify all environment settings, also these environments is also
missing in the documentation:



But now I did specify the driver folder as well as the node uri.

The node is accessible from http://localhost:8080 cause the agent is
deployed in the same docker container as the server node. I do get 1 cluster
connected in the web console UI.

[2018-06-01 11:08:40,676][INFO ][main][AgentLauncher] Starting Apache Ignite
Web Console Agent...
[2018-06-01 11:08:41,277][WARN ][main][AgentLauncher] Failed to find agent
property file: default.properties

Agent configuration:

User's security tokens : ****************2lKB
URI to Ignite node REST server: http://localhost:8080
URI to Ignite Console server : http://demo-webconsole
Path to agent property file : default.properties
Path to JDBC drivers folder : ./jdbc-drivers

Demo mode : enabled

[2018-06-01 11:08:41,873][INFO ][main][AgentLauncher] Connecting to:
http://demo-webconsole
[2018-06-01 11:08:42,499][INFO ][EventThread][AgentLauncher] Connection
established.
[2018-06-01 11:08:42,890][INFO ][EventThread][AgentLauncher] Authentication
success.
[2018-06-01 11:08:43,140][WARN ][pool-1-thread-1][RestExecutor] Failed
connect to cluster [url=http://localhost:8080, parameters={attr=true,
mtr=false, cmd=top}]
[2018-06-01 11:08:43,141][WARN ][pool-1-thread-1][RestExecutor] Failed
connect to cluster. Please ensure that nodes have [ignite-rest-http] module
in classpath (was copied from libs/optional to libs folder).
[2018-06-01 11:08:49,647][INFO ][pool-1-thread-1][RestExecutor] Connected to
cluster [url=http://localhost:8080]
[2018-06-01 11:08:49,690][INFO ][pool-1-thread-1][ClusterListener]
*Connection successfully established to cluster with nodes: [F2708F6F]*

And the command from the agent docker container:
wget -qO- ${NODE_URI}/ignite?cmd=version                              
*{"successStatus":0,"sessionToken":null,"error":null,"response":"2.5.0"}*

Humphrey




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/