Results 1 to 10 of 10

Thread: Clamavd gone missing

Hybrid View

  1. #1
    Ecky NNTP User

    Default Clamavd gone missing


    Spotted errors like these in mail.log:

    Jan 26 14:04:11 beastie amavis[4126]: (04126-07) (!)run_av
    (ClamAV-clamd, built-in i/f): Too many retries to talk to
    /var/run/clamav/clamd (Can't connect to UNIX socket
    /var/run/clamav/clamd: No such file or directory) at (eval 99) line
    310.

    Went for a look to see if the clamavd file was there, and found that
    the /var/run/clamav folder was missing

    According to Yast clamav was still installed but in an attempt to get
    the files back I uninstalled and then reinstalled clamav

    Still no clamavd file or /var/run/clamav folder

    What provides clamavd if it isn't clamav?

    Any ideas on how I get clamavd back appreciated


    --
    Ecky
    ------------------------------------------------------------------------
    Ecky's Profile: http://forums.opensuse.org/member.php?userid=3518
    View this thread: http://forums.opensuse.org/showthread.php?t=406077


  2. #2
    Ecky NNTP User

    Default Re: Clamavd gone missing


    Typo there, clamd not clamavd ... doh at me!

    And after re-installing it's in /usr/sbin not /var/run/clamav so I'm
    editing amavisd.conf to suit and seeing how it goes


    --
    Ecky
    ------------------------------------------------------------------------
    Ecky's Profile: http://forums.opensuse.org/member.php?userid=3518
    View this thread: http://forums.opensuse.org/showthread.php?t=406077


  3. #3
    Tilman Schmidt NNTP User

    Default Re: Clamavd gone missing

    Ecky schrieb:
    > Typo there, clamd not clamavd ... doh at me!
    >
    > And after re-installing it's in /usr/sbin not /var/run/clamav so I'm
    > editing amavisd.conf to suit and seeing how it goes


    Don't. These are two separate things. /usr/sbin/clamd is the actual
    program, while /var/run/clamav/clamd is the communication socket for
    talking to it. The socket is created by the program once it is running.
    So start clamd by entering (as root)

    /usr/sbin/rcclamd start

    give it a minute or so to get up to speed, and then look again whether
    the socket is there with

    ls -l /var/run/clamav

    If it isn't, look in in the system log (/var/log/messages) for messages
    from clamd telling you why it couldn't start.

    HTH
    T.

Posting Permissions

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