Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 9 replies
  • Subscribers 31 subscribers
  • Views 11918 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

Unable to Categorize any website

hatem elkalaawy

Content Filter has been unable to categorize my web traffic.  When I do a test URL lookup, the category is Uncategorized and the description is now "Unable to Categorize". Restart has not solved the problem

Anyone know how to fix it and show me the categories of websites?



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to Michael Dunn

    i don't use upstream proxy.

    but it is solved by made any modification on dns settings like change order or replace one, something like internal dns need to refresh.

  • 0 in reply to Michael Dunn

    Hello 

    I'm going trough the same problem 

    all sites are Uncategorized

    /log/nSXLd.log

    [2018-09-04 14:51:44] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:44] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files
    [2018-09-04 14:51:45] <1994557376> [error] nSXLd: Unable to create socket because: Too many open files

     

    CR100iNG (SFOS 17.0.8 MR-8)

     

    thanks if anybody could help me 

     

  • 0 in reply to rdebraga

    Hi,

     

    this is caused by a bug we've fixed in SFOS 17.1.

    Please update your appliance to the latest version.

     

    Regards,

    Janos