HAVP must be reinstalled after *every* reboot & workaround found in board.

  • Hello

    I've a box with HAVP+Squid-reverse and everytime i reboot the machine the antivirus doesn't start and web browsing is unavailable. The Antivirus Proxy is stopped after reboot and no way to start it.

    This is pfSense 2.0 64bit and Squid-reverse as transparent proxy and HAVP as parent for Squid. With Squid 2 the same problem was there.

    The only way to get it working again is to remove and install again then it works until reboot.

    I've found a workaround in this board that works. This: http://forum.pfsense.org/index.php/topic,31869.msg201968.html#msg201968

    When i reinstall the package, the user havp is in /etc/passwd, after reboot is missing. The workaround works because it "fixes" the user in /etc/passwd.

    Anyone knows how to fix the problem without this workaround?


  • SSDD (same sh*it distribution different)…  ;D

    Same behavior of HAVP under pfSense 2.0.1 nanobsd 4G i386.
    Reinstalling the package makes it work, does not survive a reboot.

    The user havp stays in /etc/passwd so the fix proposed here http://forum.pfsense.org/index.php/topic,31869.msg201968.html#msg201968 doesn't apply
    But database in /var/db/clamav disappears (actually even the directory clamav dissappears).

    Is this a bug or is HAVP still not supposed to run with nanobsd ?

  • Similar issues. After the third time of HAVP crapping the bed on me I've removed it and the proxy from my system and have no plans to reinstall. When it works, it works great. When it does not you are kicked back to the stone age.  If donations to this module would get it back on its feet and working well with 2.0 I would be up for doing as such.

  • Amarth,

    Untils this havp issue is fixed, try dansguardian package, it has a built in clamav integration.

    Marcello Coutinho

  • on reboot dansguardian blocks all access, unless i start clamv manually, is there a work around?

  • @samham:

    on reboot dansguardian blocks all access, unless i start clamv manually, is there a work around?

    Did you waited few minutes to check if service is running?

    I do not see this issue on my dansguardian servers.

    You can create a clamav.sh script on /usr/local/etc/rc.d folder to force it startup.

  • thanks creating the script file took care of it

Log in to reply