Error Db_open Permission Denied
Contents |
More info... Needs Expansion This article is incomplete, and needs to be expanded. More info... Contents Introduction Installation Key File Locations Squid Configuration SquidGuard Configuration Testing Troubleshooting SquidGuard Emergency Mode External Links aliases db permission denied In Need Of Further Documentation This howto describes the process of setting up mkdir data db permission denied Squid and SquidGuard for the purpose of internet content filtering. It is revised for Karmic 9.10 and Squid 2.7 squidguard -b -d -c all in the repositories with it. Older versions work a little different. There are many different configuration options available. The settings used in this howto are very simplistic and may not suit
Squidguard Configuration Pfsense
your needs. In any case it will get you up and running. More complex settings can be added afterwards. Introduction Squid is a proxy server, HTTP requests are sent to Squid instead of being sent directly to the internet. SquidGuard is a web filter plugin for Squid which is used to restrict access to domains/URLs based upon access control lists. When SquidGuard receives restart squidguard a request it is examined and will either allow the page to load or will redirect to a predetermined “block” page or script. SquidGuard makes its decisions based upon the use of access control lists and databases of domains, URLs, and expressions. Installation If you'd like to host your own block page, install apache2 sudo apt-get install apache2Install Squid Make sure you have the Universe repository enabled Install SquidGuard sudo apt-get install squidguard Key File Locations File Purpose /etc/squid/squid.conf Squid configuration file /var/log/squid/access.log Squid access log file /etc/squid/squidGuard.conf SquidGuard configuration file /var/lib/squidguard/db SquidGuard database files /var/log/squid/squidGuard.log SquidGuard log file Squid Configuration The squid.conf file is huge, with hundreds of options. In this howto we will only be changing a few settings. Open the squid.conf file for editing using sudo and a text editor. You can use graphical sudo (gksudo) and gedit for this task, or sudonano gksudo gedit /etc/squid/squid.confTurn on line numbers in gedit (Edit > Preferences) Find the http_porttag. By default it reads #http_port3128 This is the default port that Squid will listen on for requests. If you want to change it, uncomment the line and se
help us to make SME Server a better product. More info here Wiki Forums Bugs Lists Manual FAQ Howto Contribs Download Donate Search Login Register Contribs.org > Obsolete Releases > SME 7.x Contribs > Topic: Problems updating the Blacklist within SquidGuard « what is squidguard previous next » Pages: [1] Go Down Print Author Topic: Problems updating the Blacklist within
Squid Squidguard
SquidGuard (Read 5768 times) bhay3s Home away from home Offline Posts: 175 Problems updating the Blacklist within SquidGuard « on: November 28, 2011, 07:53:26
Squidguard Whitelist
PM » Hello ,I am currently running SME Server 7.5.1 and I am trying to update the Blacklist within SquidGuad something the previous network admin did not care to do. I browse the SME gui to 'Security' - https://help.ubuntu.com/community/SquidGuard 'Content Filtering' - 'Blacklist Controls' and this is where you input a url for the blacklist control that you have decided to use. As advised by Squidguards documentation, I decided on Shalla's list which is at location: http://www.shallalist.de/Downloads/shallalist.tar.gz. After placing the url in the url location box and then clicking 'Submit data' I get the following message:The blacklist setting is now a DB value - config show squidguardThe default squidguard blacklist is:http://ftp.ost.eltele.no/pub/www/proxy/squidGuard/contrib/blacklists.tar.gzwhich doesn't seem to be being https://forums.contribs.org/index.php?topic=48126.0 updated. There is another list that is being maintained,here, http://squidguard.shalla.de/Downloads/shallalist.tar.gz, but you must adhere to theirCopyright terms if you want to use it in a commercial setting.You can get more details here, squidguard.orgI verified there was no change with the additional categories or with the untrusted domain list and I also chose one domain out of the entire list to see if I was able to get to it and I was. Once I verified that this did work I decided to research on the net of possible fixes and I don't find anything that's concrete in the way of a clear answer. I personally use squidguard on my personal server at my house although it's on a Debian distro so there are many differences as I can see. Squidguard does not take a rocket scientist to use so I am either missing some much needed command line or maybe this is a bug, not sure. Anyways any help is much appreciated. Logged Stefano Silver Supporter Offline Posts: 9,762 Skype account: maghissimo Re: Problems updating the Blacklist within SquidGuard « Reply #1 on: November 28, 2011, 08:42:17 PM » just a question: did you search the forums with "shalla" key? and, for you, another one: did you take a look to the logs to check what's going wrong?please, forget debian, here it's just a different world.. Logged Consulente di Smeserver.
- Filter Fails after update script « previous next » Print Pages: [1] Go Down Author Topic: Problem SquidGuard + https://forum.pfsense.org/index.php?topic=59354.0 Blacklist updates - Filter Fails after update script (Read http://www.squid-cache.org/mail-archive/squid-users/201110/0331.html 3072 times) 0 Members and 1 Guest are viewing this topic. duanes Jr. Member Posts: 51 Karma: +1/-1 Problem SquidGuard + Blacklist updates - Filter Fails after update script « on: February 25, 2013, 08:03:21 am » Version permission denied - Current Full AMD64 2.02 on PC.I have been having difficultly with my Squidguard where is stops operating every morning. The symptom was that the Squidguard filters seem to be ignored regardless of transparent proxy or regular proxy (port:3128).What I found was that I am using this db permission denied short script on cron to update my blacklist from shalla each morning at 4:04am.---------------4 4 * * * /usr/local/bin/squidGuard_blacklist_update.sh#!/usr/local/bin/php -f---------------But, this shows up in the squidguard cache.log when the update runs:---------------2013/02/22 04:05:34| Reconfiguring Squid Cache (version 2.7.STABLE9)...2013/02/22 04:05:34| FD 48 Closing HTTP connection2013/02/22 04:05:34| FD 49 Closing HTTP connection2013/02/22 04:05:34| FD 50 Closing HTCP socket2013/02/22 04:05:34| FD 62 Closing SNMP socket2013/02/22 04:05:34| logfileClose: closing log /var/squid/logs/access.log2013/02/22 04:05:34| Including Configuration File: /usr/local/etc/squid/squid.conf (depth 0)2013/02/22 04:05:34| Cache dir '/var/squid/cache' size remains unchanged at 102400000 KB2013/02/22 04:05:34| WARNING: use of 'override-expire' in 'refresh_pattern' violates HTTP2013/02/22 04:05:34| WARNING: use of 'override-lastmod' in 'refresh_pattern' violates HTTP2013/02/22 04:05:34| WARNING: HTTP requires the use of Via2013/02/22 04:05:34| Initialising SSL.2013/02/22 04:05:34| logfileOpen: opening log /v
+0000 Hi, I hope somebody can help :) CentOS 5.5 (2.6.18-194.el5) Squid Cache: Version 2.6.STABLE21 SquidGuard: 1.4 Sleepycat Software: Berkeley DB 4.3.29 I have installed squid & squidGuard (as above) and I am having the followin= g problem. When I start squid with "service squid start" I get the following errors in= /var/log/squid/cache.log: 2011-10-21 11:27:32 [32053] (squidGuard): can't write to logfile /usr/local= /squidGuard/log/squidGuard.log 2011-10-21 11:27:32 [32053] New setting: dbhome: /usr/local/squidGuard/db 2011-10-21 11:27:32 [32053] New setting: logdir: /usr/local/squidGuard/log 2011-10-21 11:27:32 [32053] init domainlist /usr/local/squidGuard/db/allowa= ll.destdomainlist 2011-10-21 11:27:32 [32053] loading dbfile /usr/local/squidGuard/db/allowal= l.destdomainlist.db 2011-10-21 11:27:32 [32052] (squidGuard): can't write to logfile /usr/local= /squidGuard/log/squidGuard.log 2011-10-21 11:27:32 [32052] New setting: dbhome: /usr/local/squidGuard/db 2011-10-21 11:27:32 [32052] New setting: logdir: /usr/local/squidGuard/log 2011-10-21 11:27:32 [32052] init domainlist /usr/local/squidGuard/db/allowa= ll.destdomainlist 2011-10-21 11:27:32 [32052] loading dbfile /usr/local/squidGuard/db/allowal= l.destdomainlist.db 2011-10-21 11:27:32 [32053] Error db_open: Permission denied 2011-10-21 11:27:32 [32052] Error db_open: Permission denied 2011-10-21 11:27:32 [32053] Going into emergency mode 2011-10-21 11:27:32 [32052] Going into emergency mode However, if I start squid manually with "squid -f /etc/squid/squid.conf" th= ere is no issue and both squid & squidGuard start without issue. I have checked the permissions on all DB files & log files and they are fin= e: -rwxr-xr-x 1 squid root 11K Oct 21 11:04 squidGuard.log -rwxr-xr-x 1 squid squid 8.0K Oct 21 11:01 allowall.destdomainlist.db I have rebuilt all of the DB files with squidGuard -C all still not noavail= . I have installed this solution many times before and never hit this probl= em so I am confused as to what I am forgetting. Look forward to your replies. Thanks Adam Received on Fri Oct 21 2011 - 10:52:15 MDT This message: [ Message body ] Next message: jeffrey j donovan: "Re: [squid-users] Squid & SquidGuard" Previous message: Kaiwang Chen: "Re: [squid-users] How to filter response in squid-3.1.x?" Next in thread: jeffrey j donovan: "Re: [squid-users] Squid & S