[prev in list] [next in list] [prev in thread] [next in thread] 

List:       varnish-bugs
Subject:    Re: [Varnish] #1396: Assert error in VGZ_NewGzip(), cache_gzip.c line 209: Condition(Z_OK == i) not
From:       "Varnish" <varnish-bugs () varnish-cache ! org>
Date:       2013-12-19 14:48:55
Message-ID: 058.8755985ab60462be24517af708fea8b3 () varnish-cache ! org
[Download RAW message or body]

#1396: Assert error in VGZ_NewGzip(), cache_gzip.c line 209: Condition(Z_OK == i)
not true.
----------------------+--------------------
 Reporter:  geoff     |       Owner:
     Type:  defect    |      Status:  new
 Priority:  normal    |   Milestone:
Component:  varnishd  |     Version:  3.0.3
 Severity:  major     |  Resolution:
 Keywords:  gzip      |
----------------------+--------------------

Comment (by geoff):

 Some sensitive data in the panic.log has been masked.

 The crash happened once in production some time ago (there may have been a
 billion requests since then), so the problem is not urgent.

 zlib may have attempted a malloc that failed -- errno is ENOMEM, and one
 of the possible return codes from deflateInit2() is Z_MEM_ERROR (not
 enough memory).

 I think that varnishd can throw a 503 error when this happens, rather than
 crashing. That would have the added benefit that the return value from
 deflateInit2() could be recorded in the log, making it easier to
 understand what the problem.

-- 
Ticket URL: <https://www.varnish-cache.org/trac/ticket/1396#comment:1>
Varnish <https://varnish-cache.org/>
The Varnish HTTP Accelerator

_______________________________________________
varnish-bugs mailing list
varnish-bugs@varnish-cache.org
https://www.varnish-cache.org/lists/mailman/listinfo/varnish-bugs
[prev in list] [next in list] [prev in thread] [next in thread]