log_limit = 4096 isnt applied, still truncated at 1024

[pschonmann]

Frequently asked questions

• [ x] I have read Frequently Asked Questions
• [ x] I have looked at the list of the existing issues (including closed issues) and searched if my issue has been already reported
• [ x] I have tried to resolve the issue myself and will describe what I did in clear and concise manner

Describe the bug
i set log_limit = 4096 in all fpms config

/etc/php/8.1/fpm/php-fpm.conf:log_limit = 4096
/etc/php/8.2/fpm/php-fpm.conf:log_limit = 4096
/etc/php/8.0/fpm/php-fpm.conf:log_limit = 4096
/etc/php/7.3/fpm/php-fpm.conf:log_limit = 4096
/etc/php/8.3/fpm/php-fpm.conf:log_limit = 4096
/etc/php/7.4/fpm/php-fpm.conf:log_limit = 4096

But log still give me 1024 truncate

/logs/blah.cz/error.log:[Mon May 20 12:53:42.770542 2024] [proxy_fcgi:error] [pid 3717616:tid 140472760637184] [client XXX:59408] AH01071: Got error 'the log buffer is full (1024). The access log request has been truncated.'

To Reproduce
Set limit /etc/php/8.1/fpm/php-fpm.conf:log_limit = 4096 and reload fpm / apache2, nothing chanded

Your understanding of what is happening
Probably hardcoded limit ??
https://serverfault.com/questions/1017932/php-fpm-notice-the-log-buffer-is-full-1024-the-access-log-request-has-been

Expected behavior
Log 1024+ lines

Distribution (please complete the following information):

• OS: Debian 11
• Architecture: amd64
• Repository: packages.sury.org

Package(s) (please complete the following information):

php7.4-fpm:
  Installed: 1:7.4.33-10+0~20240422.92+debian11~1.gbp6bc7ef
  Candidate: 1:7.4.33-10+0~20240422.92+debian11~1.gbp6bc7ef
  Version table:
 *** 1:7.4.33-10+0~20240422.92+debian11~1.gbp6bc7ef 500
        500 https://packages.sury.org/php bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     7.4.33-1+deb11u5 500
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     7.4.33-1+deb11u4 500
        500 http://ftp.cz.debian.org/debian bullseye/main amd64 Packages

[todeveni]

It's a hardcoded feature/bug in PHP itself.