Sporadische ClamAV Fehler

Debian macht sich hervorragend als Web- und Mailserver. Schau auch in den " Tipps und Tricks"-Bereich.
Antworten
WolfG
Beiträge: 7
Registriert: 28.07.2013 11:11:14

Sporadische ClamAV Fehler

Beitrag von WolfG » 06.04.2023 18:24:28

Guten Tag allerseits,

hier läuft ein kleiner privater Mailserver (5 User) Debian GNU/Linux 9 (stretch) .
Es laufen die Dienste
postfix dovecot clamav-freshclam clamav-daemon spamassassin amavis mariadb

clamav-freshclam passiert via /etc/cron.d/clamav-freshclam.

Alles soweit ok.

Ich finde jedoch sporadisch Fehler im
/var/log/mail.err
/var/log/mail.log
/var/log/mail.err
Mar 28 22:43:04 magro-soft postfix/smtpd[7029]: fatal: no SASL authentication mechanisms
Mar 28 22:49:57 magro-soft amavis[4440]: (04440-05) (!!)AV: ALL VIRUS SCANNERS FAILED
Mar 28 22:51:49 magro-soft amavis[4440]: (04440-05) (!!)TROUBLE in process_request: Error writing an SMTP response to the socket: Broken pipe at (eval 95) line 1346.

/var/log/mail.log
Mar 28 22:42:49 magro-soft amavis[4440]: (04440-05) (!)ClamAV-clamd av-scanner FAILED: run_av error: ask_daemon_internal: Exceeded allowed time at (eval 98) line 611.\n
Mar 28 22:42:49 magro-soft amavis[4440]: (04440-05) (!)WARN: all primary virus scanners failed, considering backups
Mar 28 22:43:04 magro-soft postfix/smtpd[7029]: fatal: no SASL authentication mechanisms
Mar 28 22:43:05 magro-soft postfix/master[939]: warning: process /usr/lib/postfix/sbin/smtpd pid 7029 exit status 1
Mar 28 22:43:05 magro-soft postfix/master[939]: warning: /usr/lib/postfix/sbin/smtpd: bad command startup -- throttling
/var/log/clamav/clamd.log zeigt
Tue Mar 28 22:37:03 2023 -> Reading databases from /var/lib/clamav
Tue Mar 28 22:52:58 2023 -> Database correctly reloaded (8659494 signatures)
Tue Mar 28 22:52:58 2023 -> Database reload completed.
Tue Mar 28 22:52:58 2023 -> Activating the newly loaded database...
Tue Mar 28 22:52:58 2023 -> Client disconnected (FD 3)
Um diese Zeit läuft der cron job
/etc/cron.d/clamav-freshclam
# m h dom mon dow user command
22 22 * * * clamav /usr/bin/freshclam
Frage: wo gehört der timeout in freshclam.conf bzw clamd.conf erhöht?
Oder sollte während des freschclam update postfix pausieren?


Danke für Tips und Kommentare.
Wolf



/etc/clamav/freshclam.conf

Code: Alles auswählen

# Automatically created by the clamav-freshclam postinst
DatabaseOwner clamav
UpdateLogFile /var/log/clamav/freshclam.log
LogVerbose false
LogSyslog false
LogFacility LOG_LOCAL6
LogFileMaxSize 0
LogRotate true
LogTime true
Foreground false
Debug true
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 180
ReceiveTimeout 180
TestDatabases yes
ScriptedUpdates yes
CompressLocalDatabase no
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
# Check for new database x times a day
Checks 1
DatabaseMirror db.local.clamav.net
DatabaseMirror database.clamav.net
/etc/clamav/clamd.conf

Code: Alles auswählen

LocalSocket /var/run/clamav/clamd.ctl
FixStaleSocket true
LocalSocketGroup clamav
LocalSocketMode 666
User clamav
ScanMail true
ScanArchive true
ArchiveBlockEncrypted false
MaxDirectoryRecursion 15
FollowDirectorySymlinks false
FollowFileSymlinks false
ReadTimeout 600
MaxThreads 12
MaxConnectionQueueLength 15
LogSyslog false
LogRotate true
LogFacility LOG_LOCAL6
LogClean false
LogVerbose true
PreludeEnable no
PreludeAnalyzerName ClamAV
DatabaseDirectory /var/lib/clamav
OfficialDatabaseOnly false
#SelfCheck 3600 -> WG freshclam cron
SelfCheck 0
Foreground false
Debug false
ScanPE true
MaxEmbeddedPE 10M
ScanOLE2 true

Benutzeravatar
cosinus
Beiträge: 3422
Registriert: 08.02.2016 13:44:11
Lizenz eigener Beiträge: GNU General Public License
Wohnort: Bremen

Re: Sporadische ClamAV Fehler

Beitrag von cosinus » 06.04.2023 18:32:00

Ganz ehrllich? ClamAV kannst du vergessen. Was glaubst du was du damit erreichst?

Antworten