Filtering proxy fails at "Initialising Distributed Intellegence Architecture"

February 04, 2013 • Customer Services       

If the Filtering Proxy service fails with the error "Initialising Distributed Intellegence Architecture" then it could indicate a problem with connectivity or the URL database. This article explains how to fix it.

This article is out of date. Please check the new Documentation Portal for CensorNet Professional.

If the Filtering Proxy fails with the message "Initialising the DIA database" what's happening is that the URL database can't be initialised for some reason. This normally means that either DNS or the internet connection is failing, or that there's something wrong with the URL database. In 90% of the cases, its the connectivity rather than the database.

What the URL database needs to do on first start is to initialise itself. It does this by connecting to our servers over the Internet. If there's an issue with the connectivity, be it DNS or access, then the filtering proxy can't start.

When this happens the procedure to solve it is as follows:

1. Check the DNS lookup is working from the command line. Run (for example):


or similar and verify this is correct and not delayed.

2. Check the internet connectivity. There's two ways to do this:

    - If there's no upstream proxy in use, you can just telnet directly to port 80 - eg

telnet 80

    - If there is an upstream proxy in use, run the folowing commands to install and use a text-based browser (yes, there is still such a thing!)

export http_proxy=
apt-get install lynx

    Once this is installed, you can run it again at any time. Use the "export http_proxy=" line to set the command line to use the censornet setup for the upstream and run:


3. If the above all checks out ok, then the problem is probably a corrupt URL database. You can fix this by running:

/etc/init.d/cnv4 stop
mkdir /tmp/sitefilter
mv /usr/share/cnv4/sitefilter/* /tmp/sitefilter
/etc/init.d/cnv4 start

Then go to the Filters -> URL Database Updates menu option and re-download the URL database.

If none of the above workarounds solve the problem then please contact Technical Support.



Related articles

Last modified on Mon, February 04, 2013 « Back