<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.web.nginx.english">
    <title>gmane.comp.web.nginx.english</title>
    <link>http://blog.gmane.org/gmane.comp.web.nginx.english</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39012"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39011"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39010"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39009"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39008"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39007"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39006"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39005"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39004"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39003"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39002"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39001"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/39000"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38999"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38998"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38997"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38996"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38995"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38994"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.comp.web.nginx.english/38993"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39012">
    <title>Re: Can't log/print in header_filter_by_lua</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39012</link>
    <description>&lt;pre&gt;OK. I was able to resolve it by doing a clean install of nginx. Dunno what
the underlying issue was, but my hunch is I was logging to an a different
location and the logs I was looking at were the default logs from nginx.

Thanks anyway!


On Mon, May 20, 2013 at 2:47 PM, Ramesh Muraleedharan
&amp;lt;ramesh1987-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>Ramesh Muraleedharan</dc:creator>
    <dc:date>2013-05-21T00:18:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39011">
    <title>Re: Can't log/print in header_filter_by_lua</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39011</link>
    <description>&lt;pre&gt;I've tried print() as well, and neither that nor ngx.log() have worked as
yet.


On Mon, May 20, 2013 at 2:42 PM, Jader H. Silva &amp;lt;jaderhs5-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>Ramesh Muraleedharan</dc:creator>
    <dc:date>2013-05-20T21:47:41</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39010">
    <title>Re: Can't log/print in header_filter_by_lua</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39010</link>
    <description>&lt;pre&gt;*ngx.print()* is only valid for r*ewrite_by_lua*, access_by_lua* and
content_by_lua*.* Maybe your looking for* print()

ngx.log* should work though*.
*

*
*


2013/5/20 Ramesh Muraleedharan &amp;lt;ramesh1987-Re5JQEeQqe8AvxtiuMwx3w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>Jader H. Silva</dc:creator>
    <dc:date>2013-05-20T21:42:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39009">
    <title>Can't log/print in header_filter_by_lua</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39009</link>
    <description>&lt;pre&gt;Hi all,

I've been experimenting with rewriting 'Set Cookie' headers in a
nginx-reverse-proxy effort.

The Set-Cookie rewrite doesn't seem to work yet, and more importantly, my
log/print statements don't print to error_log as directed, making it very
difficult to debug.

http {

server {
     access_log /home/bhedia/access.log;
     #error_log /home/bhedia/errors.log debug;
     error_log /home/bhedia/errors.log notice;

     listen   80;

     root /usr/share/nginx/www;
     #index index.html index.htm;

     # Make site accessible from http://localhost:8080/
     server_name localhost;

     location / {

          proxy_pass           http://10.45.17.85:50088/;
          proxy_set_header     Host booga.booga.com;
          #proxy_cookie_domain    test-sites.com booga.booga.com;

          header_filter_by_lua '
       ngx.log(ngx.NOTICE, "hello world")
               local cookies = ngx.header.set_cookie
               if not cookies then return end
               if type(cookies) ~= "table" then cookies = {cookies} end
               local newcookies = {}
               for i, val in ipairs(cookies) do
                   local newval = string.gsub(val,
"([dD]omain)=[%w_-\\\\.-]+",
                          "%1=booga.booga.com")
   ngx.print(val)
   ngx.print(newval)
                   table.insert(newcookies, newval)
               end
               ngx.header.set_cookie = newcookies
              ';
     }
}
}

Any help would be appreciated.

Thanks!
_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>Ramesh Muraleedharan</dc:creator>
    <dc:date>2013-05-20T21:20:56</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39008">
    <title>Re: Fancyindex module hangs connection</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39008</link>
    <description>&lt;pre&gt;Thanks!

I found solution myself:
http://serverfault.com/questions/507375/nginx-not-finishing-fancyindex

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239168,239355#msg-239355
&lt;/pre&gt;</description>
    <dc:creator>peku33</dc:creator>
    <dc:date>2013-05-20T21:11:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39007">
    <title>Re: valid_referers dynamic hostname</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39007</link>
    <description>&lt;pre&gt;Hello!

On Mon, May 20, 2013 at 02:14:02PM -0400, vlad031-7DHrFgVBAElWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org wrote:


Just a side note: this statement isn't needed.  Both http and 
https schemes are allowed by a "https?" in the regular expression 
I provided, "?" makes preceeding character option.


You probably mean to write

    if ($test = A) {
        return 444;
    }

instead, as your initial message suggests you want to allow 
requests where Referer matches Host.

&lt;/pre&gt;</description>
    <dc:creator>Maxim Dounin</dc:creator>
    <dc:date>2013-05-20T18:34:01</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39006">
    <title>Re: valid_referers dynamic hostname</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39006</link>
    <description>&lt;pre&gt;I suggest you take a look at the order in which 'if' statements are
evaluated.
Consider reading the 'if' directive
documentation&amp;lt;http://nginx.org/en/docs/http/ngx_http_rewrite_module.html#if&amp;gt;
.
---
*B. R.*


On Mon, May 20, 2013 at 2:14 PM, vlad031-7DHrFgVBAElWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org
&amp;lt;nginx-forum-LhBSS6c2AZM&amp;lt; at &amp;gt;public.gmane.org&amp;gt;wrote:

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>B.R.</dc:creator>
    <dc:date>2013-05-20T18:26:24</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39005">
    <title>Re: valid_referers dynamic hostname</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39005</link>
    <description>&lt;pre&gt;Hello,

Thank you for your example Maxim. This is what I've wrote in my config:

set $temp "$host:$http_referer";

valid_referers none blocked server_names ~\.google\. ~\.yahoo\. ~\.bing\.
~\.ask\. ~\.live\. ~\.googleusercontent.com\. ;

if ($invalid_referer){
    set $test A ;
}

if ($temp ~* "^(.*):http?://\1") {
    set $test "${test}B";
}

if ($temp ~* "^(.*):https?://\1") {
    set $test "${test}C";
}

if ($test = ABC) {
    return 444 ;
}

It is always returning 444 ... what am I doing wrong?!

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239318,239352#msg-239352
&lt;/pre&gt;</description>
    <dc:creator>vlad031-7DHrFgVBAElWk0Htik3J/w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-20T18:14:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39004">
    <title>Re: Nginx returns HTTP 200 with Content-Length: 0</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39004</link>
    <description>&lt;pre&gt;it's GET request?


2013/5/20 apeman &amp;lt;nginx-forum-LhBSS6c2AZM&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

_______________________________________________
nginx mailing list
nginx-jCiJ2l+ov5bYtjvyW6yDsg&amp;lt; at &amp;gt;public.gmane.org
http://mailman.nginx.org/mailman/listinfo/nginx&lt;/pre&gt;</description>
    <dc:creator>suttya</dc:creator>
    <dc:date>2013-05-20T16:02:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39003">
    <title>Re: valid_referers dynamic hostname</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39003</link>
    <description>&lt;pre&gt;Hello!

On Sat, May 18, 2013 at 01:31:50PM -0400, vlad031-7DHrFgVBAElWk0Htik3J/w&amp;lt; at &amp;gt;public.gmane.org wrote:


The "$host" string here means exactly "$host".  There is no 
variable expansion for server_name (expect for a special name 
"$hostname", which isn't actually a variable but a special name).

Most likely requests are handled in the sever{} block in question 
as it's used as a default server.


The valid_referers directive doesn't support variables.


What you are trying to do, i.e. allow referers which match Host 
header in a request, currently can't be done using the referers 
module only.

With a litle help from the rewrite module it's possible though.  
Something like this should work:

    valid_referers none blocked server_names ~\.google\. ...;

    set $temp "$host:$http_referer";

    if ($temp ~* "^(.*):https?://\1") {
        set $invalid_referer "0";
    }

    if ($invalid_referer) {
        return 403;
    }


&lt;/pre&gt;</description>
    <dc:creator>Maxim Dounin</dc:creator>
    <dc:date>2013-05-20T13:19:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39002">
    <title>Re: valid_referers dynamic hostname</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39002</link>
    <description>&lt;pre&gt;Also,

Isn't this a bug since I have added server_names to valid_referers?

And since server_names knows the domain, it should work...


Any ideas?

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239318,239343#msg-239343
&lt;/pre&gt;</description>
    <dc:creator>vlad031-7DHrFgVBAElWk0Htik3J/w&lt; at &gt;public.gmane.org</dc:creator>
    <dc:date>2013-05-20T11:27:26</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39001">
    <title>Re: The truth about gzip_buffers?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39001</link>
    <description>&lt;pre&gt;Hello!

On Sat, May 18, 2013 at 09:02:14AM -0400, spdyg wrote:


Just keep the default?


Rest of the response will be kept till some buffers are sent to 
the client.

Keeping upstream connection open is generally irrelevant - it 
depends mostly on proxy_buffers/proxy_max_temp_file_size - but 
might happen in some configurations.


Much like with other buffers in nginx, small buffers means better 
memory utilization, but larger buffers might result in smaller CPU 
usage as there are some amount of work done per-buffer.


No.

&lt;/pre&gt;</description>
    <dc:creator>Maxim Dounin</dc:creator>
    <dc:date>2013-05-20T11:26:28</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/39000">
    <title>Nginx balancing mechanism</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/39000</link>
    <description>&lt;pre&gt;Hello

What balancing mechanism is used in nginx: connections are balanced, or
messages in connections are balanced?

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239340,239340#msg-239340
&lt;/pre&gt;</description>
    <dc:creator>Sabik2006</dc:creator>
    <dc:date>2013-05-20T10:39:05</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38999">
    <title>Re: nginx cache opendir failed</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38999</link>
    <description>&lt;pre&gt;the Web server is run by "www" , and owns the parent directory of the cache.

Le 20 mai 2013 à 11:19, Stev e Holdoway &amp;lt;steve-k8kDZgyTY1dGT1zXwTwi5w&amp;lt; at &amp;gt;public.gmane.org&amp;gt; a écrit :

&lt;/pre&gt;</description>
    <dc:creator>Ronald Van Assche</dc:creator>
    <dc:date>2013-05-20T09:26:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38998">
    <title>Re: nginx cache opendir failed</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38998</link>
    <description>&lt;pre&gt;So, you need to ensure all files can only be deleted by the owner, all 
files created in the directory are in the same group as the directory 
and, to the best of my knowledge, setuid is meaningless.

Ah, I see that it's a freebsd machine... setgid is the default 
functionality on that OS.

This may work, but a basic understanding of file permissions will 
produce a more workable solution. Who runs the web server? That's who 
you need to set access up for.

Steve


On 20/05/13 21:10, Ronald Van Assche wrote:
&lt;/pre&gt;</description>
    <dc:creator>Stev e Holdoway</dc:creator>
    <dc:date>2013-05-20T09:19:17</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38997">
    <title>Re: nginx cache opendir failed</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38997</link>
    <description>&lt;pre&gt;SOLVED:

Just chmod 7777 ( 4 seven)  /var/cache/www , the parent directory of the nginx cache and voilà, it works.

Le 19 mai 2013 à 17:51, Ronald Van Assche &amp;lt;rva-QgsYLkXU0MPQT0dZR+AlfA&amp;lt; at &amp;gt;public.gmane.org&amp;gt; a écrit :

&lt;/pre&gt;</description>
    <dc:creator>Ronald Van Assche</dc:creator>
    <dc:date>2013-05-20T09:10:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38996">
    <title>Re: Unbuffered requests in a reverse proxy?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38996</link>
    <description>&lt;pre&gt;
See the nginx mailinglist archives for a "no_buffer" patch to nginx 1.2.7:
http://yaoweibin.cn/patches/nginx-1.2.7-no_buffer-v6.patch

You'll find the usage / configuration syntax from the archives.

"no_buffer" patch for nginx 1.4.x isn't ready/stable yet.

&lt;/pre&gt;</description>
    <dc:creator>Pasi Kärkkäinen</dc:creator>
    <dc:date>2013-05-20T07:57:03</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38995">
    <title>Re: Nginx returns HTTP 200 with Content-Length: 0</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38995</link>
    <description>&lt;pre&gt;I never use SPDY. The problem still exists. I don't know how to fix it.

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,205826,239334#msg-239334
&lt;/pre&gt;</description>
    <dc:creator>apeman</dc:creator>
    <dc:date>2013-05-20T07:29:25</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38994">
    <title>Re: 1.4.1 + spdy + centos 6 + openssl-1.0.1e (static), firefox 21 ajax requests ssl spdy = segfault</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38994</link>
    <description>&lt;pre&gt;For closure: I took this to the bug tracker and a patch was posted that
resolves this issue:
http://trac.nginx.org/nginx/ticket/357

Apologies for newsletter spam.

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239327,239331#msg-239331
&lt;/pre&gt;</description>
    <dc:creator>epsilon2930</dc:creator>
    <dc:date>2013-05-20T01:20:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38993">
    <title>Unbuffered requests in a reverse proxy?</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38993</link>
    <description>&lt;pre&gt;Hi

Can nginx be configured to pass through a reverse proxy request before
it has been transmitted completely?

My set-up is a public facing nginx server accepting file uploads passed
to another server via a reverse proxy configuration.
I appears as nginx is reading the entire request before passing it on to
the reverse proxy.

The back end is written to abort early if the file size is not
acceptable depending which account the client is logged in to or abort
immediately if not logged in.
Is there any buffer setting that can be set to 0 so that the request
won't be buffered?
&lt;/pre&gt;</description>
    <dc:creator>Peter Hultqvist</dc:creator>
    <dc:date>2013-05-19T19:50:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.comp.web.nginx.english/38992">
    <title>1.4.1 + spdy + centos 6 + openssl-1.0.1e (static), firefox 21 ajax requests ssl spdy = segfault</title>
    <link>http://permalink.gmane.org/gmane.comp.web.nginx.english/38992</link>
    <description>&lt;pre&gt;Hello, on one of my servers, nginx suddenly started crashing on some
AJAX-heavy pages when accessed via SSL+SPDY. It seems to happen only when
Firefox is the client (tested with Firefox 21), latest version of chrome
uses SPDY without crashing.

uname -a:
Linux myserver.com 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC
2013 x86_64 x86_64 x86_64 GNU/Linux

nginx compile flags:
CFLAGS="-g -O0" ./configure --with-pcre=/usr/local/src/nginx-1.4.1/pcre-8.32
 --sbin-path=/usr/local/sbin  --conf-path=/etc/nginx/nginx.conf 
--pid-path=/var/run/nginx.pid  --error-log-path=/var/log/nginx/error.log 
--http-log-path=/var/log/nginx/access.log  --with-http_realip_module 
--with-http_ssl_module 
--with-openssl=/usr/local/src/nginx-1.4.1/openssl-1.0.1e
--with-http_spdy_module --http-client-body-temp-path=/tmp/nginx_client 
--http-proxy-temp-path=/tmp/nginx_proxy 
--http-fastcgi-temp-path=/tmp/nginx_fastcgi  --with-http_stub_status_module
--with-debug

nginx log when crash happens:
2013/05/19 18:05:58 [notice] 26737#0: start worker process 26899
2013/05/19 18:05:58 [notice] 26737#0: signal 29 (SIGIO) received
2013/05/19 18:05:59 [notice] 26737#0: signal 17 (SIGCHLD) received
2013/05/19 18:05:59 [alert] 26737#0: worker process 26897 exited on signal
11 (core dumped)
2013/05/19 18:05:59 [notice] 26737#0: start worker process 26907
2013/05/19 18:05:59 [notice] 26737#0: signal 29 (SIGIO) received
2013/05/19 18:06:00 [notice] 26737#0: signal 17 (SIGCHLD) received
2013/05/19 18:06:00 [alert] 26737#0: worker process 26899 exited on signal
11 (core dumped)
2013/05/19 18:06:00 [notice] 26737#0: start worker process 26909
2013/05/19 18:06:00 [notice] 26737#0: signal 29 (SIGIO) received

nginx.conf
http://pastebin.com/G9wAgyeh

gdb backtrace:
# gdb /usr/local/sbin/nginx core.26899

... snip gpl stuff ...

Reading symbols from /usr/local/sbin/nginx...done.
[New Thread 26899]
Missing separate debuginfo for
Try: yum --disablerepo='*' --enablerepo='*-debug*' install
/usr/lib/debug/.build-id/50/fc20fea18a6f375789f0f86e28f463d50714fd
Reading symbols from /lib64/libpthread.so.0...(no debugging symbols
found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /lib64/libpthread.so.0
Reading symbols from /lib64/libcrypt.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libcrypt.so.1
Reading symbols from /lib64/libdl.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libdl.so.2
Reading symbols from /lib64/libz.so.1...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libz.so.1
Reading symbols from /lib64/libc.so.6...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libc.so.6
Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib64/libfreebl3.so...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libfreebl3.so
Reading symbols from /lib64/libnss_files.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib64/libnss_files.so.2
Core was generated by `nginx: worker process                         '.
Program terminated with signal 11, Segmentation fault.
#0  0x0000003455283c56 in __memset_sse2 () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.107.el6.x86_64 nss-softokn-freebl-3.12.9-11.el6.x86_64
zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0  0x0000003455283c56 in __memset_sse2 () from /lib64/libc.so.6
#1  0x0000000000493a67 in ngx_http_spdy_state_data (sc=0x3035ba0,
pos=0x37c78f8 "", end=0x37c78f8 "")
    at src/http/ngx_http_spdy.c:1193
#2  0x0000000000492673 in ngx_http_spdy_state_head (sc=0x3035ba0,
pos=0x37c78f8 "", end=0x37c78f8 "")
    at src/http/ngx_http_spdy.c:699
#3  0x00000000004919e2 in ngx_http_spdy_read_handler (rev=0x7f0318ffe3b8) at
src/http/ngx_http_spdy.c:364
#4  0x000000000042ac31 in ngx_event_process_posted (cycle=0x2893a30,
posted=0x8d1b68)
    at src/event/ngx_event_posted.c:40
#5  0x000000000042887c in ngx_process_events_and_timers (cycle=0x2893a30) at
src/event/ngx_event.c:276
#6  0x0000000000435ebd in ngx_worker_process_cycle (cycle=0x2893a30,
data=0x1)
    at src/os/unix/ngx_process_cycle.c:807
#7  0x00000000004327ca in ngx_spawn_process (cycle=0x2893a30, proc=0x435cf7
&amp;lt;ngx_worker_process_cycle&amp;gt;,
    data=0x1, name=0x609c9b "worker process", respawn=1) at
src/os/unix/ngx_process.c:198
#8  0x0000000000435906 in ngx_reap_children (cycle=0x2893a30) at
src/os/unix/ngx_process_cycle.c:619
#9  0x00000000004345ed in ngx_master_process_cycle (cycle=0x2893a30) at
src/os/unix/ngx_process_cycle.c:180
#10 0x00000000004041b6 in main (argc=3, argv=0x7fffb6c2dbd8) at
src/core/nginx.c:412

Server has a Core i3 540 with HT, OS is 64-bit CentOS 6 fully patched (as of
date of this message).

- kernel log when error occurred:
May 19 18:06:00 saruman kernel: nginx[26899]: segfault at 0 ip
0000003455283c56 sp 00007fffb6c2d498 error 6 in
libc-2.12.so[3455200000+18a000]

The crash is highly reproducible and when it crashes the ip and sp
parameters and offsets are always the same.

I hope I've posted enough info for devs to fix this, sorry for the long
message.

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239327,239327#msg-239327
&lt;/pre&gt;</description>
    <dc:creator>epsilon2930</dc:creator>
    <dc:date>2013-05-19T16:43:37</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.web.nginx.english">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.web.nginx.english</link>
  </textinput>
</rdf:RDF>
