# 1.3.12 occasional segfaults

**URL:** <https://www.ruby-forum.com/t/1-3-12-occasional-segfaults/226786>\
**Category:** NGINX\
**Created:** [February 21, 2013, 8:39am UTC](https://www.ruby-forum.com/t/1-3-12-occasional-segfaults/226786 "2013-02-21T08:39:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![digitalpoint](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/6a8cbe/32.png) [@digitalpoint](https://www.ruby-forum.com/u/digitalpoint)\
**Post date:** [February 21, 2013, 8:39am UTC](https://www.ruby-forum.com/t/1-3-12-occasional-segfaults/226786/1 "2013-02-21T08:39:27Z")

</div>

It’s a fairly vanilla install of nginx (with the exception of the SPDY  
patch). We are seeing roughly 1 segfault every hour or so on each web  
server… I didn’t generate a debugging log, because I wasn’t sure how  
big  
something like that would be for an entire hour, but I can if needed.

* * *

## nginx -V

nginx version: nginx/1.3.12  
built by gcc 4.5.1 20101208 [gcc-4\_5-branch revision 167585] (SUSE  
Linux)  
TLS SNI support enabled  
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx  
–pid-path=/var/run/nginx.pid --error-log-path=/usr/log/ngnix/error.log  
–http-log-path=/usr/log/ngnix/access.log  
–with-openssl=/home/software\_source/openssl-1.0.1c --with-cc-opt=‘-I  
/usr/local/ssl/include’ --with-ld-opt=‘-L /usr/local/ssl/lib’  
–without-http\_proxy\_module --without-http\_ssi\_module  
–with-http\_ssl\_module  
–with-http\_stub\_status\_module --with-http\_spdy\_module

* * *

## backtrace from core dump:

# #0 0x00000000004514ea in ngx\_http\_spdy\_send\_output\_queue (sc=0xd77610) at src/http/ngx\_http\_spdy.c:713 cl = c = 0x7fe9a5436f90 clcf = out = frame = 0xa250d0 fn = #1 0x00000000004520b2 in ngx\_http\_spdy\_write\_handler (wev=) at src/http/ngx\_http\_spdy.c:644 rc = c = fc = ctx = r = stream = s = sn = sc = 0xd77610 #2 0x000000000041a5ba in ngx\_event\_process\_posted (cycle=, posted=0x854a88) at src/event/ngx\_event\_posted.c:40 ev = #3 0x000000000041a1d5 in ngx\_process\_events\_and\_timers (cycle=0x885a90) at src/event/ngx\_event.c:276 flags = 3 timer = delta = 81 #4 0x0000000000420038 in ngx\_worker\_process\_cycle (cycle=0x885a90, data=) at src/os/unix/ngx\_process\_cycle.c:807 worker = i = c = #5 0x000000000041e9a3 in ngx\_spawn\_process (cycle=0x885a90, proc=0x41ff6c \<ngx\_worker\_process\_cycle\>, data=0x2, name=0x59b51a “worker process”, respawn=-3) at src/os/unix/ngx\_process.c:198 on = 1 pid = 0 s = 2 #6 0x000000000041f5f6 in ngx\_start\_worker\_processes (cycle=0x885a90, n=4, type=-3) at src/os/unix/ngx\_process\_cycle.c:362 i = ch = {command = 1, pid = 6348, slot = 1, fd = 19} #7 0x00000000004206d1 in ngx\_master\_process\_cycle (cycle=0x885a90) at src/os/unix/ngx\_process\_cycle.c:136 title = 0x973f74 “master process /usr/sbin/nginx” p = size = 31 i = 1 n = sigio = set = {\_\_val = {0, 0, 0, 0, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 0}} itv = {it\_interval = {tv\_sec = 0, tv\_usec = 0}, it\_value = {tv\_sec = 0, tv\_usec = 0}} live = delay = ls = ccf = 0x0 #8 0x000000000040546c in main (argc=, argv=) at src/core/nginx.c:412 i = log = 0x84d7a0 cycle = 0x0 init\_cycle = {conf\_ctx = 0x0, pool = 0x884fa0, log = 0x84d7a0, new\_log = {log\_level = 0, file = 0x0, connection = 0, handler = 0, data

0x0, action = 0x0}, files = 0x1, free\_connections = 0x0,  
free\_connection\_n =  
0, reusable\_connections\_queue = {  
prev = 0x0, next = 0x0}, listening = {elts = 0x0, nelts = 0,  
size = 0, nalloc = 0, pool = 0x0}, paths = {elts = 0x0, nelts = 0, size  
= 0,  
nalloc = 1, pool = 0x0}, open\_files = {last = 0x0, part = {elts = 0x0,  
nelts  
= 0, next = 0x0}, size = 0,  
nalloc = 0, pool = 0x0}, shared\_memory = {last = 0x0, part =  
{elts = 0x0, nelts = 0, next = 0x0}, size = 1, nalloc = 0, pool = 0x0},  
connection\_n = 0, files\_n = 0, connections = 0x0, read\_events = 0x0,  
write\_events = 0x0, old\_cycle = 0x0, conf\_file = {  
len = 0, data = 0x0}, conf\_param = {len = 0, data = 0x0},  
conf\_prefix = {len = 1, data = 0x0}, prefix = {len = 0, data = 0x0},  
lock\_file = {len = 0, data = 0x0}, hostname = {len = 0, data = 0x0}}  
ccf =

Posted at Nginx Forum:

> **[1.3.12 occasional segfaults](https://forum.nginx.org/read.php?2,236409,236409#msg-236409)**
>
> It's a fairly vanilla install of nginx (with the exception of the SPDY patch). We are seeing roughly 1 segfault every hour or so on each web server... I didn't generate a debugging log, because I wasn't sure how big something like that would be for...

---

<div class="post-metadata">

**Author:** ![digitalpoint](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/6a8cbe/32.png) [@digitalpoint](https://www.ruby-forum.com/u/digitalpoint)\
**Post date:** [February 21, 2013, 11:00am UTC](https://www.ruby-forum.com/t/1-3-12-occasional-segfaults/226786/2 "2013-02-21T11:00:54Z")

</div>

On Thursday 21 February 2013 11:39:04 digitalpoint wrote:

> It’s a fairly vanilla install of nginx (with the exception of the SPDY  
> patch). We are seeing roughly 1 segfault every hour or so on each web  
> server… I didn’t generate a debugging log, because I wasn’t sure how big  
> something like that would be for an entire hour, but I can if needed.

First of all, please update nginx and spdy-patch to the latest versions:  
[http://nginx.org/download/nginx-1.3.13.tar.gz](http://nginx.org/download/nginx-1.3.13.tar.gz)  
[http://nginx.org/patches/spdy/patch.spdy-65\_1.3.13.txt](http://nginx.org/patches/spdy/patch.spdy-65_1.3.13.txt)

It is possible that the problem is already solved.

wbr, Valentin V. Bartenev

–

> **[F5 NGINX: Built for cloud-native apps. Ready for AI traffic.](https://www.f5.com/products/nginx)**
>
> Deliver modern applications with NGINX. Explore high-performance load balancing, API gateways, and web server solutions trusted by top global enterprises.

> **[nginx: donation](http://nginx.org/en/donation.html)**

> –with-openssl=/home/software\_source/openssl-1.0.1c --with-cc-opt=‘-I  
> /usr/local/ssl/include’ --with-ld-opt=‘-L /usr/local/ssl/lib’  
> –without-http\_proxy\_module --without-http\_ssi\_module  
> –with-http\_ssl\_module --with-http\_stub\_status\_module  
> –with-http\_spdy\_module

[…]

---

<div class="post-metadata">

**Author:** ![digitalpoint](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/6a8cbe/32.png) [@digitalpoint](https://www.ruby-forum.com/u/digitalpoint)\
**Post date:** [February 22, 2013, 1:52am UTC](https://www.ruby-forum.com/t/1-3-12-occasional-segfaults/226786/3 "2013-02-22T01:52:26Z")

</div>

Yeah sorry… I didn’t see 1.3.13 came out the day prior. Either way,  
glad  
whatever it was seems to have been fixed before I asked… Upgrading to  
1.3.13 and the occasional segfaults stopped.

Posted at Nginx Forum:

> **[Re: 1.3.12 occasional segfaults](https://forum.nginx.org/read.php?2,236409,236454#msg-236454)**
>
> It's a fairly vanilla install of nginx (with the exception of the SPDY patch). We are seeing roughly 1 segfault every hour or so on each web server... I didn't generate a debugging log, because I wasn't sure how big something like that would be for...
