Is there a reason that Nginx continuously logs the sort of message below in
the info log when client_body_in_file_only is set to either "clean" or
"on"? Regardless of which of those two settings you're using for that
directive, the request body is always going to be buffered to a temporary
file (that is the whole point of that setting).
"[notice] 3951130#3951130: *769735 a client request body is buffered to a
temporary file"
Seems like even the info log should be suppressing that notice if you're
using settings that force the request body to a temp file.
Getting good info out of the info log is proving to be difficult when the
log is flooded with information that is just reaffirming that you have a
setting in place to do exactly what the log is saying. Certainly we can
grep around it too. But it's also bloating the info logs so that isn't
great either.
--
Lance Dockins
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20230920/5d10cedb/attachment.htm>
Hello!
On Wed, Sep 20, 2023 at 11:47:48AM -0500, Lance Dockins wrote:
> Is there a reason that Nginx continuously logs the sort of message below in
> the info log when client_body_in_file_only is set to either "clean" or
> "on"? Regardless of which of those two settings you're using for that
> directive, the request body is always going to be buffered to a temporary
> file (that is the whole point of that setting).
>
> "[notice] 3951130#3951130: *769735 a client request body is buffered to a
> temporary file"
>
> Seems like even the info log should be suppressing that notice if you're
> using settings that force the request body to a temp file.
That's exactly the reason why it is logged at the "notice" level,
and not "warn" as it used to be under normal conditions. If you
don't want to see these messages, consider configuring error_log
logging level to a higher one, see http://nginx.org/r/error_log
for details.
--
Maxim Dounin
http://mdounin.ru/
Thank you. Normally I don’t even use the info logs but while troubleshooting a memory problem, I was looking through them and noticed that even just using an error_log file at the info level was writing a ton of data despite that config. I guess I can just shut the info log back off.
—
Lance Dockins
> On Wednesday, Sep 20, 2023 at 1:41 PM, Maxim Dounin <mdounin at mdounin.ru (mailto:mdounin at mdounin.ru)> wrote:
> Hello!
>
> On Wed, Sep 20, 2023 at 11:47:48AM -0500, Lance Dockins wrote:
>
> > Is there a reason that Nginx continuously logs the sort of message below in
> > the info log when client_body_in_file_only is set to either "clean" or
> > "on"? Regardless of which of those two settings you're using for that
> > directive, the request body is always going to be buffered to a temporary
> > file (that is the whole point of that setting).
> >
> > "[notice] 3951130#3951130: *769735 a client request body is buffered to a
> > temporary file"
> >
> > Seems like even the info log should be suppressing that notice if you're
> > using settings that force the request body to a temp file.
>
> That's exactly the reason why it is logged at the "notice" level,
> and not "warn" as it used to be under normal conditions. If you
> don't want to see these messages, consider configuring error_log
> logging level to a higher one, see http://nginx.org/r/error_log
> for details.
>
> --
> Maxim Dounin
> http://mdounin.ru/
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> https://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20230920/32ae7472/attachment.htm>