Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Problem with web uploads in new dansguardian 2.12.0.3

    Scheduled Pinned Locked Moved Cache/Proxy
    69 Posts 26 Posters 33.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      neil
      last edited by

      Thanks for the quick reply - I did as you suggested, made a change in DG/PFsense, and saved the change - presumably this recreates the dansguardian.sh script - unfortunately no change.

      Just to recap all I did was:

      1. killall dansguardian
      2. cd /usr/local/sbin
      3. mv dansguardian dansguardian.orig (ie backed up the old version)
      4. fetch https://e-sac….....etc
      This retrieved a file of size 994216 dated feb 8.
      The permissions on this file did not match those on the old version and in particular were not executable.
      So I typed chmod 555 dansguardian and the permissions then matched (ie -r-xr-xr-x)
      5. cd /usr/local/etc/rc.d
      6. ./dansguardian.sh start

      This resulted in the error I reported.

      When I copy the original dansguardian binary back again, the startup script runs without any error.

      Any further thoughts?

      1 Reply Last reply Reply Quote 0
      • marcellocM
        marcelloc
        last edited by

        @neil:

        Any further thoughts?

        No. :( Except for the mv dansguardian dansguardian.orig I've did it again here and it started up fine.

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • N
          neil
          last edited by

          Hmmmm - I'm not getting anywhere here.
          If I copy the dansguardian.orig back to dansguardian and run ./dansguardian.sh start , DG starts without error.
          The "syntax error: " etc seems to be coming from the binary not from the script.

          I've tried downloading the binary again, and there is no improvement.

          Could you send the binary to me at neil@darfield.school.nz?

          Thanks

          1 Reply Last reply Reply Quote 0
          • N
            neil
            last edited by

            DOH this was my problem - my production servers are all x64 while my development server is x86.
            I was trying to apply the x64 version of DG to an x86 PFsense install.
            I've downloaded the x86 version and this starts correctly.
            Thanks for your replies

            1 Reply Last reply Reply Quote 0
            • L
              Legion
              last edited by

              Also had problems uploading, also downloaded your patch, also worked. Thanks marcelloc.

              1 Reply Last reply Reply Quote 0
              • E
                eldersouza
                last edited by

                @marcelloc:

                @samham:

                Marcello when will you push the patch?

                I've pushed it to dansguardian sourceforge project.

                But not for freebsd ports.

                I'm waiting feedbacks to see if there are other bugs that I can help to fix.

                Estava com esse problema aqui no dansguardian, só fiz substituir o arquivo que você disponibilizou e pronto!! Problema resolvido !!

                Valeuz Marcello

                1 Reply Last reply Reply Quote 0
                • H
                  Hugovsky
                  last edited by

                  Me too! Thanks marcelloc.  8)

                  1 Reply Last reply Reply Quote 0
                  • E
                    engellion
                    last edited by

                    I have the same problem, but I can not download the patch. When I try ato fetch, I get a: fetch http://e-sac.sitesguro.ws/pfsense/8/dansguardian: Operation timed out

                    I tried a traceroute on http://e-sac.sitesguro.ws and got the following:

                    traceroute e-sac.stesguro.ws
                    traceroute to e-sac.stesguro.ws (64.70.19.198), 64 hops max, 52 byte packets
                    1  10.1.1.1 (10.1.1.1)  0.463 ms  0.335 ms  0.281 ms
                    2  nexthop.qld.iinet.net.au (203.215.9.250)  14.452 ms  14.227 ms  16.294 ms
                    3  150.101.33.158 (150.101.33.158)  31.716 ms  13.708 ms  16.490 ms
                    4  ae1.br1.syd4.on.ii.net (150.101.33.18)  29.600 ms  28.967 ms  31.846 ms
                    5  te0-0-0-1.br1.lax1.on.ii.net (203.16.213.69)  178.061 ms
                        te0-1-1-2.bd1.lax1.on.ii.net (203.16.213.65)  206.041 ms
                        te0-0-0-1.br1.lax1.on.ii.net (203.16.213.69)  177.792 ms
                    6  144.223.30.1 (144.223.30.1)  218.953 ms  207.542 ms  203.939 ms
                    7  sl-crs2-ana-0-15-0-0.sprintlink.net (144.232.19.226)  175.235 ms
                        144.232.1.177 (144.232.1.177)  176.961 ms  179.663 ms
                    8  sl-st21-la-13-0-0.sprintlink.net (144.232.20.69)  208.509 ms
                        sl-st21-la-0-0-0.sprintlink.net (144.232.20.206)  210.669 ms  210.212 ms
                    9  208.174.196.113 (208.174.196.113)  211.137 ms  208.013 ms  208.514 ms
                    10  pr2-so-6-1-0.losangelesequinix.savvis.net (204.70.200.97)  191.378 ms
                        pr2-so-6-0-0.losangelesequinix.savvis.net (204.70.200.93)  195.916 ms
                        pr2-so-6-2-0.losangelesequinix.savvis.net (204.70.200.101)  195.221 ms
                    11  hr1-te-1-0-0.irvine2oc2.savvis.net (204.70.204.189)  190.690 ms  191.125 ms  190.078 ms
                    12  hr2-te-1-0-1.irvine2oc2.savvis.net (204.70.204.166)  218.562 ms  220.108 ms  221.215 ms
                    13  hr1-te-1-0-0.elsegundola1.savvis.net (204.70.204.194)  188.445 ms  189.647 ms  188.262 ms
                    14  das1-v3006.la1.savvis.net (64.70.11.54)  187.990 ms  190.962 ms  191.201 ms
                    15  * * *
                    16  * * *
                    17  * * *
                    18  * * *
                    19  * * *
                    (this went up to 44 * * * before a did a ctrl-C)

                    Is this patch accessible from Australia?

                    Thanks.
                    Paul.

                    1 Reply Last reply Reply Quote 0
                    • L
                      Legion
                      last edited by

                      @engellion:

                      Is this patch accessible from Australia?

                      Yes, but sometimes marcelloc might turn off his server. I remember once I couldn't get something either, but OTOH I've downloaded lots of dansguardian and squid stuff from his site at other times. In fact, I've just browsed to his site now and it's accessible to me.

                      1 Reply Last reply Reply Quote 0
                      • P
                        Phobia
                        last edited by

                        Hi there,

                        As of today - September 23, 2013 - Is this patch still necessary, or has it been merged into the package?

                        Phob

                        1 Reply Last reply Reply Quote 0
                        • A
                          asterix
                          last edited by

                          Still the same.. Hasn't changed yet..

                          1 Reply Last reply Reply Quote 0
                          • P
                            Phobia
                            last edited by

                            Thanks for this. I tried following the instructions, but it didn't seem to work. The DG process kept crapping out after a few minutes, and browsing was quite slow. Also, DG started blocking content I didn't ask it to.

                            I removed the package, but it left behind the dansguardian file in the sbin folder. I manually deleted that and have gone back to the package version for now.

                            Do the permissions need to be adjusted, or should it work without further intervention?

                            1 Reply Last reply Reply Quote 0
                            • P
                              Phobia
                              last edited by

                              Hi again,

                              So I'm still having trouble with the process from earlier in this thread that fetches the new executable via fetch.

                              Via SSH I did :

                              1. killall dansguardian
                              2. cd /usr/local/sbin
                              3. fetch http://e-sac.sitesguro.ws/pfsense/8/dansguardian

                              I noted Neil's earlier post, so I also:

                              4. chmod 555 dansguardian
                              5. cd /usr/local/etc/rc.d
                              6. ./dansguardian.sh start

                              I then restarted the process from the GUI (Status>Services>Dansguardian)  Seeing no improvement, I also rebooted the firewall (pfSense) box.

                              I still see very slow browsing performance, and DG no longer seems to respond to the configuration changes I make in the pfSense GUI.  I've tried clicking through each tab and clicking save thinking that there could be a new configuration version or something, but it still doesn't seem to want to work.

                              What is stranger, is that DG starts blocking things that couldn't possibly match what I've defined, which is essentially to only block pornography.  It even started blocking sites I used to originally learn about the solution:

                              http://old.theninjageek.co.za/2013/07/02/pfsense-squid3-and-dansguardian-a-better-alternative-to-squidguard/

                              For now, I'm back to the "stock" package available through the pfSense GUI.  I'm running:

                              2.1-RELEASE (i386)
                              built on Wed Sep 11 18:16:50 EDT 2013
                              FreeBSD 8.3-RELEASE-p11

                              Dansguardian Services 2.12.0.3 pkg v.0.1.8
                              squid3 Network 3.1.20 pkg 2.0.6

                              If anybody has some other tips to try, please let me know!

                              Thanks,

                              Phob

                              1 Reply Last reply Reply Quote 0
                              • T
                                timthetortoise
                                last edited by

                                It appears this is still an issue in the latest release. I've tried the new binary fix, and it seems to hose the DG install beyond repair, resulting in having to completely remove and reinstall the DG package.

                                1 Reply Last reply Reply Quote 0
                                • R
                                  rjcrowder
                                  last edited by

                                  @timthetortoise:

                                  It appears this is still an issue in the latest release. I've tried the new binary fix, and it seems to hose the DG install beyond repair, resulting in having to completely remove and reinstall the DG package.

                                  Works fine if you do the following:
                                    1.) download the fixed dansguardian file
                                    2.) extract the dansguardian executable
                                    3.) stop dansguardian
                                    4.) copy the new executable over the old one
                                    5.) start dansguardian

                                  Make sure you download the proper fixed dg. I saw some posts where someone was installing the wrong binary (32 bit vs. 64 bit).

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    timthetortoise
                                    last edited by

                                    Indeed that was what I did. It then complained that it couldn't find dansguardian.pbiopt, and couldn't load any of the filter files. I'm guessing the patched executable wants the /usr/local/blahblahblah instead of /usr/pbi/blahblahblah directory.

                                    Edit: To be more precise, here is my log when I start DG after using the patched amd64 binary:

                                    
Oct  3 11:20:02 firewall php: dansguardian_ldap.php: Starting Dansguardian
Oct  3 11:20:02 firewall dansguardian[58327]: Error reading /usr/local/etc/dansguardian/dansguardianf3.conf
Oct  3 11:20:02 firewall dansguardian[58327]: Error opening filter group config: /usr/local/etc/dansguardian/dansguardianf3.conf
Oct  3 11:20:02 firewall dansguardian[58327]: Error reading filter group conf file(s).
Oct  3 11:20:02 firewall dansguardian[58327]: Error parsing the dansguardian.conf file or other DansGuardian configuration files
Oct  3 11:20:02 firewall root: /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian
Oct  3 11:20:02 firewall php: dansguardian_ldap.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. Error reading: /usr/local/etc/dansguardian/dansguardianf3.conf Error opening filter group config: /usr/local/etc/dansguardian/dansguardianf3.conf Error reading filter group conf file(s). Error parsing the dansguardian.conf file or other DansGuardian configuration files /usr/local/etc/rc.d/dansguardian.sh: WARNING: failed to start dansguardian'

                                    I will be testing this on a different VM to see if this is amd64-specific, but it does not happen on a test 386 box.

                                    Edit2: not sure what the deal is on my production system, but it worked fine on my new amd64 install.
                                    I ended up fixing it with this command-set:

                                    
rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian
/usr/local/etc/rc.d/dansguardian.sh start

                                    Now to test whether uploads are fixed or not!

                                    Edit3: Test

                                    Edit4: Hooray, it's fixed! Many thanks for the modified binary.

                                    1 Reply Last reply Reply Quote 0
                                    • R
                                      rjcrowder
                                      last edited by

                                      Yea… I was just in the process of posting back about the sym links. Glad you got it working!

                                      1 Reply Last reply Reply Quote 0
                                      • W
                                        wheelz
                                        last edited by

                                        I had to make a slight adjustment to what timthetortoise did for x64 on 2.1:

                                        rm -rf /usr/local/etc/dansguardian
ln -s /usr/pbi/dansguardian-amd64/etc/dansguardian /usr/local/etc/dansguardian
killall dansguardian
cd /usr/local/sbin
fetch http://e-sac.siteseguro.ws/pfsense/8/amd64/dansguardian
chmod +x /usr/local/sbin/dansguardian
/usr/local/etc/rc.d/dansguardian.sh start

                                        and now I am uploading this post via dansguardian.  ;D

                                        1 Reply Last reply Reply Quote 0
                                        • T
                                          timthetortoise
                                          last edited by

                                          Oops, forgot about chmod +x! Good call!

                                          1 Reply Last reply Reply Quote 0
                                          • marcellocM
                                            marcelloc
                                            last edited by

                                            It will need to push a fix to freebsd ports before a new compile run.

                                            To have more then 1024 clients it also needs some changes on freebsd too.

                                            I'll try again to build a new pbi and put on my repo.

                                            Treinamentos de Elite: http://sys-squad.com

                                            Help a community developer! ;D

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.