503 service unavailable on fresh install
fenix011 opened this issue · comments
Hi Jibon !
Just installed super PlugNmeet in 4 Gb RAM - 2 vCPU VPS. And ... we'll, when trying to browse it here:
503 Service Unavailable
No server is available to handle this request.
what are we missing here ? how to debug this issue ?
thanks, thanks, thanks
Well, just found that the service was KO :
root@localhost:~# systemctl status plugnmeet.service
● plugnmeet.service - plugNmeet service
Loaded: loaded (/etc/systemd/system/plugnmeet.service; enabled; vendor preset: enabled)
Active: inactive (dead)
root@localhost:~# systemctl restart plugnmeet.service
root@localhost:~# systemctl status plugnmeet.service
● plugnmeet.service - plugNmeet service
Loaded: loaded (/etc/systemd/system/plugnmeet.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2023-01-28 23:47:58 UTC; 21s ago
Process: 2204386 ExecStartPre=/usr/bin/docker-compose down (code=exited, status=0/SUCCESS)
Main PID: 2204528 (docker-compose)
Tasks: 8 (limit: 4675)
Memory: 28.5M
CPU: 1.706s
CGroup: /system.slice/plugnmeet.service
└─2204528 /usr/bin/python3 /usr/bin/docker-compose up
Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] InnoDB: Loadin>Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] Plugin 'FEEDBA>Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Warning] You need to>Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] InnoDB: Buffer>Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] Server socket >Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] Server socket >Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:10 0 [Note] mariadbd: read>Jan 28 23:48:10 localhost plugNmeet[2204528]: db_1 | Version: '10.10.2-MariaDB-1:10.10.2+maria~u>Jan 28 23:48:14 localhost plugNmeet[2204528]: db_1 | 2023-01-28 23:48:14 3 [Warning] Aborted con>Jan 28 23:48:14 localhost plugNmeet[2204528]: plugnmeet_plugnmeet_1 exited with code 1
after a 'systemctl restart' ... the service is now reported as 'Active' by systemD.
Yet, from the user's perspective it remains KO
503 Service Unavailable
No server is available to handle this request.
what are we missing here ?
thanks, thanks, thanks
Installation wasn't successful. Did you get any error message during installation?
Get more details log by:
journalctl -u plugnmeet -n 300 --no-pager
&
cat /opt/plugNmeet/log/plugNmeet.log
plugNmeet is trying to connect to DB using IPV6. So, you can do like this:
Edit:
nano /opt/plugNmeet/docker-compose.yaml
& add another environment
variable under db
:
MYSQL_ROOT_HOST: '%'
So, it will be looks like:
environment:
MYSQL_ROOT_PASSWORD: YOUR_PASS_DON'T_NEED_TO_CHANGE
MYSQL_ROOT_HOST: '%'
You'll also need to delete this directory: /opt/plugNmeet/mariadb-data
Later restart plugNmeet.
Hi Jibon !... did the change on the database parameters, as per your suggestion.
root@localhost:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
96b76af2e050 mynaparrot/plugnmeet-server "plugnmeet-server --…" 2 minutes ago Restarting (1) 11 seconds ago plugnmeet_plugnmeet_1
237bf73a1581 mynaparrot/plugnmeet-etherpad "docker-entrypoint.s…" 2 minutes ago Up 2 minutes (healthy) plugnmeet_etherpad_1
5973e16d2a35 livekit/livekit-server "/livekit-server --c…" 2 minutes ago Up 2 minutes (healthy) plugnmeet_livekit_1
5ed56ba61e10 redis:6 "docker-entrypoint.s…" 2 minutes ago Up 2 minutes (healthy) plugnmeet_redis_1
905cc1c4a4bb mariadb:10.10 "docker-entrypoint.s…" 2 minutes ago Up 2 seconds (health: starting) plugnmeet_db_1
root@localhost:~# history 6
31 rm -rf /opt/plugNmeet/mariadb-data
32 systemctl restart plugnmeet.service
33 systemctl status plugnmeet.service
34 systemctl status plugnmeet.service
35 docker ps
36 history 6
root@localhost:~#
No joy (until now) .
What are we missing here ?
thanks, thanks, thanks
Need to see log again to find the problem. You can send me an email to jibon[@]mynaparrot.com with server's details. I can check for you.