Dansguardian 2.12.0.3_2 does not work



  • The new package of dansguardian 2.12.0.3_2 uploaded on 9th april 2014 does not work properly
    The previous package 2.12.0.3_1 of feb 2014 patched by marcello worked properly
    Request to restore the link for dansguardian to 2.12.0.3_1 for proper functionality
    2.12.0.3_2 gives contentscanner files missing and package cannot be restarted by starting/stopping/restarting dansguargian.sh
    Pl help

    Thanks
    cirkit



  • How do I get to the older package..
    Upgraded now Dans does not work..

    THX

    @cirkit:

    The new package of dansguardian 2.12.0.3_2 uploaded on 9th april 2014 does not work properly
    The previous package 2.12.0.3_1 of feb 2014 patched by marcello worked properly
    Request to restore the link for dansguardian to 2.12.0.3_1 for proper functionality
    2.12.0.3_2 gives contentscanner files missing and package cannot be restarted by starting/stopping/restarting dansguargian.sh
    Pl help

    Thanks
    cirkit



  • Went to /tmp and deleted and .dguardianipc and .dgaurdianurlipc
    Rebooted and it works again…..



  • That fix didit work for me. Here is what I see in the log:

    Apr 13 10:54:23 check_reload_status: Reloading filter
    Apr 13 10:54:19 php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/dansguardian.sh start' returned exit code '1', the output was 'kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting dansguardian. Unable to load plugin config: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf cs_plugin_load() returned NULL pointer with config file: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf Error loading CS plugins Error parsing the dansguardian.conf file or other DansGuardian configuration files /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian'
    Apr 13 10:54:19 root: /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian
    Apr 13 10:54:19 dansguardian[64986]: Error parsing the dansguardian.conf file or other DansGuardian configuration files
    Apr 13 10:54:19 dansguardian[64986]: Error loading CS plugins
    Apr 13 10:54:19 dansguardian[64986]: cs_plugin_load() returned NULL pointer with config file: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf
    Apr 13 10:54:19 dansguardian[64986]: Unable to load plugin config /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf
    Apr 13 10:54:19 php: /pkg_mgr_install.php: Starting Dansguardian
    Apr 13 10:54:12 php: /pkg_mgr_install.php: New alert found:
    Apr 13 10:54:12 php: /pkg_mgr_install.php: Blacklist update process started
    Apr 13 10:54:08 php: /pkg_mgr_install.php: [Dansguardian] - Save settings package call pr: bp: rpc:no
    Apr 13 10:54:08 php: /pkg_mgr_install.php: The command '/usr/local/etc/rc.d/dansguardian.sh start' returned exit code '1', the output was 'kern.ipc.somaxconn: 16384 -> 16384 kern.maxfiles: 131072 -> 131072 kern.maxfilesperproc: 104856 -> 104856 kern.threads.max_threads_per_proc: 4096 -> 4096 Starting dansguardian. Unable to load plugin config: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf cs_plugin_load() returned NULL pointer with config file: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf Error loading CS plugins Error parsing the dansguardian.conf file or other DansGuardian configuration files /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian'
    Apr 13 10:54:08 root: /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian
    Apr 13 10:54:08 dansguardian[46726]: Error parsing the dansguardian.conf file or other DansGuardian configuration files
    Apr 13 10:54:08 dansguardian[46726]: Error loading CS plugins
    Apr 13 10:54:08 dansguardian[46726]: cs_plugin_load() returned NULL pointer with config file: /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf
    Apr 13 10:54:08 dansguardian[46726]: Unable to load plugin config /usr/pbi/dansguardian-amd64/etc/dansguardian/contentscanners/clamdscan.conf
    Apr 13 10:54:08 php: /pkg_mgr_install.php: Starting Dansguardian
    Apr 13 10:54:02 check_reload_status: Syncing firewall
    Apr 13 10:53:58 check_reload_status: Syncing firewall
    Apr 13 10:53:56 php: /pkg_mgr_install.php: [Dansguardian] - Save settings package call pr: bp: rpc:no
    Apr 13 10:53:08 php: /pkg_mgr_install.php: Beginning package installation for Dansguardian .



  • Yes it worked on one install nut not the other two..
    Not sure why it worked on the one yet..



  • This why I keep saying not to publish new versions without doing a fulll UAT. Just updating the version to fix one thing breaks 2 other things. Just one developer working on a package and not having enough resources or time to devote to it… is exactly why this happened.



  • Agree with what you are saying about testing. Marcello has done a great job in maintaining this package over time, so I'm certainly not denigrating any of his work. There's just so many use cases, install variations, etc. that it is very difficult for one person to test adequately.

    The but the biggest issue at the moment is that it is pretty badly broken, Marcello is obviously too busy to address it (haven't gotten any responses on these threads), and I haven't found any easy way to roll back to the previous version. This makes it impossible to do any new installs that need dansguardian.



  • pfsense seriously needs a package version rollback feature. If you like the new version to your expectations then you can delete the  older version files OR if somthing breaks like the case we have here, it would help rollback to the earlier version with simple clicks and delete the corrupt version out of the system.



  • @asterix:

    pfsense seriously needs a package version rollback feature. If you like the new version to your expectations then you can delete the  older version files OR if somthing breaks like the case we have here, it would help rollback to the earlier version with simple clicks and delete the corrupt version out of the system.

    When you are about to upgrade, it lets you do a full backup. But it seems that this is not a true image, i rolled back and dansguardian is broken no matter the version (2.1 or 2.1.2). The backup is taking almost 2 gigs of space,  I don't understand why it doesn't contain previous package states.



  • See this thread for a workaround on the issues with 2.12.0.3_2 https://forum.pfsense.org/index.php?topic=75243.0



  • @rjcrowder:

    See this thread for a workaround on the issues with 2.12.0.3_2 https://forum.pfsense.org/index.php?topic=75243.0

    Unfortunately it's still unusable for me. At least the service now runs, but neither of the content scanners are working. My internet just breaks if I route my traffic through DG proxy.

    DG reports the status of the content scanners as (off). So I ran clamd in shell and got ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock is in use by another process.

    I then removed /var/run/clamav/clamd.sock and ran clamd again with no errors. DG still shows content scanner (off) and No traffic is routed to final destination.



  • OK… in my case at least (on a fresh install as described in the other thread) clam wasn't starting... here's what I did to fix it...

    
    cd /usr/local/bin
    ln -s /usr/pbi/dansguardian-amd64/bin/freshclam freshclam
    cd /usr/local/etc/                                                          
    ln -s /usr/pbi/dansguardian-amd64/etc/freshclam.conf freshclam.conf
    cd /usr/local/sbin
    ln -s /usr/pbi/dansguardian-amd64/sbin/clamd clamd
    
    


  • @abbey:

    @rjcrowder:

    See this thread for a workaround on the issues with 2.12.0.3_2 https://forum.pfsense.org/index.php?topic=75243.0

    Unfortunately it's still unusable for me. At least the service now runs, but neither of the content scanners are working. My internet just breaks if I route my traffic through DG proxy.

    DG reports the status of the content scanners as (off). So I ran clamd in shell and got ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock is in use by another process.

    I then removed /var/run/clamav/clamd.sock and ran clamd again with no errors. DG still shows content scanner (off) and No traffic is routed to final destination.

    What other packages do you have installed?



  • cron, squid3 and lightsquid…

    Install order was
    cron
    dansguardian
    squid3
    lightsquid

    Then installed the pbi of the older version of the dansguardian package. After that, downloaded the blacklists and created the symbolic links to fix clam.



  • @rjcrowder:

    OK… in my case at least (on a fresh install as described in the other thread) clam wasn't starting... here's what I did to fix it...

    
    cd /usr/local/bin
    ln -s /usr/pbi/dansguardian-amd64/bin/freshclam freshclam
    cd /usr/local/etc/                                                          
    ln -s /usr/pbi/dansguardian-amd64/etc/freshclam.conf freshclam.conf
    cd /usr/local/sbin
    ln -s /usr/pbi/dansguardian-amd64/sbin/clamd clamd
    
    

    Files already exist, and still no clamd on DG.

    @mschiek01:

    @abbey:

    @rjcrowder:

    See this thread for a workaround on the issues with 2.12.0.3_2 https://forum.pfsense.org/index.php?topic=75243.0

    Unfortunately it's still unusable for me. At least the service now runs, but neither of the content scanners are working. My internet just breaks if I route my traffic through DG proxy.

    DG reports the status of the content scanners as (off). So I ran clamd in shell and got ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock is in use by another process.

    I then removed /var/run/clamav/clamd.sock and ran clamd again with no errors. DG still shows content scanner (off) and No traffic is routed to final destination.

    What other packages do you have installed?

    Cron and Squid



  • @abbey:

    I then removed /var/run/clamav/clamd.sock and ran clamd again with no errors. DG still shows content scanner (off) and No traffic is routed to final destination.

    Do "ps -ax | grep clam" and see if clam is actually running…
    Do "ps -ax | grep dans" to see if dans is actually running

    Also, what do you mean by "DG still shows content scanner (off)"? As far as I know, the way to turn clam on is by selecting it in the list (either clam or icapscan) on the general setup tab. I didn't think there was anywhere that indicated if it was running or not. What are you looking at?

    If clam is selected, but not running when you try to browse to a page that should be virus scanned you will get an error indicating that dans could not scan the page. If you are not getting that error, and both dans and squid are running, then something else is likely setup wrong...



  • @abbey:

    @rjcrowder:

    OK… in my case at least (on a fresh install as described in the other thread) clam wasn't starting... here's what I did to fix it...

    
    cd /usr/local/bin
    ln -s /usr/pbi/dansguardian-amd64/bin/freshclam freshclam
    cd /usr/local/etc/                                                          
    ln -s /usr/pbi/dansguardian-amd64/etc/freshclam.conf freshclam.conf
    cd /usr/local/sbin
    ln -s /usr/pbi/dansguardian-amd64/sbin/clamd clamd
    
    

    Files already exist, and still no clamd on DG.

    @mschiek01:

    @abbey:

    @rjcrowder:

    See this thread for a workaround on the issues with 2.12.0.3_2 https://forum.pfsense.org/index.php?topic=75243.0

    Unfortunately it's still unusable for me. At least the service now runs, but neither of the content scanners are working. My internet just breaks if I route my traffic through DG proxy.

    DG reports the status of the content scanners as (off). So I ran clamd in shell and got ERROR: LOCAL: Socket file /var/run/clamav/clamd.sock is in use by another process.

    I then removed /var/run/clamav/clamd.sock and ran clamd again with no errors. DG still shows content scanner (off) and No traffic is routed to final destination.

    What other packages do you have installed?

    Cron and Squid

    run this command and post the output "ls -la /var/run/"



  • @rjcrowder:

    Do "ps -ax | grep clam" and see if clam is actually running…
    Do "ps -ax | grep dans" to see if dans is actually running

    Also, what do you mean by "DG still shows content scanner (off)"? As far as I know, the way to turn clam on is by selecting it in the list (either clam or icapscan) on the general setup tab. I didn't think there was anywhere that indicated if it was running or not. What are you looking at?

    If clam is selected, but not running when you try to browse to a page that should be virus scanned you will get an error indicating that dans could not scan the page. If you are not getting that error, and both dans and squid are running, then something else is likely setup wrong...

    "ps -ax | grep clam
    16871  ??  Is    0:00.00 /usr/pbi/dansguardian-amd64/sbin/clamd
    52631  0  S+    0:00.00 grep clam

    ps -ax | grep dans
    16871  ??  Is    0:00.00 /usr/pbi/dansguardian-amd64/sbin/clamd
    29973  ??  Ss    0:00.01 /usr/local/sbin/dansguardian
    30006  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30028  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30145  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30166  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30180  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30457  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30466  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30810  ??  I      0:00.00 /usr/local/sbin/dansguardian
    30985  ??  I      0:00.00 /usr/local/sbin/dansguardian
    31042  ??  I      0:00.00 /usr/local/sbin/dansguardian
    34492  0  S+    0:00.00 grep dans

    @mschiek01:

    run this command and post the output "ls -la /var/run/"

    .
    .
    .
    drwxr-xr-x  2 clamav  wheel      512 Apr 18 12:26 clamav
    -rw–-----  1 root    wheel        5 Apr 18 12:26 cron.pid
    -rw-r--r--  1 root    wheel        6 Apr 18 12:30 dansguardian.pid
    .
    .
    .



  • OK… so both clam and dans appear to be running. Is squid running? Is DG configured and listening on a port and talking to squid on the port that squid is listening on? What happens when you set dansguardian as your proxy and try to browse a page? What if you set squid as the proxy and try to browse?

    Also - what do you mean when you say that the content scanner is "off".



  • Does your configuration page look like this??




  • @rjcrowder:

    OK… so both clam and dans appear to be running. Is squid running? Is DG configured and listening on a port and talking to squid on the port that squid is listening on? What happens when you set dansguardian as your proxy and try to browse a page? What if you set squid as the proxy and try to browse?

    Also - what do you mean when you say that the content scanner is "off".

    Ok, i reinstalled the package and followed the steps in your other thread (linked earlier). Changed Dan to listen on LAN, proxy on loopback. It could have been my settings, since I frantically messed with various settings to get DG working. Now everything works great!!

    I was under the impression that under General->Content Scanner->Clamdscan (on) would show once enabled. Now i see that it shows the default value even when calmav is running.

    I greatly appreciate your efforts. Thanks



  • Hi guys,

    There is no updates on dasguardian code for more then one year, a lot of patches were submitted but none merged.

    Every manual patch I have applied to dansguardian source code are not commited/applied on freebsd port too, so it's hard to have it compiled my core team.

    Fredb has pushed a lot of uncommited fixes that he forked the project to have it applied.
    https://forum.pfsense.org/index.php?topic=61811.msg376192#msg376192

    Full changelog from current dansguardian official code to e2guardian
    https://raw.githubusercontent.com/e2guardian/e2guardian/master/e2guardian.release



  • Marcello… I don't know if you've been watching the forums or not, but something definitely got broken in the 2.12.0.3_2 version of the package. There is something wrong with the content scanner stuff - multiple executables and configuration files are missing. Also, the blacklist download site is not being set.

    At any rate... the workaround seems to be installing the 2.12.0.3 version from your repository...



  • @rjcrowder:

    something definitely got broken in the 2.12.0.3_2 version of the package.

    That's the official version from ports compiled by core team, the code doesn't have some patches

    @rjcrowder:

    At any rate… the workaround seems to be installing the 2.12.0.3 version from your repository...

    I'm trying to port e2guardian to freebsd and then pfsense. As I said, dansguardian is no longer being updated by maintainers on sourceforge.
    Many commits are pending.

    AFAIK, e2guardian will not have use restrictions as dasnguardian has.
    The gui will be almost the same, just the package name will change. If core team aproves, it will be applied to pfsense 2.1



  • @marcelloc:

    @rjcrowder:

    something definitely got broken in the 2.12.0.3_2 version of the package.

    That's the official version from ports compiled by core team, the code doesn't have some patches

    @rjcrowder:

    At any rate… the workaround seems to be installing the 2.12.0.3 version from your repository...

    I'm trying to port e2guardian to freebsd and then pfsense. As I said, dansguardian is no longer being updated by maintainers on sourceforge.
    Many commits are pending.

    AFAIK, e2guardian will not have use restrictions as dasnguardian has.
    The gui will be almost the same, just the package name will change. If core team aproves, it will be applied to pfsense 2.1

    Very nice… I'll look forward to that... Thanks again Marcello