Dansguardian package for 2.0
-
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.
-
another issue I noticed since the upgrade is that on every save dansguardian creates a new entry in the crontab, this easily reproduced by clicking the save button. I'm running 2.12.0.3 pkg v.0.1.7_3 here's how mine looks like:
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist -
another issue I noticed since the upgrade is that on every save dansguardian creates a new entry in the crontab, this easily reproduced by clicking the save button. I'm running 2.12.0.3 pkg v.0.1.7_3 here's how mine looks like:
I'm not getting this issue here. tried with and without clamav update
-
@aru:
Can you please tell me which files need to edit to increase php memory?
create a backup file for /etc/inc/config.inc on /root folder then edit it and change
ini_set("memory_limit","128M") to ini_set("memory_limit","256M")
and on dansguardian.inc file, comment line 42
if ($uname['machine'] == 'amd64')
maybe you will need to reboot the box.
Keep in mind that editng pfsense files is a Do at your own risk job ;)
-
Thanks marcelloc. Is this a dansguardian, clamav, or general pfsense issue? I'd like to make the change for now to work around it but then if there is a bug submitted somewhere then I could track it for when it is fixed without bugging you about it. If you know of one, please share. Thanks again!
-
I'ts not an issue. The code is the to prevent php from using a lot of memory.
-
I'ts not an issue. The code is the to prevent php from using a lot of memory.
Well… ok... but since the saves are not fully completing and instead are throwing an error, that is an issue. Perhaps not a problem with pfsense then but with the packages? Obviously either the packages need to use less memory or the limit needs raised (or perhaps have an option in the GUI to set the limit). Unless you consider an error on every save a feature. ;)
-
New AMD64 8gig memory 2.03 build
Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 17023308 bytes) in /usr/local/pkg/dansguardian.inc on line 1151
Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 17023067 bytes) in /usr/local/pkg/mailscanner.inc on line 593I have tried increasing the memory /etc/rc.php_ini_setup
In /etc/inc/config.inc
& both mailscanner.inc and dansguardian.inc.
The error still exists neither will start.
-
It will need more, try 384MB on both files
I'm debuggin it and trying to reduce memory load during config apply.
-
Hmm.. yea, just to confirm from another system, I tried setting 512M and then 1024M (rebooted after each) and I still got this on save:
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 42 bytes) in /usr/local/pkg/dansguardian.inc on line 1138
-
Hi,
i have resolved our issue for the php and blacklist problem.
I deleted /usr/local/pkg/blacklist.tgz and everything else regarding blacklist.
I then deinstalled dansguardian and reinstalled it.
That has it solved.
-
I have another problem :o
Since a few days internal dns resolving doesn't work anymore.
I can resolve forum.pfsense.org with not problems but, for example, not http://wpad.
That causes my automatic proxy configuration to stop and our clients have no internet access anymore.
If i bypass the proxy, it works like before.
Any hints in the right direction?
Cheers.
-
Do you have at least one of your DNS server entries on the box pointing to your local machine. Also is your DHCP server assign you local machine as a DNS server? If not that is most likely your problem.
