Xibo docker upgrade from 2.x to 3.0.3

Hi Another Newbie has an issue. Running on Linux Mint was running CMS 2.3.10 without issue. Followed the upgrade process and have this error at the end of the process:

cms-web_1 | crontab: can’t open ‘/etc/crontabs/apache’: Permission denied
cms-web_1 | Starting cron
cms-web_1 | Starting webserver
cms-web_1 | AH00558: httpd: Could not reliably determine the server’s fully qualified domain name, using Set the ‘ServerName’ directive globally to suppress this message

The CMS is working whilst the terminal window is open but as the process never finishes I cannot shut the terminal down. Whilst Terminal Open the CMS seems to work fine and all previous data has been updated. CTRL+C shuts down the operation but also shuts down the Docker session and the CMS is hence unavailable.

How do I resolve so I can close the Terminal?

Just ran updates including docker. This seemed to stop and restart the docker and The terminal came back to normal checked and the CMS is live. Just had some output following the shutdown. Anyway seems OK now odd.

cms-db_1 | 2021-11-05T13:31:48.404245Z 0 [Note] mysqld: Shutdown complete
cms-db_1 |
xibo_cms-memcached_1 exited with code 0
xibo_cms-xmr_1 exited with code 137
xibo_cms-quickchart_1 exited with code 137
xibo_cms-web_1 exited with code 137
xibo_cms-db_1 exited with code 137

PS shows the container running now.

opt/xibo$ sudo docker ps
6353d3d7a29d xibosignage/xibo-cms:release-3.0.3 “/entrypoint.sh” 2 hours ago Up 6 minutes>80/tcp, :::80->80/tcp xibo_cms-web_1
6991b2659976 mysql:5.7 “docker-entrypoint.s…” 2 hours ago Up 6 minutes 3306/tcp, 33060/tcp xibo_cms-db_1
065664f1b589 ianw/quickchart “node --max-http-hea…” 2 hours ago Up 6 minutes 3400/tcp xibo_cms-quickchart_1
4b9ac2d070a0 xibosignage/xibo-xmr:release-0.8 “/entrypoint.sh” 2 hours ago Up 6 minutes>9505/tcp, :::9505->9505/tcp, 50001/tcp xibo_cms-xmr_1
f4a46268d9b9 memcached:alpine “docker-entrypoint.s…” 2 hours ago Up 6 minutes 11211/tcp xibo_cms-memcached_1

I think you just missed the -d from the docker-compose up -d command. -d means to run in the background.


I think you are right. The restart must have auto started the container. Thanks for the heads up.

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.