Installation runs forever
themask96 opened this issue · comments
The installation of plugnmeet following the instruction keeps on running forever. After fixing initial issues with the certificate, the installation proces keeps on running. I've let it running for 3 days, but nothing changes.
It seems after some time it doesn't do anything anymore except add more dots to the screen. I didn't see any error message.
Here a screenshot after 2 hours:
That's long running script indicating that services wasn't started properly & keep hang. You'll require to debug to know the reason. You can check logs
cd /opt/plugNmeet
docker-compose logscan manually down:
docker-compose down& start again
docker-compose upif none works then try to delete /opt/plugNmeet directory & run installer again.
rm -rf /opt/plugNmeet
docker rm -vf $(docker ps -aq)
docker rmi -f $(docker images -aq)
docker system prune -a --volumestnx for your reply. I've tried all of the above but couldn't get it to work.
So I setup a complete new server and installed everything again and it worked. Probably something got broken somehow on the older server but it wasn't clear from the logs what caused it.
Same issue here ! ... @jibon57 .
Waited for hours... , seeing the dots passing by in the screen 🤣 with no luck
Suddenly i decided to restart the server computer and while trying to take the plugnmeet server control back, i failed, as long as ? :
Active: active (running) since Fri 2023-01-20 13:27:20 UTC; 20min ago
Process: 822 ExecStartPre=/usr/bin/docker-compose down (code=exited, status=0/SUCCESS)
Main PID: 823 (docker-compose)
Tasks: 8 (limit: 1129)
Memory: 42.2M
CPU: 7.387s
CGroup: /system.slice/plugnmeet.service
└─823 /usr/bin/python3 /usr/bin/docker-compose up
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] InnoDB: log sequence number 46786; transaction id 14
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] Plugin 'FEEDBACK' is disabled.
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seco>
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] Server socket created on IP: '0.0.0.0'.
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] Server socket created on IP: '::'.
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] InnoDB: Buffer pool(s) load completed at 230120 13:48:03
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | 2023-01-20 13:48:03 0 [Note] mariadbd: ready for connections.
Jan 20 13:48:03 localhost plugNmeet[823]: db_1 | Version: '10.10.2-MariaDB-1:10.10.2+maria~ubu2204' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org bi>
root@localhost:~# systemctl restart plugnmeet.service
root@localhost:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bcab92267b3f mynaparrot/plugnmeet-server "plugnmeet-server --…" 4 seconds ago Restarting (1) Less than a second ago plugnmeet_plugnmeet_1
378dc5d7bec9 mynaparrot/plugnmeet-etherpad "docker-entrypoint.s…" 5 seconds ago Up 4 seconds (health: starting) plugnmeet_etherpad_1
4dc9629ac80f livekit/livekit-server "/livekit-server --c…" 5 seconds ago Up 4 seconds (health: starting) plugnmeet_livekit_1
784c064f59a1 mariadb:10.10 "docker-entrypoint.s…" 5 seconds ago Up 4 seconds (health: starting) plugnmeet_db_1
0d2b29abfd5a redis:6 "docker-entrypoint.s…" 5 seconds ago Up 4 seconds (health: starting) plugnmeet_redis_1
root@localhost:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bcab92267b3f mynaparrot/plugnmeet-server "plugnmeet-server --…" 8 seconds ago Restarting (1) 3 seconds ago plugnmeet_plugnmeet_1
378dc5d7bec9 mynaparrot/plugnmeet-etherpad "docker-entrypoint.s…" 9 seconds ago Up 8 seconds (health: starting) plugnmeet_etherpad_1
4dc9629ac80f livekit/livekit-server "/livekit-server --c…" 9 seconds ago Up 8 seconds (health: starting) plugnmeet_livekit_1
784c064f59a1 mariadb:10.10 "docker-entrypoint.s…" 9 seconds ago Up 8 seconds (health: starting) plugnmeet_db_1
0d2b29abfd5a redis:6 "docker-entrypoint.s…" 9 seconds ago Up 8 seconds (health: starting) plugnmeet_redis_1
root@localhost:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
bcab92267b3f mynaparrot/plugnmeet-server "plugnmeet-server --…" 12 seconds ago Restarting (1) 3 seconds ago plugnmeet_plugnmeet_1
378dc5d7bec9 mynaparrot/plugnmeet-etherpad "docker-entrypoint.s…" 13 seconds ago Up 12 seconds (health: starting) plugnmeet_etherpad_1
4dc9629ac80f livekit/livekit-server "/livekit-server --c…" 13 seconds ago Up 12 seconds (health: starting) plugnmeet_livekit_1
784c064f59a1 mariadb:10.10 "docker-entrypoint.s…" 13 seconds ago Up 1 second (health: starting) plugnmeet_db_1
0d2b29abfd5a redis:6 "docker-entrypoint.s…" 13 seconds ago Up 12 seconds (healthy) plugnmeet_redis_1
root@localhost:~#
uh
It looks like the plugnmeet-server docker container is not able to start but others (plugnmeet-etherpad , livekit-server, redis and mariadb ) do ?
thanks for your support !
:-)
Can you get the log of mynaparrot/plugnmeet-server?
docker logs bcab92267b3f -n 300
First use docker ps to get id of the server later use docker logs CONTAINER ID -n 300
I did that, but no logs are shown.
Umh...Maybe there's an issue with the overall installation process while not meeting to the minimum harwdare requirements kind of ? (using a 1 GB RAM - 1 vCPU server here ) Dunno...
The installation wasn't successful that for sure. You can try to reinstall server with little bit more RAM e.g 4GB & CPU 2. Also you can check logs by:
cat /opt/plugNmeet/log/plugNmeet.log
Ah..Why not ? I'm gonna re-install super PlugNmeet in 8 Gb RAM - 4vCPU baremetal server. And ... we'll see how it goes ? Thanks, thanks, thanks