[squid-users] Problem with ssl_crtd

[Amos Jeffries]

On 2016-12-29 06:16, Eduardo Carneiro wrote:
> Hi everyone.
> 
> I have a strange issue with my squid 3.5.19. When I enable ssl-bump and
> url_rewrite in order to make dynamic content cache,


URL has nothing to do with cachability of dynamic content.
If that content is not cachign by default then you probably still have 
some very outdated rules in your squid.conf prohibiting that content 
from being stored.



> I've got, sporadically,
> this error in my cache.log:
> 
> /assertion failed: Read.cc:69: "fd_table[conn->fd].halfClosedReader !=
> NULL"/
> 
> When the error occur, my squid simply stops.
> 
> Here is a part of my cache.log:
> 
> ---
> 2016/12/28 12:29:17 kid1| assertion failed: Read.cc:69:
> "fd_table[conn->fd].halfClosedReader != NULL"


<http://bugs.squid-cache.org/show_bug.cgi?id=4270>


> 2016/12/28 12:36:21 kid1| helperOpenServers: Starting 5/32 'ssl_crtd'
> processes
> FATAL: Ipc::Mem::Segment::open failed to
> shm_open(/squid-ssl_session_cache.shm): (2) No such file or directory
> 
> Squid Cache (Version 3.5.19): Terminated abnormally.
> 

Hmm, seems there is a part of bug 3805 still present
  <http://bugs.squid-cache.org/show_bug.cgi?id=3805>

> ---
> 
> If I disable ssl-bump and url_rewrite, the error does not occur. I saw 
> here
> in the list that this were a bug on squid 3.4, but I'm using squid 
> 3.5.19.
> 
> Someone knows how to fix this?

The bug about it is still open. That usually means no.

However, I think we should look at why you have resorted to screwing 
around with URLs to "make dynamic content cache". Squid-3.2 and later 
are quite good at caching dynamic content. Current 3.5 have even reached 
the point where private content can be cached safely.

  What is your squid.conf?
  and what do you have the re-writer doing?

Amos