Squidguard
-
Firefox and IE
But the problem is not on the progress bar itself, i.e. the progress bar for packages installation works sucessfully.
When I click on "Download" button, nothing happens at all.
-
Update: tried again, I don't know why, this time it worked, I got that message:
Begin blacklist update Start download. Download archive http://urlblacklist.com/cgi-bin/commercialdownload.pl?type=download Download complete Unpack archive Scan blacklist categories. Start rebuild DB. Copy DB to workdir. Reconfigure Squid proxy. Blacklist update complete.But the progress bar has never moved from 0%, and now the message above is not cleared.
-
Update: tried again, I don't know why, this time it worked, I got that message:
But the progress bar has never moved from 0%, and now the message above is not cleared.I'm working on it as time allows. A lot had to change, so mistakes are inevitable
-
No problem take your time. Thanks :)
-
Stranger & stranger,
Running on version Tue Feb 1 19:36:32 - Squidguard is working fine, updates when asked, progress bar works.
Only thing missing would be an automated update of the script.
Regards
Andrew
-
On pfSense 2.0 with IE8 not work for me.
And pfSense 1.2 with IE8 work fine.This task does not require frequent updates
-
Should have mentioned running on Firefox 3.6.13
Just the ability to run the update script once a month?
Andrew
-
Should have mentioned running on Firefox 3.6.13
Just the ability to run the update script once a month?
Andrew
Well, maybe, but later - after editing bugs.
-
Totally agree - fix bugs first (though I have found very, very few)
Just updated to latest snapshot - squidguard works fine
Regards
Andrew
-
Everything seems to be working fine after the upgrade to RC1 - but still these same message in syslog
Mar 2 07:38:59 saslpasswd2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"
Mar 2 07:38:59 saslpasswd2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"
Mar 2 07:38:59 sshlockout[31715]: sshlockout/webConfigurator v3.0 starting up
Mar 2 07:38:59 sasldblistusers2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"
Mar 2 07:38:59 sasldblistusers2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"
Mar 2 07:38:59 saslpasswd2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"
Mar 2 07:38:59 saslpasswd2: unable to dlopen /usr/local/lib/sasl2/libgssapiv2.so.2: Shared object "libgssapi.so.10" not found, required by "libgssapiv2.so.2"Mar 2 08:51:16 php: : The command 'umount -f /tmp/squidGuard' returned exit code '1', the output was 'umount: /tmp/squidGuard: not a file system root directory'
Mar 2 08:48:52 php: : The command 'chmod 1777 /tmp/squidGuard' returned exit code '1', the output was 'chmod: /tmp/squidGuard: No such file or directory'
Mar 2 08:48:52 php: : The command '/sbin/mdmfs -s 200M md15 /tmp/squidGuard' returned exit code '1', the output was 'mdmfs: mount exited with error code 64'Tried the deinstall and reinstall approach - not a scrap of difference - do I need to be woried or just ignore them? As I say everything seems to work.
Regards
Andrew
-
This may be unrelated to this thread, but after installing SquidGuard on 1.2.3 twice(tried completely removing both SquidGuard and Squid) neither service will start. The log gives me this error:
squid[28794]: The url_rewriter helpers are crashing too rapidly, need help!
Followed shortly by:
squid[27741]: Exiting due to repeated, frequent failures.
I haven't gotten around to adding any blacklists, just wanted to see how much config I have beforehand.
Any clues what I should do?
[Edit] -
I am using transparent proxy, will that prevent SquidGuard from working? -
No, it's probably the squidguard update I did last night on the server. It's trying to use a newer version of the ldap library, and failing because it isn't there. I'm looking into it.
-
Awesome, thanks for the reply! :)
I'm heading home for the day but I'll check back in tonight and tomorrow, in case you've found the glitch. Thanks a stack!
-
squidGuard should be OK on 1.2.3 again, you might have to uninstall squid/squidguard, pkg_delete openldap*, then reinstall squid and then squidguard.
New installs of squid should be fine.
-
Thanks again, the package installed and works now :-)
