Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 1031 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

[7.011] Categorisation Errors

James Bourne
Proxy in transparent mode
ASG 7.011 Active/Passive cluster on ESX Server 3.0.2

All web traffic passing the HTTP proxy fails due to a categorization error. If I turn off the proxy or setup a skip list everything works fine.

Is Categorisation broken again?


This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to lonjones
    I think Astaro is not compiled to support a large number of TCP/IP connections and/or its packet processing engine has limited capacity. When Astaro gets "busy" doing something that requires a lot of connections (say BitTorrent or even the fast download of a single large file), then Astaro's other services do not work, or do not work reliably. This may result in the so-called "categorization error". I have seen this latter error many times whenever I am using BitTorrent.

    The larger question is, of course, why does this sort of error occur? One user mentioned that Astaro phones home to talk to some sort of master server on every single HTTP filter request. If this is true, it would explain some of the glitches as it may not be possible to connect back to this master server within a specified timeframe.

    I am hoping Astaro can shed a bit more light on how the HTTP filter works and when it would start producing these sorts of "categorization" errors.
  • 0 in reply to proxyagenda
    If you're on 7.011, definitely try 7.100 ... it seems to have taken care of those errors (at least so far)... if you're on 6.312, maybe now's the time to consider moving up as well.

    CTO, Convergent Information Security Solutions, LLC

    https://www.convergesecurity.com

    Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries.  Use the advice given at your own risk.

  • 0 in reply to BrucekConvergent
    Hmmm ... I'll let everyone else beta test 7.100 for a while O_o.
  • 0 in reply to James Bourne
    Hi proxyagenda,
    that was my summation during beta testing of v7.008 to v7.010. I even experienced the problems when I upgraded from 1500/512 to 4000/800. I guessed the issue being to a timing one in the proxy, the timeout being too short.

    The problem doesn't seem to be happening at all in v7.100.

    Ian M