extern/egroupware
1
0
Fork 1
mirror of https://github.com/EGroupware/egroupware.git synced 2024-11-25 09:23:38 +01:00
Code Issues Packages Projects Releases Wiki Activity

added some more trouble-shooting and the available support options

Ralf Becker 2019-09-15 09:37:20 +02:00
parent 9ff3468c51
commit 22e3a72165
1 changed files with 85 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

84
Update-recommendations-and-troubleshooting.md

@ -33,3 +33,87 @@ While an update of a PostgreSQL instance works similar to MariaDB/MySQL, a new i
```
2. start the containers as usual with: ```docker-compose up -d```
3. Go to http://example.org/egroupware/setup/ and do a manual installation
> Keep in mind, that you can NOT use ```localhost``` to address a service eg. PostgreSQL inside the container, as it does NOT refer to the host, but the container itself. You have to use the IP address of the host or the docker0 bridge AND make sure the service is not just bound to localhost!
# Trouble-shooting a not working installation after the update
What to do if you can not access EGroupware after the update:
1. run ```docker ps``` to check all containers are running:
```
root@debian:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
9f9ad54d14b5 nginx:stable-alpine "nginx -g 'daemon of…" 8 days ago Up 3 minutes 127.0.0.1:8080->80/tcp egroupware-nginx
d439a0f65fc8 download.egroupware.org/egroupware/epl:latest "/entrypoint.sh php-…" 8 days ago Up 3 minutes 9000/tcp egroupware
5218213c1d48 containrrr/watchtower "/watchtower --sched…" 8 days ago Up 3 minutes egroupware-watchtower
b705d3fb27f4 rocketchat/rocket.chat:latest "bash -c 'for i in `…" 3 weeks ago Up 3 minutes 127.0.0.1:3000->3000/tcp rocketchat
f512abc0d03d mongo:4.0 "docker-entrypoint.s…" 3 weeks ago Up 3 minutes 27017/tcp rocketchat-mongo
b8e3dbdf4541 quay.io/egroupware/collabora-key:stable "/bin/sh -c 'bash st…" 3 weeks ago Up 3 minutes 127.0.0.1:9980->9980/tcp collabora-key
```
(If you only installed EGroupware and not Collabora and Rocket.Chat, you should have only the first 3 containers with names starting with ```egroupware```.
2. Look at the logs:
```
cd /etc/egroupware-docker
docker-compose logs -f
root@debian:/etc/egroupware-docker# docker-compose logs
Attaching to egroupware-nginx, egroupware, egroupware-watchtower
egroupware | Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
egroupware |
egroupware | EGroupware successful updated
egroupware | * Starting periodic command scheduler cron
egroupware | ...done.
egroupware |
egroupware | EGroupware successful updated
egroupware |
egroupware | EGroupware successful updated
egroupware |
egroupware | EGroupware successful updated
egroupware | [06-Sep-2019 10:41:13] NOTICE: fpm is running, pid 1
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 with is shared with Nginx, so the webserver can deliver static files (CSS, JavaScript, images, ...).
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):
```
root@debian:/etc/egroupware-docker# curl -i http://localhost:8080/egroupware/
HTTP/1.1 302 Found
Server: nginx/1.16.1
Date: Sun, 15 Sep 2019 07:19:10 GMT
Content-Type: text/html; charset=UTF-8
Transfer-Encoding: chunked
Connection: keep-alive
Cache-Control: no-store, no-cache, must-revalidate
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
Location: /egroupware/login.php?phpgw_forward=%252Findex.php
```
If you see the above EGroupware containers are running, it is installed and has a working database connection.
4. Try accessing EGroupware through the host webserver / proxy possibly with https, if you configured that already:
```
RalfsMac:epl-19.1 ralf$ curl -i https://testbox9.egroupware.org/egroupware/
HTTP/1.1 302 Found
Date: Sun, 15 Sep 2019 07:26:42 GMT
Server: nginx/1.16.1
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Pragma: no-cache
Location: /egroupware/login.php?phpgw_forward=%252Findex.php
Transfer-Encoding: chunked
```
If you can see the correct output of 3., but not the above one, something is wrong with your proxy configuration on the host.
# If you can not figure it out by yourself
We offer the following support options:
a) [payed professional support through EGroupware GmbH](https://www.egroupware.org/en/egroupware-support/), the developer of EGroupware
b) [our special update packages](https://www.egroupware.org/en/migration-update-packages/) created to get you hassle-free to the latest version
c) [our forum help.egroupware.org](https://help.egroupware.org) were users help other users and our community manager and developers answer questions