Dansguardian package for 2.0
-
Did you changed authentication methods? auth set to none
Change report log format to dansguardian and check if it's showing group applied.
-
I see the groups in log "DENIED Banned Regular Expression URL:" however still able to view the link
-
I see the groups in log "DENIED Banned Regular Expression URL:" however still able to view the link
:o I'll try to simulate it here.
If this bug is confirmed, I'll push on dansguardian sourceforge project.
-
Reboot fixed my error. Is it just best practice to reboot after a package update?
I haven't gotten to fully testing the filtering yet as I'm still working on my config… (sooooo many parameters) :o
Edit:
On my other machine where I had a blacklist set up to download, the dansguardian package update/reinstall gets stuck here:
Checking Dansguardian Blacklists… One moment please...
Found previous blacklist database, skipping download...I let it sit for a while and it didn't move. I then moved on and rebooted. Now dansguardian GUI menu is missing. I'm re-running and I'll leave it for a few hours to see if it ever completes gracefully.
-
Reboot fixed my error. Is it just best practice to reboot after a package update?
Not at all. I usually do an uninstall and then reinstall to be sure binary was killed.
I haven't gotten to fully testing the filtering yet as I'm still working on my config… (sooooo many parameters) :o
On my other machine where I had a blacklist set up to download, the dansguardian package update/reinstall gets stuck here:
I'm not seeing this issue here, can you check the size of you blacklist file (/usr/local/pkg/blacklist.tgz)?
-
On my other machine where I had a blacklist set up to download, the dansguardian package update/reinstall gets stuck here:
I'm not seeing this issue here, can you check the size of you blacklist file (/usr/local/pkg/blacklist.tgz)?
I didn't get back to it and so I left it overnight. It still was stuck on that screen when I came back to it this morning. Here is the file info (user name x'd out):
-rw-r–r-- 1 root xxxxx 9917215 Feb 13 19:00 /usr/local/pkg/blacklist.tgz
-
completed downloaded file size:
-rw-r–r-- 1 root wheel 20825700 Feb 8 00:10 /usr/local/pkg/blacklist.tgz
-
On my other machine where I had a blacklist set up to download, the dansguardian package update/reinstall gets stuck here:
I'm not seeing this issue here, can you check the size of you blacklist file (/usr/local/pkg/blacklist.tgz)?
I didn't get back to it and so I left it overnight. It still was stuck on that screen when I came back to it this morning. Here is the file info (user name x'd out):
-rw-r–r-- 1 root xxxxx 9917215 Feb 13 19:00 /usr/local/pkg/blacklist.tgz
I ended up having to completely uninstall dansguardian, squid3 and then reinstall. Will continue testing…
-
Same error. Hangs on checking blacklist.
-
I'm testing on 2.0.3. What version are you using?
-
2.12.0.3
-
My pfsense version is 2.0.2
-
so I guess it is fully a code/package issue?
It's a php limit on pfsense, the problem is to fit large lists on this 256Mb limit on amd64 version
Anything I can do to work around it until you update it? At some point it was working until I started making my groups.
How big are your groups user list?
I've pushed pkg v 0.1.7_2 with group acl check.
Actually, right now I only have 5 users in those groups…
I ran into the memory issue again. I'm guessing that since so there are so many config files for dansguardian that it is filling up its max memory easily when you start configuring everything. Any way to increase the amount of memory it can use? I have like 4GB in my box and it show only 17% used right now so I have plenty to spare.
-
2.12.0.3
pfsense version 2.0.2?
did you tried to update danguardian bin from my hepo to fix upload size bug?
-
I ran into the memory issue again. I'm guessing that since so there are so many config files for dansguardian that it is filling up its max memory easily when you start configuring everything. Any way to increase the amount of memory it can use? I have like 4GB in my box and it show only 17% used right now so I have plenty to spare.
I'll try to reduce php memory usage on dansguardian apply this weekend.
On amd64 system it's set to 256. to use more, you need to edit php limit on pfsense config files and on package inc file.
-
Hi,
i have the same issues.
Allowed memory size of 262144000 bytes exhausted (tried to allocate 71 bytes) in /usr/local/pkg/dansguardian.inc on line 1138and also it doesn't continue installing the package after downloading blacklists file.
-
I'll try to reduce php memory usage on dansguardian apply this weekend.
On amd64 system it's set to 256. to use more, you need to edit php limit on pfsense config files and on package inc file.
Is that standard for all packages? If so, perhaps I'll submit it as an enhancement request to allow changing the max memory for a package in the GUI.
and also it doesn't continue installing the package after downloading blacklists file.
Not sure what the issue here was but I was able to get it to install by first deleting the blacklists file and then doing an uninstall and reinstall of dansguardian and squid3 (I use squid3 in my case).
-
Do you have Clamav enabled on your dansguardian config? I've received a report today saying that clamav settings are reaching php memory limit.
-
Do you have Clamav enabled on your dansguardian config? I've received a report today saying that clamav settings are reaching php memory limit.
Yes, I do. Is there a fix for it because it is happening every save now. If not, which files do you edit exactly to raise the limit? Obviously like to get it fixed the right way but that would at least help me configure it for now without getting the error every save.
-
Hi Marcelloc,
I am also facing the same memory exhausted issues on pf 2.0.2-RELEASE (i386). I have installed dg 2.12.0.3 pkg v.0.1.7_3 with
squid 3.1.20 pkg 2.0.6 and sarg reports. Can you please tell me which files need to edit to increase php memory?Regards.
