Problems with custom log file format

[Lucas Rolff]

1st one matches your log format, the 2nd one matches the `combined` 
format - so:

- Maybe you've still some old nginx processes that are still not closed 
after reloading, which causes it to log in the combined format, or can 
it be another vhost logging to same log file, without using access_log 
.... main ?

Can you paste your *full* config?, that allows for easier debugging.

lists at lazygranch.com wrote:
> Configuration file included in the post. I already checked it.
>
>
>    Original Message  
> From: Maxim Dounin
> Sent: Tuesday, August 23, 2016 10:10 AM
> To: nginx at nginx.org
> Reply To: nginx at nginx.org
> Subject: Re: Problems with custom log file format
>
> Hello!
>
> On Tue, Aug 23, 2016 at 10:07:56AM -0700, lists at lazygranch.com wrote:
>
>> Looks like I have no takers on this problem. Should I filed a
>> bug report? If so, where?
>
> I would recommend you to start with double-checking your
> configuration instead.
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20160823/030a65f5/attachment.html>