Squidguard, pfSense 2.3, not starting, fresh install

  • Hello,

    I have recently installed squidguard for the first time unter the package manager.

    I enabled the blacklist, set the blacklist URL and was able to download the blacklist. I also set a Common ACL, I set Groups ACL and a dummy Target category.

    However I am not able to start squidguard by clicking at the "Apply" button under General settings.

    Moreover I only have following a log file located at: "/var/log/squidGuard/squidGuard.log" that only says the following:

    2016-05-17 10:34:58 [4408] squidGuard 1.4 started (1463459698.364)
    2016-05-17 10:34:58 [4408] db update done
    2016-05-17 10:34:58 [4408] squidGuard stopped (1463459698.365)
    2016-05-17 10:36:33 [60975] squidGuard 1.4 started (1463459793.950)
    2016-05-17 10:36:33 [60975] db update done
    2016-05-17 10:36:33 [60975] squidGuard stopped (1463459793.950)
    2016-05-17 10:37:07 [72209] squidGuard 1.4 started (1463459827.060)
    2016-05-17 10:37:07 [72209] db update done
    2016-05-17 10:37:07 [72209] squidGuard stopped (1463459827.060)

    I also verified the owner ship to squid of the folders /var/log/squid and /var/log/squidGuard.

    I don't know why squidGuard doesn't start.

    Thanks in advance and kind regards,

  • Hello,

    any new hints? Can't get it running.

    Thanks very much in advance.

  • Sorry, I cannot help, but have the same issue. (fresh install pfSense 2.3.1)

    In the Log (Package/SquidGuard/Logs > FilterLog) I see the same "starting, db update done, stopping" behaviour as you described.

    I checked from the console to verify whether a separate install of the Squid package via the webGUI is needed. But thats a "no". - When the squidGuard package is installed via the webGUI then it automatically installs also squid 3. (But the webGUI still shows the squid package as not installed. which is simply due to the fact the the squid package in the webGUI is a bundle of several packaged, not squid 3 alone.)
    However, I have read that SG somehow looks for squid2, so perhaps that is related to the problem. I will keep looking in the logs for more infos.

    EDIT: I am not sure yet as I don't know how to verify it, but it seems that SG is running even thogh its show as stopped. I just had a certain site being the access rejected, and after removing the SG package it worked again. (Direct correlation not verified, but I had the impression.)

    Anyone an idea how I can get more reliable infos on the real state of SG?

Log in to reply