The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

clamd update to 0.93 failed on some freebsd boxes

Discussion in 'E-mail Discussions' started by nyjimbo, Apr 19, 2008.

  1. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Today we did a upcp to the new CURRENT, which appears to upgrade clamd to 0.93 and while one machine came up clean with clamd the other did not. We didnt get any errors or anything via email that clamd was down (probably because it couldnt process email with clamd down) but a few hours later I checked that machine and saw a huge paniclog full of errors about clamd.

    Restarting clamd manually came up with an error about an "Archive...." entry in clamd.conf and thats why it would not start. Had to edit out the statement and then was able to bring up clamd with a "restartsrv_clamd" and then ran a "freshclam" to be sure it was all ok.

    We had experienced this problem recently with a non-cpanel box so we knew what it was. I am not sure if the "Archive...." statement was put in by us or if it was there from the start.
     
  2. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    Another note, I see a "freshclam.conf" on both freebsd boxes with todays date, brand new OR replacements of the originals?.

    Regardless, now freshclam does not write to /var/log/clam-update.log and the entry in
    freshclam.conf shows it to write to /var/log/freshclam.log BUT is commented out.

    If I uncomment it and run freshclam it produces errors like it cant write to it due to permissions.

    Seems like the same things we are seeing on non-cpanel boxes when updating to 0.93.
     
    #2 nyjimbo, Apr 19, 2008
    Last edited: Apr 19, 2008
  3. nyjimbo

    nyjimbo Well-Known Member

    Joined:
    Jan 25, 2003
    Messages:
    1,125
    Likes Received:
    0
    Trophy Points:
    36
    Location:
    New York
    NOTE: This is also happening on our Centos 5.1 box. Clamd is running, but a new freshclam.conf is installed and no more clam-update.log entries.
     
  4. rclemings

    rclemings Member

    Joined:
    Nov 5, 2007
    Messages:
    23
    Likes Received:
    1
    Trophy Points:
    3
    I'm not noticing any problems with ClamAV 0.93 ...

    Except ...

    It seems to be crashing three or four times a day since the upgrade (last weekend). It restarts just fine, so no damage is done except for whatever slips by in the minute or two while it's down, but still ...

    WHM 11.15.0 cPanel 11.17.0-R19434
    CENTOS Enterprise 4.6 i686 on virtuozzo - WHM X v3.1.0

    rac
     
  5. deddy

    deddy Well-Known Member

    Joined:
    Oct 13, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    clamd on VPS optimized WHM/cPanel fails

    Something seems to be wrong with clamd - at least on VPS server:

    Cron Daemon message:
    Cron <root@ns1> /usr/bin/freshclam --quiet --no-warnings
    /bin/sh: /usr/bin/freshclam: No such file or directory

    service exim restart
    Shutting down exim: [ OK ]
    Shutting down antirelayd: [ OK ]
    Shutting down spamd: [ OK ]
    Starting exim: [ OK ]
    Starting exim-smtps: [ OK ]
    Starting antirelayd: [ OK ]
    Starting spamd: [ OK ]
    no clamd available

    /scripts/restartsrv_clamd
    Unable to locate clamd

    --> Manage Plugins --> Uninstall clamavconnector
    Install it again. Problem persist.

    Server Manager got no clamd entry.

    WHM 11.15.0 cPanel 11.18.6-R24255

    updating to S24255, same result :(
     
  6. deddy

    deddy Well-Known Member

    Joined:
    Oct 13, 2003
    Messages:
    131
    Likes Received:
    0
    Trophy Points:
    16
    My problem belongs to a buggy gcc compiler.

    Changing the gcc compiler to a proper working
    version did solve this issue. ;)
     
Loading...

Share This Page