Bad Gateway

[hbsimon]

Hi,

I upgraded from egroupware-epl-17.1.20190808-1.3 to the latest version, from SUSE repository using the zypper update command. After the upgrade I encounteed two issues.

1. Users can no more access the mailserver.
2. After a reboot no web logon, it fails with following message:
   Bad Gateway!

The proxy server received an invalid response from an upstream server.

The proxy server could not handle the request

Reason: Error reading from remote server

If you think this is a server error, please contact the webmaster.
Error 502

The OS is openSUSE Leap 15.2
WEB Server: Apache 2.4.43 with PHP 7.4.6 and OpenSSL 1.1.1d
Database mariadb 10.4.14
Mail Server : Postfix and Dovecot 2.3
What logs I need to check and provide to solve the gateway issue first?
Output of:
docker-compose logs -f egroupware
Attaching to egroupware
egroupware | Fix APC(u) configuration, set apc.shm_size=128M in /etc/php/7.3/cli/conf.d/20-apcu.ini
egroupware | PHP Deprecated: stripos(): Non-string needles will be interpreted as strings in the future. Use an explicit chr() call to preserve the current behavior in /usr/share/egroupware/api/src/Storage.php on line 591
egroupware |
egroupware | EGroupware successful updated
egroupware | * Starting periodic command scheduler cron
egroupware | …done.
egroupware | [31-Aug-2020 13:04:29] NOTICE: fpm is running, pid 1
egroupware | [31-Aug-2020 13:04:29] NOTICE: ready to handle connections
egroupware | [31-Aug-2020 13:04:29] NOTICE: systemd monitor interval set to 10000ms
egroupware | [31-Aug-2020 13:09:19] NOTICE: Terminating …
egroupware | [31-Aug-2020 13:09:19] NOTICE: exiting, bye-bye!
egroupware |
egroupware | EGroupware successful updated
egroupware | * Starting periodic command scheduler cron
egroupware | …done.
egroupware | [31-Aug-2020 13:20:05] NOTICE: fpm is running, pid 1
egroupware | [31-Aug-2020 13:20:05] NOTICE: ready to handle connections
egroupware | [31-Aug-2020 13:20:05] NOTICE: systemd monitor interval set to 10000ms

Thanks and Regards,
Horst

[StefanU]

Hi Horst.

What exactly is “your” latest version?
We had recently fixed a bug that could lead to a 502.

You update from 17.1 to 20.1. This includes a technology change:
Docker (in EGroupware 19.1)?
Hope you know that(?)…

Stefan

[hbsimon]

Hi Stefan,

I know that since 19.1 it is using Docker. The version it updated too is 20.1.20200818-lp152.5.1 and the install log showed following;
EGroupware successful updated

EGroupware successful updated

EGroupware successful updated

After the upgrade I could connect to the setup and user login screens and successful logon, but not connect to the mail server, all the other connection to the database where fine.
After I did the reboot no I received the gateway error.

Regards,
Horst

[RalfBecker]

After the upgrade I could connect to the setup and user login screens and successful logon, but not connect to the mail server, all the other connection to the database where fine.

That is probably because you used localhost as hostname of the mail-server and in docker that’s just the EGroupware container, no longer the host itself. Edit your mail account(s) and change localhost eg. to the real IP address of your host:

EGroupware/egroupware

Ralf

[hbsimon]

Thanks Ralf,
After setting it to the servers IP IMAP and SMTP are connecting. The only problem now is the sieve section which will not connect. In Dovecot the inet_listener sieve is set to IP 127.0.0.1 and port 4190. I us

ed localhost and the IP Address 127.0.0.1, but still getting “Error connecting to server”.

It appears the gateway error might be that I didn’t wait long enough for all services to start, will monitor it.
Regards,
Horst[

[RalfBecker]

Please read what I said: you can NOT use localhost!

Use either the docker0 address (usually 172.17.0.1) or the IP address of your host, but not localhost (127.0.0.1), as localhost refers to the container itself and NOT your host.

Ralf

[hbsimon]

All ok now after changing all relevant configuration files from localhost to the servers ip.
Thanks and Regards

Horst