<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div><br>
</div>
<div><br>
</div>
<div>On Mon, 2016-10-03 at 11:33 -0600, Alex Rousskov wrote:</div>
<blockquote type="cite">
<pre>On 10/03/2016 04:50 AM, Jasper Van Der Westhuizen wrote:
<blockquote type="cite">
This morning I had some problems with some of our proxies. 2 Proxies in
cluster A crashed with the below errors. The shortly afterwards 4 in
cluster B did the same. Both clusters are configured to run their cache
in memory with SMP and 4 workers configured.
FATAL: Received Bus Error...dying.
</blockquote>
There are at least two possible reasons:
1. A bug in Squid and
2. Memory overallocation by the OS kernel.
To fix the former, the developers will need a stack trace (at least). I
recommend filing a bug report after getting that trace and excluding
reason #2. Squid wiki and various system administration guides explain
how to make Squid dump core files.
To check for memory overallocation, you can temporary start Squid v4.0
with "shared_memory_locking on". Unfortunately, that squid.conf
directive is not available in Squid v3. You may be able to emulate it
using some OS-specific sysctl or environment variables, but doing so may
be far from trivial, and I do not have instructions.
</pre>
</blockquote>
<div><br>
</div>
<div>Thanks Alex. We have patched the servers to the latest and will monitor. If it happens again I will fill in a bug report and see where it takes us. </div>
<div><br>
</div>
<div>Regards</div>
<div>Jasper</div>
<div><br>
</div>
<br>
<br>
<mc type="body"><br>
<br>
<font face="Arial;" size="1">Disclaimer:<br>
<a href="http://www.shopriteholdings.co.za/Pages/ShopriteE-mailDisclaimer.aspx" target="_blank">http://www.shopriteholdings.co.za/Pages/ShopriteE-mailDisclaimer.aspx</a>
</font>
</body>
</html>