Nginx/PHP-FPM long log lines get truncated

Question

I am unsure is that is a Nginx or PHP-FPM setting, but long log lines are getting truncated. Is there a setting to increase the max log line length?

score 5 · Answer 1 · answered Jun 09 '16 at 21:45

5

The limit of 1024 characters is hard-coded in php-fpm not nginx.

If you want to go over 2048 characters you need to re-compiled both nginx and php-fpm, else only php-fpm.

There is a full solution with patches here for 8192 characters: https://forums.freebsd.org/threads/56543/

answered Jun 09 '16 at 21:45

Daniel Ylitalo

59
1
1

You don't need to recompile. See my answer below. – Max S. Jul 19 '23 at 21:55

score 5 · Answer 2 · answered Aug 19 '19 at 05:31

I recommend using php 7.3

From https://www.php.net/ChangeLog-7.php :

Fixed bug #69031 (Long messages into stdout/stderr are truncated incorrectly) - added new log related FPM configuration options: log_limit, log_buffering and decorate_workers_output.

score 4 · Answer 3 · answered Mar 12 '12 at 11:00

You need to recompile Nginx if you want log lines longer than 2048 bytes. From http://wiki.nginx.org/HttpLuaModule:

There is a hard-coded length limitation on the error messages in the Nginx core. It is 2048 bytes at most, including the trailing newlines and the leading timestamps. You can manually modify this limit by modifying the NGX_MAX_ERROR_STR macro definition in the src/core/ngx_log.h file in the Nginx source tree. If the message size exceeds this limit, the Nginx core will truncate the message text automatically.

Recompiled with increased NGX_MAX_ERROR_STR. Did not help, same as before. — Benjamin Peter, May 31 '16 at 13:01

score 3 · Answer 4 · edited Mar 18 '19 at 01:47

3

I believe you need to have a look at

log_errors_max_len

From here

edited Mar 18 '19 at 01:47

Sergey Kolodyazhnyy

103
3

answered Apr 03 '18 at 05:49

Alexandru R

150
1
11

1

This is correct answer. Increase log_errors_max_len in php.ini, solve this problem. – James M May 17 '18 at 12:20
1

This did not solve the problem for me with php7.3-fpm. The log_limit setting in php-fpm.conf is the place to go, per @realization and Max's answers. – John Rix Aug 27 '21 at 10:03

score 2 · Answer 5 · answered Sep 09 '19 at 21:19

2

Open /etc/php-fpm.conf and update the value of log_limit = 4096 or higher if you like, then systemctl restart php-fpm.

answered Sep 09 '19 at 21:19

Max S.

138
6

2

It might be worth mentioning this wouldn't work in versions prior to PHP 7.3. – pstryk Oct 28 '21 at 08:09
From the comments in the conf file, this only controls the "limit on number of characters in a single line" – miken32 Feb 09 '23 at 23:20
@miken32 That's exactly what Jason asked. – Max S. Feb 10 '23 at 03:37
Indeed it is; I was looking at a few questions at the same time about log output getting cut off and didn't notice this question was specifically about line length! – miken32 Feb 10 '23 at 16:05

Nginx/PHP-FPM long log lines get truncated

5 Answers5

Linked