<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">1st one matches your log
format, the 2nd one matches the `combined` format - so:<br>
<br>
- 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 ?<br>
<br>
Can you paste your *full* config?, that allows for easier debugging.<br>
<br>
<span><a class="moz-txt-link-abbreviated" href="mailto:lists@lazygranch.com">lists@lazygranch.com</a> wrote:</span><br>
<blockquote cite="mid:20160823172701.5468238.38788.9151@lazygranch.com"
type="cite">
<pre wrap="">Configuration file included in the post. I already checked it.
Original Message
From: Maxim Dounin
Sent: Tuesday, August 23, 2016 10:10 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:nginx@nginx.org">nginx@nginx.org</a>
Reply To: <a class="moz-txt-link-abbreviated" href="mailto:nginx@nginx.org">nginx@nginx.org</a>
Subject: Re: Problems with custom log file format
Hello!
On Tue, Aug 23, 2016 at 10:07:56AM -0700, <a class="moz-txt-link-abbreviated" href="mailto:lists@lazygranch.com">lists@lazygranch.com</a> wrote:
</pre>
<blockquote type="cite"><pre wrap="">Looks like I have no takers on this problem. Should I filed a
bug report? If so, where?
</pre></blockquote>
<pre wrap=""><!---->
I would recommend you to start with double-checking your
configuration instead.
</pre>
</blockquote>
<br>
</body></html>