Opened 8 years ago
Closed 8 years ago
#1078 closed defect (wontfix)
FastCGI stderr gets split into two lines
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | other | Version: | 1.10.x |
| Keywords: | Cc: | ||
| uname -a: | FreeBSD www-07-portlane.mytaste.name 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264: Fri Mar 25 02:10:02 UTC 2016 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 | ||
| nginx -V: | nginx version: nginx/1.10.1 | ||
Description
Hi!
Sometimes we have quite big stack-traces being sent from php-fpm through stderr, our problem is that nginx splits the error message into two separate log lines (see attached example).
It seems nginx splits the error into multiple lines when the log line reaches over 4096 chars but I can't seem to find where that is happening in the code.
I have changed NGX_MAX_ERROR_STR in src/core/ngx_log.h line 76 to 16384 (just for the sake of it) but that doesn't help, it still gets split into multiple lines.
Attachments (1)
Change History (2)
by , 8 years ago
| Attachment: | log-output.txt added |
|---|
comment:1 by , 8 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Stderr records are logged once they received, no attempts to preserve their integrity are done. The 4096 limit you are observing is likely due to some buffer sizes - either in nginx (fastcgi_buffer_size, fastcgi_buffers) or in PHP itself.