Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After unplanned reboot GL3 doesn't come back to life #5867

Open
clementgineste opened this issue Jun 26, 2024 · 2 comments
Open

After unplanned reboot GL3 doesn't come back to life #5867

clementgineste opened this issue Jun 26, 2024 · 2 comments

Comments

@clementgineste
Copy link

Installed through bbb-install.sh within BBB version 2.7.6 (584). GL3 Docker version.
GL3, version 3.3.1

After unplanned reboot GL3 could encounter issue with PID file. See logs

greenlight-v3  | A server is already running. Check /usr/src/app/tmp/pids/server.pid.

Then container restart indefinitly.

Solution:

root@bbb1:~/greenlight-v3# docker compose exec -it greenlight-v3 rm /usr/src/app/tmp/pids/server.pid
WARN[0000] /root/greenlight-v3/docker-compose.yml: `version` is obsolete 
Error response from daemon: Container ead7c306ba9cda180d7b82675a5d8a8c290ee5fc5cbf0f1853450728f1c8d16a is restarting, wait until the container is running

We can do a while true or restart within compose and run the rm

root@bbb1:~/greenlight-v3# docker compose start greenlight-v3 
WARN[0000] /root/greenlight-v3/docker-compose.yml: `version` is obsolete 
[+] Running 1/1
 ✔ Container greenlight-v3  Started                                                                                                                                                                                                      0.2s 
root@bbb1:~/greenlight-v3# docker compose exec -it greenlight-v3 rm /usr/src/app/tmp/pids/server.pid
WARN[0000] /root/greenlight-v3/docker-compose.yml: `version` is obsolete 

Yes "unplanned reboot" could include crash 🥃

Maybe we could add some hints in a troubleshooting page for GL3 or find a fix to remove the PID file after a reboot.

@clementgineste
Copy link
Author

No one experimented the same issue ?

@jakes670
Copy link

I had the same issue, here is my fix

root@bigbluebutton:~# docker stop greenlight-v3
greenlight-v3

root@bigbluebutton:~# find / -name server.pid
/var/lib/docker/overlay2/d4e40e61020d45e8343aa3d87b38f9d9e225d5f449185afe136284178f11fe78/diff/usr/src/app/tmp/pids/server.pid

root@bigbluebutton:~# rm /var/lib/docker/overlay2/d4e40e61020d45e8343aa3d87b38f9d9e225d5f449185afe136284178f11fe78/diff/usr/src/app/tmp/pids/server.pid

root@bigbluebutton:~# docker start greenlight-v3

Working

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants