clamav qmail-scanner updates
clamav qmail-scanner updates
as I was updating:
clamav i386 0.90-1.el4.art atomicorp 990 k
clamav-db i386 0.90-1.el4.art atomicorp 8.5 M
clamd i386 0.90-1.el4.art atomicorp 81 k
qmail-scanner noarch 1:2.01-13.el4.art atomicorp 326 k
spamassassin i386 1:3.1.8-1.el4.art atomicorp 908 k
I got this error:
unning Transaction
Updating : spamassassin ####################### [ 1/10]
Updating : qmail-scanner ####################### [ 2/10]
Updating : clamav-db # [ 3/10]warning: /var/clamav/daily.cvd created as /var/clamav/daily.cvd.rpmnew
Updating : clamav-db ###################### [ 3/10]warning: /var/clamav/main.cvd created as /var/clamav/main.cvd.rpmnew
Updating : clamav-db ####################### [ 3/10]
Updating : clamav [ 4/10]warning: /etc/freshclam.conf created as /etc/freshclam.conf.rpmnew
Updating : clamav ####################### [ 4/10]
Updating : clamd # [ 5/10]warning: /etc/clamd.conf created as /etc/clamd.conf.rpmnew
Updating : clamd ####################### [ 5/10]
error: %trigger(qmail-scanner-2.01-12.rhel4.art.noarch) scriptlet failed, exit status 1
error: %trigger(qmail-scanner-2.01-13.el4.art.noarch) scriptlet failed, exit status 1
Cleanup : clamav ####################### [ 6/10]
Cleanup : qmail-scanner ####################### [ 7/10]
Cleanup : spamassassin ####################### [ 8/10]
Cleanup : clamav-db ####################### [ 9/10]
Updated: clamav.i386 0:0.90-1.el4.art clamav-db.i386 0:0.90-1.el4.art clamd.i386 0:0.90-1.el4.art qmail-scanner.noarch 1:2.01-13.el4.art spamassassin.i386 1:3.1.8-1.el4.art
Complete!
clamd did not restart after this and poped this error:
Starting Clam AntiVirus Daemon: ERROR: Parse error at line 34: Option LogTime requires boolean argument.
ERROR: Can't open/parse the config file /etc/clamd.conf
after moving /etc/clamd.conf.rpmnew to /etc/clamd.conf it did work though
after the qmail-scanner error I did run /usr/bin/qmail-scanner-reconfigure just to be sure and all went OK
how worring is this?
clamav i386 0.90-1.el4.art atomicorp 990 k
clamav-db i386 0.90-1.el4.art atomicorp 8.5 M
clamd i386 0.90-1.el4.art atomicorp 81 k
qmail-scanner noarch 1:2.01-13.el4.art atomicorp 326 k
spamassassin i386 1:3.1.8-1.el4.art atomicorp 908 k
I got this error:
unning Transaction
Updating : spamassassin ####################### [ 1/10]
Updating : qmail-scanner ####################### [ 2/10]
Updating : clamav-db # [ 3/10]warning: /var/clamav/daily.cvd created as /var/clamav/daily.cvd.rpmnew
Updating : clamav-db ###################### [ 3/10]warning: /var/clamav/main.cvd created as /var/clamav/main.cvd.rpmnew
Updating : clamav-db ####################### [ 3/10]
Updating : clamav [ 4/10]warning: /etc/freshclam.conf created as /etc/freshclam.conf.rpmnew
Updating : clamav ####################### [ 4/10]
Updating : clamd # [ 5/10]warning: /etc/clamd.conf created as /etc/clamd.conf.rpmnew
Updating : clamd ####################### [ 5/10]
error: %trigger(qmail-scanner-2.01-12.rhel4.art.noarch) scriptlet failed, exit status 1
error: %trigger(qmail-scanner-2.01-13.el4.art.noarch) scriptlet failed, exit status 1
Cleanup : clamav ####################### [ 6/10]
Cleanup : qmail-scanner ####################### [ 7/10]
Cleanup : spamassassin ####################### [ 8/10]
Cleanup : clamav-db ####################### [ 9/10]
Updated: clamav.i386 0:0.90-1.el4.art clamav-db.i386 0:0.90-1.el4.art clamd.i386 0:0.90-1.el4.art qmail-scanner.noarch 1:2.01-13.el4.art spamassassin.i386 1:3.1.8-1.el4.art
Complete!
clamd did not restart after this and poped this error:
Starting Clam AntiVirus Daemon: ERROR: Parse error at line 34: Option LogTime requires boolean argument.
ERROR: Can't open/parse the config file /etc/clamd.conf
after moving /etc/clamd.conf.rpmnew to /etc/clamd.conf it did work though
after the qmail-scanner error I did run /usr/bin/qmail-scanner-reconfigure just to be sure and all went OK
how worring is this?
ok problem solved! (kinda)
qmail would not start:
Starting Clam AntiVirus Daemon: Running as user qscand (UID 10042, GID 105)
ERROR: Can't open /var/log/clamav/clamd.log in append mode (check permissions!).
ERROR: Problem with internal logger. Please check the permissions on the /var/log/clamav/clamd.log file.
it seems when updating last night
clamd was not uninstalled to install the new version!
Removing:
clamd i386 0.90-1.el4.art installed 8.7 M
clamd i386 0.88.7-1.rhel4.art installed 7.4 M
so i did yum remove and removed both 0.88 and 0.90 and erinstalled 0.90
only ran /us/bin/qmail-scanner-reconfigure and all seems well till now
(at least i can send email)
qmail would not start:
Starting Clam AntiVirus Daemon: Running as user qscand (UID 10042, GID 105)
ERROR: Can't open /var/log/clamav/clamd.log in append mode (check permissions!).
ERROR: Problem with internal logger. Please check the permissions on the /var/log/clamav/clamd.log file.
it seems when updating last night
clamd was not uninstalled to install the new version!
Removing:
clamd i386 0.90-1.el4.art installed 8.7 M
clamd i386 0.88.7-1.rhel4.art installed 7.4 M
so i did yum remove and removed both 0.88 and 0.90 and erinstalled 0.90
only ran /us/bin/qmail-scanner-reconfigure and all seems well till now
(at least i can send email)
-
- Forum User
- Posts: 67
- Joined: Wed Jun 01, 2005 5:52 pm
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
This should be fixed with the latest qmail-scanner update. Me and Scott worked out this one yesterday.
Lemonbit Internet Dedicated Server Management
-
- Forum User
- Posts: 67
- Joined: Wed Jun 01, 2005 5:52 pm
i had to remove clamav...breun wrote:This should be fixed with the latest qmail-scanner update. Me and Scott worked out this one yesterday.
my maillog was full of:
Mar 25 14:57:47 hostname X-Qmail-Scanner-2.01st: [hostname***482746776317061] clamdscan: corrupt or unknown clamd scanner error or memory/resource/perms problem - exit status 512/2
and was having varius problems (also in sending email using php mail() function)... i think they depends on that...tail clamd.log.1
Sat Mar 24 19:27:54 2007 -> SelfCheck: Database status OK.
Sat Mar 24 20:24:17 2007 -> SelfCheck: Database status OK.
Sat Mar 24 20:54:55 2007 -> SelfCheck: Database status OK.
Sat Mar 24 21:33:43 2007 -> SelfCheck: Database status OK.
Sat Mar 24 22:11:24 2007 -> SelfCheck: Database status OK.
Sun Mar 25 00:02:57 2007 -> SelfCheck: Database status OK.
Sun Mar 25 01:46:19 2007 -> SelfCheck: Database status OK.
Sun Mar 25 03:27:46 2007 -> SelfCheck: Database status OK.
Sun Mar 25 04:02:04 2007 -> SelfCheck: Database status OK.
Sun Mar 25 04:13:40 2007 -> SIGHUP caught: re-opening log file.
centos4 32bit
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
For RHEL4 rpms you can check the new channel: http://www.atomicorp.com/channels/atomi ... i386/RPMS/
No RHEL3 there though.
You can try http://dag.wieers.com/rpm/packages/clamav/ for RHEL3.
No RHEL3 there though.
You can try http://dag.wieers.com/rpm/packages/clamav/ for RHEL3.
Lemonbit Internet Dedicated Server Management
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
Nope. RHEL3 itself is not EOL yet, but Scott stopped supporting a couple of older distributions in the [atomic] channel.
Source: http://www.atomicrocketturtle.com/Jooml ... iew/159/1/As for the new [atomic] channel, Red Hat 9, RHEL3, CentOS3, and FC2 are NOT supported.
Lemonbit Internet Dedicated Server Management