> -----Original Message-----
> From: [EMAIL PROTECTED]
> On Behalf Of [EMAIL PROTECTED]
> Sent: Tuesday, August 20, 2002 10:53 PM
>
> After 8 months of running SquidGuard successfully and reinstalling it at
> least 5 times successfully, I am having problems.
You don't mention if anything has ever changed... Did you install and
reinstall on the same system 5 times successfully, and now you are
having problem reinstalling it the 6th time on that system? Or were
all of your successes on one system, and the problem on a different
system? Mandrake worked and Red Hat doesn't? Red Hat 6.2 worked and
7.1 doesn't? Those details might be important.
> Red Hat 7.1 With Squid 2.3 STABLE4-10 SquidGuard 1.1.4 13mdk RPM.
Just for reference: I'm running a Red Hat 7.1 system that was
installed from the Red Hat CDs and subsequently maintained under their
up2date program, and my version numbers are RH 7.1, Squid 2.4 STABLE6
and squidGuard 1.20.
squidGuard 1.1.4 was released in April/2000, and the current version,
1.2.0, was released in December/2001.
> I even use the same conf files for Squid and SquidGuard, just make
> sure my formula is consistent until I learn it.
We don't know anything about the previous system or network, so we
don't know if that is a good plan or a bad plan.
> when I try to go to the web Squid answers but not Squid Guard,
> even though it is running, (I check all running processes) example, I can
> get to all the porn even though the test porn site is in the "domains"
> list. If I try to go to a bogus site squid (not sqidGuard) comes back with
> the error message...
You would get the same results if squidGuard was approving all of the
requests that it receives from Squid, which is what squidGuard would do
if it was running in emergency mode. What entries are being logged into
squidGuard.log?
> It seems as if Squid is not calling SquidGuard.. What must I do
> now.. I am fairly new, and so I stick to using RPM's even though I run this
> one from the command line. the exact pharse is:
> rpm -i nodeps squidGuard-1.1.4-13mdk.i586.rpm
Your statement ("I am fairly new, and so I stick to using RPM's")
indicates that you at least have a sense that installing a package
via an RPM is easier than installing the same package from a non-RPM
file. It is easier because RPM handles a bunch of important tasks so
you don't have to worry about them. For example, when you install
package 'A', RPM first verifies that all of the dependencies required
by package 'A' are in place, and will not install until they are.
(The dependencies list can be substantial and includes the
required packages and the acceptable version numbers of each.)
Which brings me to the question, why are you using the nodeps switch
when installing the squidGuard RPM? When you use the nodeps switch you
are saying to RPM, "Hey listen, don't worry about those dependencies,
I'm taking care of that and I know what I am doing". It's almost
analogous to putting your airplane on autopilot and telling it not
to worry about the heading or the altitude.
So we don't know what dependency problems exist for squidGuard 1.1.4
on your Red Hat 7.1 machine. We could make some observations based on
packages and versions included with the 7.1 distribution, e.g. the
version of the Berkeley DB included in Red Hat 7.1 is not compatible
with squidGuard 1.1.4. But RH 7.1 may include compatible versions of
required packages that you didn't select to be installed.
Whatever version of Red Hat that you use, I would recommend that you
apply all of the recommended updates before you attempt to install
squidGuard. For that reason, you might cut you workload by starting
with Red Hat 7.2 or 7.3 and applying updates from there. If you
have the space available, select the "install everything" option.
(Please don't misunderstand, I'm not suggesting that you *run* or
activate everything.)
Try to go with the current version of squidGuard. If you've installed
everything, the compile and install process for squidGuard is simply
a matter of reading and typing from the instructions. Or see if you
can get someone to put together an RPM on the current version.
If you go with squidGuard 1.2.0, you'll need version 3.29 of the
Berkeley DB. If you stick with squidGuard 1.1.4 you'll need a 2.x
version of the Berkeley DB.
I hope I haven't overwhelmed you with this; stick with it, it's
worth it.
Rick Matthews
