This version has expired a while ago
** Changed in: clamav (Ubuntu)
Status: Confirmed => Invalid
** Changed in: exim4 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https
Stupid auto correct.
clamsmtp
On March 19, 2015 8:59:15 PM EDT, Scott Kitterman wrote:
>Does claimant work with Exim? If so, just use that.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/b
Sorry, I misread this issue. I thought it was failure for clamd to scan
when integrated with exim4. It's the same underlying issue though; clamd
cannot scan when either permissions or apparmor settings prevent it from
doing so.
Shall I submit the exim4 version of this as a separate issue, or shoul
** Also affects: exim4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to exim4 in Ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
To manage notif
The problem is caused by incorrect permissions on the directories
/var/spool/exim4
/var/spool/exim4/scan
and incorrect apparmor settings, as described here:
http://superuser.com/questions/344003/exim-clamav-file-access-error
One way to solve this problem would be to modify the exim4 and clamav-
This is STILL a bug in Ubuntu 14.04.1, nearly 4 years after the bug was
originally logged and 3 LTS releases.
# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=14.04
DISTRIB_CODENAME=trusty
DISTRIB_DESCRIPTION="Ubuntu 14.04.1 LTS"
# clamdscan /
/: lstat() failed: Permission denied. ERROR
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: clamav (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/7083
** Changed in: clamav (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
To manage notifications
** Changed in: clamav (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
To manage notifications about
[Expired for clamav (Ubuntu) because there has been no activity for 60
days.]
** Changed in: clamav (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.
Thanks for the input Imre,
I think I've done due diligence as far as users and permissions go.
clamav has been added to the admin and root user groups and the
directory I tested scanning for this bug report has been given 777
permissions. I also pasted the results of running stat on that
director
clamdscan is just a command line tool that issues commands to clamav-daemon.
The files are scanned by clamav-daemon, which runs as a daemon with clamav user
(by default). You can only scan folders and files to which clamav-daemon (the
clamav user) has access to.
So if you want to check a directo
Oops... nevermind about the errors in the last part of #5, I forgot to
use sudo on the service restart command:
--
awensley@uhs:/tmp$ sudo service clamav-daemon restart
--
The last test works now. However, I am still unable to scan
Thanks for the link, JG.
I didn't realize running clamdscan as root would cause problems. I did
that in all my tests to try to alleviate any permissions issues. I'll
make sure I run all my tests as a regular user from now on.
In the first test, clamdscan works on my machine as well. When I mak
Regardless of the efforts of steps in #3 to rule anything out, after
stopping apparmor with teardown and restarting clamd, I still can't scan
anything not owned by clamav. .
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubun
I'm having the same issue, but wanted to verify that this worked correctly:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/487631/comments/8
In that test, clamdscan works.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav i
I'm having a similar issue,
running clamscan as either root or as user will scan my home folder no
issues, installing clamav-daemon and running clamdscan will result in a
lot of permission errors being thrown up and some files being missed
entirely?
clamscan:
--- SCAN SUMMARY ---
** Changed in: clamav (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
--
Ubuntu-server-bugs mai
** Description changed:
Binary package hint: clamav-daemon
No matter what directory(ies) or file(s) I try to scan with clamdscan, I
receive the following error immediately:
root@uhs:/raid/Share/Public/# clamdscan -v /raid/Share/Public/
/raid/Share/Public: lstat() failed: Permiss
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in ubuntu.
https://bugs.launchpad.net/bugs/708395
Title:
clamdscan can't scan anything
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings o
20 matches
Mail list logo
