Log enhancements

[surapuramakhil]

Is your feature request related to a problem? Please describe.

These are my extreme pain points when I am trying to debug issue, which could have saved my hours of time if this way.

when I try to debug when something is broken - I get log truncated

Message: Could not start container nextcloud-aio-apache: Server error: `POST http://127.0.0.1/v1.41/containers/nextcloud-aio-apache/start` resulted in a `500 Internal Server Error` response:
{"message":"driver failed programming external connectivity on endpoint nextcloud-aio-apache (7733db1eb7f1a2679e44dda426 (truncated...)

I am also clueless from there this log is coming from, request update format containing this information

[Mon Jan 20 01:42:28.252459 2025] [mpm_event:notice] [pid 170:tid 170] AH00489: Apache/2.4.62 (Unix) OpenSSL/3.3.2 configured -- resuming normal operations
[Mon Jan 20 01:42:28.252480 2025] [core:notice] [pid 170:tid 170] AH00094: Command line: 'httpd -D FOREGROUND'
[20-Jan-2025 01:42:28] NOTICE: fpm is running, pid 175
[20-Jan-2025 01:42:28] NOTICE: ready to handle connections
{"level":"info","ts":1737337348.2602246,"msg":"using config from file","file":"/Caddyfile"}
{"level":"info","ts":1737337348.2609,"msg":"adapted config to JSON","adapter":"caddyfile"}
Deleting duplicate sessions
NOTICE: PHP message: Slim Application Error
Type: Exception
Code: 0
Message: Could not start container nextcloud-aio-apache: Server error: `POST http://127.0.0.1/v1.41/containers/nextcloud-aio-apache/start` resulted in a `500 Internal Server Error` response:
{"message":"driver failed programming external connectivity on endpoint nextcloud-aio-apache (7733db1eb7f1a2679e44dda426 (truncated...)

for these code - adding stack trace - information

all-in-one/php/src/Controller/DockerController.php

Lines 274 to 278 in 2992198

	try {
	$this->PerformRecursiveContainerStart($id);
	} catch (\Exception $e) {
	error_log('Could not start domaincheck container: ' . $e->getMessage());
	}

to

        try {
            $this->PerformRecursiveContainerStart($id);
        } catch (\Exception $e) {
            error_log('Could not start domaincheck container: ' . $e->getMessage() . "\n" . $e->getTraceAsString());
        }

Describe the solution you'd like

improve log message format - including

for truncated issue - TBH I don't know fix.

for having where log in coming form

update

all-in-one/Containers/mastercontainer/mastercontainer.conf

Lines 15 to 17 in 2992198

	LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" proxy
	ErrorLog /proc/self/fd/2
	ErrorLogFormat "[%t] [%l] [%E] [client: %{X-Forwarded-For}i] [%M] [%{User-Agent}i]"

to

LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" [source: php/apache]" proxy
......
ErrorLogFormat "[%t] [%l] [%E] [client: %{X-Forwarded-For}i] [%M] [%{User-Agent}i] [source: php/apache]"

Describe alternatives you've considered

grep log message, try to find from where this log would have come from.

Additional context

[szaimen]

Hi, thanks for the report!

I already tried to improve the logging in the past multiple times. Unfortunately afaik, the slim framework that we are using is truncating the logs without an option to overwrite this. So it will be improved with a hack: #5920