On 23/10/18 6:45 AM, Alex Rousskov wrote: > On 10/22/18 8:38 AM, Julian Perconti wrote: > >> assertion failed: http.cc:1530: "!Comm::MonitorsRead(serverConnection->fd)" > >> Any idea? > > Without the stack trace, it is difficult to say much about this bug. > Please collect a stack trace from the crash and post it to Squid > bugzilla. If the stack trace looks similar to that in Bug 4896, please > post it there: https://bugs.squid-cache.org/show_bug.cgi?id=4896 > > If you do not know how to enable core dumps and/or how to collect a > stack trace, please search Squid wiki for pointers or consult your local > sysadmin. >
FWIW I'm not seeing any changes in those Squid versions which relate to persistent connection or pipeline handling. There is <https://bugs.squid-cache.org/show_bug.cgi?id=4673> from last year which still lacks any hints about what might be causing it. FYI: Details on obtaining backtrace info can be found at <https://wiki.squid-cache.org/SquidFaq/BugReporting>. This issue though spans multiple transactions. So we will need a detailed (ALL,9 if possible) cache.log trace of everything that FD has been used for in addition to the trace. The trace itself is useful for identifying the code path and FD value to look at within that log. Amos _______________________________________________ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
