Page 1 of 2 12 LastLast
Results 1 to 20 of 31

Thread: ClamAV fails to start after update to v0.97.3

  1. #1
    Join Date
    Sep 2006
    Posts
    57

    ClamAV fails to start after update to v0.97.3

    ClamAV fails to start after update to v0.97.3. After the update/compile, I receive these error messages:

    Restarting freshclam.
    Shutting down freshclam: [FAILED]
    Starting freshclam: ERROR: This tool requires libclamav with functionality level 63 or higher (current f-level: 62)
    [FAILED]
    Restarting clamd.
    cat: /var/run/clamd.pid: No such file or directory
    kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]
    Starting clamd daemon: /usr/local/sbin/clamd
    Bytecode: Security mode set to "TrustSigned".
    LibClamAV Error: cl_load(): Can't get status of /var/lib/clamav
    ERROR: Can't get file status
    Starting freshclam daemon: /usr/local/bin/freshclam -d -c 6
    ERROR: This tool requires libclamav with functionality level 63 or higher (current f-level: 62)

    Running ./build versions still shows that an ClamAV can be updated to to v0.97.3. It's as if the update didn't take?

    Google search for "This tool requires libclamav with functionality level 63 or higher" didn't really reveal helpful information.


    Any ideas?

    Thanks,
    Sloane

  2. #2
    Join Date
    Aug 2008
    Posts
    4,695
    freshclam -v

    cd /usr/local/directadmin/custombuild
    ./build update
    ./build clean
    ./build clamav d

  3. #3
    Join Date
    Sep 2006
    Posts
    57
    freshclam -v yields "This tool requires libclamav with functionality level 63 or higher (current f-level: 62)"

    I did try to build it again, same error messages as 1st post. Thanks for the suggestion, though.
    This is a Centos 5 box, 32 bit, up to date.
    One thing that stands out: /var/lib/clamav no longer exists (thus I am assuming the error "LibClamAV Error: cl_load(): Can't get status of /var/lib/clamav").

    I will see what my recent backups can provide.

    Sloane

  4. #4
    Join Date
    Feb 2006
    Posts
    231
    I have the same error:

    Code:
    Starting freshclam: ERROR: This tool requires libclamav with functionality level 63 or higher (current f-level: 62)
                                                               [FAILED]
    Restarting clamd.
    Shutting down clamd:                                       [  OK  ]
    Starting clamd: ERROR: This tool requires libclamav with functionality level 63 or higher (current f-level: 62)
                                                               [FAILED]
    Anyone knows a solution?

  5. #5
    Join Date
    Aug 2008
    Posts
    4,695

  6. #6
    Join Date
    Feb 2006
    Posts
    231
    Thanks for replying. I did

    Code:
    ldconfig
    but nothing happens. In the past I succesfully updated clamav with custumbuild twice. Is the filename just libclamav and how can I remove and update the file?

  7. #7
    Join Date
    Feb 2006
    Posts
    231
    Under /usr/lib/ I have libclamav.so and libclamav.so.6 both linking to libclamav.so.6.1.12
    Under /usr/local/lib/ I have libclamav.so and libclamav.so.6 both linking to libclamav.so.6.1.11

    Should I delete one of them?

  8. #8
    Join Date
    Aug 2008
    Posts
    4,695
    I would remove the symbolic links in /usr/local/lib

    More than likely that is the problem.

  9. #9
    Join Date
    Aug 2006
    Location
    LT, EU
    Posts
    7,795
    If you want to use CustomBuild for ClamAV installation, you need to be sure that there is no other instance of it installed on the server, or at least that you have no start/stop scripts on the system. Why? Because CustomBuild doesn't touch start/stop script if it exists on the system, we let users do any changes they want (that's why the file is not replaced with every installation). In addition to, ClamAV is installed to /usr, not /usr/local, so if you have an installation in /usr/local, the system uses binaries from /usr/local (it gives the priority to them). The same could be said about apache, pureftpd and other CustomBuild installations. For example, if you'd install apache to /usr/local, the system would use /usr/local/bin/httpd instead of /usr/bin/httpd when you call it from ssh, and which service to start is described in start/stop script.
    Martynas Bendorius
    MB Martynas IT. Professional server management company. Official DirectAdmin, CloudLinux, LiteSpeed and Comodo partners.

  10. #10
    Join Date
    Feb 2006
    Posts
    231
    Thank you scsi for the fast replies. And thank you Martinas for your clear reply. I now understand more about the way custombuild works. I removed the libclam* symbolic links in /usr/local/lib and all works fine now. Thanks again!

  11. #11
    Join Date
    May 2010
    Posts
    16
    Quote Originally Posted by smtalk View Post
    If you want to use CustomBuild for ClamAV installation, you need to be sure that there is no other instance of it installed on the server, or at least that you have no start/stop scripts on the system. Why? Because CustomBuild doesn't touch start/stop script if it exists on the system, we let users do any changes they want (that's why the file is not replaced with every installation). In addition to, ClamAV is installed to /usr, not /usr/local, so if you have an installation in /usr/local, the system uses binaries from /usr/local (it gives the priority to them). The same could be said about apache, pureftpd and other CustomBuild installations. For example, if you'd install apache to /usr/local, the system would use /usr/local/bin/httpd instead of /usr/bin/httpd when you call it from ssh, and which service to start is described in start/stop script.
    Can u explain how to check if u have a doble installation of something or in particular Clamav and Freshclam(i' m full of this process instaces)
    Ho to remove the installation with and without directadmin custom buil?
    That will be very usefull!!
    Thanks in advance

    GMC

  12. #12
    Join Date
    Aug 2006
    Location
    LT, EU
    Posts
    7,795
    If you used http://forum.directadmin.com/showthread.php?t=22587, then you can cd to clamav directory and execute "make uninstall".
    Martynas Bendorius
    MB Martynas IT. Professional server management company. Official DirectAdmin, CloudLinux, LiteSpeed and Comodo partners.

  13. #13
    Join Date
    Oct 2003
    Posts
    165
    Quote Originally Posted by smtalk View Post
    If you used http://forum.directadmin.com/showthread.php?t=22587, then you can cd to clamav directory and execute "make uninstall".
    How to make uninstall clamav exactly?

    Thanks!
    DRKT - IT Manager
    OS: RedHat, CentOS
    Apache 2.4 - Php 5.6 - MySQL 5.6
    Exim 4.89 - dovecot 2.2 - IMAP - SpamAssassin - ClamAV

  14. #14
    Join Date
    May 2014
    Posts
    2

    solved?

    i've solved with this:

    Code:
    mkdir /usr/local/share/clamav
    chmod 775 /usr/local/share/clamav
    chown -R clamav:clamav /usr/local/share/clamav
    freshclam -v

  15. #15
    Join Date
    Apr 2011
    Location
    Amsterdam, NL
    Posts
    102
    The update to clamav-0.98.5 fails with
    Code:
    [root@vps ~]# service clamd start
    Starting clamd: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    [root@vps ~]# service freshclam start
    Starting freshclam: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    Before the update clamav ran fine.

  16. #16
    Join Date
    Nov 2010
    Location
    Alezio - Lecce- Apulia - South Italy
    Posts
    103
    Quote Originally Posted by Jan_E View Post
    The update to clamav-0.98.5 fails with
    Code:
    [root@vps ~]# service clamd start
    Starting clamd: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    [root@vps ~]# service freshclam start
    Starting freshclam: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    Before the update clamav ran fine.
    me too, I've the same problem with a server, not a vps

  17. #17
    Join Date
    Nov 2014
    Posts
    6
    Quote Originally Posted by Jan_E View Post
    The update to clamav-0.98.5 fails with
    Code:
    [root@vps ~]# service clamd start
    Starting clamd: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    [root@vps ~]# service freshclam start
    Starting freshclam: ERROR: This tool requires libclamav with functionality level 79 or higher (current f-level: 77)
                                                               [FAILED]
    Before the update clamav ran fine.
    If you are updating from source code, go back to your your SRC directory and run make uninstall.
    This should remove the now out-of-date libclamav libs and symlinks from the previous version install (usually in /usr/local/lib or /usr/local/lib64).

  18. #18
    Join Date
    Nov 2014
    Posts
    6
    Quote Originally Posted by axelerator View Post
    If you are updating from source code, go back to your your SRC directory and run make uninstall.
    This should remove the now out-of-date libclamav libs and symlinks from the previous version install (usually in /usr/local/lib or /usr/local/lib64).
    clamav-upgrade.PNG

    From the horses mouth..

  19. #19
    Join Date
    Nov 2014
    Posts
    6
    Quote Originally Posted by axelerator View Post
    clamav-upgrade.PNG

    From the horses mouth..
    http://http://www.clamav.net/doc/upgrade.html

  20. #20
    Join Date
    Apr 2011
    Location
    Amsterdam, NL
    Posts
    102
    Quote Originally Posted by axelerator View Post
    If you are updating from source code, go back to your your SRC directory and run make uninstall.
    This should remove the now out-of-date libclamav libs and symlinks from the previous version install (usually in /usr/local/lib or /usr/local/lib64).
    I am not updating from source code. I am using custombuild for ClamAV:
    Code:
    #ClamAV-related Settings
    clamav=yes
    clamav_exim=yes
    Custombuild did the update to 0.98.5 and failed.

Page 1 of 2 12 LastLast

Similar Threads

  1. clamav update via custombuild fails
    By shaggy in forum General Technical Discussion & Troubleshooting
    Replies: 10
    Last Post: 06-21-2013, 11:14 AM
  2. Apache fails to start
    By Ankit in forum Apache (WWW)
    Replies: 4
    Last Post: 01-19-2009, 07:16 AM
  3. Update from 1.31.5 to 1.32 fails
    By bruno in forum DirectAdmin Version Updates
    Replies: 8
    Last Post: 06-09-2008, 08:24 PM
  4. update 1.28.0 > 1.28.1 fails
    By Remco00 in forum Admin-Level Difficulties
    Replies: 8
    Last Post: 11-13-2006, 11:49 PM
  5. Clamav fails in rar v3 freesbd
    By tsiou in forum FreeBSD 5.x
    Replies: 0
    Last Post: 10-20-2006, 12:40 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •