Dansguardian package for 2.0
-
I'm not sure what's going on with this, but I had the same error. I discovered that the clamav startup script in /usr/local/etc/rc.d had tons of duplicated lines in it! Each line was duplicated thousounds of times! Here's what I did that seemed to fix it (at least for the moment).
1.) Bumped up the memory limits listed previously in this thread
2.) Fixed the clamav startup script (not sure necessary - think it is rewritten each startup? not sure).After reboot, everything started up fine.
pfSense: 2.0.2-RELEASE (amd64)
Dansguardian: 2.12.0.3 pkg v.0.1.7_3So the solution to the out of memory error during a save in DS is to uninstall, look for strays via pkg_info, delete any if found then reinstall?
Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 17023308 bytes) in /usr/local/pkg/dansguardian.inc on line 1151
-
I'll take a look on clamav startup script.
-
Probably yes. I'm calling the mount_rw feature but I did not tested this package on nanobsd yet.
Apparently that is the problem. I checked the "Keep media mounted read/write at all times" box under Diagnostics > NanoBSD, and all the read-only errors went away. There were still three errors showing up during boot however:
Warning: closedir() expects parameter 1 to be resource, null given in /usr/local/pkg/dansguardian on line 69 Warning: file(/usr/local/share/certs/ca-root-nss.crt): failed to open stream: No such file or directory in /usr/local/pkg/dansguardian.inc on line 74 Warning: Invalid argument supplied for foreach() in /usr/local/pkg/dansguardian.inc on line 76
I ran "pkg_add -r ca-root-nss" and rebooted, and now there are no errors at all. So apparently all the problems have been solved.
Now a different question. How does the process of adding banned sites, urls, etc work exactly? I added a second list to the Site Lists under ACLs with a couple in the "Blocked" section to test if it was working. After saving, it's still not blocking them. I did make sure the "Enable" box for banned was checked. Am I doing something wrong, or is there still a problem that's just not showing up during boot?
-
First issue I'm having (a minor one): crontab is filled up with at least 100 entries of:
0 0 */7 * * root /usr/local/bin/php /usr/local/www/dansguardian.php fetch_blacklist
Maybe it writes another entry each time I save a config? I have manually deleted all these entries (except one) a couple of times now but it keeps filling up.
Second issue is getting clamav to work. Out of the box I kept getting a lot of:
Error connecting to ClamD socket
Unknown return code from content scanner: -1To start with, after installing DG it seemed a bunch of files and directories are missing. So e.g. I had to manually create /var/run/clamav and chown to clamav. And then touch clamd.sock inside that directory and make sure it had 755 permissions and clamav owner. Also maybe some /var/log/clamav settings.
I tried a number of things after that, like manually running freshclam (OK), manually restarting DG (OK as long as I created clamd.sock as above), manually installing the latest version of clamav I could find (pkg_add -r http://files.pfsense.org/packages/8/All/clamav-0.97.6.tbz). Still nothing.
The final thing that got it working for me was to restart clamav-clamd myself. I'm not sure why this works since the system logs show it "starting" when I enable clamav via the GUI config:
Maybe it's a restart that is necessary? With stop/start? Because that's what I did.
Anyway, right now my system is working fine with pfSense -> DG w/ clamav -> Squid3 -> Internet using DHCP/wpad but I'll be interested to see if I have to manually set up the services in the right order again after rebooting.
-
Just rebooted and it works fine, so maybe my installation had gotten out of sync or something and I was running some older version of clamav. At any rate, the manually installed version fixed it for me. Now to get https AV working.
-
Firstly I would like to thank Marcello for this great package, saved me so much time!
I have a suggestion, I guess you could call it a feature request.
On the ACL's when creating new site lists, phrase lists, etc. A button to create a new list based on the default would be handy, similar to that for firewall rules, it would just make life simpler!
Oh and separate html templates for the denied page… falls under the htmltemplate= variable in the dansguardianfx.confHow dificult would it be to run two copies of dansguardian on the same server? (listening to different ports of course!) I'm wanting some traffic from one vlan transparently filtered and another explicitly.
-
So… I was still having problems with the lines in /usr/local/etc/rc.d/clamav-clamd being duplicated. Unless I'm missing something, I think the fix is to change /usr/local/pkg/dansguardian.inc lines 1150-51 as follows:
$new_script_line=preg_replace("/NO/","YES",$script_line); $new_clamav_startup.=preg_replace("@/usr/local@",DANSGUARDIAN_DIR,$new_script_line);
in other words… the old code did to "preg_replace" in a row appending the same script line... it was causing duplicate lines.
I'll take a look on clamav startup script.
-
in other words… the old code did to "preg_replace" in a row appending the same script line... it was causing duplicate lines.
I've fixed the code today.
I'm including new sync options to push noew package version to github.
-
in other words… the old code did to "preg_replace" in a row appending the same script line... it was causing duplicate lines.
I've fixed the code today.
I'm including new sync options to push noew package version to github.
Did you include the "web upload error fix"?
-
Did you include the "web upload error fix"?
web upload fix It's a binary update, I'm pushing gui fix.
I'll need to update freebsd ports before asking a new package build by core team.
-
new gui version 0.1.8 is out with:
-
New sync style that can use default system sync settings
-
Fix to clamav-clamd startup manipulation
**Note1:**If you have a messed up startup script, you can download default script with this cmd on 2.0.x pfsense version:
fetch -o /usr/local/etc/rc.d/clamav-clamd http://e-sac.siteseguro.ws/packages/dansguardian/clamav-clamd
**Note2:**Memory issues was direct related to this bug, I suggest a remove/fix of this old file before package reinstall. -
Fix missing ip-acls array on package sync to remote host
I'll try to push on next release current dansguardian patches to freebsd ports and get an official "web upload error free" dansguardian version.
-
-
new gui version 0.1.8 is out with:
-
New sync style that can use default system sync settings
-
Fix to clamav-clamd startup manipulation
Note:If you have a messed up startup script, you can download default script with this cmd on 2.0.x pfsense version:
fetch -o /usr/local/etc/rc.d/clamav-clamd http://e-sac.siteseguro.ws/packages/dansguardian/clamav-clamd -
Fix missing ip-acls array on package sync to remote host
I'll try to push on next release current dansguardian patches to freebsd ports and get an official "web upload error free" dansguardian version.
Slight error in new version…
When creating the clamav-clamd file you need clamd.conf to be in "/usr/local/etc" rather than "/etc" and the path to clamdscan is "/usr/local/bin" rather than "/bin".
-
-
new gui version 0.1.8 is out with:
-
New sync style that can use default system sync settings
-
Fix to clamav-clamd startup manipulation
Note:If you have a messed up startup script, you can download default script with this cmd on 2.0.x pfsense version:
fetch -o /usr/local/etc/rc.d/clamav-clamd http://e-sac.siteseguro.ws/packages/dansguardian/clamav-clamd -
Fix missing ip-acls array on package sync to remote host
I'll try to push on next release current dansguardian patches to freebsd ports and get an official "web upload error free" dansguardian version.
Slight error in new version…
When creating the clamav-clamd file you need clamd.conf to be in "/usr/local/etc" rather than "/etc" and the path to clamdscan is "/usr/local/bin" rather than "/bin".
There is a typo in line 1160. cpreg_p should be cpreg_r
-
-
When creating the clamav-clamd file you need clamd.conf to be in "/usr/local/etc" rather than "/etc" and the path to clamdscan is "/usr/local/bin" rather than "/bin".
Where did you found on code that it's not saved on /usr/local?
There is a typo in line 1160. cpreg_p should be cpreg_r
Found (and fixed), thanks. :)
-
I keep getting "Error connecting to the clamd socket" when trying to access through DG. DG and Squid are running.
-
I keep getting "Error connecting to the clamd socket" when trying to access through DG. DG and Squid are running.
Check your /usr/local/etc/rc.d/clamd-clamav file. If it has a lot of duplicated files, try to remove it and fetch original file from my previous post.
@marcelloc:Note1:If you have a messed up startup script, you can download default script with this cmd on 2.0.x pfsense version:
fetch -o /usr/local/etc/rc.d/clamav-clamd http://e-sac.siteseguro.ws/packages/dansguardian/clamav-clamdTry to run freshclam on console too.
-
I keep getting "Error connecting to the clamd socket" when trying to access through DG. DG and Squid are running.
Check your /usr/local/etc/rc.d/clamd-clamav file. If it has a lot of duplicated files, try to remove it and fetch original file from my previous post.
@marcelloc:Note1:If you have a messed up startup script, you can download default script with this cmd on 2.0.x pfsense version:
fetch -o /usr/local/etc/rc.d/clamav-clamd http://e-sac.siteseguro.ws/packages/dansguardian/clamav-clamdTry to run freshclam on console too.
I replaced the clamd-clamav file with yours and did run freshclam on the console with success. I also did a reboot. But the error is still there if i try to access websites through DG.
-
I replaced the clamd-clamav file with yours and did run freshclam on the console with success. I also did a reboot. But the error is still there if i try to access websites through DG.
What you got running freshclam on console?
-
What you got running freshclam on console?
ClamAV update process started at Fri Apr 26 15:26:53 2013
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.6 Recommended version: 0.97.8
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd is up to date (version: 54, sigs: 1044387, f-level: 60, builder: sven)
daily.cvd is up to date (version: 17096, sigs: 1164088, f-level: 63, builder: neo)
safebrowsing.cvd is up to date (version: 40506, sigs: 1254288, f-level: 63, builder: google)
bytecode.cvd is up to date (version: 214, sigs: 41, f-level: 63, builder: neo) -
ok, now try to start dansguardian from console too.
/usr/local/etc/rc.d/dansguardian.sh start
kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting dansguardian.
and then check if clamd is running
ps ax | grep -i clamd42895 ?? Is 0:09.65 /usr/local/sbin/clamd 41545 4 S+ 0:00.00 grep -i clam