extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-22 07:53:27 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Update recommendations and troubleshooting (markdown)

Ralf Becker 2019-09-15 14:05:47 +02:00
parent 86400837a3
commit 039b5d1b3d
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Update-recommendations-and-troubleshooting.md

@ -63,7 +63,9 @@ egroupware | [06-Sep-2019 10:41:13] NOTICE: ready to handle connections
egroupware | [06-Sep-2019 10:41:13] NOTICE: systemd monitor interval set to 10000ms
egroupware-watchtower | time="2019-09-15T07:11:12Z" level=info msg="Waiting for running update to be finished..."
```
If you don't see the line ```fpm is running, pid 1``` you will will only get a 503 from Nginx, when you try to connect to EGroupware. The startup of the egroupware container might take a little longer then you expect, as it has to copy the EGroupware sources into a volume which is shared with Nginx, so the webserver can deliver the static content (CSS, JavaScript, images, ...).
If you don't see the line ```fpm is running, pid 1``` you will will only get a 502 Bad Gateway from Nginx, when you try to connect to EGroupware. The startup of the egroupware container might take a little longer then you expect, as it has to copy the EGroupware sources into a volume which is shared with Nginx, so the webserver can deliver the static content (CSS, JavaScript, images, ...).
If egroupware container alone was restarted without Nginx, Nginx still uses the old IP of egroupware and you get a 502 Bad Gateway. Always restart both: ```(cd /etc/egroupware-docker; docker-compose restart)```
3. Try to connect to EGroupware container without using the proxy running on the host webserver. We use a tool called ```curl``` for these kind of checks. Install it with ```apt install -y curl``` (or yum or zypper instead of apt depending on your distribution):
```