Can't start squidGuard



  • Hi,

    I installed squidGuard 1.4_7 pkg v.1.9.10 together with Squid3 3.4.10_2 pkg 0.2.6, but  the service doesn't start. The system logs don't give any clue what is going on, but during the installation process I got the following warning:

    Warning: file_put_contents(/usr/pbi/squidguard-amd64/etc/squidGuard/squidguard_conf.xml): failed to open stream: No such file or directory in /usr/local/pkg/squidguard.inc on line 1031
    

    Is there a patch to make it run? The box itself is running on the pfSense 2.2-RELEASE  (amd64)  built on Thu Jan 22 14:03:54 CST 2015.



  • me too, any solution?  :-[

    [img]

    ![sg 22.jpg](/public/imported_attachments/1/sg 22.jpg)
    ![sg 22.jpg_thumb](/public/imported_attachments/1/sg 22.jpg_thumb)



  • I also cannot get this version of Squidguard to start :'(  Somebody throw us a bone here!



  • Update:  I was able to get filtering working by removing Squid 3 and putting 2.x on instead but that is not ideal, especially since it doesn't filter for viruses.  Guess I will wait for the next version of 3 at this point…



  • Somehow after update rules for squid-guard i manage to have it all work. Was really nice to see all processes works fine. That lasted for 2-3 days, and then i needed to reboot system and pow - it worked never again :(

    I remember taht nightmare when i update it to 2.1; i think they will sort it out. But me, for now keeping good old 2.1.5. I would be satisfied with it if t has new pflocker and squid as 2.2. But yeah, waiting pay out every time :)

    Cheers!



  • Hi,

    I am running AMD64 pfsense 2.2. It ist working fine with squid 3.4.10_2 pkg 0.2.6 transparent with http/https.
    I have problems, too, with squidguard 1.4_7 pkg v.1.9.10

    I rea somewhere that there could be a problem when only using the "Common" tab to configure squidguard. So I added my blacklist rules and networks to "Group ACL", saved and the on "General Settings" clicked "Save" and then "Apply" made squidguard start. I did no further tests but perhaps this could help you on your problems.

    But squid in general should work first before trying squidguard.



  • Had a similar problem, which I did to solve was to delete the squid package and squidguard then accessing via SSH and accessing the console used the viconfig command and edited the configuration file, deleted all the lines related to squidguard / squid (using the? squid). Reinstalled the packages and worked properly.

    Just be careful if delete wrong in the configuration file will stop your pfSense

    Sorry for bad english



  • This is what I have seen.  Squidguard won't actually start until traffic goes thru squid.  Also, after a reboot, you have to download the blacklists.  Right now, I have pfSense 2.2 with Squid and Squidguard up and running successfully against LDAP authentication.



  • I have the same problem.

    Squidguard runs after first installation. Then after the next reboot it wont start.

    Additionally, CPU load ist running at 100%.

    Only after you donwload the blacklist manually again the service will start.

    Thats not the way it should be, right?

    I have installed a fresh pfsense VM - the same problem.



  • I, too, can't get squidguard to start from a reboot without manually downloading the blacklist.  Once that is done, it takes off just fine.  I did just discover this in my system log from the most recent restart:

    Mar 11 07:51:03 php: squidGuard_blacklist_update.sh: The command 'umount -f /tmp/squidGuard' returned exit code '1', the output was 'umount: /tmp/squidGuard: not a file system root directory'
    Mar 11 07:51:03 php: squidGuard_blacklist_update.sh: The command '/usr/pbi/squid-amd64/local/sbin/squid -k reconfigure' returned exit code '1', the output was 'Shared object "libmd5.so.0" not found, required by "squid"'
    Mar 11 07:48:46 php: squidGuard_blacklist_update.sh: The command 'chmod 1777 /tmp/squidGuard' returned exit code '1', the output was 'chmod: /tmp/squidGuard: No such file or directory'
    Mar 11 07:48:46 php: squidGuard_blacklist_update.sh: The command '/sbin/mdmfs -s 300M md15 /tmp/squidGuard' returned exit code '1', the output was 'mdmfs: mount exited with error code 1'
    Mar 11 07:46:08 squid[58752]: Squid Parent: (squid-1) process 77849 started

    I also experienced high CPU after the system had been running for at least a day, so it makes me wonder if there is something wrong with the configuration of the automatic Blacklist update that is causing the download to be created in the wrong directory.

    Thanks for any assistance you can provide.



  • @l4k3k3m4n:

    I have the same problem.

    Squidguard runs after first installation. Then after the next reboot it wont start.

    Additionally, CPU load ist running at 100%.

    Only after you donwload the blacklist manually again the service will start.

    Thats not the way it should be, right?

    I have installed a fresh pfsense VM - the same problem.

    Same problem for me … someone report this as a bug ?



  • From what I understand:

    New squidGUard does not always run when there is no work for it to do.
    'Shared object "libmd5.so.0" not found, required by "squid"' error seems to go away once you have downloaded and compiled the blacklist.



  • Rebuilding the DB only lasts till a reboot.



  • I am facing the same problem too.
    Is there away to get the blacklist autorebuild & the squidguard will run automatically after a reboot?

    thanks!



  • I think I found a workaround. I am using amd64 pfsense 2.2.2

    1. goto the blacklist configuration tab for squidGuard, click download.
          - the system will update & reconfigure the blacklist.

    2. you shall find a script file at /tmp/squidGuard_blacklist_update.sh

    3. copy this sh file to somewhere else, eg. /usr/local/bin/squidGuard_blacklist_update.sh

    4. edit the /usr/local/etc/rc.d/squid.sh to include the above script.

    therefore, after a reboot, the system would download a fresh blacklist & do the neccessary configuration before start the squid.  ;)

    tq



  • @kudamuda:

    I think I found a workaround. I am using amd64 pfsense 2.2.2

    1. goto the blacklist configuration tab for squidGuard, click download.
          - the system will update & reconfigure the blacklist.

    2. you shall find a script file at /tmp/squidGuard_blacklist_update.sh

    3. copy this sh file to somewhere else, eg. /usr/local/bin/squidGuard_blacklist_update.sh

    4. edit the /usr/local/etc/rc.d/squid.sh to include the above script.

    therefore, after a reboot, the system would download a fresh blacklist & do the neccessary configuration before start the squid.  ;)

    tq

    Can you tell me how you managed this?  I tried to do this as you say however 2 things are unclear:-

    1. /usr/local/etc/rc.d/squid.sh appears to be overwritten every reboot which means any changes made are overwritten.
    2. Where in the script did you place it? I thought this would suffice but cant test due to 1)
    rc_start() {
            if [ -z "`ps auxw | grep "[s]quid -D"|awk '{print $2}'`" ];then
            /usr/pbi/squid-amd64/sbin/squid -D
            /usr/local/bin/squidGuard_blacklist_update.sh
    fi
    


  • I managed to produce a working system by just:

    1. goto the blacklist configuration tab for squidGuard, click download.
          - the system will update & reconfigure the blacklist.

    2. you shall find a script file at /tmp/squidGuard_blacklist_update.sh

    3. copy this sh file to /usr/local/etc/rc.d/

    granted that i did build on kudamuda's work which was spot on. i am rather worried about the initial error though, this hack is only so as to continue moving along with my setup. once i find some time ill look further into the error, from the logs i can tell that it has something to do with squidGuard losing its DB on boot… ;)



  • @kudamuda:

    I think I found a workaround. I am using amd64 pfsense 2.2.2

    1. goto the blacklist configuration tab for squidGuard, click download.
          - the system will update & reconfigure the blacklist.

    2. you shall find a script file at /tmp/squidGuard_blacklist_update.sh

    3. copy this sh file to somewhere else, eg. /usr/local/bin/squidGuard_blacklist_update.sh

    4. edit the /usr/local/etc/rc.d/squid.sh to include the above script.

    therefore, after a reboot, the system would download a fresh blacklist & do the neccessary configuration before start the squid.  ;)

    tq

    Dear Expert,

    I am trying to follow the instructions which need your help.

    1-  I have Copied the squidGuard_blacklist_update.sh from the path /tmp
    But i unable to understand the above steps no 4  can you guide me in detail how i can follow the above step no 4 need your help in detail.

    thanks in Advance.

    Regards,
    Noor Uz Zaman



  • Hi!
    I did this:
    After downloading a blacklist from shallalist.de , create a target Category (call it as you want) add a least one domain and start Squidguard with the apply button (if it hasn't started yet) According to certain posts regarding to the Squidguar manual, this is a necesary condition to use blacklists and another configurations. In my particular case, I've created a target category called "White_list" on which I've added the sites contained in the default blacklist but that I wish to access anytime (for example, wikipedia.org, wikimedia.org and pfsense.org).

    after doing this, I can reboot the server, an the SquidGuard service boots automatically after one minute.

    Try it and, if it works for you, come back and tell us!



  • @chidgear:

    Hi!
    I did this:
    After downloading a blacklist from shallalist.de , create a target Category (call it as you want) add a least one domain and start Squidguard with the apply button (if it hasn't started yet) According to certain posts regarding to the Squidguar manual, this is a necesary condition to use blacklists and another configurations. In my particular case, I've created a target category called "White_list" on which I've added the sites contained in the default blacklist but that I wish to access anytime (for example, wikipedia.org, wikimedia.org and pfsense.org).

    after doing this, I can reboot the server, an the SquidGuard service boots automatically after one minute.

    Try it and, if it works for you, come back and tell us!

    Thanx. It really works.



  • You can try the following if you have / had a line similar to this during install (and it's not the lack of blacklist update!):
    "Warning: file_put_contents(/usr/pbi/squidguard-amd64/etc/squidGuard/squidguard_conf.xml): failed to open stream: No such file or directory in /usr/local/pkg/squidguard.inc on line 1032"

    Open the file '/usr/local/pkg/squidguard_configurator.inc'

    Find the line:
    define('SQUIDGUARD_WORKDIR', SQUIDGUARD_LOCALBASE . '/etc/squidGuard');

    Change it to:
    define('SQUIDGUARD_WORKDIR', SQUIDGUARD_LOCALBASE . '/local/etc/squidGuard');

    Worked for me!



  • I have tried ismaelnoble's approach. Working for me so far.



  • Did the trick for me to….. this has been driving me mad!!!!

    Thanks.

    @chidgear:

    Hi!
    I did this:
    After downloading a blacklist from shallalist.de , create a target Category (call it as you want) add a least one domain and start Squidguard with the apply button (if it hasn't started yet) According to certain posts regarding to the Squidguar manual, this is a necesary condition to use blacklists and another configurations. In my particular case, I've created a target category called "White_list" on which I've added the sites contained in the default blacklist but that I wish to access anytime (for example, wikipedia.org, wikimedia.org and pfsense.org).

    after doing this, I can reboot the server, an the SquidGuard service boots automatically after one minute.

    Try it and, if it works for you, come back and tell us!


Log in to reply