After following the Getting started guide, exo container do not start correctly

[rdenarie]

I continue a discussion started by email :

After following the instructions, I always get that it exits with a code 1. Can you help point out what would be the issue. I am using an ubuntu Server

22.04 LTS with docker and docker-compose installed.

[rdenarie]

I asked for exo server logs :
docker logs exo_home_exo_1
results are :
exo installation error.txt

I asked for database server logs :
docker logs exo_home_mysql_1
Results :
error 2.txt

[rdenarie]

Can you try to complety stop all containers wit this command
docker-compose -f docker-compose.yml down

And then restart it with
docker-compose -f docker-compose.yml up

If it doesnt work, we will try to update the docker-compose configuration.

[BivanOdima]

1. Result of :
   sudo apt-get install mysql-client

ubuntu@ubuntu:~$ sudo apt-get install mysql-client
[sudo] password for ubuntu:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
mysql-client is already the newest version (8.0.30-0ubuntu0.22.04.1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

2. Result of:
   docker inspect exo_home_mysql_1

"IPAddress": "172.19.0.3"

3. Reuslt of:

mysql -u exo -p -h 172.19.0.3

Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8
Server version: 8.0.28 MySQL Community Server - GPL

Copyright (c) 2000, 2022, Oracle and/or its affiliates.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql>

I have realized the step.

[rdenarie]

Hello,
So the mysql server is available on the port 3306.
We will now check that exo and mysql are correctly on the same network.

Can you pass these commands :
docker inspect exo_home_exo_1 | grep IPAddress
docker inspect exo_home_mysql_1 | grep IPAddress

In addition, can you provide docker and docker-compose version :
docker --version
docker-compose --version

[BivanOdima]

1. Result of:

ubuntu@ubuntu:~$ sudo docker inspect exo_home_exo_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "",

2.Result of

ubuntu@ubuntu:~$ sudo docker inspect exo_home_mysql_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.19.0.3",

3. Result of

ubuntu@ubuntu:~$ docker --version
Docker version 20.10.18, build b40c2f6

4.Result of

ubuntu@ubuntu:$ docker-compose --version
docker-compose version 1.29.2, build 5becea4c
ubuntu@ubuntu:$

[BivanOdima]

It looks like the exo_home_exo_1 container doesn't have an IP Address

[rdenarie]

It is because the container is stopped.
Can you redo the command during the startup (before the container stops) ?

[BivanOdima]

1. Result of:

ubuntu@ubuntu:~$ sudo docker inspect exo_home_exo_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "",

2.Result of

ubuntu@ubuntu:~$ sudo docker inspect exo_home_mysql_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.19.0.3",

3. Result of

ubuntu@ubuntu:~$ docker --version
Docker version 20.10.18, build b40c2f6

4.Result of

ubuntu@ubuntu:$ docker-compose --version
docker-compose version 1.29.2, build 5becea4c
ubuntu@ubuntu:$

[rdenarie]

For 1), as you exo container is stopped we dont see his ipAdress.

Can you try to down all containers
docker-compose -f docker-compose.yml down

And then restart it with
docker-compose -f docker-compose.yml up

Then during the restart, recheck the both ipAdress (before exo container stops)

sudo docker inspect exo_home_exo_1 | grep IPAddress
sudo docker inspect exo_home_mysql_1 | grep IPAddress

[BivanOdima]

1. When the exo_home container is still up. Result is

ubuntu@ubuntu:~$ sudo docker inspect exo_home_exo_1 | grep IPAddress
[sudo] password for ubuntu:
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.19.0.5",

2. Result of

ubuntu@ubuntu:$ sudo docker inspect exo_home_mysql_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.19.0.3",
ubuntu@ubuntu:$

[rdenarie]

I quite puzzled about your problem.
The 2 container seems in the same network, but are unable to discuss.

So, I propose to change the docker-compose file to expose the port 3306 of the mysql server on your local machine, and configure exo to join directly your local machine instead of directly the mysql container.

For that, firsly, shutdown all the container :
docker-compose -f docker-compose.yml down

Then, find your local ip (use command ifconfig). On my side, it is 192.168.0.2, so I'll take that as example. Change with your real IP
In docker-compose.yml, change line
EXO_DB_HOST: mysql
to
EXO_DB_HOST: 192.168.0.2
Then, in the mysql part, add these lines :

ports:
  - "3306:3306"

mysql part should be :

mysql:
image: mysql:8.0.28
environment:
MYSQL_ROOT_PASSWORD: my-super-secret-pw
MYSQL_DATABASE: exo
MYSQL_USER: exo
MYSQL_PASSWORD: my-secret-pw
volumes:
- mysql_data:/var/lib/mysql
ports:
- "3306:3306"

Save the docker file.

We will also drop all volumes already created. Find them with
docker volume ls |grep exo_home
Then delete it :

docker volume rm exo_home_exo_data
docker volume rm exo_home_exo_logs
docker volume rm exo_home_mongo_data
docker volume rm exo_home_mysql_data
docker volume rm exo_home_search_data

Finally, restart all containers :
docker-compose -f docker-compose.yml up

After that, if it still not working, can you provide me the docker-compose.yml file, and all the starting log ?

Thanks

[BivanOdima]

Hello,

After exposing mysql port and running docker-compose -f docker-compose.yml up
It brought a mongo db error. I exposed mongo db too and changed the exo_mongo_host to my IP. It was able to connect to both Mongo and MySql.
However its now unable to connect to the Elastic Search Container Port.

Looks like we also have to expose that port.

I have attached a start up log
startup log exo.txt
startup log exo.txt

[rdenarie]

You're right, I think we should expose es port.
For that, modify the docker-compose.yml by changing

  EXO_ES_HOST: es

to

  EXO_ES_HOST: 192.168.0.2

an in es part, add ports to expose :

ports:
  - "9200:9200"
  - "9300:9300"

Then, restart your containers with

docker-compose -f docker-compose.yml down
docker-compose -f docker-compose.yml up

[BivanOdima]

It looks like all containers have started as shown below.

ubuntu@ubuntu:~/EXO_HOME$ sudo docker ps
[sudo] password for ubuntu:

CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
15246881b77a exoplatform/elasticsearch:2.0.3 "/bin/tini -- /usr/l…" 42 minutes ago Up 42 minutes 0.0.0.0:9200->9200/tcp, :::9200->9200/tcp, 0.0.0.0:9300->9300/tcp, :::9300->9300/tcp exo_home_es_1
f4c5afcd513a exoplatform/nginx:1.21.0 "/usr/bin/supervisord" 54 minutes ago Up 42 minutes 81/tcp, 0.0.0.0:80->80/tcp, :::80->80/tcp, 443/tcp exo_home_web_1
49a56f5c55f0 exoplatform/exo-community:6.3 "/usr/local/bin/tini…" 54 minutes ago Up 42 minutes (healthy) 0.0.0.0:8080->8080/tcp, :::8080->8080/tcp exo_home_exo_1
68711671d713 mongo:4.4 "docker-entrypoint.s…" 54 minutes ago Up 42 minutes 0.0.0.0:27017->27017/tcp, :::27017->27017/tcp mongo
10bbd994b9a0 mysql:8.0.28 "docker-entrypoint.s…" 54 minutes ago Up 42 minutes 0.0.0.0:3306->3306/tcp, :::3306->3306/tcp, 33060/tcp exo_home_mysql_1

However, I am trying to access it using the server ip from the browser but I cant http://192.168.0.150. The Server ip is 192.168.0.150 for my Ubuntu server 22.04 LTS with no GUI.

Running the below ip of the exo_home_exo_1 and exo_home_mysql_1

ubuntu@ubuntu:/EXO_HOME$ sudo docker inspect exo_home_exo_1 | grep IPAddress
[sudo] password for ubuntu:
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.21.0.5",
ubuntu@ubuntu:/EXO_HOME$ sudo docker inspect exo_home_mysql_1 | grep IPAddress
"SecondaryIPAddresses": null,
"IPAddress": "",
"IPAddress": "172.21.0.2",

[BivanOdima]

The following is the start up log.
log.txt

[rdenarie]

Can you try to access on http://192.168.0.150:8080 ?
It will bypass the frontend nginx.

There is a network issue with the docker, and I dont understand why for now. So I guess nginx can not communicate with eXo like eXo cannot communicate directly with mongo or es or mysql.

[rdenarie]

Great news !

Thanks for your feedback.

[PIAODEV]

Hello, I tried my best to follow these responses, but my installation is still not working.

When accessing the localhost, I am only seeing the "Welcome to nginx!" screen.

I have uploaded my cmd lines.
cmd.txt

Also, I modified our docker-compose.yml file to mimic BivanOdima's. Do you have any suggestions?

[PIAODEV]

I think the issue somehow has to do with this:

The web-1 seems to bypass the EXO Platform and direct straight to nginx:1.21.0 - could it be a folder issue by any chance?

[rdenarie]

Hello @PIAODEV

Can you start a new discussion to describe your problem ?
In it, can you provided the modified docker compose ? and the startup logs ?

Thanks a lot.

[PIAODEV]

Thank you @rdenarie - please see this discussion. I appreciate you help.

[BivanOdima]

I have Bivan Odima (ICT)​​ Systems Administrator Madison Group Limited +254 020 2864000, +254 709 922 000 www.madison.co.ke<http://www.madison.co.ke/> [Facebook]<https://www.facebook.com/MadisonGroupKenya/> [LinkedIn]<https://www.linkedin.com/company/madison-group-ltd/> [Twitter]<https://twitter.com/MadisonGroupKe> [YouTube]<https://www.youtube.com/user/MadisonInsurance> [Instagram]<https://www.instagram.com/madisongroup_ke/> ***@***.*** From: Romain Dénarié ***@***.***> Sent: Tuesday, 20 September 2022 16:58 To: exoplatform/exo-community ***@***.***> Cc: Bivan Odima (ICT) ***@***.***>; Manual ***@***.***> Subject: Re: [exoplatform/exo-community] After following the Getting started guide, exo container do not start correctly (Discussion #5) It is because the container is stopped. Can you redo the command during the startup (before the container stops) ? — Reply to this email directly, view it on GitHub<https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fexoplatform%2fexo%2dcommunity%2fdiscussions%2f5%23discussioncomment%2d3690790&umid=99e17e33-84dc-417d-ac9b-8746d00d210c&auth=2bac1cb4d351ee871b02d99b7034420f7c9fcf0e-486f33d60d0ce8eac7965572688a9a30468015f3>, or unsubscribe<https://cas5-0-urlprotect.trendmicro.com:443/wis/clicktime/v1/query?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe%2dauth%2fA3FT32QDQXV3YY44XJE4CSLV7G7FLANCNFSM6AAAAAAQQ3LISI&umid=99e17e33-84dc-417d-ac9b-8746d00d210c&auth=2bac1cb4d351ee871b02d99b7034420f7c9fcf0e-9cddfa43c1c4cfb4fe7d9f531d045a647a60a806>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>>