Differences between version 10 and predecessor to the previous major change of ClamAvNotes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 10 | Last edited on Friday, July 30, 2004 4:09:04 am | by AristotlePagaltzis | Revert |
| Older page: | version 8 | Last edited on Sunday, July 18, 2004 9:21:16 am | by CraigBox | Revert |
@@ -1,29 +1,37 @@
-!! Clamd
dies at morning maintenance, Debian Woody (.60-10, backported)
+!!! <tt>clamd</tt>
dies at morning maintenance, Debian Woody (.60-10, backported)
-Sometimes, clamd dies during its morning maintenance. I've not found any rhyme or reason to this, however it's a pain for me as I use exim4 + exiscan, and this will stop delivering mail if it can't talk to its virus
scanner. Bugger
.
+Sometimes, <tt>
clamd</tt>
dies during its morning maintenance. I've not found any rhyme or reason to this, however it's a pain for me as I use exim4 + exiscan, and this will stop delivering mail if it can't talk to its [Virus]
scanner. My current workaround: A crontab(5) script that checks to see if the socket is writeable, and stops and starts <tt>clamd</tt> if not
.
-My current workaround: A
cron script that checks to see if the socket is writeable, and if not it stops
clamd, then starts it again
.
+<verbatim>
+# cat /etc/
cron.d/check-clamd
+TESTFILE="/var/run/
clamd.ctl"
- # cat
/etc/cron
.d/check
-clamd
- TESTFILE="
/var/run
/clamd
.ctl"
+* * * * * root [ -w $TESTFILE ] || \
+ (
/etc/init
.d/clamav
-daemon stop; \
+
/etc
/init
.d/clamav-daemon start)
+</verbatim>
- * * * * * root [[ -w $TESTFILE ] || \
- (/etc/init
.d/clamav
-daemon stop; \
- /etc/init.d/clamav
-daemon start)
+I know this isn't the prettiest, but I don't have time to track down ''why'' its dying just yet
. -- DanielLawson
+A similar script is available at http://mikecathey.com/code/clamdwatch/ and in the <tt>contrib/clamdwatch</tt> directory.
-Yeah, I know this isn
't the prettiest, but I don't have time to track down *why* its dying just yet -- DanielLawson
+!!! <tt>clamdscan</tt> can
't read files (when run from Amavis or some other scanner)
-A similar script is available at http
://mikecathey.com
/code
/clamdwatch
/ and in
the contrib
/clamdwatch directory -- NERv
+<verbatim>
+Jun 9 10:21:02 firewall amavis[17934]: (17934-02) Clam Antivirus-clamd FAILED -
+unknown status
: /var
/lib
/amavis
/amavis-msg-id
/parts: Can't access
the file ERROR
+<
/verbatim>
-!! clamdscan can't read files
(when run from
amavis or some other scanner)
+[ClamAV] runs as the <tt>clamav</tt> user
(on [Debian]/Woody anyway), and
when Amavis unpacks its email for scanning as the <tt>
amavis</tt> user. Add <tt>clamav</tt> to the <tt>amavis</tt> group, and restart <tt>clamd</tt>.
- Jun 9 10:21:02 firewall amavis[[17934]: (17934-02) Clam Antivirus-
clamd FAILED -
- unknown status: /var/lib
/amavis/amavis-msg-id/parts: Can't access
the file ERROR
+Another way around this is to run <tt>
clamd<
/tt> and <tt>
amavis<
/tt> as
the same user. Apparently this change needs to be made for Conectiva Linux.
-clamav
-daemon runs as the 'clamav' user (on Debian/Woody anyway),
and when amavis unpacks its email for scanning as the 'amavis' user. Add
clamav to the amavis group, and restart the clamav daemon.
+This worked on [Debian] with Exim4
-daemon-heavy
and clamav:
-Another way around this is to run clamav and amavis as
the same
user. Apparently this
change needs
to be made for Conectiva Linux
.
+* Find
the user [Exim] runs as using <tt>exim -bP exim_user</tt>, in my case <tt>Debian_exim</tt>
.
+* Edit <tt>/etc/clamav/clamav.conf</tt> to
change its user
to <tt>Debian_exim</tt>
.
+* Allow <tt>Debian_exim</tt> access to [ClamAV]'s files: <tt>adduser Debian_exim clamav</tt>
+* Allow [ClamAV] to save its [PID] file: <tt>chmod g+w /var/run/clamav</tt>
----
CategoryMailNotes
