Hi Tov, while you aren't running the http proxy would you at least review your kernel log to see if there are any entries similar to that shown in the other thread. This might help debug the error.
2010:09:26-01:29:25 ****** kernel: httpproxy[1089]: segfault at 0 ip 00000000f72ff733 sp 00000000dc5fb19c error 4 in libc-2.9.so[f728c000+155000]
2010:09:26-03:06:27 ****** kernel: httpproxy[4360]: segfault at 0 ip 00000000f73ac733 sp 00000000dbffa19c error 4 in libc-2.9.so[f7339000+155000]
2010:09:26-08:26:42 ****** kernel: httpproxy[15743]: segfault at a ip 00000000f73d070b sp 00000000daff819c error 4 in libc-2.9.so[f735d000+155000]
2010:09:26-10:16:34 ****** kernel: httpproxy[18832]: segfault at 0 ip 00000000f7300733 sp 00000000dadf819c error 4 in libc-2.9.so[f728d000+155000]
2010:09:26-21:28:28 ****** kernel: ADDRCONF(NETDEV_UP): eth2: link is not ready
2010:09:26-21:28:30 ****** kernel: e1000: eth2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX
2010:09:26-21:28:30 ****** kernel: ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
2010:09:27-14:22:44 **** kernel: httpproxy[18147]: segfault at ed9c9500 ip 00000000f19cb22d sp 00000000eb1fc210 error 4 in geoipscanner.so[f19ca000+2000]
2010:09:27-15:40:45 **** kernel: httpproxy[21700]: segfault at c0f10d3a ip 00000000f739f70b sp 00000000eb1a219c error 4 in libc-2.9.so[f732c000+155000]
I had the same issue and after disabling GEOIP I am not getting any HTTP restarts and kerner errors.(The problem has been identified by Team and are working to resolve it)