Thread Info
  • State Verified Answer
  • +14 person also asked this people also asked this
  • Locked Locked
  • Replies 67 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 119035 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

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

R0n1

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
  • 0

    I've the same problem since today morning. 

     

    2017:08:07-10:27:27 gateway01-1 kernel: [1598882.432805] NAVLWorker_01[29078]: segfault at 50813da1 ip 00000000f68485da sp 00000000e8cb3fec error 4 in libc-2.11.3.so[f67cc000+16c000]

    2017:08:07-10:28:49 gateway01-1 kernel: [1598964.521499] NAVLWorker_29[29471]: segfault at 11f5a000 ip 00000000f68255e1 sp 00000000e5474f8c error 4 in libc-2.11.3.so[f67a9000+16c000]

    2017:08:07-10:30:14 gateway01-1 kernel: [1599049.706193] NAVLWorker_09[29991]: segfault at 11ffa000 ip 00000000f68185e1 sp 00000000e7c7bfbc error 4 in libc-2.11.3.so[f679c000+16c000]

    2017:08:07-10:32:33 gateway01-1 kernel: [1599189.149697] NAVLWorker_10[30471]: segfault at fb04b982 ip 00000000f68b45e1 sp 00000000e7b16fec error 4 in libc-2.11.3.so[f6838000+16c000]

    2017:08:07-10:34:11 gateway01-1 kernel: [1599287.004292] NAVLWorker_03[31023]: segfault at 11242000 ip 00000000f68ba5e1 sp 00000000b8f0ffec error 4 in libc-2.11.3.so[f683e000+16c000]

    2017:08:07-10:35:05 gateway01-1 kernel: [1599341.131014] NAVLWorker_20[31309]: segfault at 11ff4000 ip 00000000f68a85e1 sp 00000000e6700fbc error 4 in libc-2.11.3.so[f682c000+16c000]

    2017:08:07-10:36:29 gateway01-1 kernel: [1599424.552923] NAVLWorker_04[31796]: segfault at de41a000 ip 00000000f68395e1 sp 00000000e86a1fec error 4 in libc-2.11.3.so[f67bd000+16c000]

    2017:08:07-10:37:40 gateway01-1 kernel: [1599495.824539] NAVLWorker_30[32257]: segfault at e58e9000 ip 00000000f68965e1 sp 00000000e52e4fbc error 4 in libc-2.11.3.so[f681a000+16c000]

    2017:08:07-10:40:52 gateway01-1 kernel: [1599688.116735] NAVLWorker_29[32500]: segfault at 4f4ca647 ip 00000000f68585da sp 00000000e54a7fbc error 4 in libc-2.11.3.so[f67dc000+16c000]

    2017:08:07-10:42:01 gateway01-1 kernel: [1599757.564248] NAVLWorker_25[531]: segfault at 11f62000 ip 00000000f680c5e1 sp 00000000e5c5ffbc error 4 in libc-2.11.3.so[f6790000+16c000]

  • 0 in reply to renehoehle

    Same here with Pattern 130296

    Auto Update for pattern was activated in 15min step but did not update to 130302

    Manually updating patterns did the trick.

    Cheers,
    Chris

  • 0 in reply to ChrisBKA

    ChrisBKA said:
    Manually updating patterns did the trick.

    Stupid question, but how did you manually update? Changing the update interval to manual and pressing the update button did nothing for me. :(

  • 0 in reply to Mateusz Bender

    Yeee, just wait some time ... did it the same way ... up2date maybe exhausted ;-)

  • 0 in reply to ChrisBKA

    I've made an manual update but it tells me that there is no newer version available. 

    Starting Up2Date Download
    No new packages available, exiting.

  • 0 in reply to renehoehle

    Hi,

    this is not up2date... go to up2date->Config->Pattern interval

    Set to manual

    as soon as i did this. it told me this:

  • 0 in reply to renehoehle

    I've talked to the support a few minutes ago. He said that there was a faulty pattern update at 09:05 CEST and the developers will provide an old pattern to fix it in an hour.

Reply Children
Unfiltered HTML