I tried setting MW_DOCKER_UID and MW_DOCKER_GID both to 0, and that at least allows me to see the various files - it looks like the apache log files are on the -web container under /tmp/, I hadn't noticed that before. So that's at least part of the answer. On the main mediawiki container there is a log file in /tmp/php7.2-fpm.log but it doesn't seem to log very much there; I'm still getting 500 server errors when I try to set $wgDebugLogFile and can't find any trace of what the problem is.

Arthur

On Wed, Feb 10, 2021 at 11:17 AM Arthur Smith <arthurpsmith@gmail.com> wrote:

I've been using mediawiki in the docker containers for a while, and I just did a git pull to the latest, replaced the containers I was running etc, and now I can't figure out where errors are being logged to or how I'm supposed to see them. Help!

This may be related to the new '.env' file that seems to be required, which sets a MW_DOCKER_UID and MW_DOCKER_GID value... If I run

docker-compose logs

I do see some "Permission denied" errors for files in /etc/php/7.2/cli and /etc/php/7.2/fpm but those don't seem to be log files exactly (20-xdebug.ini files ?)

If I do docker-compose exec mediawiki bash I get a login shell on the container and I can look around, but there are no mediawiki log files in /var/log where I would expect them, and again I don't have permission to create a file there. Also if I docker exec into the web container I don't have permission to look at the apache logs (but those do exist).

If I try to add a $wgDebugLogFile to LocalSettings.php the mediawiki instance completely collapses, I can't look at anything, and I see no errors explaining what's going on!

Help!

Arthur