store | blogs | forums | twitter | facebook | wiki | downloads | support portal
Atomic Secure Linux
It is currently Sat Nov 29, 2014 2:00 am

» Feed - Atomicorp

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 4 posts ] 
Author Message
 Post subject: ClamAV 0.95 - lstat() failed [SOLVED]
Unread postPosted: Sun Apr 05, 2009 6:10 am 
Offline
Forum User
Forum User

Joined: Tue Mar 28, 2006 4:03 am
Posts: 59
Hello,
I installed ClamAV 0.95 from the atomic repository, and now I see this in my logwatch email:

lstat() failed on: /var/spool/qscan/tmp/host.tld123879626679212033
lstat() failed on: /var/spool/qscan/tmp/host.tld123879681779212278
lstat() failed on: /var/spool/qscan/tmp/host.tld123879682279212300
lstat() failed on: /var/spool/qscan/tmp/host.tld123879740679212594
lstat() failed on: /var/spool/qscan/tmp/host.tld123879751079212695
lstat() failed on: /var/spool/qscan/tmp/host.tld123879752379212716
lstat() failed on: /var/spool/qscan/tmp/host.tld123879754079212738
lstat() failed on: /var/spool/qscan/tmp/host.tld123879763379212809

What can I do to correct this problem (which doesn't seem to block any email)?
Could it be an access problem to /var/spool/qscan/tmp/ by clamd?
Thanks!


Top
 Profile  
 
 Post subject: Re: ClamAV 0.95 - lstat() failed
Unread postPosted: Sun Apr 05, 2009 11:09 am 
Offline
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin

Joined: Wed Dec 31, 1969 8:00 pm
Posts: 7959
Location: earth
That means that clamd cant read the file, its generally permissions related.


Top
 Profile  
 
 Post subject: Re: ClamAV 0.95 - lstat() failed
Unread postPosted: Tue Apr 07, 2009 2:19 am 
Offline
Forum User
Forum User

Joined: Wed Feb 11, 2009 7:42 am
Posts: 26
Okay, I chmoded /var/spool/qscan/tmp/ to 777 (not so clean) and everything works fine again!


Top
 Profile  
 
 Post subject: Re: ClamAV 0.95 - lstat() failed [SOLVED]
Unread postPosted: Sun Aug 30, 2009 2:11 pm 
Offline
Forum User
Forum User

Joined: Sat Jul 21, 2007 7:31 pm
Posts: 28
This is an older thread but for people looking for a solution to the problem try this:

It may be as easy as restarting clamd. It was in my case. To be sure though go through these steps:
Code:
ps -ef | grep clamd

Look at the first column. If the user is clamd and not qscand then check the clamd conf file for the line "User qscand":
Code:
vi /etc/clamd.conf
/User

If it says "User clamd" then change it to "User qscand". Either way, restart clamd afterwards.
Code:
service clamd restart

Verify that the process is now owned by qscand:
Code:
ps -ef | grep clamd

Then verify that /var/spool/qscan/tmp is owned by qscand:
Code:
ls -l /var/spool/qscan

If it's not, then change it:
Code:
chmod -R qscand:qscand /var/spool/qscan/tmp


This was based on Centos 5.3 with the following packages:
clamd-0.95.2-1.el5.art
qmail-scanner-2.06-1.el5.art


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 4 posts ] 

» Feed - Atomicorp

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: Google [Bot] and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group