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

    HAVP not found, fail clamd

    Scheduled Pinned Locked Moved pfSense Packages
    3 Posts 3 Posters 1.4k 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.
    • M
      maykel535
      last edited by

      Hi, I have installed HAVP proxy antivirus http. When I start the havp:

      22/01/2014 13:02:51 Running as user: havp, group: havp
      22/01/2014 13:02:51 Use transparent proxy mode
      22/01/2014 13:02:51 –- Initializing Clamd Socket Scanner
      22/01/2014 13:03:20 === Starting HAVP Version: 0.91
      22/01/2014 13:03:20 === Mandatory locking disabled! KEEPBACK settings not used!
      22/01/2014 13:03:20 Running as user: havp, group: havp
      22/01/2014 13:03:20 Use transparent proxy mode
      22/01/2014 13:03:20 --- Initializing Clamd Socket Scanner
      22/01/2014 13:04:20 Clamd: Could not connect to scanner! Scanner down?
      22/01/2014 13:04:20 ERROR: Clamd Socket Scanner failed EICAR virus test! (Could not connect to scanner socket)

      Clamd fails... I need the squid install?? or not necesary?

      Thanks in advanced.

      1 Reply Last reply Reply Quote 0
      • BBcan177B
        BBcan177 Moderator
        last edited by

        If you wait a little bit, I think it will download the latest virus database and start on its own.

        "Experience is something you don't get until just after you need it."

        Website: http://pfBlockerNG.com
        Twitter: @BBcan177  #pfBlockerNG
        Reddit: https://www.reddit.com/r/pfBlockerNG/new/

        1 Reply Last reply Reply Quote 0
        • Z
          Zosimo
          last edited by

          Actually, this happens because the HAVP config expects to find the following files at /var/run/clamav:

          • clamd.sock

          • clamd.pid

          The thing is, in pfSense those files are found in /var/run, which is why the package can't find them. Moreover, there seems to be no way to change the path in the config file (and I read somewhere this was hardcoded into the scanner). The current workaround for this is creating this directory and linking the files together.

          mkdir /var/run/clamav
          ln -s /var/run/clamd.sock /var/run/clamav/clamd.sock && ln -s /var/run/clamd.pid /var/run/clamav/clamd.pid
          
          

          The problem is that these files get lost on every reboot. I've tried modifying the service startup script to check for this automatically, but have had no luck so far.

          Hope this helps

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