I powered up this docker app and get 502 Bad Gateway,

In the log:

# docker restart egroupware
egroupware
# docker logs -f egroupware

EGroupware successful updated
 * Starting periodic command scheduler cron
   ...done.
[30-Jun-2021 04:00:26] NOTICE: fpm is running, pid 1
[30-Jun-2021 04:00:26] NOTICE: ready to handle connections
[30-Jun-2021 04:00:26] NOTICE: systemd monitor interval set to 10000ms
[01-Jul-2021 04:20:01] NOTICE: [pool www] child 49 exited with code 0 after 87575.267016 seconds from start
[01-Jul-2021 04:20:01] NOTICE: [pool www] child 2889 started
[01-Jul-2021 04:25:01] NOTICE: [pool www] child 50 exited with code 0 after 87875.331164 seconds from start
[01-Jul-2021 04:25:01] NOTICE: [pool www] child 2892 started
[01-Jul-2021 04:30:45] NOTICE: [pool www] child 53 exited with code 0 after 88218.874783 seconds from start
[01-Jul-2021 04:30:45] NOTICE: [pool www] child 2895 started
[01-Jul-2021 04:30:46] NOTICE: [pool www] child 51 exited with code 0 after 88219.339383 seconds from start
.....
[07-Jul-2021 02:45:01] NOTICE: [pool www] child 19432 started
/usr/bin/php7.4 -d memory_limit=-1 /usr/share/egroupware/setup/setup-cli.php --update 'all,admin,)MTbcbDERN1Xo4J2'
EGroupware API version 21.1 found.
EGroupware configuration file (header.inc.php) version 1.29 exists and is up to date
Your database is not working! mysqli://egroupware:()b?Il64Ja)Wa7w=@db/egroupware:

Installation failed --> exiting!

Retrying EGroupware installation in 3 seconds ...
/usr/bin/php7.4 -d memory_limit=-1 /usr/share/egroupware/setup/setup-cli.php --update 'all,admin,-24d]&J=Xs3p&|CP'
EGroupware API version 21.1 found.
EGroupware configuration file (header.inc.php) version 1.29 exists and is up to date
Your database is not working! mysqli://egroupware:()b?Il64Ja)Wa7w=@db/egroupware:

Installation failed --> exiting!

Retrying EGroupware installation in 3 seconds ...
/usr/bin/php7.4 -d memory_limit=-1 /usr/share/egroupware/setup/setup-cli.php --update 'all,admin,GWlm?kF#gTg(eS|#'
EGroupware API version 21.1 found.
EGroupware configuration file (header.inc.php) version 1.29 exists and is up to date
Your database is not working! mysqli://egroupware:()b?Il64Ja)Wa7w=@db/egroupware:

Installation failed --> exiting!
....

Does it appear there’s a database corruption?

Any advice??

Thanks,
Justin

Is there any other way to install eGroupware besides via Docker?

Do these instruction for installing a development version of EG still work with the latest release tags? (I ask because I use composer to maintain other apps and I’m more comfortable with it). If yes, then is it possible to run periodic updates to the codebase and DB schema?

Recently I had setup a Debian VM and installed EG, but within a week I got “502 Bad gateway”. I reported it here, and I all I got was Stefan’s note, but he didn’t say where the backup would be located or how to apply it, just what it would contain:

Finally I tracked it down to a failing database, and so I asked “how do I reinitialize the database?”, but I got no response.

After running a few docker-compose commands that were supposed to (recreate? rebuild? reset?) egroupware-docker, I no longer had a working docker.service. Due to this I now cannot apt upgrade my Debian guest, etc etc.

Is eGroupware a LAMP application or Node.JS? Have you considered having a set of PHP or Node requirements, a sample Apache/Node config, and a script to populate a fresh database? I find that using Docker, installing the DB via docker-compose (is that even possible?), and routing through an Nginx reverse proxy, though it may be easy to install initially, lead to an unmaintainable system (at least for me).

Not sure I’m going to rebuild this on Debian, as I’m not confident in the stability. Are there any other setups you recommend? On a NAS – say QNAP – can I run the two depreciated modules Wiki & Knowledge-base simply by checking them out of the repo into /etc/egroupware/ and restarting the container?

Thank you

Ok, I totally understand. And I’m sorry if I come off as a squeaky wheel.
I will say that I stumbled upon the instructions to install a development version, and now the architecture of EG is becoming a bit more clear to me. This method allowed me to install without Docker, under Apache (with a redirect to the Nginx proxy(?)), and I got a sense of how the database setup works. I realize that this may side-step some useful features, such as update automation, etc, but at least some the fog of what’s under the hood has cleared. I will probably get back on the mainstream bandwagon at some point. Thank you!