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

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]

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

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. :(

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

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.

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.

Hi,

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

Set to manual

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

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.

Hi all,

so when 130302 doesn't fix it... why the hack these messages stopped when installing this pattern version ?

Cheers,
Chris

But i can't update nothing happen... but perhaps it's stoped i wait for the fix :) 

I did the same thing, but pressing the update button does nothing in my case (it supposedly updates in the background, but that doesn't really seem to do anything). How big ARE those pattern updates?

EDIT: It seems there's a new pattern: 130303 - I was able to manually download that one.

EDIT 2: Pattern 130303 still causes the faults!

BTW: Is it safe to remove the files in /var/storage/cores?

Now i have the latest version but that doesn't fix the problem. Only disable the Application control can stop that error until we get some new patterns :)