After unplanned reboot GL3 doesn't come back to life

[clementgineste]

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 :tumbler_glass:

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]

No one experimented the same issue ?

[jakes670]

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

[pdelboca]

I have the same issue. An small outage in Hetzner stopped our service. Once the VPS was running trying to navigate to our instance was throwing 502 Bad Gateway.

I fixed it by stopping, finding the file and removing it manually like @jakes670 suggested.

Note: The initial installation was following the Official BBB documentation: https://docs.bigbluebutton.org/greenlight/v3/install/