> > Program received signal SIGHUP, Hangup. Yes, I did not realized that I have executed 'squid -k reconfigure', hence that SIGHUP signal. I don not know if the following is relevant but: When the exception occurred, I had executed (earlier) 'squid -k reconfigure'. Then, I made a full squid stop and clean squid start, then entered the site that caused Squid to crash and did not happen again, I tried many times without reach the crash again. > > By other hand, what can I do with those squid's crashes? > > Please try the patch for bug 4864. That bug may be a duplicate of bug 4896, > and it has an unpolished/unofficial fix: Let me know if I patched correctly: ~ (...)/squid-4.3-20181021-r17614d5# patch -p1 < /etc/squid/debug/patches/SQUID-385-Comm_MonitorsRead-assertion-t3.patch patching file src/FwdState.cc (without errors nor warnings) make/make install and start Squid from systemd (i.e.: systemctl start squid.service) instead of gdb. And now when I try to connect to site that made squid to crash, I get an error page from squid (instead of chrome page, like before) telling the same thing with different words: "(...): (104) Connection reset by peer". And Squid does not crash. Even doing a squid -k reconfigure and access again to that site, does not crash. Anyway I am going to run squid via gdb again, and wait for a similar crash. > https://bugs.squid-cache.org/show_bug.cgi?id=4864 > > Please update bug 4896 to let us know whether bug 4864 fix worked for you > (including cases where the posted patch no longer applies). I'll let you know if the patch definitely solves the bug , after test it few days. Thank You! _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
