I'm trying to get amavis to play using clamd and tried to follow this:
# ### http://www.clamav.net/ ['ClamAV-clamd', &ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"], qr/\bOK$/, qr/\bFOUND$/, qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], # # NOTE: run clamd under the same user as amavisd, or run it under its own # # uid such as clamav, add user clamav to the amavis group, and then add # # AllowSupplementaryGroups to clamd.conf; # # NOTE: match socket name (LocalSocket) in clamav.conf to the socket name in # # this entry; when running chrooted one may prefer socket "$MYHOME/clamd".
# ### http://www.clamav.net/ and CPAN (memory-hungry! clamd is preferred) # # note that Mail::ClamAV requires perl to be build with threading! # ['Mail::ClamAV', &ask_clamav, "*", [0], [1], qr/^INFECTED: (.+)/],
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
What am I doing wrong?
Anne
Anne Wilson wrote on Mon, 13 Apr 2009 10:00:40 +0100:
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
And maybe that's true, did you check whether it exists? I think your question is much better suited for the amavisd list.
Kai
On Monday 13 April 2009 12:31:15 Kai Schaetzl wrote:
Anne Wilson wrote on Mon, 13 Apr 2009 10:00:40 +0100:
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
And maybe that's true, did you check whether it exists?
It doesn't. I'm under the impression that a socket cannot be manually created, but has to be created by the application, so I simply don't know what to do about this.
I think your question is much better suited for the amavisd list.
If I have to, but I'm already on very many lists, so it's a last resort. There are so many skilled sysadmins here that I'm sure someone knows the answer.
Anne
Anne Wilson wrote:
On Monday 13 April 2009 12:31:15 Kai Schaetzl wrote:
Anne Wilson wrote on Mon, 13 Apr 2009 10:00:40 +0100:
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
And maybe that's true, did you check whether it exists?
It doesn't. I'm under the impression that a socket cannot be manually created, but has to be created by the application, so I simply don't know what to do about this.
My tired brain has only just digested the above paragraph - my guess would be that the clamav user doesn't have permissions to write to $MYHOME so can't create the socket?
My socket is located at /var/run/clamav/clamd and the /var/run/clamav dir is owned by clamav:clamav with 755 perms. The clamav user is also a member of the amavis group.
On Monday 13 April 2009 19:29:42 Ned Slider wrote:
Anne Wilson wrote:
On Monday 13 April 2009 12:31:15 Kai Schaetzl wrote:
Anne Wilson wrote on Mon, 13 Apr 2009 10:00:40 +0100:
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
And maybe that's true, did you check whether it exists?
It doesn't. I'm under the impression that a socket cannot be manually created, but has to be created by the application, so I simply don't know what to do about this.
My tired brain has only just digested the above paragraph - my guess would be that the clamav user doesn't have permissions to write to $MYHOME so can't create the socket?
My socket is located at /var/run/clamav/clamd and the /var/run/clamav dir is owned by clamav:clamav with 755 perms. The clamav user is also a member of the amavis group.
I'm not at the server at the moment, so I'm writing this from memory. I did check that the user clamav is a mamber of the amavis group. Clamd is using /tmp/clamd.socket (IIRC) so I've set amavis to that. Both clamd and amavisd restarted correctly, so I'm hoping that's fixed it.
Thanks for your help
Anne
Anne Wilson wrote on Mon, 13 Apr 2009 12:47:50 +0100:
It doesn't.
I thought so. You should have found that out yourself and told here in your first posting!
I'm under the impression that a socket cannot be manually created,
but has to be created by the application, so I simply don't know what to do about this.
Nothing. So far I haven't seen a reason to change it from the default. There is *NO* instruction in that short tutorial that tells you to do this. So, simply leave it where it was and tell amavisd where to find that socket! I remember you had the exact same problem some weeks ago, when you also changed the clamd socket for some obscure reason and it stopped working. Didn't you learn from that? You can't just change those paths for fun. The program has to be able to write to that new path, of course!
Kai
On Monday 13 April 2009 23:31:22 Kai Schaetzl wrote:
Anne Wilson wrote on Mon, 13 Apr 2009 12:47:50 +0100:
It doesn't.
I thought so. You should have found that out yourself and told here in your first posting!
I had already found that out, and thought it so obvious that it didn't need mentioning. You really are judgemental, aren't you?
I'm under the impression that a socket cannot be manually created,
but has to be created by the application, so I simply don't know what to do about this.
Nothing. So far I haven't seen a reason to change it from the default. There is *NO* instruction in that short tutorial that tells you to do this. So, simply leave it where it was and tell amavisd where to find that socket! I remember you had the exact same problem some weeks ago, when you also changed the clamd socket for some obscure reason and it stopped working. Didn't you learn from that? You can't just change those paths for fun. The program has to be able to write to that new path, of course!
Judgemental again - I had not changed the path, which is why I had the problem this time. The default did not work. I made the mistake of assuming that if it was default there would not be a problem with it.
Anne
Anne Wilson wrote on Tue, 14 Apr 2009 07:55:07 +0100:
I had already found that out, and thought it so obvious that it didn't need mentioning.
http://www.catb.org/~esr/faqs/smart-questions.html
You really are judgemental, aren't you?
Uuh, what is that? Pissed? Good. That was the purpose of my reply. You are always asking in the same manner with few information, laid out confusingly and not even done the most obvious solution steps. I would have hoped you learn over time.
Judgemental again - I had not changed the path, which is why I had the problem this time. The default did not work.
Which is contrary to this:
If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
Obviously, only one of your statements can be true.
Kai
On Tuesday 14 April 2009 10:31:15 Kai Schaetzl wrote:
Judgemental again - I had not changed the path, which is why I had the problem this time. The default did not work.
Which is contrary to this:
If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
Obviously, only one of your statements can be true.
Wrong again. Both are true. If the default had worked I would not have needed to try alternatives. Fortunately there are readers of this mailing list that are a good deal more helpful than you are.
Anne
Anne Wilson wrote on Tue, 14 Apr 2009 15:14:19 +0100:
Wrong again. Both are true.
First you say, you changed it, then you didn't change it. As I said, both cannot be true.
If the default had worked I would not have needed to try alternatives.
clamd in default settings works out-of-the-box. Just not for you. As it already did not for you last time. Think about that.
Kai
On Tuesday 14 April 2009 17:09:37 Kai Schaetzl wrote:
Anne Wilson wrote on Tue, 14 Apr 2009 15:14:19 +0100:
Wrong again. Both are true.
First you say, you changed it, then you didn't change it. As I said, both cannot be true.
For heavens' sake! You can read! Your conclusions are insulting. I'll spell it out.
I did not change the default - amavis did not work, and I got error messages. I read the documentation which told me to make changes and suggested what the change should be. I then did exactly what it said, but that also did not work. Correctly, I believe, it was said that this was a permissions problem. Finally Ned Slider kindly pointed me in the right direction.
If the default had worked I would not have needed to try alternatives.
clamd in default settings works out-of-the-box. Just not for you. As it already did not for you last time. Think about that.
I freely admitted that I had misunderstood an instruction on the last occasion. Like everyone else (except you, perhaps?) I'm not infallible. I learn as I go on, and thank the people who teach me. I fail to see how you have helped anyone learn anything by your attitude in this thread.
Anne
On Monday 13 April 2009 12:32:43 Joseph L. Casale wrote:
What am I doing wrong?
Running SELinux?
No, I don't run SELinux.
Anne
Anne Wilson wrote:
I'm trying to get amavis to play using clamd and tried to follow this:
# ### http://www.clamav.net/ ['ClamAV-clamd', &ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"], qr/\bOK$/, qr/\bFOUND$/, qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], # # NOTE: run clamd under the same user as amavisd, or run it under its own # # uid such as clamav, add user clamav to the amavis group, and then add # # AllowSupplementaryGroups to clamd.conf; # # NOTE: match socket name (LocalSocket) in clamav.conf to the socket name in # # this entry; when running chrooted one may prefer socket "$MYHOME/clamd".
# ### http://www.clamav.net/ and CPAN (memory-hungry! clamd is preferred) # # note that Mail::ClamAV requires perl to be build with threading! # ['Mail::ClamAV', &ask_clamav, "*", [0], [1], qr/^INFECTED: (.+)/],
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
What am I doing wrong?
Anne
Check the settings match in both /etc/amavisd.conf AND /etc/clamd.conf (eg, /var/run/clamav/clamd). IIRC they are different by default so you must change one of them.
Also, in /etc/clamd.conf make sure you've commented out TCPSocket if you're using a local UNIX socket.
For reference:
On Monday 13 April 2009 13:02:55 Ned Slider wrote:
Anne Wilson wrote:
I'm trying to get amavis to play using clamd and tried to follow this:
# ### http://www.clamav.net/ ['ClamAV-clamd', &ask_daemon, ["CONTSCAN {}\n", "/var/run/clamav/clamd"], qr/\bOK$/, qr/\bFOUND$/, qr/^.*?: (?!Infected Archive)(.*) FOUND$/ ], # # NOTE: run clamd under the same user as amavisd, or run it under its own # # uid such as clamav, add user clamav to the amavis group, and then add # # AllowSupplementaryGroups to clamd.conf; # # NOTE: match socket name (LocalSocket) in clamav.conf to the socket name in # # this entry; when running chrooted one may prefer socket "$MYHOME/clamd".
# ### http://www.clamav.net/ and CPAN (memory-hungry! clamd is preferred) # # note that Mail::ClamAV requires perl to be build with threading! # ['Mail::ClamAV', &ask_clamav, "*", [0], [1], qr/^INFECTED: (.+)/],
I came unstuck with the instruction regarding the LocalSocket. If I change that in clamd.conf to $MYHOME/amavisd.sock or $MYHOME/clamd the clamd service won't start, saying the socket doesn't exist.
What am I doing wrong?
Anne
Check the settings match in both /etc/amavisd.conf AND /etc/clamd.conf (eg, /var/run/clamav/clamd). IIRC they are different by default so you must change one of them.
Also, in /etc/clamd.conf make sure you've commented out TCPSocket if you're using a local UNIX socket.
OK, done all that. We'll see what logwatch reports tomorrow.
For reference:
I'd looked for configuration help on the web and found some, but found them difficult to understand. This one looks much more useful, thanks.
Anne
-
Anne Wilson -
Joseph L. Casale -
Kai Schaetzl -
Ned Slider