On 29/09/17 12:35, Aaron Turner wrote:
Ok, i'll work on that. One other thing, is that if I let it run long enough, squid will crash with errors like the following: FATAL: Received Bus Error...dying. 2017/09/28 23:28:09 kid4| Closing HTTP port 10.93.3.4:3128 2017/09/28 23:28:09 kid4| Closing HTTP port 127.0.0.1:3128 2017/09/28 23:28:09 kid4| storeDirWriteCleanLogs: Starting... 2017/09/28 23:28:09 kid4| Finished. Wrote 0 entries. 2017/09/28 23:28:09 kid4| Took 0.00 seconds ( 0.00 entries/sec). CPU Usage: 0.541 seconds = 0.466 user + 0.075 sys Maximum Resident Size: 121440 KB Page faults with physical i/o: 0 At first I thought the bus error was hardware, but it's happened on two different EC2 instances now.
Yes "Bus Error" is definitely hardware. The OS kernel had an error loading some data from RAM into the CPU or something along those lines.
The only things we can do about it is check that your Squid is up to date with the system environment - eg fairly recent Squid version built with the OS latest compiler version against its current libc or whatever the equivalents of those are for your system. If there are binary level issues with the libc interfaces weird things can happen.
Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
