Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 5 subscribers
  • Views 6307 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Http proxy not running - restarted (multiple segfaults in kernel log)

isoffice

Hi all,

We have a pair of SG450 UTM Hardware Appliances (Firmware Version 9.500-9: Pattern Version 132702) running in Active-Passive mode.

Over the last 24 hours we have received 19 alerts that the HTTP Proxy has stopped and is being restarted.

The kernel log includes the following entries:

/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-03:21:23 utm425-1 kernel: [4293813.040850] EpollWorker_29[22928]: segfault at fffe6000 ip 00000000f73a1fde sp 00000000f2149be0 error 6 in libtcmalloc.so.4.1.0[f737f000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-08:32:31 utm425-1 kernel: [4312463.252385] EpollWorker_12[926]: segfault at fffe0000 ip 00000000f7337fde sp 00000000f42f0b90 error 6 in libtcmalloc.so.4.1.0[f7315000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-12:24:56 utm425-1 kernel: [4326394.943141] EpollWorker_18[13711]: segfault at fffe0000 ip 00000000f73d3fde sp 00000000f3784b60 error 6 in libtcmalloc.so.4.1.0[f73b1000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-14:32:18 utm425-1 kernel: [4334030.093115] EpollWorker_02[25867]: segfault at fffe6000 ip 00000000f734efde sp 00000000f570fb60 error 6 in libtcmalloc.so.4.1.0[f732c000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-16:10:39 utm425-1 kernel: [4339925.224453] EpollWorker_10[16013]: segfault at fffec000 ip 00000000f738afde sp 00000000f4743b60 error 6 in libtcmalloc.so.4.1.0[f7368000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-17:45:40 utm425-1 kernel: [4345620.873459] httpproxy[4187]: segfault at fffe2000 ip 00000000f73d2fde sp 00000000eef64710 error 6 in libtcmalloc.so.4.1.0[f73b0000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-19:19:27 utm425-1 kernel: [4351242.921050] EpollWorker_19[19560]: segfault at ffffa000 ip 00000000f73e1fde sp 00000000f3593b90 error 6 in libtcmalloc.so.4.1.0[f73bf000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-20:48:36 utm425-1 kernel: [4356587.260486] httpproxy[1438]: segfault at fffe8000 ip 00000000f73e2fde sp 00000000f5fac710 error 6 in libtcmalloc.so.4.1.0[f73c0000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-22:13:09 utm425-1 kernel: [4361655.541929] httpproxy[14373]: segfault at fffe8000 ip 00000000f73c2fde sp 00000000f035e710 error 6 in libtcmalloc.so.4.1.0[f73a0000+48000]
/var/log/kernel/2017/09/kernel-2017-09-26.log.gz:2017:09:26-23:35:51 utm425-1 kernel: [4366612.652705] EpollWorker_28[26613]: segfault at ffff6000 ip 00000000f73cefde sp 00000000f2371b40 error 6 in libtcmalloc.so.4.1.0[f73ac000+48000]
/var/log/kernel.log:2017:09:27-00:55:26 utm425-1 kernel: [4371382.994370] EpollWorker_23[5384]: segfault at fffec000 ip 00000000f73f2fde sp 00000000f2d9eb60 error 6 in libtcmalloc.so.4.1.0[f73d0000+48000]
/var/log/kernel.log:2017:09:27-02:12:20 utm425-1 kernel: [4375992.952093] httpproxy[17009]: segfault at ffffc000 ip 00000000f7353fde sp 00000000ea4c0710 error 6 in libtcmalloc.so.4.1.0[f7331000+48000]
/var/log/kernel.log:2017:09:27-03:25:37 utm425-1 kernel: [4380385.635096] EpollWorker_29[27798]: segfault at ffff4000 ip 00000000f73a6fde sp 00000000f214eb90 error 6 in libtcmalloc.so.4.1.0[f7384000+48000]
/var/log/kernel.log:2017:09:27-04:36:40 utm425-1 kernel: [4384644.843466] EpollWorker_29[5691]: segfault at fffe6000 ip 00000000f73b3fde sp 00000000f215bb90 error 6 in libtcmalloc.so.4.1.0[f7391000+48000]
/var/log/kernel.log:2017:09:27-06:03:36 utm425-1 kernel: [4389856.168680] EpollWorker_23[15456]: segfault at ffff8000 ip 00000000f7367fde sp 00000000f2d15b90 error 6 in libtcmalloc.so.4.1.0[f7345000+48000]
/var/log/kernel.log:2017:09:27-07:13:30 utm425-1 kernel: [4394045.674336] EpollWorker_09[27742]: segfault at ffff6000 ip 00000000f734ffde sp 00000000f4905b40 error 6 in libtcmalloc.so.4.1.0[f732d000+48000]
/var/log/kernel.log:2017:09:27-08:34:15 utm425-1 kernel: [4398885.834460] EpollWorker_16[6398]: segfault at ffff6000 ip 00000000f73adfde sp 00000000f3b60b60 error 6 in libtcmalloc.so.4.1.0[f738b000+48000]
/var/log/kernel.log:2017:09:27-09:30:17 utm425-1 kernel: [4402244.914225] EpollWorker_28[18577]: segfault at ffff0000 ip 00000000f73effde sp 00000000f2396b60 error 6 in libtcmalloc.so.4.1.0[f73cd000+48000]
/var/log/kernel.log:2017:09:27-10:43:01 utm425-1 kernel: [ 3441.990289] httpproxy[7157]: segfault at ffff6000 ip 00000000f73fbfde sp 00000000f03963e0 error 6 in libtcmalloc.so.4.1.0[f73d9000+48000]

I recall, just over a month ago, a similar issue arising (https://community.sophos.com/products/unified-threat-management/f/general-discussion/94763/info-141-http-proxy-not-running---restarted-notification-segfaults-in-kernel-log-since-this-morning) when Sophos had issued a faulty pattern update. A temporary workaround at that time was to suspend Application Control until a new pattern update was issued.

I'm wondering if anyone else has experienced this issue recently and is there the possibility that another faulty pattern update is once again the culprit?

Many thanks,

John P

 


This thread was automatically locked due to age.
Parents Reply
  • 0 in reply to isoffice

    Hi all,

    So far, so good, no restarts of HTTP proxy in approximately 24 hours.

    If I were a cynic, I would say that this issue was probably caused (again) by a dodgy Pattern Update and Sophos moved quicker than the previous occurrence to address the problem......but I'm not, so all is good :)

    John P

Children
No Data