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

    HAVP Problems

    2.1 Snapshot Feedback and Problems - RETIRED
    2
    6
    6.5k
    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.
    • F
      fredfred5
      last edited by

      Hey guys,

      I'm using the May 1st build and am having problems getting HAVP to run properly.
      When the package is first installed the service wont start and the database can't be updated. By looking at the various errors I've worked out I needed to do the following to get the service to start and updating:

      Under System -> User Manager in the pfsense web interface
      Create user group "havp"
      Create user "havp" and join "havp" and admin groups
      Create user "clamav" and  join "havp" and admin groups (I don't know if joining groups is necessary for this user but I've yet to test it)

      Using the shell (option 8 ) on the pfsense machine

      mkdir /var/db/clamav
      mkdir /var/log/clamav
      chown clamav /var/db/clamav
      chown clamav /var/log/clamav
      mkdir /var/log/havp
      chown havp /var/log/havp
      

      On restarting pfsense this will now stop the errors when attempting to start the HAVP package, it will also allow freshclam to update the virus database. All seems ok at this point.

      However under Services -> Antivirus on the web interface when the File Scanner is started, for example with the Temp path, this message is displayed:

      2012.05.02 07:23:13 Starting scan file '/tmp'.
      --------------------------------------
      ERROR: Can't connect to clamd: No such file or directory
      
      ----------- SCAN SUMMARY -----------
      Infected files: 0
      Total errors: 1
      Time: 0.000 sec (0 m 0 s)
      

      I've looked in /usr/local/etc/clamd.conf (I'm assuming that's the correct place) and I see these lines:

      # socket
      LocalSocket /var/run/clamd.sock
      

      I've check that clamd.sock is where it is supposed to be (it is), and i've made sure that users clamav and havp both have permissions for it.
      I still get the same error when I try to run the file scanner again.

      I don't know if it relevant but on a previous snapshot (I can't remember which, sorry) when using freshclam from the shell in pfsense, I got an error like:

      clamd not notified: Can't connect to clamd through /var/run/clamav/clamd.sock
      no such file
      

      Now it wouldn't find the socket there beacause its in /var/run/clamd.sock, I don't understand where its getting the clamav folder from. I cant find a reference to that path in any other file I've looked at though.

      What am I missing?  ??? Any help would be greatly appreciated.

      p.s sorry for the wall of text   :-[

      1 Reply Last reply Reply Quote 0
      • D
        dvserg
        last edited by

        This package has not been tested to work with the 2.1

        SquidGuardDoc EN  RU Tutorial
        Localization ru_PFSense

        1 Reply Last reply Reply Quote 0
        • F
          fredfred5
          last edited by

          @dvserg:

          This package has not been tested to work with the 2.1

          That will probably be why its not working then.

          Are there any plans for supporting HAVP under 2.1? Or is there an alternative you can suggest?

          1 Reply Last reply Reply Quote 0
          • D
            dvserg
            last edited by

            It will be done in some time

            SquidGuardDoc EN  RU Tutorial
            Localization ru_PFSense

            1 Reply Last reply Reply Quote 0
            • D
              dvserg
              last edited by

              Try again.

              SquidGuardDoc EN  RU Tutorial
              Localization ru_PFSense

              1 Reply Last reply Reply Quote 0
              • F
                fredfred5
                last edited by

                OK I'm now using the Sunday May 13 build, fresh install. Still the same problem.

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