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/
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
Okay I got it running, I think the agent is really using the 80 port instead
of the 3000 or 3001.
Can you explain what the 3000 or 3001 port is for?
[2018-05-31 12:27:44,882][INFO ][main][AgentLauncher] Starting Apache Ignite
Web Console Agent...
[2018-05-31 12:27:45,498][WARN
Hi Humphrey,
1. Could you try to specify `URI to Ignite Console server` without port
(just http://172.17.0.3)?
2. If you run web agent inside docker container you won't be able to connect
a cluster node using http://localhost:8080
3. If you use docker deployment for web console, please make
Let me put the picture I have in my head here.
Pod 1 < ip = 12345 >:
- container 1: Ignite Server node
- container 2: Web Agent
Pod 2 < ip = 67890 >:
- container 1: Web Console Standalone
I assume that every node would need to have an Agent next to it to
communicate with the WebConsole.
When I
Roman — can you advise?
> On 31 May 2018, at 13:32, Humphrey wrote:
>
> I've done the steps you noted but it seems to do the same as the other 2.4
> version.
>
> web-console-standalone:
>
> 09:55:33 0|index | All Ignite migrations finished successfully.
> 09:55:33 0|index | Running Ignite
Hi Humphrey,
The default frontend port is 80 and for backend is 3000.
So for web-agent to connect to web-console, you need to provide
:.
I think, you are using backend port 3000.
Regards,
Vishwas
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
I've done the steps you noted but it seems to do the same as the other 2.4
version.
web-console-standalone:
09:55:33 0|index | All Ignite migrations finished successfully.
09:55:33 0|index | Running Ignite Modules migrations...
09:55:33 0|index | There are no Ignite Modules migrations to run.
This image is delivered within the frames of Apache Ignite Nightly Builds only
for now.
To pull the image from the link I’ve provided, download corresponding tar.gz
archive, gunzip it and use ‘docker load < web-agent-*-docker-image.tar’ to add
it to local registry.
> On 31 May 2018, at
How do I do a pull from that repository? Currently my docker is only looking
at dockerhub.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Humphrey,
AFAIK, Web Console Standalone is deliberately designed to have
self-contained Web Agent.
Can you try separate Web Console docker image from experimental nightly
build? [1]
[1]
Looks like it can't connect to the webconsole as the webconsole is only
listening to localhost:
Start listening on 127.0.0.1:3000
How can we change this so that the agents (which have different IP) in the
cluster are able to communicate with the webconsole?
--
Sent from:
Web agent I used was apacheignite/web-console-standalone from docker hub.
Am able to login and see the corresponding token used in the agent from the
profile.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
13 matches
Mail list logo
