We've been running pre-9.4xx releases on SG450 smoothly since initial deployment. However, after upgrading to 9.402-7 in Jun, unexpected httpproxy segfault comes:
/var/log/kernel/2016/06/kernel-2016-06-15.log.gz:2016:06:15-17:10:43 sophos450-2 kernel: [1582959.343159] httpproxy[6930]: segfault at 80cc3a0 ip 00000000f73f37f9 sp 00000000ecb01f58 error 7 in libglib-2.0.so.0.2200.5[f73df000+c5000]
/var/log/kernel/2016/06/kernel-2016-06-15.log.gz:2016:06:15-17:24:58 sophos450-1 kernel: [1583461.042708] httpproxy[7004]: segfault at 3534314d ip 00000000f748b85e sp 00000000ee78ff60 error 4 in libglib-2.0.so.0.2200.5[f745f000+c5000]
And after we upgraded to 9.404-5, it keeps coming:
/var/log/kernel/2016/07/kernel-2016-07-27.log.gz:2016:07:27-09:04:32 sophos450-2 kernel: [2212858.251975] EpollWorker_25[8452]: segfault at 0 ip 00000000f6a864d1 sp 00000000f2b8ff2c error 4 in libc-2.11.3.so[f6a0c000+16c000]
Such segfault is so nasty that it freezes up the web UI, doesn't restart in timely fashion, doesn't trigger HA failover, and prevents reboot in web UI or SSH. We have to physically attend to the device to reboot. We've contacted support and they've collected some logs already. But my gut feeling tells me that they might not come up with solution soon.
Not sure if anybody have the similar experience on this?
This thread was automatically locked due to age.
