Dansguardian package for 2.0
-
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.
-
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.
You did?… that sounds really familiar:
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).
It's all good, just had to harrass you a little. ;) Could have saved you some trial and error.
-
Hi,
I'm installing several new VSATs in the near future and would like to use pfSense with DansGuardian. I would also like to have the time groups features of SquidGuard. Is it possible to run both of these packages on pfSense? I tried installing them both but once I did DG didn't work anymore. I'm guessing it was a configuration issue. If I can run both at the same time, how should they be configured to pass traffic properly between them?
My ultimate goal is to have the filtering of DG and be able to block certain websites/file types/mime types during certain times of the day. An example would be to block Facebook from 7am until 5pm and all video files from 5am until midnight.
Thanks for any help.
-
Hi marcelloc,
I increased memory to 384MB as you suggested, seems working, will report back if any issues.
I have another issue here. MS Outlook isn't working behind pfsense. I have setup wpad and tried manually setting proxy in ie also.
I have squid3 in non-transparent mode with DG.
Any suggestions..?
-
@aru:
I have another issue here. MS Outlook isn't working behind pfsense. I have setup wpad and tried manually setting proxy in ie also.
You mean owa or msoutlook communication to exchange server?
-
I mean outlook pop3 mail fetching. No exchange server. Clients in lan configured pop3 are unable to download. server authentication not happening.
-
Pop3 is not http. Dansguardian does not affect it.
-
@aru:
Hi marcelloc,
I increased memory to 384MB as you suggested, seems working, will report back if any issues.
I have another issue here. MS Outlook isn't working behind pfsense. I have setup wpad and tried manually setting proxy in ie also.
I have squid3 in non-transparent mode with DG.
Any suggestions..?
I did this and I still get
Fatal error: Allowed memory size of 402653184 bytes exhausted (tried to allocate 71 bytes) in /usr/local/pkg/dansguardian.inc on line 1138
. However when I bump it to 512 or higher it goes back to saying my allowed memory size is 134217728…. ???
-
The hard limit is configured to 512. Try 500.
I'll find the option to increase it and post here.
-
It turns out to be exactly 488 MB is the most I can give it. If I do 489 MB or higher the error seems to indicate that it didn't actually do it and it is still set to 128MB. I still get the memory errors with 488 MB as well.
