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

[INFO-141] Http proxy not running - restarted notification + segfaults in kernel log since this morning

Update 11:27 Sophos official workaround https://community.sophos.com/kb/en-us/127257
Update 13:48 Sophos fix: https://community.sophos.com/kb/en-us/127257 A new pattern called u2d-appctrl43-9-42 was recently released to resolve this issue. Please enable application control again. Manual Cleanup required /var/storages/cores could contain large coredump files that need to be manually removed.

Good morning,

 

This morning we received multiple  [INFO-141] Http proxy not running - restarted notifications around 09:11


When looking in the log's it seemed it occured straight after an up2date pattern update.

Looking in the kernel logs:

2017:08:07-09:11:17 gateway-1 kernel: [1448439.994411] NAVLWorker_01[31756]: segfault at 18b09499 ip 00000000f68495da sp 00000000e8cc0fec error 4 in libc-2.11.3.so[f67cd000+16c000]
2017:08:07-09:24:28 gateway-1 kernel: [1449231.586930] NAVLWorker_10[32179]: segfault at e78ba000 ip 00000000f68045e1 sp 00000000c36d8fbc error 4 in libc-2.11.3.so[f6788000+16c000]
2017:08:07-09:25:09 gateway-1 kernel: [1449272.038211] NAVLWorker_01[5095]: segfault at e9122000 ip 00000000f68875e1 sp 00000000bed45fbc error 4 in libc-2.11.3.so[f680b000+16c000]
2017:08:07-09:26:18 gateway-1 kernel: [1449341.488162] NAVLWorker_08[5501]: segfault at 4ca50b2b ip 00000000f68625df sp 00000000e7ed2fbc error 4 in libc-2.11.3.so[f67e6000+16c000]





This thread was automatically locked due to age.
Parents
  • We've got same issue (firmware 9.502-4)

     

    2017:08:07-10:11:50 sophos-2 kernel: [1613257.964536] NAVLWorker_19[12891]: segfault at ec0d7000 ip 00000000f68965c6 sp 00000000e6904fe8 error 4 in libc-2.11.3.so[f681a000+16c000]
    2017:08:07-10:12:25 sophos-2 kernel: [1613292.257840] NAVLWorker_28[14135]: segfault at 1e0c0000 ip 00000000f67e35c6 sp 00000000e5648fb8 error 4 in libc-2.11.3.so[f6767000+16c000]
    2017:08:07-10:28:05 sophos-2 kernel: [1614233.168712] NAVLWorker_15[14542]: segfault at 1e0c0000 ip 00000000f67e25e1 sp 00000000e7054f8c error 4 in libc-2.11.3.so[f6766000+16c000]
    2017:08:07-10:29:11 sophos-2 kernel: [1614299.394111] NAVLWorker_01[23030]: segfault at ade60000 ip 00000000f680a5e1 sp 00000000e8c8afbc error 4 in libc-2.11.3.so[f678e000+16c000]
    2017:08:07-10:36:07 sophos-2 kernel: [1614715.150723] NAVLWorker_29[23616]: segfault at 2dc52523 ip 00000000f68015da sp 00000000e5465fbc error 4 in libc-2.11.3.so[f6785000+16c000]
    2017:08:07-10:41:16 sophos-2 kernel: [1615023.963992] NAVLWorker_01[27413]: segfault at 1e0c0000 ip 00000000f67ff5e1 sp 00000000e8c7ffbc error 4 in libc-2.11.3.so[f6783000+16c000]

Reply
  • We've got same issue (firmware 9.502-4)

     

    2017:08:07-10:11:50 sophos-2 kernel: [1613257.964536] NAVLWorker_19[12891]: segfault at ec0d7000 ip 00000000f68965c6 sp 00000000e6904fe8 error 4 in libc-2.11.3.so[f681a000+16c000]
    2017:08:07-10:12:25 sophos-2 kernel: [1613292.257840] NAVLWorker_28[14135]: segfault at 1e0c0000 ip 00000000f67e35c6 sp 00000000e5648fb8 error 4 in libc-2.11.3.so[f6767000+16c000]
    2017:08:07-10:28:05 sophos-2 kernel: [1614233.168712] NAVLWorker_15[14542]: segfault at 1e0c0000 ip 00000000f67e25e1 sp 00000000e7054f8c error 4 in libc-2.11.3.so[f6766000+16c000]
    2017:08:07-10:29:11 sophos-2 kernel: [1614299.394111] NAVLWorker_01[23030]: segfault at ade60000 ip 00000000f680a5e1 sp 00000000e8c8afbc error 4 in libc-2.11.3.so[f678e000+16c000]
    2017:08:07-10:36:07 sophos-2 kernel: [1614715.150723] NAVLWorker_29[23616]: segfault at 2dc52523 ip 00000000f68015da sp 00000000e5465fbc error 4 in libc-2.11.3.so[f6785000+16c000]
    2017:08:07-10:41:16 sophos-2 kernel: [1615023.963992] NAVLWorker_01[27413]: segfault at 1e0c0000 ip 00000000f67ff5e1 sp 00000000e8c7ffbc error 4 in libc-2.11.3.so[f6783000+16c000]

Children