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 is running on more than 100% CPU since 9.101

Gentlemen,

with version 9.101, we had several reports from customers that the HTTP Proxy is running under heavy load. We could identify the issue and track it internally under:

26192: Since 9.101 http proxy is running on more than 100% cpu load


If you experience that behaviour, please contact our support teams refering to that post. They will give you a patch for the issue.

The official fix is scheduled for 9.102, planned for end of June.

Regards,
Dominic


This thread was automatically locked due to age.
  • Hello,

    great news.
    When will 9.102 expected to be on GA?

    Thx,

    Manuel
  • isn't it a faster, better solution to provide a mini-up2date/ file download when this problem is known? [:S]

    I think that would also help supporters to concentrate on other problems than this one

    ---

  •  
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • Can home users get the patch ? [:D]
  • Hello,

    rpm patch from Sophos support.
  • After a lot of

    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x184e20d0" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "
    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x184d0b00" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "
    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x183020d0" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "
    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x18305908" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "
    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x18304ac8" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "
    2013:06:12-13:09:35 ********* httpproxy[8449]: id="0003" severity="info" sys="SecureWeb" sub="http" request="0x184e2cd0" function="urid_categorize_url" file="uri_scanner.c" line="246" message="urid_query failed: (-2) "


    the http proxy CPU went down. Hopefully they will fix the segfault issue for release 9.102
  • Gents,

    two things on that issue for understanding:

    1: This is not related to any SAVI pattern but to another change in HTTP proxy in 9.101.

    2: Please contact support to receive a patch rather than installing *ANY* patch without confirmation from Sophos support.

    Regards
    Dominic
  • Gents,

    two things on that issue for understanding:

    1: This is not related to any SAVI pattern but to another change in HTTP proxy in 9.101.

    2: Please contact support to receive a patch rather than installing *ANY* patch without confirmation from Sophos support.

    Regards
    Dominic


    Thanks Dominic

    Home users are unable to contact support. Will they receive the patch or should they wait until 9.102(ETA end of june)?
  • I've got the same problem and changing to avira as mentioned in the other thread doesn't help much. 
    Somehow I lost my product registration in the change vorm astaro to sophos. Although I registered the update licenses in January.
  • The patch is available at http://download.astaro.de/UTM/v9/rpms/9.101/

    Please make sure that you or your customer is really affected by this problem. If your device runs with high CPU load, please make sure using the command 'top' that the httpproxy process is making the device busy. Once confirmed you can download the patch and install it using the command 

    'rpm -Uvh ep-httpproxy-9.10-75.g51d5937.i686.rpm'.

    Restart the HTTP proxy.

    I hope this helps!

    Regards
    Dominic