Thread Info
  • Locked Locked
  • Replies 3 replies
  • Subscribers 3 subscribers
  • Views 9432 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

KWyrick1

I'm getting this about every 30 minutes to an hour. We were getting that error on our old ASG220, running 9.411-3, constantly to the point we had to reboot it 3 or 4 times a day. We purchased a new 135, loaded 4.11-3 from ISO and restored out backup. We are still getting the errors.

[INFO-141] Http proxy not running - restarted

Followed by

[CRIT-310] Up2Date prefetch failed

Followed by

[INFO-310] Up2Date prefetch is working again

Over and over again.

I get this in the self monitoring log. This is not the entire log, just a sample but it repeats over and over.

I get these in the kernel logs

2017:04:07-01:18:24 asg kernel: [202795.148826] httpproxy[27967]: segfault at 0 ip 00000000f7365103 sp 00000000ebbc6a30 error 4 in libtcmalloc.so.4.1.0[f733e000+48000]

 

Any ideas?

2017:04:07-00:42:53 asg selfmonng[4005]: [INFO-141] Http proxy not running - restarted
2017:04:07-00:42:53 asg selfmonng[4005]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 sent
2017:04:07-00:42:53 asg selfmonng[4005]: W triggerAction: 'cmd'
2017:04:07-00:42:53 asg selfmonng[4005]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2017:04:07-00:42:55 asg selfmonng[4005]: W child returned status: exit='0' signal='0'
2017:04:07-00:50:15 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 1 - 3
2017:04:07-00:50:20 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 2 - 3
2017:04:07-00:50:25 asg selfmonng[4005]: W check Failed increment httpproxy_running counter 3 - 3
2017:04:07-00:50:25 asg selfmonng[4005]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2017:04:07-00:50:25 asg selfmonng[4005]: W triggerAction: 'cmd'
2017:04:07-00:50:25 asg selfmonng[4005]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2017:04:07-00:50:27 asg selfmonng[4005]: W child returned status: exit='0' signal='0'
2017:04:07-01:07:38 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 1 - 3
2017:04:07-01:07:43 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 2 - 3
2017:04:07-01:07:48 asg selfmonng[4005]: W check Failed increment httpproxy_running counter 3 - 3
2017:04:07-01:07:48 asg selfmonng[4005]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2017:04:07-01:07:48 asg selfmonng[4005]: W triggerAction: 'cmd'
2017:04:07-01:07:48 asg selfmonng[4005]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2017:04:07-01:07:50 asg selfmonng[4005]: W child returned status: exit='0' signal='0'
2017:04:07-01:18:40 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 1 - 3
2017:04:07-01:18:45 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 2 - 3
2017:04:07-01:18:50 asg selfmonng[4005]: W check Failed increment httpproxy_running counter 3 - 3
2017:04:07-01:18:50 asg selfmonng[4005]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2017:04:07-01:18:50 asg selfmonng[4005]: W triggerAction: 'cmd'
2017:04:07-01:18:50 asg selfmonng[4005]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2017:04:07-01:18:52 asg selfmonng[4005]: W child returned status: exit='0' signal='0'
2017:04:07-01:27:17 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 1 - 3
2017:04:07-01:27:22 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 2 - 3
2017:04:07-01:27:27 asg selfmonng[4005]: W check Failed increment httpproxy_running counter 3 - 3
2017:04:07-01:27:27 asg selfmonng[4005]: W NOTIFYEVENT Name=httpproxy_running Level=INFO Id=141 suppressed
2017:04:07-01:27:27 asg selfmonng[4005]: W triggerAction: 'cmd'
2017:04:07-01:27:27 asg selfmonng[4005]: W actionCmd(+):  '/var/mdw/scripts/httpproxy restart'
2017:04:07-01:27:29 asg selfmonng[4005]: W child returned status: exit='0' signal='0'
2017:04:07-01:45:40 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 1 - 3
2017:04:07-01:45:45 asg selfmonng[4005]: I check Failed increment httpproxy_running counter 2 - 3
2017:04:07-01:45:50 asg selfmonng[4005]: W check Failed increment httpproxy_running counter 3 - 3
2017:04:07-01:45:50 asg selfmonng[4005]: [INFO-141] Http proxy not running - restarted


This thread was automatically locked due to age.
Parents

  • [CRIT-310] Up2Date prefetch failed

    Followed by

    [INFO-310] Up2Date prefetch is working again

    That's an indication that your ISP isn't very reliable.  There's an outside chance it could be solved with DNS best practice.

    "Http proxy not running - restarted" is something I see from several devices.  If you think it's causing a problem, get a case open with Sophos Support and then let us know what they told you.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • in reply to BAlfson

    I opened a case day before yesterday and am waiting on them to contact me.

  • in reply to KWyrick1

    This was the result of a bug known to support. NUTM-6867

    Support indicated that not all appliances have this issue. An indication is to access the UTM via ssh and look in /var/storage/cores and look for numerous httpproxy core dumps with the current days date.

    Support has a fix they can apply. They also indicated the bug will be fixed in the next update however, update 9.412-2 doesn't mention it.

     

Reply
  • in reply to KWyrick1

    This was the result of a bug known to support. NUTM-6867

    Support indicated that not all appliances have this issue. An indication is to access the UTM via ssh and look in /var/storage/cores and look for numerous httpproxy core dumps with the current days date.

    Support has a fix they can apply. They also indicated the bug will be fixed in the next update however, update 9.412-2 doesn't mention it.

     

Children
No Data
Unfiltered HTML