Can't connect after upgrade to 21.1.20210521

[timnash]

Hello,

I just upgraded from 21.1.20210503 to 21.1.20210521 using the debian package. I’m running debian 10.

The command I ran was:
apt update
apt upgrade

Everything seemed to go well, but when I try connecting I get an nginx bad gateway error. When I run /etc/egroupware-docker/egroupware-logs.sh I see:

`2021/05/26 12:14:00 [error] 23#23: *11 connect() failed (111: Connection refused) while connecting to upstream, client: 172.18.0.1, server: _, request: "GET /egroupware/index.php HTTP/1.1", upstream: "fastcgi://172.18.0.2:9000", host: "egroupware.dmz.nicethreads.net"`

When I run ‘docker ps’ I get:

    CONTAINER ID        IMAGE                                     COMMAND                  CREATED             STATUS                  PORTS                      NAMES
    4e4d7bf330b0        nginx:stable-alpine                       "/docker-entrypoint."   24 minutes ago      Up 18 minutes           127.0.0.1:8080->80/tcp     egroupware-nginx
    7f1599ef93a3        phpswoole/swoole:4.6-php7.4-alpine        "docker-php-entrypoi"   30 minutes ago      Up 24 minutes                                      egroupware-push
    d18391122874        containrrr/watchtower:latest              "/watchtower --sched"   30 minutes ago      Up 24 minutes           8080/tcp                   egroupware-watchtower
    951f7051bc58        egroupware/egroupware:21.1                "/entrypoint.sh php-"   About an hour ago   Up Less than a second   9000/tcp                   egroupware
    653f48ce7aa8        mariadb:10.4                              "docker-entrypoint.s"   About an hour ago   Up Less than a second   3306/tcp                   egroupware-db
    5c9e9173811c        quay.io/egroupware/collabora-key:stable   "/bin/sh -c 'bash st"   11 days ago         Up Less than a second   127.0.0.1:9980->9980/tcp   collabora-key

It looks to me like there is a problem connecting to the docker that is supposed to run the PHP code, but I’m not sure where I need to be looking to fix this.

Please let me know if you have any ideas.

Thanks in advance!
-Tim

[RalfBecker]

Hi Tim,

try running ps axf on the host to see what the EGroupware container is currently “doing”.

This is how it should look:

 8847 ?        Sl     0:20  |   \_ docker-containerd-shim -namespace moby -workdir /var/lib/docker/containerd/daemon/io.containerd.runtime.v1.linux/moby/0a157076d94ac7a6bd9648da76996179fb7851816b01d879062b9ac925a00662 -address /var/run/docker/co
 8864 ?        Ss     0:56  |   |   \_ php-fpm: master process (/etc/php/8.0/fpm/php-fpm.conf)
 9244 ?        Ss     0:02  |   |       \_ /usr/sbin/cron
28356 ?        S      0:00  |   |       \_ php-fpm: pool www
28411 ?        S      0:00  |   |       \_ php-fpm: pool www
28521 ?        S      0:00  |   |       \_ php-fpm: pool www
28771 ?        S      0:01  |   |       \_ php-fpm: pool www
28828 ?        S      0:00  |   |       \_ php-fpm: pool www

If you see the entrypoint.sh running doc/rpm-build/post_install.php, you know it’s still running the update.

You can install strace and run strace -p <pid>, where <pid> is the process-ID of the lowest row from the post_install.php chain, so see the executed commands eg. DB queries.

Ralf

[timnash]

Hi Ralf,

Thanks for the quick response! I just got back in to the office and tried again and now it seems to be working, so it must have still been doing the upgrade in the background. Sorry about jumping the gun there, when it didn’t come back up after a couple minutes I panicked. I just ran ps axf and it’s looking like your example.

Thanks for the pointers on tracing this problem, I will keep them in mind if I run into something like this again.

Thanks!
Tim