Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

Updating Virus Patterns - Logger Error

Discussion in 'General Discussion' started by urantian, Nov 12, 2007.

  1. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    Greetings!

    I have the following error in the output of my UPCP cron job:

    Updating Virus Patterns...ERROR: Problem with internal logger
    (--log=/var/log/clam-update.log).
    ...Done

    I have searched for a solution, and have been unable to find one. I am wondering whether there is something wrong with the permission settings for the CLAIM-UPDATE.LOG file.

    This is how the file is listed on my server:

    -rw------- 1 clamav root 141602 Oct 30 21:46 clam-update.log

    Are these permissions correct? If yes, what else could be the cause and solution?

    Thank you!

    ---Michael
     
  2. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    I found a posting here indicating that the file permissions should this:

    -rw-r--r-- 1 clamav clamav 141602 Oct 30 21:46 clam-update.log

    I have updated the file as above, and will see how the update performs tonight.

    ---Michael
     
  3. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    Well, that didn't work. After updating the file permissions, I am still getting the same error in the log. Does anyone know what could be wrong?

    Thank you!

    ---Michael
     
  4. Tam

    Tam Well-Known Member

    Joined:
    Jul 31, 2004
    Messages:
    108
    Likes Received:
    1
    Trophy Points:
    168
    We had the same error in last night's cpup on one of our dedicated servers. But looking at the output from a manual cpup in WHM showed ...

    I ran freshclam -v in SSH and it appeared to update with a few errors though ...

    Checked permissions on the clamav folder and files and they were set with group and user ID numbers rather than the expected user clamav, so I ran ...

    chown -R clamav:clamav /usr/share/clamav

    Then ran freshclam -v again and no errors, although there seems to be a problem with retrieving the incremental update ...

    AND cpup runs with no errors now :)

    .
     
    #4 Tam, Nov 13, 2007
    Last edited: Nov 13, 2007
  5. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    Thank you! I applied the CHMOD on the directory and FRESHCLAM appeared to run okay. Here is the output from an additional run:

    So, it appears to work now.

    ---Michael
     
  6. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    I am still getting the same, original error during the UPCP cron job, even though the FRESHCLAM appears to be working:

    What else could be causing this?

    ---Michael
     
  7. Tam

    Tam Well-Known Member

    Joined:
    Jul 31, 2004
    Messages:
    108
    Likes Received:
    1
    Trophy Points:
    168
    Micheal, going back to the previous post, there was no chmod involved, I just chowned the problem files with user and group clamav (which is what they should be). Just try running chown clamav:clamav on that file, I no longer have the issue.

    .
     
  8. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    I'm sorry! I *DID* use CHOWN earlier, but mistakenly said CHMOD in my post here. The directory is set up as CLAMAV:CLAMAV and I am still having the logger problem.

    In the CLAMAV directory structure, what should the files be set as, as far as CHMOD? the files in the .INC directories are 644 (rw-r--r--).

    ---Michael
     
  9. Tam

    Tam Well-Known Member

    Joined:
    Jul 31, 2004
    Messages:
    108
    Likes Received:
    1
    Trophy Points:
    168
    Perhaps I failed to mention that you should ...

    chown clamav:root /var/log/clam-update.log

    See if that helps :)

    Permissions was not the issue for me (and the permissions you mentioned are right)

    .
     
  10. urantian

    urantian Well-Known Member

    Joined:
    Jan 26, 2005
    Messages:
    95
    Likes Received:
    1
    Trophy Points:
    158
    Location:
    Fayetteville, Arkansas
    cPanel Access Level:
    Root Administrator
    Thank you! I have that in place now, and will see how it works tonight.

    ---Michael
     
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice