Re: [qmailtoaster] ClamAV Upgrade

[Eric Broch]

Hi Jeff,

I believe that the qmt version of ClamAV is redundant like Spamassassin. 
Why should what already exists be maintained?


Anyway, here's a like to switch from qmt version to epel version:

https://www.qmailtoaster.org/qttoepelclam.html

Be mindful if you use ramdisk for simscan:

https://www.qmailtoaster.org/simscanramdisk.html

Eric

On 8/17/2020 8:26 AM, Jeff Koch wrote:

Hi List:

I see in our logs that

WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.101.1 Recommended version: 0.102.4

We're using QMT7. What's the recommended procedure for upgrading ClamAV

Thanks, Jeff

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

Istvan,

Send yourself an email and check the proper header by viewing message
source:

Received: by simscan 1.4.0 ppid: 24028, pid: 24032, t: 2.5615s
 scanners: attach: 1.4.0 clamav: 0.98.7/m:


You can also check /var/log/qmail/clamd/current log file, I think to see
if there are any errors.

I don't think anyone is in your situation (having CentOS5 toaster
binaries on CentOS6 machine), so this binaries are probably for you alone.

Eric

On 11/8/2015 1:51 AM, Istvan Köpe wrote:
>
> Hi Eric,
>
>  
>
> I followed your steps and the upgrade worked. I had no errors. Thank you!
>
>  
>
> Now how can I make sure that everything is ok?
>
>  
>
> rpm -Uvh clamav-toaster-0.98.7-1.4.11.x86_64.rpm
>
> Preparing...   
> ### [100%]
>
>1:clamav-toaster
> ### [100%]
>
> ClamAV update process started at Sun Nov  8 10:42:27 2015
>
> main.cld is up to date (version: 55, sigs: 2424225, f-level: 60,
> builder: neo)
>
> daily.cld is up to date (version: 21043, sigs: 1668608, f-level: 63,
> builder: neo)
>
> bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63,
> builder: shurley)
>
> simscan versions cdb file built. /var/qmail/control/simversions.cdb
>
> simscan cdb file built. /var/qmail/control/simcontrol.cdb
>
>  
>
> The packages looks ok:
>
> rpm -qa | grep toaster
>
> ucspi-tcp-toaster-0.88-1.3.9.x86_64
>
> qmail-toaster-1.03-1.3.22.x86_64
>
> autorespond-toaster-2.0.5-1.4.0.x86_64
>
> qmailadmin-toaster-1.2.16-1.4.1.x86_64
>
> isoqlog-toaster-2.1-1.3.7.x86_64
>
> ripmime-toaster-1.4.0.6-1.3.6.x86_64
>
> clamav-toaster-0.98.7-1.4.11.x86_64
>
> qmailtoaster-plus-0.3.2-1.4.19.noarch
>
> daemontools-toaster-0.76-1.3.6.x86_64
>
> vpopmail-toaster-5.4.33-1.4.0.x86_64
>
> libsrs2-toaster-1.0.18-1.3.6.x86_64
>
> qmail-pop3d-toaster-1.03-1.3.22.x86_64
>
> courier-imap-toaster-4.1.2-1.3.10.x86_64
>
> control-panel-toaster-0.5-1.4.0.noarch
>
> ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
>
> qmailtoaster-plus.repo-0.2-2.noarch
>
> qmailmrtg-toaster-4.2-1.3.7.x86_64
>
> maildrop-toaster-devel-2.0.3-1.3.8.x86_64
>
> squirrelmail-toaster-1.4.22-1.4.0.noarch
>
> simscan-toaster-1.4.0-1.4.0.x86_64
>
> libdomainkeys-toaster-0.68-1.3.6.x86_64
>
> courier-authlib-toaster-0.59.2-1.3.10.x86_64
>
> ezmlm-toaster-0.53.324-1.3.6.x86_64
>
> maildrop-toaster-2.0.3-1.3.8.x86_64
>
> spamassassin-toaster-3.3.2-1.4.3.x86_64
>
> vqadmin-toaster-2.3.7-1.4.1.x86_64
>
>  
>
> The services looks ok:
>
> qmailctl stat
>
> authlib: up (pid 3813) 1815823 seconds
>
> clamd: up (pid 3812) 1815823 seconds
>
> imap4: down 1815823 seconds
>
> imap4-ssl: down 1815823 seconds
>
> pop3: down 1815823 seconds
>
> pop3-ssl: down 1815823 seconds
>
> send: up (pid 3810) 1815823 seconds
>
> smtp: up (pid 3806) 1815823 seconds
>
> spamd: up (pid 3814) 1815823 seconds
>
> submission: up (pid 3815) 1815823 seconds
>
> authlib/log: up (pid 3811) 1815823 seconds
>
> clamd/log: up (pid 3809) 1815823 seconds
>
> imap4/log: down 1815823 seconds
>
> imap4-ssl/log: down 1815823 seconds
>
> pop3/log: down 1815823 seconds
>
> pop3-ssl/log: down 1815823 seconds
>
> send/log: up (pid 3805) 1815823 seconds
>
> smtp/log: up (pid 3807) 1815823 seconds
>
> spamd/log: up (pid 3816) 1815823 seconds
>
> submission/log: up (pid 3808) 1815823 seconds
>
>  
>
> If everything is ok, how can I share this RPM? Or the source RPM
>
>  
>
> István
>
>  
>
> *From:*Eric Broch [mailto:ebr...@whitehorsetc.com]
> *Sent:* Monday, October 19, 2015 10:12 PM
> *To:* qmailtoaster-list@qmailtoaster.com
> *Subject:* Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
>  
>
> After the preceding, next, build the source rpm:
> rpmbuild -bs ~/rpmbuild/SPECS/clamav-toaster.spec
> And, finally, build the rpm:
> rpmbuild --rebuild --with cnt5064 ~/rpmbuild/SRPMS/clamav-toaster*.src.rpm
>
> EricB
>
>
> On 10/19/2015 12:30 PM, Eric Broch wrote:
>
> Istvan,
>
> I assume the build environment exists on your server.
> Download the qmail clamav-toaster source rpm into ~/rpmbuild/SRPMS
> and install it
> Download the new clamav source tar.gz file and put in the
> ~/rpmbuild/SOURCES directory
> Edit the ~/rpmbuild/SPECS/clamav-toaster.spec file naming the new
> sources to be used most likely the Source0: option.
> Edit the changelog section to reflect your changes.
>
>     EricB
>
>
> On 10/18/2015 11:18 PM, Istvan Köpe 

RE: [qmailtoaster] clamav upgrade on centos 6 x64

[Istvan Köpe]

Hi Eric,

 

I followed your steps and the upgrade worked. I had no errors. Thank you!

 

Now how can I make sure that everything is ok?

 

rpm -Uvh clamav-toaster-0.98.7-1.4.11.x86_64.rpm

Preparing...### [100%]

   1:clamav-toaster ### [100%]

ClamAV update process started at Sun Nov  8 10:42:27 2015

main.cld is up to date (version: 55, sigs: 2424225, f-level: 60, builder: neo)

daily.cld is up to date (version: 21043, sigs: 1668608, f-level: 63, builder: 
neo)

bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63, builder: 
shurley)

simscan versions cdb file built. /var/qmail/control/simversions.cdb

simscan cdb file built. /var/qmail/control/simcontrol.cdb

 

The packages looks ok:

rpm -qa | grep toaster

ucspi-tcp-toaster-0.88-1.3.9.x86_64

qmail-toaster-1.03-1.3.22.x86_64

autorespond-toaster-2.0.5-1.4.0.x86_64

qmailadmin-toaster-1.2.16-1.4.1.x86_64

isoqlog-toaster-2.1-1.3.7.x86_64

ripmime-toaster-1.4.0.6-1.3.6.x86_64

clamav-toaster-0.98.7-1.4.11.x86_64

qmailtoaster-plus-0.3.2-1.4.19.noarch

daemontools-toaster-0.76-1.3.6.x86_64

vpopmail-toaster-5.4.33-1.4.0.x86_64

libsrs2-toaster-1.0.18-1.3.6.x86_64

qmail-pop3d-toaster-1.03-1.3.22.x86_64

courier-imap-toaster-4.1.2-1.3.10.x86_64

control-panel-toaster-0.5-1.4.0.noarch

ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64

qmailtoaster-plus.repo-0.2-2.noarch

qmailmrtg-toaster-4.2-1.3.7.x86_64

maildrop-toaster-devel-2.0.3-1.3.8.x86_64

squirrelmail-toaster-1.4.22-1.4.0.noarch

simscan-toaster-1.4.0-1.4.0.x86_64

libdomainkeys-toaster-0.68-1.3.6.x86_64

courier-authlib-toaster-0.59.2-1.3.10.x86_64

ezmlm-toaster-0.53.324-1.3.6.x86_64

maildrop-toaster-2.0.3-1.3.8.x86_64

spamassassin-toaster-3.3.2-1.4.3.x86_64

vqadmin-toaster-2.3.7-1.4.1.x86_64

 

The services looks ok:

qmailctl stat

authlib: up (pid 3813) 1815823 seconds

clamd: up (pid 3812) 1815823 seconds

imap4: down 1815823 seconds

imap4-ssl: down 1815823 seconds

pop3: down 1815823 seconds

pop3-ssl: down 1815823 seconds

send: up (pid 3810) 1815823 seconds

smtp: up (pid 3806) 1815823 seconds

spamd: up (pid 3814) 1815823 seconds

submission: up (pid 3815) 1815823 seconds

authlib/log: up (pid 3811) 1815823 seconds

clamd/log: up (pid 3809) 1815823 seconds

imap4/log: down 1815823 seconds

imap4-ssl/log: down 1815823 seconds

pop3/log: down 1815823 seconds

pop3-ssl/log: down 1815823 seconds

send/log: up (pid 3805) 1815823 seconds

smtp/log: up (pid 3807) 1815823 seconds

spamd/log: up (pid 3816) 1815823 seconds

submission/log: up (pid 3808) 1815823 seconds

 

If everything is ok, how can I share this RPM? Or the source RPM

 

István

 

From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
Sent: Monday, October 19, 2015 10:12 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64

 

After the preceding, next, build the source rpm:
rpmbuild -bs ~/rpmbuild/SPECS/clamav-toaster.spec
And, finally, build the rpm:
rpmbuild --rebuild --with cnt5064 ~/rpmbuild/SRPMS/clamav-toaster*.src.rpm

EricB


On 10/19/2015 12:30 PM, Eric Broch wrote:

Istvan,

I assume the build environment exists on your server.
Download the qmail clamav-toaster source rpm into ~/rpmbuild/SRPMS and install 
it
Download the new clamav source tar.gz file and put in the ~/rpmbuild/SOURCES 
directory
Edit the ~/rpmbuild/SPECS/clamav-toaster.spec file naming the new sources to be 
used most likely the Source0: option.
Edit the changelog section to reflect your changes.

EricB


On 10/18/2015 11:18 PM, Istvan Köpe wrote:

Hi Eric,

 

I never updated a source rpm. Can you guide me?

 

What would you recommend in my senario for long term?

 

István

 

From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
Sent: Monday, October 19, 2015 4:18 AM
To: qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64

 

Istvan,

You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no upgrades 
that anyone does for this, that I know of since it is not a part of the QMT 
planning. 

You can grab the clamav-toaster source rpm 
<http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
  and update it with the latest clamav sources 
<http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz>  and compile 
it for your own uses

Eric


On 10/18/2015 10:38 AM, Istvan Köpe wrote:

I also tried with yum and qtp-newmodel, but no success. I installed it with the 
cnt5064-install-script.sh. There were some problems, but I figured it out 
somehow and the server is running without problems since about 2 years. I think 
I made and upgrade for clamav since the server installation, but I'm not sure.
 
 
rpm -qa | grep toaster
ucspi-tcp-toaster-0.88-1.3.9.x86_64
qmail-toaster-1.03-1.3.22.x86_64
autorespond-toaster-2.0.5-1.4.0.x86_64
qmailadmin

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

After the preceding, next, build the source rpm:
rpmbuild -bs ~/rpmbuild/SPECS/clamav-toaster.spec
And, finally, build the rpm:
rpmbuild --rebuild --with cnt5064 ~/rpmbuild/SRPMS/clamav-toaster*.src.rpm

EricB


On 10/19/2015 12:30 PM, Eric Broch wrote:
> Istvan,
>
> I assume the build environment exists on your server.
> Download the qmail clamav-toaster source rpm into ~/rpmbuild/SRPMS and
> install it
> Download the new clamav source tar.gz file and put in the
> ~/rpmbuild/SOURCES directory
> Edit the ~/rpmbuild/SPECS/clamav-toaster.spec file naming the new
> sources to be used most likely the Source0: option.
> Edit the changelog section to reflect your changes.
>
> EricB
>
>
> On 10/18/2015 11:18 PM, Istvan Köpe wrote:
>>
>> Hi Eric,
>>
>>  
>>
>> I never updated a source rpm. Can you guide me?
>>
>>  
>>
>> What would you recommend in my senario for long term?
>>
>>  
>>
>> István
>>
>>  
>>
>> *From:*Eric Broch [mailto:ebr...@whitehorsetc.com]
>> *Sent:* Monday, October 19, 2015 4:18 AM
>> *To:* qmailtoaster-list@qmailtoaster.com
>> *Subject:* Re: [qmailtoaster] clamav upgrade on centos 6 x64
>>
>>  
>>
>> Istvan,
>>
>> You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no
>> upgrades that anyone does for this, that I know of since it is not a
>> part of the QMT planning.
>>
>> You can grab the clamav-toaster source rpm
>> <http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
>> and update it with the latest clamav sources
>> <http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz> and
>> compile it for your own uses
>>
>> Eric
>>
>>
>> On 10/18/2015 10:38 AM, Istvan Köpe wrote:
>>
>> I also tried with yum and qtp-newmodel, but no success. I installed it 
>> with the cnt5064-install-script.sh. There were some problems, but I figured 
>> it out somehow and the server is running without problems since about 2 
>> years. I think I made and upgrade for clamav since the server installation, 
>> but I'm not sure.
>>
>>  
>>
>>  
>>
>> rpm -qa | grep toaster
>>
>> ucspi-tcp-toaster-0.88-1.3.9.x86_64
>>
>> qmail-toaster-1.03-1.3.22.x86_64
>>
>> autorespond-toaster-2.0.5-1.4.0.x86_64
>>
>> qmailadmin-toaster-1.2.16-1.4.1.x86_64
>>
>> isoqlog-toaster-2.1-1.3.7.x86_64
>>
>> ripmime-toaster-1.4.0.6-1.3.6.x86_64
>>
>> clamav-toaster-0.98.4-1.4.8.x86_64
>>
>> qmailtoaster-plus-0.3.2-1.4.19.noarch
>>
>> daemontools-toaster-0.76-1.3.6.x86_64
>>
>> vpopmail-toaster-5.4.33-1.4.0.x86_64
>>
>> libsrs2-toaster-1.0.18-1.3.6.x86_64
>>
>> qmail-pop3d-toaster-1.03-1.3.22.x86_64
>>
>> courier-imap-toaster-4.1.2-1.3.10.x86_64
>>
>> control-panel-toaster-0.5-1.4.0.noarch
>>
>> ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
>>
>> qmailtoaster-plus.repo-0.2-2.noarch
>>
>> qmailmrtg-toaster-4.2-1.3.7.x86_64
>>
>> maildrop-toaster-devel-2.0.3-1.3.8.x86_64
>>
>> squirrelmail-toaster-1.4.22-1.4.0.noarch
>>
>> simscan-toaster-1.4.0-1.4.0.x86_64
>>
>> libdomainkeys-toaster-0.68-1.3.6.x86_64
>>
>> courier-authlib-toaster-0.59.2-1.3.10.x86_64
>>
>> ezmlm-toaster-0.53.324-1.3.6.x86_64
>>
>> maildrop-toaster-2.0.3-1.3.8.x86_64
>>
>> spamassassin-toaster-3.3.2-1.4.3.x86_64
>>
>> vqadmin-toaster-2.3.7-1.4.1.x86_64
>>
>>  
>>
>> rpm -qa | grep .qt
>>
>> dovecot-devel-2.0.11-2.qtp.x86_64
>>
>> dovecot-debuginfo-2.0.11-2.qtp.x86_64
>>
>> dovecot-2.0.11-2.qtp.x86_64
>>
>> dovecot-mysql-2.0.11-2.qtp.x86_64
>>
>> dovecot-pigeonhole-2.0.11-2.qtp.x86_64
>>
>> whtc-qmt-1-1.qt.el6.noarch
>>
>> dovecot-pgsql-2.0.11-2.qtp.x86_64
>>
>>  
>>
>> István
>>
>>  
>>
>>  
>>
>> -Original Message-
>>
>> From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
>>
>> Sent: Sunday, October 18, 2015 5:32 PM
>>
>> To: qmailtoaster-list@qmailtoaster.com
>> <mailto:qmailtoaster-list@qmailtoaster.com>
>>
>> Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64
>>
>>  
>>
>> Ist

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

Istvan,

I assume the build environment exists on your server.
Download the qmail clamav-toaster source rpm into ~/rpmbuild/SRPMS and
install it
Download the new clamav source tar.gz file and put in the
~/rpmbuild/SOURCES directory
Edit the ~/rpmbuild/SPECS/clamav-toaster.spec file naming the new
sources to be used most likely the Source0: option.
Edit the changelog section to reflect your changes.

EricB

On 10/18/2015 11:18 PM, Istvan Köpe wrote:
>
> Hi Eric,
>
>  
>
> I never updated a source rpm. Can you guide me?
>
>  
>
> What would you recommend in my senario for long term?
>
>  
>
> István
>
>  
>
> *From:*Eric Broch [mailto:ebr...@whitehorsetc.com]
> *Sent:* Monday, October 19, 2015 4:18 AM
> *To:* qmailtoaster-list@qmailtoaster.com
> *Subject:* Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
>  
>
> Istvan,
>
> You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no
> upgrades that anyone does for this, that I know of since it is not a
> part of the QMT planning.
>
> You can grab the clamav-toaster source rpm
> <http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
> and update it with the latest clamav sources
> <http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz> and
> compile it for your own uses
>
> Eric
>
>
> On 10/18/2015 10:38 AM, Istvan Köpe wrote:
>
> I also tried with yum and qtp-newmodel, but no success. I installed it 
> with the cnt5064-install-script.sh. There were some problems, but I figured 
> it out somehow and the server is running without problems since about 2 
> years. I think I made and upgrade for clamav since the server installation, 
> but I'm not sure.
>
>  
>
>  
>
> rpm -qa | grep toaster
>
> ucspi-tcp-toaster-0.88-1.3.9.x86_64
>
> qmail-toaster-1.03-1.3.22.x86_64
>
> autorespond-toaster-2.0.5-1.4.0.x86_64
>
> qmailadmin-toaster-1.2.16-1.4.1.x86_64
>
> isoqlog-toaster-2.1-1.3.7.x86_64
>
> ripmime-toaster-1.4.0.6-1.3.6.x86_64
>
> clamav-toaster-0.98.4-1.4.8.x86_64
>
> qmailtoaster-plus-0.3.2-1.4.19.noarch
>
> daemontools-toaster-0.76-1.3.6.x86_64
>
> vpopmail-toaster-5.4.33-1.4.0.x86_64
>
> libsrs2-toaster-1.0.18-1.3.6.x86_64
>
> qmail-pop3d-toaster-1.03-1.3.22.x86_64
>
> courier-imap-toaster-4.1.2-1.3.10.x86_64
>
> control-panel-toaster-0.5-1.4.0.noarch
>
> ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
>
> qmailtoaster-plus.repo-0.2-2.noarch
>
> qmailmrtg-toaster-4.2-1.3.7.x86_64
>
> maildrop-toaster-devel-2.0.3-1.3.8.x86_64
>
> squirrelmail-toaster-1.4.22-1.4.0.noarch
>
> simscan-toaster-1.4.0-1.4.0.x86_64
>
> libdomainkeys-toaster-0.68-1.3.6.x86_64
>
> courier-authlib-toaster-0.59.2-1.3.10.x86_64
>
> ezmlm-toaster-0.53.324-1.3.6.x86_64
>
> maildrop-toaster-2.0.3-1.3.8.x86_64
>
> spamassassin-toaster-3.3.2-1.4.3.x86_64
>
> vqadmin-toaster-2.3.7-1.4.1.x86_64
>
>  
>
> rpm -qa | grep .qt
>
> dovecot-devel-2.0.11-2.qtp.x86_64
>
> dovecot-debuginfo-2.0.11-2.qtp.x86_64
>
> dovecot-2.0.11-2.qtp.x86_64
>
> dovecot-mysql-2.0.11-2.qtp.x86_64
>
> dovecot-pigeonhole-2.0.11-2.qtp.x86_64
>
> whtc-qmt-1-1.qt.el6.noarch
>
> dovecot-pgsql-2.0.11-2.qtp.x86_64
>
>  
>
> István
>
>  
>
>  
>
> -Original Message-
>
> From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
>
> Sent: Sunday, October 18, 2015 5:32 PM
>
> To: qmailtoaster-list@qmailtoaster.com
> <mailto:qmailtoaster-list@qmailtoaster.com>
>
> Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
>  
>
> Istvan,
>
>  
>
> There should be no RPMS with the QMT "toaster" designation on a CentOS 6 
> machine, they should all have the ".qt" designation.
>
>  
>
> How did you go about installing QMT on this CentOS 6 machine?
>
>  
>
> Can you run a couple commands at your CLI?
>
>  
>
> 1) # rpm -qa | grep toaster
>
> 2) # rpm -qa | grep .qt
>
>  
>
> And, post your output.
>
>  
>
> Eric
>
>  
>
>  
>
> On 10/18/2015 3:36 AM, Istvan Köpe wrote:
>
> Hello,
>
>  
>
>  
>
>  
>
> I want to upgrade clamav on a Centos6 x64 but I have this error:
>
>  
>
> rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
>
>  
>
> error:

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

Istvan,

I assume the build environment exists on your server.
Download the qmail clamav-toaster source rpm into ~/rpmbuild/SRPMS and
install it
Download the new clamav source tar.gz file and put in the
~/rpmbuild/SOURCES directory
Edit the ~/rpmbuild/SPECS/clamav-toaster.spec file naming the new
sources to be used most likely the Source0: option.
Edit the changelog section to reflect your changes.

EricB


On 10/18/2015 11:18 PM, Istvan Köpe wrote:
>
> Hi Eric,
>
>  
>
> I never updated a source rpm. Can you guide me?
>
>  
>
> What would you recommend in my senario for long term?
>
>  
>
> István
>
>  
>
> *From:*Eric Broch [mailto:ebr...@whitehorsetc.com]
> *Sent:* Monday, October 19, 2015 4:18 AM
> *To:* qmailtoaster-list@qmailtoaster.com
> *Subject:* Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
>  
>
> Istvan,
>
> You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no
> upgrades that anyone does for this, that I know of since it is not a
> part of the QMT planning.
>
> You can grab the clamav-toaster source rpm
> <http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
> and update it with the latest clamav sources
> <http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz> and
> compile it for your own uses
>
> Eric
>
>
> On 10/18/2015 10:38 AM, Istvan Köpe wrote:
>
> I also tried with yum and qtp-newmodel, but no success. I installed it 
> with the cnt5064-install-script.sh. There were some problems, but I figured 
> it out somehow and the server is running without problems since about 2 
> years. I think I made and upgrade for clamav since the server installation, 
> but I'm not sure.
>
>  
>
>  
>
> rpm -qa | grep toaster
>
> ucspi-tcp-toaster-0.88-1.3.9.x86_64
>
> qmail-toaster-1.03-1.3.22.x86_64
>
> autorespond-toaster-2.0.5-1.4.0.x86_64
>
> qmailadmin-toaster-1.2.16-1.4.1.x86_64
>
> isoqlog-toaster-2.1-1.3.7.x86_64
>
> ripmime-toaster-1.4.0.6-1.3.6.x86_64
>
> clamav-toaster-0.98.4-1.4.8.x86_64
>
> qmailtoaster-plus-0.3.2-1.4.19.noarch
>
> daemontools-toaster-0.76-1.3.6.x86_64
>
> vpopmail-toaster-5.4.33-1.4.0.x86_64
>
> libsrs2-toaster-1.0.18-1.3.6.x86_64
>
> qmail-pop3d-toaster-1.03-1.3.22.x86_64
>
> courier-imap-toaster-4.1.2-1.3.10.x86_64
>
> control-panel-toaster-0.5-1.4.0.noarch
>
> ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
>
> qmailtoaster-plus.repo-0.2-2.noarch
>
> qmailmrtg-toaster-4.2-1.3.7.x86_64
>
> maildrop-toaster-devel-2.0.3-1.3.8.x86_64
>
> squirrelmail-toaster-1.4.22-1.4.0.noarch
>
> simscan-toaster-1.4.0-1.4.0.x86_64
>
> libdomainkeys-toaster-0.68-1.3.6.x86_64
>
> courier-authlib-toaster-0.59.2-1.3.10.x86_64
>
> ezmlm-toaster-0.53.324-1.3.6.x86_64
>
> maildrop-toaster-2.0.3-1.3.8.x86_64
>
> spamassassin-toaster-3.3.2-1.4.3.x86_64
>
> vqadmin-toaster-2.3.7-1.4.1.x86_64
>
>  
>
> rpm -qa | grep .qt
>
> dovecot-devel-2.0.11-2.qtp.x86_64
>
> dovecot-debuginfo-2.0.11-2.qtp.x86_64
>
> dovecot-2.0.11-2.qtp.x86_64
>
> dovecot-mysql-2.0.11-2.qtp.x86_64
>
> dovecot-pigeonhole-2.0.11-2.qtp.x86_64
>
> whtc-qmt-1-1.qt.el6.noarch
>
> dovecot-pgsql-2.0.11-2.qtp.x86_64
>
>  
>
> István
>
>  
>
>  
>
> -Original Message-
>
> From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
>
> Sent: Sunday, October 18, 2015 5:32 PM
>
> To: qmailtoaster-list@qmailtoaster.com
> <mailto:qmailtoaster-list@qmailtoaster.com>
>
> Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
>  
>
> Istvan,
>
>  
>
> There should be no RPMS with the QMT "toaster" designation on a CentOS 6 
> machine, they should all have the ".qt" designation.
>
>  
>
> How did you go about installing QMT on this CentOS 6 machine?
>
>  
>
> Can you run a couple commands at your CLI?
>
>  
>
> 1) # rpm -qa | grep toaster
>
> 2) # rpm -qa | grep .qt
>
>  
>
> And, post your output.
>
>  
>
> Eric
>
>  
>
>  
>
> On 10/18/2015 3:36 AM, Istvan Köpe wrote:
>
> Hello,
>
>  
>
>  
>
>  
>
> I want to upgrade clamav on a Centos6 x64 but I have this error:
>
>  
>
> rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
>
>  
>
> error:

RE: [qmailtoaster] clamav upgrade on centos 6 x64

[Istvan Köpe]

Hi Eric,

 

I never updated a source rpm. Can you guide me?

 

What would you recommend in my senario for long term?

 

István

 

From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
Sent: Monday, October 19, 2015 4:18 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64

 

Istvan,

You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no upgrades 
that anyone does for this, that I know of since it is not a part of the QMT 
planning. 

You can grab the clamav-toaster source rpm 
<http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
  and update it with the latest clamav sources 
<http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz>  and compile 
it for your own uses

Eric


On 10/18/2015 10:38 AM, Istvan Köpe wrote:

I also tried with yum and qtp-newmodel, but no success. I installed it with the 
cnt5064-install-script.sh. There were some problems, but I figured it out 
somehow and the server is running without problems since about 2 years. I think 
I made and upgrade for clamav since the server installation, but I'm not sure.
 
 
rpm -qa | grep toaster
ucspi-tcp-toaster-0.88-1.3.9.x86_64
qmail-toaster-1.03-1.3.22.x86_64
autorespond-toaster-2.0.5-1.4.0.x86_64
qmailadmin-toaster-1.2.16-1.4.1.x86_64
isoqlog-toaster-2.1-1.3.7.x86_64
ripmime-toaster-1.4.0.6-1.3.6.x86_64
clamav-toaster-0.98.4-1.4.8.x86_64
qmailtoaster-plus-0.3.2-1.4.19.noarch
daemontools-toaster-0.76-1.3.6.x86_64
vpopmail-toaster-5.4.33-1.4.0.x86_64
libsrs2-toaster-1.0.18-1.3.6.x86_64
qmail-pop3d-toaster-1.03-1.3.22.x86_64
courier-imap-toaster-4.1.2-1.3.10.x86_64
control-panel-toaster-0.5-1.4.0.noarch
ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
qmailtoaster-plus.repo-0.2-2.noarch
qmailmrtg-toaster-4.2-1.3.7.x86_64
maildrop-toaster-devel-2.0.3-1.3.8.x86_64
squirrelmail-toaster-1.4.22-1.4.0.noarch
simscan-toaster-1.4.0-1.4.0.x86_64
libdomainkeys-toaster-0.68-1.3.6.x86_64
courier-authlib-toaster-0.59.2-1.3.10.x86_64
ezmlm-toaster-0.53.324-1.3.6.x86_64
maildrop-toaster-2.0.3-1.3.8.x86_64
spamassassin-toaster-3.3.2-1.4.3.x86_64
vqadmin-toaster-2.3.7-1.4.1.x86_64
 
rpm -qa | grep .qt
dovecot-devel-2.0.11-2.qtp.x86_64
dovecot-debuginfo-2.0.11-2.qtp.x86_64
dovecot-2.0.11-2.qtp.x86_64
dovecot-mysql-2.0.11-2.qtp.x86_64
dovecot-pigeonhole-2.0.11-2.qtp.x86_64
whtc-qmt-1-1.qt.el6.noarch
dovecot-pgsql-2.0.11-2.qtp.x86_64
 
István
 
 
-Original Message-
From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
Sent: Sunday, October 18, 2015 5:32 PM
To: qmailtoaster-list@qmailtoaster.com 
<mailto:qmailtoaster-list@qmailtoaster.com> 
Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64
 
Istvan,
 
There should be no RPMS with the QMT "toaster" designation on a CentOS 6 
machine, they should all have the ".qt" designation.
 
How did you go about installing QMT on this CentOS 6 machine?
 
Can you run a couple commands at your CLI?
 
1) # rpm -qa | grep toaster
2) # rpm -qa | grep .qt
 
And, post your output.
 
Eric
 
 
On 10/18/2015 3:36 AM, Istvan Köpe wrote:

Hello,
 
 
 
I want to upgrade clamav on a Centos6 x64 but I have this error:
 
rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
 
error: Failed dependencies:
 
clamav-toaster is needed by (installed)
simscan-toaster-1.4.0-1.4.0.x86_64
 
 
 
Can you help me out?
 
 
 
 
 
István
 
 
 
 

 
 
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
<mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
<mailto:qmailtoaster-list-h...@qmailtoaster.com> 
 
 
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
<mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
<mailto:qmailtoaster-list-h...@qmailtoaster.com> 
 

 

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

Istvan,

You've compiled CentOS 5 SRPMS on a CentOS 6 machine. There are no
upgrades that anyone does for this, that I know of since it is not a
part of the QMT planning.

You can grab the clamav-toaster source rpm
<http://mirrors.qmailtoaster.com/current/SRPMS/clamav-toaster-0.98.4-1.4.8.src.rpm>
and update it with the latest clamav sources
<http://www.clamav.net/downloads/production/clamav-0.98.7.tar.gz> and
compile it for your own uses

Eric


On 10/18/2015 10:38 AM, Istvan Köpe wrote:
> I also tried with yum and qtp-newmodel, but no success. I installed it with 
> the cnt5064-install-script.sh. There were some problems, but I figured it out 
> somehow and the server is running without problems since about 2 years. I 
> think I made and upgrade for clamav since the server installation, but I'm 
> not sure.
>
>
> rpm -qa | grep toaster
> ucspi-tcp-toaster-0.88-1.3.9.x86_64
> qmail-toaster-1.03-1.3.22.x86_64
> autorespond-toaster-2.0.5-1.4.0.x86_64
> qmailadmin-toaster-1.2.16-1.4.1.x86_64
> isoqlog-toaster-2.1-1.3.7.x86_64
> ripmime-toaster-1.4.0.6-1.3.6.x86_64
> clamav-toaster-0.98.4-1.4.8.x86_64
> qmailtoaster-plus-0.3.2-1.4.19.noarch
> daemontools-toaster-0.76-1.3.6.x86_64
> vpopmail-toaster-5.4.33-1.4.0.x86_64
> libsrs2-toaster-1.0.18-1.3.6.x86_64
> qmail-pop3d-toaster-1.03-1.3.22.x86_64
> courier-imap-toaster-4.1.2-1.3.10.x86_64
> control-panel-toaster-0.5-1.4.0.noarch
> ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
> qmailtoaster-plus.repo-0.2-2.noarch
> qmailmrtg-toaster-4.2-1.3.7.x86_64
> maildrop-toaster-devel-2.0.3-1.3.8.x86_64
> squirrelmail-toaster-1.4.22-1.4.0.noarch
> simscan-toaster-1.4.0-1.4.0.x86_64
> libdomainkeys-toaster-0.68-1.3.6.x86_64
> courier-authlib-toaster-0.59.2-1.3.10.x86_64
> ezmlm-toaster-0.53.324-1.3.6.x86_64
> maildrop-toaster-2.0.3-1.3.8.x86_64
> spamassassin-toaster-3.3.2-1.4.3.x86_64
> vqadmin-toaster-2.3.7-1.4.1.x86_64
>
> rpm -qa | grep .qt
> dovecot-devel-2.0.11-2.qtp.x86_64
> dovecot-debuginfo-2.0.11-2.qtp.x86_64
> dovecot-2.0.11-2.qtp.x86_64
> dovecot-mysql-2.0.11-2.qtp.x86_64
> dovecot-pigeonhole-2.0.11-2.qtp.x86_64
> whtc-qmt-1-1.qt.el6.noarch
> dovecot-pgsql-2.0.11-2.qtp.x86_64
>
> István
>
>
> -Original Message-----
> From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
> Sent: Sunday, October 18, 2015 5:32 PM
> To: qmailtoaster-list@qmailtoaster.com
> Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64
>
> Istvan,
>
> There should be no RPMS with the QMT "toaster" designation on a CentOS 6 
> machine, they should all have the ".qt" designation.
>
> How did you go about installing QMT on this CentOS 6 machine?
>
> Can you run a couple commands at your CLI?
>
> 1) # rpm -qa | grep toaster
> 2) # rpm -qa | grep .qt
>
> And, post your output.
>
> Eric
>
>
> On 10/18/2015 3:36 AM, Istvan Köpe wrote:
>> Hello,
>>
>>  
>>
>> I want to upgrade clamav on a Centos6 x64 but I have this error:
>>
>> rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
>>
>> error: Failed dependencies:
>>
>> clamav-toaster is needed by (installed)
>> simscan-toaster-1.4.0-1.4.0.x86_64
>>
>>  
>>
>> Can you help me out?
>>
>>  
>>
>>  
>>
>> István
>>
>>  
>>
>>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>

RE: [qmailtoaster] clamav upgrade on centos 6 x64

[Istvan Köpe]

I also tried with yum and qtp-newmodel, but no success. I installed it with the 
cnt5064-install-script.sh. There were some problems, but I figured it out 
somehow and the server is running without problems since about 2 years. I think 
I made and upgrade for clamav since the server installation, but I'm not sure.


rpm -qa | grep toaster
ucspi-tcp-toaster-0.88-1.3.9.x86_64
qmail-toaster-1.03-1.3.22.x86_64
autorespond-toaster-2.0.5-1.4.0.x86_64
qmailadmin-toaster-1.2.16-1.4.1.x86_64
isoqlog-toaster-2.1-1.3.7.x86_64
ripmime-toaster-1.4.0.6-1.3.6.x86_64
clamav-toaster-0.98.4-1.4.8.x86_64
qmailtoaster-plus-0.3.2-1.4.19.noarch
daemontools-toaster-0.76-1.3.6.x86_64
vpopmail-toaster-5.4.33-1.4.0.x86_64
libsrs2-toaster-1.0.18-1.3.6.x86_64
qmail-pop3d-toaster-1.03-1.3.22.x86_64
courier-imap-toaster-4.1.2-1.3.10.x86_64
control-panel-toaster-0.5-1.4.0.noarch
ezmlm-cgi-toaster-0.53.324-1.3.6.x86_64
qmailtoaster-plus.repo-0.2-2.noarch
qmailmrtg-toaster-4.2-1.3.7.x86_64
maildrop-toaster-devel-2.0.3-1.3.8.x86_64
squirrelmail-toaster-1.4.22-1.4.0.noarch
simscan-toaster-1.4.0-1.4.0.x86_64
libdomainkeys-toaster-0.68-1.3.6.x86_64
courier-authlib-toaster-0.59.2-1.3.10.x86_64
ezmlm-toaster-0.53.324-1.3.6.x86_64
maildrop-toaster-2.0.3-1.3.8.x86_64
spamassassin-toaster-3.3.2-1.4.3.x86_64
vqadmin-toaster-2.3.7-1.4.1.x86_64

rpm -qa | grep .qt
dovecot-devel-2.0.11-2.qtp.x86_64
dovecot-debuginfo-2.0.11-2.qtp.x86_64
dovecot-2.0.11-2.qtp.x86_64
dovecot-mysql-2.0.11-2.qtp.x86_64
dovecot-pigeonhole-2.0.11-2.qtp.x86_64
whtc-qmt-1-1.qt.el6.noarch
dovecot-pgsql-2.0.11-2.qtp.x86_64

István


-Original Message-
From: Eric Broch [mailto:ebr...@whitehorsetc.com] 
Sent: Sunday, October 18, 2015 5:32 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] clamav upgrade on centos 6 x64

Istvan,

There should be no RPMS with the QMT "toaster" designation on a CentOS 6 
machine, they should all have the ".qt" designation.

How did you go about installing QMT on this CentOS 6 machine?

Can you run a couple commands at your CLI?

1) # rpm -qa | grep toaster
2) # rpm -qa | grep .qt

And, post your output.

Eric


On 10/18/2015 3:36 AM, Istvan Köpe wrote:
> Hello,
> 
>  
> 
> I want to upgrade clamav on a Centos6 x64 but I have this error:
> 
> rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
> 
> error: Failed dependencies:
> 
> clamav-toaster is needed by (installed)
> simscan-toaster-1.4.0-1.4.0.x86_64
> 
>  
> 
> Can you help me out?
> 
>  
> 
>  
> 
> István
> 
>  
> 
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] clamav upgrade on centos 6 x64

[Eric Broch]

Istvan,

There should be no RPMS with the QMT "toaster" designation on a CentOS 6
machine, they should all have the ".qt" designation.

How did you go about installing QMT on this CentOS 6 machine?

Can you run a couple commands at your CLI?

1) # rpm -qa | grep toaster
2) # rpm -qa | grep .qt

And, post your output.

Eric


On 10/18/2015 3:36 AM, Istvan Köpe wrote:
> Hello,
> 
>  
> 
> I want to upgrade clamav on a Centos6 x64 but I have this error:
> 
> rpm -Uvh clamav-0.98.7-0.qt.el6.x86_64.rpm
> 
> error: Failed dependencies:
> 
> clamav-toaster is needed by (installed)
> simscan-toaster-1.4.0-1.4.0.x86_64
> 
>  
> 
> Can you help me out?
> 
>  
> 
>  
> 
> István
> 
>  
> 
> 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Clamav Upgrade on Centos 6.6

[Chandran Manikandan]

Thank you Eric. It's working now.

On Wed, Jan 14, 2015 at 11:04 PM, Eric Broch 
wrote:

>  On 1/14/2015 8:01 AM, Eric Broch wrote:
>
> On 1/14/2015 2:57 AM, Chandran Manikandan wrote:
>
> Hi All,
>
>  I have installed Qmailtoaster on this machine and after that if i run
> this command freshclam it's shown clamav outdated. How to update new clamav
> release on this machine. I hope anyone could help me.
>
>  --
>  *Thanks,*
> *Manikandan.C*
> *System Administrator*
>
> Chandran,
>
> It looks like you can use the qmailtoaster 'testing' repo to install it.
> When using yum you'll 'enablerepo testing' ( I can't remember the command
> specifically).
>
> Eric
>
> Chandran,
>
> Here's the proper command:
>
> # yum --enablerepo=qmailtoaster-testing update clamav
>
> Eric
>



-- 
*Thanks,*
*Manikandan.C*
*System Administrator*

Re: [qmailtoaster] Clamav Upgrade on Centos 6.6

[Eric Broch]

On 1/14/2015 8:01 AM, Eric Broch wrote:
> On 1/14/2015 2:57 AM, Chandran Manikandan wrote:
>> Hi All,
>>
>> I have installed Qmailtoaster on this machine and after that if i run
>> this command freshclam it's shown clamav outdated. How to update new
>> clamav release on this machine. I hope anyone could help me.
>>
>> -- 
>> *Thanks,*
>> *Manikandan.C*
>> *System Administrator*
> Chandran,
>
> It looks like you can use the qmailtoaster 'testing' repo to install
> it. When using yum you'll 'enablerepo testing' ( I can't remember the
> command specifically).
>
> Eric
Chandran,

Here's the proper command:

# yum --enablerepo=qmailtoaster-testing update clamav

Eric

Re: [qmailtoaster] Clamav Upgrade on Centos 6.6

[Eric Broch]

On 1/14/2015 2:57 AM, Chandran Manikandan wrote:
> Hi All,
>
> I have installed Qmailtoaster on this machine and after that if i run
> this command freshclam it's shown clamav outdated. How to update new
> clamav release on this machine. I hope anyone could help me.
>
> -- 
> *Thanks,*
> *Manikandan.C*
> *System Administrator*
Chandran,

It looks like you can use the qmailtoaster 'testing' repo to install it.
When using yum you'll 'enablerepo testing' ( I can't remember the
command specifically).

Eric

Re: [qmailtoaster] ClamAV Upgrade Deciding

[Erik A. Espinoza]

whose repistory is that?

EE

On Mon, Apr 21, 2008 at 8:57 AM,  <[EMAIL PROTECTED]> wrote:
>
>Deciding the problem of clamav it follows,
>
>
>   1) service qmail stop
>   2) rpm -e --nodeps clamav-toaster
>   3) wget
>  http://repositorio.zoioroxo.com.br/rede/clamav-toaster-0.93-1.3.18.i386.rpm
>   4) rpm -ivh clamav-toaster-0.93-1.3.18.i386.rpm
>   5) qmailctl cdb
>   6) qmailctl start
>
>   made
>
>
>  -
>  QmailToaster hosted by: VR Hosted 
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV Upgrade

[emiliano]

Aid, my fedora 06 this damage error, in the hour to compile clamav



 1) service qmail stop
 2) rpm -e --nodeps clamav-toaster
 3) rpmbuild --rebuild --with fdr6 clamav-toaster-0.93-1.3.18.src.rpm


[EMAIL PROTECTED] tmp]# nm -D /usr/lib/libz.so|grep gz
0058c4c0 T gzclearerr
0058c760 T gzclose
0058c4a0 T gzdirect
0058d860 T gzdopen
0058c470 T gzeof
0058d910 T gzerror
0058ca00 T gzflush
0058d3a0 T gzgetc
0058d320 T gzgets
0058d8f0 T gzopen
0058ca60 T gzprintf
0058c8f0 T gzputc
0058c8b0 T gzputs
0058cde0 T gzread
0058c940 T gzrewind
0058d0f0 T gzseek
0058d3f0 T gzsetparams
0058d2e0 T gztell
0058c420 T gzungetc
0058c7c0 T gzwrite







e=generic -fasynchronous-unwind-tables -o .libs/freshclam output.o
cfgparser.o getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o
manager.o notify.o dns.o execute.o nonblock.o mirman.o 
../libclamav/.libs/libclamav.so -lresolv -lpthread
cdiff.o: In function `cdiff_apply':
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/cdiff.c:984:
undefined reference to `gzdopen'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/cdiff.c:994:
undefined reference to `gzgets'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/cdiff.c:997:
undefined reference to `gzclose'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/cdiff.c:1016:
undefined reference to `gzclose'
tar.o: In function `tar_addfile':
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/tar.c:82: undefined
reference to `gzwrite'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/tar.c:95: undefined
reference to `gzwrite'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/../shared/tar.c:111: undefined
reference to `gzwrite'
manager.o: In function `buildcld':
/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:932: undefined
reference to `gzclose'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:944: undefined
reference to `gzclose'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined
reference to `gzopen'
/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913: undefined
reference to `gzclose'
collect2: ld returned 1 exit status
make[2]: *** [freshclam] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93/freshclam'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93'
make: *** [all] Error 2
erro: Código de saída inválido do /var/tmp/rpm-tmp.83003 (%build)


Erros de criação do RPM:
Código de saída inválido do /var/tmp/rpm-tmp.83003 (%build)








> Hi Erik,
>
> Thanks ,but I don't think this problem is about my old linux release
> version.
>
> Look at this
> http://www.mail-archive.com/[EMAIL PROTECTED]/msg29083.html
>
> It is about "zlib-1.2.3" .
>
> Dose clamav-0.93 forget the "zlib.so" ?
>
> nm -D /usr/lib/libz.so|grep gz
> 005f2b50 T gzclearerr
> 005f29a0 T gzclose
> 005f28d0 T gzdirect
> 005f19f0 T gzdopen
> 005f28a0 T gzeof
> 005f2a10 T gzerror
> 005f2520 T gzflush
> 005f2100 T gzgetc
> 005f21a0 T gzgets
> 005f19c0 T gzopen
> 005f2300 T gzprintf
> 005f2380 T gzputc
> 005f23d0 T gzputs
> 005f1e40 T gzread
> 005f27b0 T gzrewind
> 005f2580 T gzseek
> 005f1a50 T gzsetparams
> 005f2860 T gztell
> 005f2150 T gzungetc
> 005f2220 T gzwrite
>
>
> - Original Message -
> From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
> To: 
> Sent: Sunday, April 20, 2008 11:30 PM
> Subject: Re: [qmailtoaster] ClamAV Upgrade
>
>
>> Fedora 1.0 is not really supported anymore. The code for the profile
>> is still there for historical purposes, but doesn't really work for
>> the most part.
>>
>> It's really broken. You can try cnt30 or cnt40 and see if that gives
>> you better results but I think you're on your own on this one buddy.
>>
>> EE
>>
>> On Mon, Apr 21, 2008 at 12:08 AM, Kevin <[EMAIL PROTECTED]>
>> wrote:
>>>
>>>
>>>  > 1) service qmail stop
>>>  > 2) rpm -e --nodeps clamav-toaster
>>>  > 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
>>>  ..
>>>  ..
>>>  ..
>>>  gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o
>>> cfgparser.o getopt.o misc.o options.o sha256.o cdiff.o tar.o
>>> freshclam.o manager.o notify.o dns.o execute.o nonblock.o mirman.o
>>> ../libclamav/.libs/libclamav.so -lresolv -lpthread
>>>  cdiff.o(.text+0x1bfb): In function `cdiff_apply':
>>>  ../shared/cdiff.c:984: undefined reference to `gzdopen'
>>>  cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to
>>> `gzgets'
>>>  cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: und

Re: [qmailtoaster] ClamAV Upgrade

[Kevin]

It must be uninstalled at first, and then build the package. It's unusual.

It's OK now, Thanks!

- Original Message - 
From: "Kevin" <[EMAIL PROTECTED]>
To: 
Sent: Monday, April 21, 2008 3:15 AM
Subject: Re: [qmailtoaster] ClamAV Upgrade


>I found this:
> tar jxf  tar jxf clamav-0.93.tar.bz2
> cd clamav-0.93
> ./configure --help
> ..
> --with-zlib=DIR   path to directory containing zlib library (default=
> /usr/local or /usr if not found in /usr/local)
> ..
> So,  remove these files, if thare are
> rm -f /usr/local/include/zlib.h
> rm -f /usr/local/include/zutil.h
> 
> Then, I can build the package without error.
> rpmbuild --rebuild --with fdr10 clamav-toaster-0.93-1.3.18.src.rpm
> 
> But, I had new problem when I installed the package
> rpm -e --nodeps clamav-toaster; rpm -ivh clamav-toaster-0.93-1.3.18.i386.rpm
> warning: /etc/freshclam.conf saved as /etc/freshclam.conf.rpmsave
> Preparing...### [100%]
>   1:clamav-toaster ### [100%]
> error: %post(clamav-toaster-0.93-1.3.18) scriptlet failed, exit status 1
> 
> 
> - Original Message ----- 
> From: "Kevin" <[EMAIL PROTECTED]>
> To: 
> Sent: Monday, April 21, 2008 12:01 AM
> Subject: Re: [qmailtoaster] ClamAV Upgrade
> 
> 
>> Hi Erik,
>> 
>> Thanks ,but I don't think this problem is about my old linux release version.
>> 
>> Look at this  http://www.mail-archive.com/[EMAIL PROTECTED]/msg29083.html
>> 
>> It is about "zlib-1.2.3" .
>> 
>> Dose clamav-0.93 forget the "zlib.so" ?
>> 
>> nm -D /usr/lib/libz.so|grep gz
>> 005f2b50 T gzclearerr
>> 005f29a0 T gzclose
>> 005f28d0 T gzdirect
>> 005f19f0 T gzdopen
>> 005f28a0 T gzeof
>> 005f2a10 T gzerror
>> 005f2520 T gzflush
>> 005f2100 T gzgetc
>> 005f21a0 T gzgets
>> 005f19c0 T gzopen
>> 005f2300 T gzprintf
>> 005f2380 T gzputc
>> 005f23d0 T gzputs
>> 005f1e40 T gzread
>> 005f27b0 T gzrewind
>> 005f2580 T gzseek
>> 005f1a50 T gzsetparams
>> 005f2860 T gztell
>> 005f2150 T gzungetc
>> 005f2220 T gzwrite
>> 
>> 
>> - Original Message - 
>> From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
>> To: 
>> Sent: Sunday, April 20, 2008 11:30 PM
>> Subject: Re: [qmailtoaster] ClamAV Upgrade
>> 
>> 
>>> Fedora 1.0 is not really supported anymore. The code for the profile
>>> is still there for historical purposes, but doesn't really work for
>>> the most part.
>>> 
>>> It's really broken. You can try cnt30 or cnt40 and see if that gives
>>> you better results but I think you're on your own on this one buddy.
>>> 
>>> EE
>>> 
>>> On Mon, Apr 21, 2008 at 12:08 AM, Kevin <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>  > 1) service qmail stop
>>>>  > 2) rpm -e --nodeps clamav-toaster
>>>>  > 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
>>>>  ..
>>>>  ..
>>>>  ..
>>>>  gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o cfgparser.o 
>>>> getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o manager.o 
>>>> notify.o dns.o execute.o nonblock.o mirman.o  
>>>> ../libclamav/.libs/libclamav.so -lresolv -lpthread
>>>>  cdiff.o(.text+0x1bfb): In function `cdiff_apply':
>>>>  ../shared/cdiff.c:984: undefined reference to `gzdopen'
>>>>  cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to 
>>>> `gzgets'
>>>>  cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: undefined reference to 
>>>> `gzclose'
>>>>  cdiff.o(.text+0x1d0b):../shared/cdiff.c:1010: undefined reference to 
>>>> `gzclose'
>>>>  tar.o(.text+0x11e): In function `tar_addfile':
>>>>  ../shared/tar.c:82: undefined reference to `gzwrite'
>>>>  tar.o(.text+0x15d):../shared/tar.c:95: undefined reference to `gzwrite'
>>>>  tar.o(.text+0x204):../shared/tar.c:111: undefined reference to `gzwrite'
>>>>  manager.o(.text+0x1c25): In function `buildcld':
>>>>  /usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined 
>>>> reference to `gzopen'
>>>>  
>>>> manager.o(.text+0x1c7e):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913:
>>>>  unde

Re: [qmailtoaster] ClamAV Upgrade

[James Palmer]

Thanks Erik, that method worked perfectly for me.


On 20 Apr 2008, at 19:09, Erik A. Espinoza wrote:


1) service qmail stop
2) rpm -e --nodeps clamav-toaster
3) rpmbuild --rebuild --with $OSTAG clamav-toaster-newpkg.src.rpm
4) rpm -Uhv newclamavrpm
5) service qmail cdb
6) service qmail start


Erik

On Sun, Apr 20, 2008 at 9:37 AM, James Palmer <[EMAIL PROTECTED]>  
wrote:

Hi all,

Could somebody let me know the easiest way to upgrade from ClamAV  
0.92 to
0.93?  On the QmailToaster site it says " be sure to remove prior  
versions
of ClamAV before building this new one, otherwise it will cause a  
circular
dependency." and I'm unsure how to do that and then install the new  
clamav

package.


Cheers!


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV Upgrade

[Kevin]

I found this:
tar jxf  tar jxf clamav-0.93.tar.bz2
cd clamav-0.93
./configure --help
..
--with-zlib=DIR   path to directory containing zlib library (default=
 /usr/local or /usr if not found in /usr/local)
..
So,  remove these files, if thare are
rm -f /usr/local/include/zlib.h
rm -f /usr/local/include/zutil.h

Then, I can build the package without error.
rpmbuild --rebuild --with fdr10 clamav-toaster-0.93-1.3.18.src.rpm

But, I had new problem when I installed the package
rpm -e --nodeps clamav-toaster; rpm -ivh clamav-toaster-0.93-1.3.18.i386.rpm
warning: /etc/freshclam.conf saved as /etc/freshclam.conf.rpmsave
Preparing...### [100%]
   1:clamav-toaster ### [100%]
error: %post(clamav-toaster-0.93-1.3.18) scriptlet failed, exit status 1


- Original Message - 
From: "Kevin" <[EMAIL PROTECTED]>
To: 
Sent: Monday, April 21, 2008 12:01 AM
Subject: Re: [qmailtoaster] ClamAV Upgrade


> Hi Erik,
> 
> Thanks ,but I don't think this problem is about my old linux release version.
> 
> Look at this  http://www.mail-archive.com/[EMAIL PROTECTED]/msg29083.html
> 
> It is about "zlib-1.2.3" .
> 
> Dose clamav-0.93 forget the "zlib.so" ?
> 
> nm -D /usr/lib/libz.so|grep gz
> 005f2b50 T gzclearerr
> 005f29a0 T gzclose
> 005f28d0 T gzdirect
> 005f19f0 T gzdopen
> 005f28a0 T gzeof
> 005f2a10 T gzerror
> 005f2520 T gzflush
> 005f2100 T gzgetc
> 005f21a0 T gzgets
> 005f19c0 T gzopen
> 005f2300 T gzprintf
> 005f2380 T gzputc
> 005f23d0 T gzputs
> 005f1e40 T gzread
> 005f27b0 T gzrewind
> 005f2580 T gzseek
> 005f1a50 T gzsetparams
> 005f2860 T gztell
> 005f2150 T gzungetc
> 005f2220 T gzwrite
> 
> 
> - Original Message ----- 
> From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
> To: 
> Sent: Sunday, April 20, 2008 11:30 PM
> Subject: Re: [qmailtoaster] ClamAV Upgrade
> 
> 
>> Fedora 1.0 is not really supported anymore. The code for the profile
>> is still there for historical purposes, but doesn't really work for
>> the most part.
>> 
>> It's really broken. You can try cnt30 or cnt40 and see if that gives
>> you better results but I think you're on your own on this one buddy.
>> 
>> EE
>> 
>> On Mon, Apr 21, 2008 at 12:08 AM, Kevin <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>  > 1) service qmail stop
>>>  > 2) rpm -e --nodeps clamav-toaster
>>>  > 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
>>>  ..
>>>  ..
>>>  ..
>>>  gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o cfgparser.o 
>>> getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o manager.o 
>>> notify.o dns.o execute.o nonblock.o mirman.o  
>>> ../libclamav/.libs/libclamav.so -lresolv -lpthread
>>>  cdiff.o(.text+0x1bfb): In function `cdiff_apply':
>>>  ../shared/cdiff.c:984: undefined reference to `gzdopen'
>>>  cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to 
>>> `gzgets'
>>>  cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: undefined reference to 
>>> `gzclose'
>>>  cdiff.o(.text+0x1d0b):../shared/cdiff.c:1010: undefined reference to 
>>> `gzclose'
>>>  tar.o(.text+0x11e): In function `tar_addfile':
>>>  ../shared/tar.c:82: undefined reference to `gzwrite'
>>>  tar.o(.text+0x15d):../shared/tar.c:95: undefined reference to `gzwrite'
>>>  tar.o(.text+0x204):../shared/tar.c:111: undefined reference to `gzwrite'
>>>  manager.o(.text+0x1c25): In function `buildcld':
>>>  /usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined 
>>> reference to `gzopen'
>>>  
>>> manager.o(.text+0x1c7e):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913:
>>>  undefined reference to `gzclose'
>>>  
>>> manager.o(.text+0x1dd6):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:932:
>>>  undefined reference to `gzclose'
>>>  
>>> manager.o(.text+0x1e2a):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:944:
>>>  undefined reference to `gzclose'
>>>  collect2: ld returned 1 exit status
>>>  make[2]: *** [freshclam] Error 1
>>>  make[2]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93/freshclam'
>>>  make[1]: *** [all-recursive] Error 1
>>>  make[1]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93'
>>>  make: *** [all] Error 2
>>>  erro

Re: [qmailtoaster] ClamAV Upgrade

[Kevin]

Hi Erik,

Thanks ,but I don't think this problem is about my old linux release version.

Look at this  http://www.mail-archive.com/[EMAIL PROTECTED]/msg29083.html

It is about "zlib-1.2.3" .

Dose clamav-0.93 forget the "zlib.so" ?

nm -D /usr/lib/libz.so|grep gz
005f2b50 T gzclearerr
005f29a0 T gzclose
005f28d0 T gzdirect
005f19f0 T gzdopen
005f28a0 T gzeof
005f2a10 T gzerror
005f2520 T gzflush
005f2100 T gzgetc
005f21a0 T gzgets
005f19c0 T gzopen
005f2300 T gzprintf
005f2380 T gzputc
005f23d0 T gzputs
005f1e40 T gzread
005f27b0 T gzrewind
005f2580 T gzseek
005f1a50 T gzsetparams
005f2860 T gztell
005f2150 T gzungetc
005f2220 T gzwrite


- Original Message - 
From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, April 20, 2008 11:30 PM
Subject: Re: [qmailtoaster] ClamAV Upgrade


> Fedora 1.0 is not really supported anymore. The code for the profile
> is still there for historical purposes, but doesn't really work for
> the most part.
> 
> It's really broken. You can try cnt30 or cnt40 and see if that gives
> you better results but I think you're on your own on this one buddy.
> 
> EE
> 
> On Mon, Apr 21, 2008 at 12:08 AM, Kevin <[EMAIL PROTECTED]> wrote:
>>
>>
>>  > 1) service qmail stop
>>  > 2) rpm -e --nodeps clamav-toaster
>>  > 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
>>  ..
>>  ..
>>  ..
>>  gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o cfgparser.o 
>> getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o manager.o 
>> notify.o dns.o execute.o nonblock.o mirman.o  
>> ../libclamav/.libs/libclamav.so -lresolv -lpthread
>>  cdiff.o(.text+0x1bfb): In function `cdiff_apply':
>>  ../shared/cdiff.c:984: undefined reference to `gzdopen'
>>  cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to `gzgets'
>>  cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: undefined reference to 
>> `gzclose'
>>  cdiff.o(.text+0x1d0b):../shared/cdiff.c:1010: undefined reference to 
>> `gzclose'
>>  tar.o(.text+0x11e): In function `tar_addfile':
>>  ../shared/tar.c:82: undefined reference to `gzwrite'
>>  tar.o(.text+0x15d):../shared/tar.c:95: undefined reference to `gzwrite'
>>  tar.o(.text+0x204):../shared/tar.c:111: undefined reference to `gzwrite'
>>  manager.o(.text+0x1c25): In function `buildcld':
>>  /usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined 
>> reference to `gzopen'
>>  
>> manager.o(.text+0x1c7e):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913:
>>  undefined reference to `gzclose'
>>  
>> manager.o(.text+0x1dd6):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:932:
>>  undefined reference to `gzclose'
>>  
>> manager.o(.text+0x1e2a):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:944:
>>  undefined reference to `gzclose'
>>  collect2: ld returned 1 exit status
>>  make[2]: *** [freshclam] Error 1
>>  make[2]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93/freshclam'
>>  make[1]: *** [all-recursive] Error 1
>>  make[1]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93'
>>  make: *** [all] Error 2
>>  error: Bad exit status from /var/tmp/rpm-tmp.57 (%build)
>>
>>
>>  RPM build errors:
>> Bad exit status from /var/tmp/rpm-tmp.57 (%build)
>>
>>
>>
>>
>>  - Original Message -
>>  From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
>>  To: 
>>  Sent: Sunday, April 20, 2008 10:09 AM
>>  Subject: Re: [qmailtoaster] ClamAV Upgrade
>>
>>
>>  > 1) service qmail stop
>>  > 2) rpm -e --nodeps clamav-toaster
>>  > 3) rpmbuild --rebuild --with $OSTAG clamav-toaster-newpkg.src.rpm
>>  > 4) rpm -Uhv newclamavrpm
>>  > 5) service qmail cdb
>>  > 6) service qmail start
>>  >
>>  >
>>  > Erik
>>  >
>>  > On Sun, Apr 20, 2008 at 9:37 AM, James Palmer <[EMAIL PROTECTED]> wrote:
>>  >> Hi all,
>>  >>
>>  >> Could somebody let me know the easiest way to upgrade from ClamAV 0.92 to
>>  >> 0.93?  On the QmailToaster site it says " be sure to remove prior 
>> versions
>>  >> of ClamAV before building this new one, otherwise it will cause a 
>> circular
>>  >> dependency." and I'm unsure how to do that and then install the new 
>> clamav
>>  >> package.
>>  >>
>>  >>
>>  >> Cheers!
>>  >
>>
>>
>> > -
>>  > QmailToaster hosted by: VR Hosted <http://www.vr.org>
>>  > -
>>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>>  > For additional commands, e-mail: [EMAIL PROTECTED]
>>  >
>>  >
> 
> -
> QmailToaster hosted by: VR Hosted <http://www.vr.org>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Re: [qmailtoaster] ClamAV Upgrade

[Erik A. Espinoza]

Fedora 1.0 is not really supported anymore. The code for the profile
is still there for historical purposes, but doesn't really work for
the most part.

It's really broken. You can try cnt30 or cnt40 and see if that gives
you better results but I think you're on your own on this one buddy.

EE

On Mon, Apr 21, 2008 at 12:08 AM, Kevin <[EMAIL PROTECTED]> wrote:
>
>
>  > 1) service qmail stop
>  > 2) rpm -e --nodeps clamav-toaster
>  > 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
>  ..
>  ..
>  ..
>  gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o cfgparser.o 
> getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o manager.o 
> notify.o dns.o execute.o nonblock.o mirman.o  ../libclamav/.libs/libclamav.so 
> -lresolv -lpthread
>  cdiff.o(.text+0x1bfb): In function `cdiff_apply':
>  ../shared/cdiff.c:984: undefined reference to `gzdopen'
>  cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to `gzgets'
>  cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: undefined reference to 
> `gzclose'
>  cdiff.o(.text+0x1d0b):../shared/cdiff.c:1010: undefined reference to 
> `gzclose'
>  tar.o(.text+0x11e): In function `tar_addfile':
>  ../shared/tar.c:82: undefined reference to `gzwrite'
>  tar.o(.text+0x15d):../shared/tar.c:95: undefined reference to `gzwrite'
>  tar.o(.text+0x204):../shared/tar.c:111: undefined reference to `gzwrite'
>  manager.o(.text+0x1c25): In function `buildcld':
>  /usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined 
> reference to `gzopen'
>  
> manager.o(.text+0x1c7e):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913:
>  undefined reference to `gzclose'
>  
> manager.o(.text+0x1dd6):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:932:
>  undefined reference to `gzclose'
>  
> manager.o(.text+0x1e2a):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:944:
>  undefined reference to `gzclose'
>  collect2: ld returned 1 exit status
>  make[2]: *** [freshclam] Error 1
>  make[2]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93/freshclam'
>  make[1]: *** [all-recursive] Error 1
>  make[1]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93'
>  make: *** [all] Error 2
>  error: Bad exit status from /var/tmp/rpm-tmp.57 (%build)
>
>
>  RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.57 (%build)
>
>
>
>
>  - Original Message -
>  From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
>  To: 
>  Sent: Sunday, April 20, 2008 10:09 AM
>  Subject: Re: [qmailtoaster] ClamAV Upgrade
>
>
>  > 1) service qmail stop
>  > 2) rpm -e --nodeps clamav-toaster
>  > 3) rpmbuild --rebuild --with $OSTAG clamav-toaster-newpkg.src.rpm
>  > 4) rpm -Uhv newclamavrpm
>  > 5) service qmail cdb
>  > 6) service qmail start
>  >
>  >
>  > Erik
>  >
>  > On Sun, Apr 20, 2008 at 9:37 AM, James Palmer <[EMAIL PROTECTED]> wrote:
>  >> Hi all,
>  >>
>  >> Could somebody let me know the easiest way to upgrade from ClamAV 0.92 to
>  >> 0.93?  On the QmailToaster site it says " be sure to remove prior versions
>  >> of ClamAV before building this new one, otherwise it will cause a circular
>  >> dependency." and I'm unsure how to do that and then install the new clamav
>  >> package.
>  >>
>  >>
>  >> Cheers!
>  >
>
>
> > -
>  > QmailToaster hosted by: VR Hosted <http://www.vr.org>
>  > -
>  > To unsubscribe, e-mail: [EMAIL PROTECTED]
>  > For additional commands, e-mail: [EMAIL PROTECTED]
>  >
>  >

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV Upgrade

[Kevin]

> 1) service qmail stop
> 2) rpm -e --nodeps clamav-toaster
> 3) rpmbuild --rebuild --with fdr10 clamav-toaster-newpkg.src.rpm
..
..
..
gcc -O2 -g -march=i386 -mcpu=i686 -o .libs/freshclam output.o cfgparser.o 
getopt.o misc.o options.o sha256.o cdiff.o tar.o freshclam.o manager.o notify.o 
dns.o execute.o nonblock.o mirman.o  ../libclamav/.libs/libclamav.so -lresolv 
-lpthread 
cdiff.o(.text+0x1bfb): In function `cdiff_apply':
../shared/cdiff.c:984: undefined reference to `gzdopen'
cdiff.o(.text+0x1c42):../shared/cdiff.c:994: undefined reference to `gzgets'
cdiff.o(.text+0x1cbd):../shared/cdiff.c:1016: undefined reference to `gzclose'
cdiff.o(.text+0x1d0b):../shared/cdiff.c:1010: undefined reference to `gzclose'
tar.o(.text+0x11e): In function `tar_addfile':
../shared/tar.c:82: undefined reference to `gzwrite'
tar.o(.text+0x15d):../shared/tar.c:95: undefined reference to `gzwrite'
tar.o(.text+0x204):../shared/tar.c:111: undefined reference to `gzwrite'
manager.o(.text+0x1c25): In function `buildcld':
/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:884: undefined reference 
to `gzopen'
manager.o(.text+0x1c7e):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:913:
 undefined reference to `gzclose'
manager.o(.text+0x1dd6):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:932:
 undefined reference to `gzclose'
manager.o(.text+0x1e2a):/usr/src/redhat/BUILD/clamav-0.93/freshclam/manager.c:944:
 undefined reference to `gzclose'
collect2: ld returned 1 exit status
make[2]: *** [freshclam] Error 1
make[2]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93/freshclam'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/redhat/BUILD/clamav-0.93'
make: *** [all] Error 2
error: Bad exit status from /var/tmp/rpm-tmp.57 (%build)


RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.57 (%build)


- Original Message - 
From: "Erik A. Espinoza" <[EMAIL PROTECTED]>
To: 
Sent: Sunday, April 20, 2008 10:09 AM
Subject: Re: [qmailtoaster] ClamAV Upgrade


> 1) service qmail stop
> 2) rpm -e --nodeps clamav-toaster
> 3) rpmbuild --rebuild --with $OSTAG clamav-toaster-newpkg.src.rpm
> 4) rpm -Uhv newclamavrpm
> 5) service qmail cdb
> 6) service qmail start
> 
> 
> Erik
> 
> On Sun, Apr 20, 2008 at 9:37 AM, James Palmer <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> Could somebody let me know the easiest way to upgrade from ClamAV 0.92 to
>> 0.93?  On the QmailToaster site it says " be sure to remove prior versions
>> of ClamAV before building this new one, otherwise it will cause a circular
>> dependency." and I'm unsure how to do that and then install the new clamav
>> package.
>>
>>
>> Cheers!
> 
> -
> QmailToaster hosted by: VR Hosted <http://www.vr.org>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Re: [qmailtoaster] ClamAV Upgrade

[Erik A. Espinoza]

Nope, you have to 'rpm -e --nodeps' the old clamav before building the new one.

Erik

On Sun, Apr 20, 2008 at 11:09 AM, Roxanne Sandesara
<[EMAIL PROTECTED]> wrote:
> I would assume you need to rpmbuild the 0.93 package. Then before rpm -Uvh
> of the new package, you first need to rpm -e --nodeps the old package. Then
> rpm -Uvh the new package. That's how I interpreted those instructions.
>
>  Roxanne
>
>
>
>  On Apr 20, 2008, at 12:37 PM, James Palmer wrote:
>
>
> > Hi all,
> >
> > Could somebody let me know the easiest way to upgrade from ClamAV 0.92 to
> 0.93?  On the QmailToaster site it says " be sure to remove prior versions
> of ClamAV before building this new one, otherwise it will cause a circular
> dependency." and I'm unsure how to do that and then install the new clamav
> package.
> >
> >
> > Cheers!
> >
>
>
>  -
> QmailToaster hosted by: VR Hosted 
>  -
>  To unsubscribe, e-mail: [EMAIL PROTECTED]
>  For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV Upgrade

[Erik A. Espinoza]

1) service qmail stop
2) rpm -e --nodeps clamav-toaster
3) rpmbuild --rebuild --with $OSTAG clamav-toaster-newpkg.src.rpm
4) rpm -Uhv newclamavrpm
5) service qmail cdb
6) service qmail start


Erik

On Sun, Apr 20, 2008 at 9:37 AM, James Palmer <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Could somebody let me know the easiest way to upgrade from ClamAV 0.92 to
> 0.93?  On the QmailToaster site it says " be sure to remove prior versions
> of ClamAV before building this new one, otherwise it will cause a circular
> dependency." and I'm unsure how to do that and then install the new clamav
> package.
>
>
> Cheers!

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV Upgrade

[Roxanne Sandesara]

I would assume you need to rpmbuild the 0.93 package. Then before rpm  
-Uvh of the new package, you first need to rpm -e --nodeps the old  
package. Then rpm -Uvh the new package. That's how I interpreted  
those instructions.


Roxanne

On Apr 20, 2008, at 12:37 PM, James Palmer wrote:


Hi all,

Could somebody let me know the easiest way to upgrade from ClamAV  
0.92 to 0.93?  On the QmailToaster site it says " be sure to remove  
prior versions of ClamAV before building this new one, otherwise it  
will cause a circular dependency." and I'm unsure how to do that  
and then install the new clamav package.



Cheers!



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[P.V.Anthony]

Hi,

Just wanted to share on my experience with clamAV.

Was using clamav-0.90.2, built from source files. Was working ok. Used a 
lot of cpu.


Upgraded to clamav-0.90.3. That was a very bad experience. Clamd was 
always crashing for me on fedora 01 whenever a html email came in.


Took a gamble on the release candidate clamav-0.91rc1. This one is 
sweet. Really fast. The cpu usage is very low. It is working great.


The rest of qmailtoaster is rpm version 1.2. Only simscan and clamAV is 
from source.


P.V.Anthony

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[slamp slamp]

yes. but this was always set. did not have this issue with 0.90.1 and 0.90.2.

On 6/4/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:

Do you have NOP0FCHECK="1" set in tcprules?

Erik

On 6/4/07, slamp slamp <[EMAIL PROTECTED]> wrote:
> ok i think mine is fixed after removing, rebuilding simscan. however i
> did get a connect() error on the first message i sent. why is this so?
> this happens every single time i stop/start qmailtoaster.
>
> 2007-06-04 20:25:54.199359500 tcpserver: status: 0/100
> 2007-06-04 20:35:57.808546500 tcpserver: status: 0/100
> 2007-06-04 20:36:29.352728500 tcpserver: status: 1/100
> 2007-06-04 20:36:29.352734500 tcpserver: pid 18868 from 209.85.146.179
> 2007-06-04 20:36:29.352737500 tcpserver: ok 18868
> mail.mydomain.com:172.16.133.4:25 :209.85.146.179::18920
> 2007-06-04 20:36:29.637169500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-04 20:36:29.798822500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-04 20:36:29.981328500 connect(): No such file or directory
> 2007-06-04 20:36:29.982487500 qmail-smtpd: qq soft reject (mail server
> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
> RCPTTO:[EMAIL PROTECTED]
> 2007-06-04 20:36:30.067644500 tcpserver: end 18868 status 0
> 2007-06-04 20:36:30.067650500 tcpserver: status: 0/100
> 2007-06-04 20:37:43.501797500 tcpserver: status: 1/100
> 2007-06-04 20:37:43.501802500 tcpserver: pid 18913 from 64.233.162.231
> 2007-06-04 20:37:43.501806500 tcpserver: ok 18913
> mail.mydomain.com:172.16.133.4:25 :64.233.162.231::24401
> 2007-06-04 20:37:43.663915500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-04 20:37:43.703492500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-04 20:37:44.156439500 simscan:[18913]:CLEAN
> (-2.60/12.00):0.4173s:test
> 2:64.233.162.231:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
> 2007-06-04 20:38:14.229914500 tcpserver: end 18913 status 0
> 2007-06-04 20:38:14.229920500 tcpserver: status: 0/100
> 2007-06-04 20:43:10.262579500 tcpserver: status: 1/100
> 2007-06-04 20:43:10.263528500 tcpserver: pid 18986 from 209.85.146.176
> 2007-06-04 20:43:10.263533500 tcpserver: ok 18986
> mail.mydomain.com:172.16.133.4:25 :209.85.146.176::26338
> 2007-06-04 20:43:10.569443500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-04 20:43:10.723094500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-04 20:43:11.225284500 simscan:[18986]:CLEAN
> (-2.60/12.00):0.4140s:test
> 1:209.85.146.176:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
> 2007-06-04 20:43:41.39500 tcpserver: end 18986 status 0
> 2007-06-04 20:43:41.390006500 tcpserver: status: 0/100
> 2007-06-04 20:46:53.250620500 tcpserver: status: 1/100
> 2007-06-04 20:46:53.250626500 tcpserver: pid 19049 from 167.206.4.196
> 2007-06-04 20:46:53.250630500 tcpserver: ok 19049
> mail.mydomain.com:172.16.133.4:25 :167.206.4.196::61759
> 2007-06-04 20:46:53.321438500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-04 20:46:53.333287500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-04 20:46:53.753752500 simscan:[19049]:CLEAN
> (-2.50/12.00):0.4194s:test
> 3:167.206.4.196:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
> 2007-06-04 20:46:53.794284500 tcpserver: end 19049 status 0
> 2007-06-04 20:46:53.794290500 tcpserver: status: 0/100
>
> On 6/4/07, Philip Nix Guru <[EMAIL PROTECTED]> wrote:
> > Removing, rebuilding simscan didnt fix the connect(): No such file or
> > directory  problem
> >
> > it is coz of that :
> > 2007-06-04 19:07:01.995582500 No stats for Database check - forcing reload
> > 2007-06-04 19:07:01.995611500 Reading databases from /usr/share/clamav
> >
> > Erik A. Espinoza wrote:
> > > Remove, rebuild, and reinstall simscan after you install clamav-toaster.
> > >
> > > Erik
> > >
> > > On 6/4/07, Philip <[EMAIL PROTECTED]> wrote:
> > >> Hey
> > >> I had that same issue with the
> > >>
> > >> connect(): No such file or directory
> > >>
> > >> looks like clamd got delayed somehow when it was supposed to start
> > >> but it worked fine after
> > >>
> > >> And that 90.3 fixes the problem with the connection dying I had on
> > >> many machines with the 90.2
> > >>
> > >> Hopefully simscan will have the feature in next version not to just
> > >> reject a mail if a scanner is down like clamd
> > >>
> > >> -P
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> [EMAIL PROTECTED] wrote:
> > >> > Since you rebooted and clamd was running I really don't know what
> > >> to say
> > >> > on that one. As long as you did the 'rebuild' thing first and then
> > >> the rpm
> > >> >

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[Erik A. Espinoza]

Do you have NOP0FCHECK="1" set in tcprules?

Erik

On 6/4/07, slamp slamp <[EMAIL PROTECTED]> wrote:

ok i think mine is fixed after removing, rebuilding simscan. however i
did get a connect() error on the first message i sent. why is this so?
this happens every single time i stop/start qmailtoaster.

2007-06-04 20:25:54.199359500 tcpserver: status: 0/100
2007-06-04 20:35:57.808546500 tcpserver: status: 0/100
2007-06-04 20:36:29.352728500 tcpserver: status: 1/100
2007-06-04 20:36:29.352734500 tcpserver: pid 18868 from 209.85.146.179
2007-06-04 20:36:29.352737500 tcpserver: ok 18868
mail.mydomain.com:172.16.133.4:25 :209.85.146.179::18920
2007-06-04 20:36:29.637169500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:36:29.798822500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:36:29.981328500 connect(): No such file or directory
2007-06-04 20:36:29.982487500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-04 20:36:30.067644500 tcpserver: end 18868 status 0
2007-06-04 20:36:30.067650500 tcpserver: status: 0/100
2007-06-04 20:37:43.501797500 tcpserver: status: 1/100
2007-06-04 20:37:43.501802500 tcpserver: pid 18913 from 64.233.162.231
2007-06-04 20:37:43.501806500 tcpserver: ok 18913
mail.mydomain.com:172.16.133.4:25 :64.233.162.231::24401
2007-06-04 20:37:43.663915500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:37:43.703492500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:37:44.156439500 simscan:[18913]:CLEAN
(-2.60/12.00):0.4173s:test
2:64.233.162.231:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:38:14.229914500 tcpserver: end 18913 status 0
2007-06-04 20:38:14.229920500 tcpserver: status: 0/100
2007-06-04 20:43:10.262579500 tcpserver: status: 1/100
2007-06-04 20:43:10.263528500 tcpserver: pid 18986 from 209.85.146.176
2007-06-04 20:43:10.263533500 tcpserver: ok 18986
mail.mydomain.com:172.16.133.4:25 :209.85.146.176::26338
2007-06-04 20:43:10.569443500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:43:10.723094500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:43:11.225284500 simscan:[18986]:CLEAN
(-2.60/12.00):0.4140s:test
1:209.85.146.176:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:43:41.39500 tcpserver: end 18986 status 0
2007-06-04 20:43:41.390006500 tcpserver: status: 0/100
2007-06-04 20:46:53.250620500 tcpserver: status: 1/100
2007-06-04 20:46:53.250626500 tcpserver: pid 19049 from 167.206.4.196
2007-06-04 20:46:53.250630500 tcpserver: ok 19049
mail.mydomain.com:172.16.133.4:25 :167.206.4.196::61759
2007-06-04 20:46:53.321438500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:46:53.333287500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:46:53.753752500 simscan:[19049]:CLEAN
(-2.50/12.00):0.4194s:test
3:167.206.4.196:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:46:53.794284500 tcpserver: end 19049 status 0
2007-06-04 20:46:53.794290500 tcpserver: status: 0/100

On 6/4/07, Philip Nix Guru <[EMAIL PROTECTED]> wrote:
> Removing, rebuilding simscan didnt fix the connect(): No such file or
> directory  problem
>
> it is coz of that :
> 2007-06-04 19:07:01.995582500 No stats for Database check - forcing reload
> 2007-06-04 19:07:01.995611500 Reading databases from /usr/share/clamav
>
> Erik A. Espinoza wrote:
> > Remove, rebuild, and reinstall simscan after you install clamav-toaster.
> >
> > Erik
> >
> > On 6/4/07, Philip <[EMAIL PROTECTED]> wrote:
> >> Hey
> >> I had that same issue with the
> >>
> >> connect(): No such file or directory
> >>
> >> looks like clamd got delayed somehow when it was supposed to start
> >> but it worked fine after
> >>
> >> And that 90.3 fixes the problem with the connection dying I had on
> >> many machines with the 90.2
> >>
> >> Hopefully simscan will have the feature in next version not to just
> >> reject a mail if a scanner is down like clamd
> >>
> >> -P
> >>
> >>
> >>
> >>
> >>
> >> [EMAIL PROTECTED] wrote:
> >> > Since you rebooted and clamd was running I really don't know what
> >> to say
> >> > on that one. As long as you did the 'rebuild' thing first and then
> >> the rpm
> >> > install. Maybe someone else knows?
> >> >
> >> > Chas.
> >> >
> >> >
> >> >> forgot to mention that machine was rebooted. clamd was running. i
> >> >> reverted to the old version and things are working again.
> >> >>
> >> >> # qmailctl stat
> >> >> authlib: up (pid 2935) 442 seconds
> >> >> clamd: up (pid 2934) 442 seconds
> >> >> imap4: up (pid 2924) 442 secon

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[slamp slamp]

ok i think mine is fixed after removing, rebuilding simscan. however i
did get a connect() error on the first message i sent. why is this so?
this happens every single time i stop/start qmailtoaster.

2007-06-04 20:25:54.199359500 tcpserver: status: 0/100
2007-06-04 20:35:57.808546500 tcpserver: status: 0/100
2007-06-04 20:36:29.352728500 tcpserver: status: 1/100
2007-06-04 20:36:29.352734500 tcpserver: pid 18868 from 209.85.146.179
2007-06-04 20:36:29.352737500 tcpserver: ok 18868
mail.mydomain.com:172.16.133.4:25 :209.85.146.179::18920
2007-06-04 20:36:29.637169500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:36:29.798822500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:36:29.981328500 connect(): No such file or directory
2007-06-04 20:36:29.982487500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-04 20:36:30.067644500 tcpserver: end 18868 status 0
2007-06-04 20:36:30.067650500 tcpserver: status: 0/100
2007-06-04 20:37:43.501797500 tcpserver: status: 1/100
2007-06-04 20:37:43.501802500 tcpserver: pid 18913 from 64.233.162.231
2007-06-04 20:37:43.501806500 tcpserver: ok 18913
mail.mydomain.com:172.16.133.4:25 :64.233.162.231::24401
2007-06-04 20:37:43.663915500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:37:43.703492500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:37:44.156439500 simscan:[18913]:CLEAN
(-2.60/12.00):0.4173s:test
2:64.233.162.231:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:38:14.229914500 tcpserver: end 18913 status 0
2007-06-04 20:38:14.229920500 tcpserver: status: 0/100
2007-06-04 20:43:10.262579500 tcpserver: status: 1/100
2007-06-04 20:43:10.263528500 tcpserver: pid 18986 from 209.85.146.176
2007-06-04 20:43:10.263533500 tcpserver: ok 18986
mail.mydomain.com:172.16.133.4:25 :209.85.146.176::26338
2007-06-04 20:43:10.569443500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:43:10.723094500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:43:11.225284500 simscan:[18986]:CLEAN
(-2.60/12.00):0.4140s:test
1:209.85.146.176:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:43:41.39500 tcpserver: end 18986 status 0
2007-06-04 20:43:41.390006500 tcpserver: status: 0/100
2007-06-04 20:46:53.250620500 tcpserver: status: 1/100
2007-06-04 20:46:53.250626500 tcpserver: pid 19049 from 167.206.4.196
2007-06-04 20:46:53.250630500 tcpserver: ok 19049
mail.mydomain.com:172.16.133.4:25 :167.206.4.196::61759
2007-06-04 20:46:53.321438500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-04 20:46:53.333287500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-04 20:46:53.753752500 simscan:[19049]:CLEAN
(-2.50/12.00):0.4194s:test
3:167.206.4.196:[EMAIL PROTECTED]:[EMAIL PROTECTED]:
2007-06-04 20:46:53.794284500 tcpserver: end 19049 status 0
2007-06-04 20:46:53.794290500 tcpserver: status: 0/100

On 6/4/07, Philip Nix Guru <[EMAIL PROTECTED]> wrote:

Removing, rebuilding simscan didnt fix the connect(): No such file or
directory  problem

it is coz of that :
2007-06-04 19:07:01.995582500 No stats for Database check - forcing reload
2007-06-04 19:07:01.995611500 Reading databases from /usr/share/clamav

Erik A. Espinoza wrote:
> Remove, rebuild, and reinstall simscan after you install clamav-toaster.
>
> Erik
>
> On 6/4/07, Philip <[EMAIL PROTECTED]> wrote:
>> Hey
>> I had that same issue with the
>>
>> connect(): No such file or directory
>>
>> looks like clamd got delayed somehow when it was supposed to start
>> but it worked fine after
>>
>> And that 90.3 fixes the problem with the connection dying I had on
>> many machines with the 90.2
>>
>> Hopefully simscan will have the feature in next version not to just
>> reject a mail if a scanner is down like clamd
>>
>> -P
>>
>>
>>
>>
>>
>> [EMAIL PROTECTED] wrote:
>> > Since you rebooted and clamd was running I really don't know what
>> to say
>> > on that one. As long as you did the 'rebuild' thing first and then
>> the rpm
>> > install. Maybe someone else knows?
>> >
>> > Chas.
>> >
>> >
>> >> forgot to mention that machine was rebooted. clamd was running. i
>> >> reverted to the old version and things are working again.
>> >>
>> >> # qmailctl stat
>> >> authlib: up (pid 2935) 442 seconds
>> >> clamd: up (pid 2934) 442 seconds
>> >> imap4: up (pid 2924) 442 seconds
>> >> imap4-ssl: up (pid 2938) 442 seconds
>> >> pop3: up (pid 2927) 442 seconds
>> >> pop3-ssl: up (pid 2937) 442 seconds
>> >> send: up (pid 2959) 442 seconds
>> >> smtp: up (pid 2922) 442 secon

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[Philip Nix Guru]

Removing, rebuilding simscan didnt fix the connect(): No such file or 
directory  problem


it is coz of that :
2007-06-04 19:07:01.995582500 No stats for Database check - forcing reload
2007-06-04 19:07:01.995611500 Reading databases from /usr/share/clamav

Erik A. Espinoza wrote:

Remove, rebuild, and reinstall simscan after you install clamav-toaster.

Erik

On 6/4/07, Philip <[EMAIL PROTECTED]> wrote:

Hey
I had that same issue with the

connect(): No such file or directory

looks like clamd got delayed somehow when it was supposed to start
but it worked fine after

And that 90.3 fixes the problem with the connection dying I had on 
many machines with the 90.2


Hopefully simscan will have the feature in next version not to just 
reject a mail if a scanner is down like clamd


-P





[EMAIL PROTECTED] wrote:
> Since you rebooted and clamd was running I really don't know what 
to say
> on that one. As long as you did the 'rebuild' thing first and then 
the rpm

> install. Maybe someone else knows?
>
> Chas.
>
>
>> forgot to mention that machine was rebooted. clamd was running. i
>> reverted to the old version and things are working again.
>>
>> # qmailctl stat
>> authlib: up (pid 2935) 442 seconds
>> clamd: up (pid 2934) 442 seconds
>> imap4: up (pid 2924) 442 seconds
>> imap4-ssl: up (pid 2938) 442 seconds
>> pop3: up (pid 2927) 442 seconds
>> pop3-ssl: up (pid 2937) 442 seconds
>> send: up (pid 2959) 442 seconds
>> smtp: up (pid 2922) 442 seconds
>> spamd: up (pid 2926) 442 seconds
>> submission: up (pid 2929) 442 seconds
>> authlib/log: up (pid 2939) 442 seconds
>> clamd/log: up (pid 2932) 442 seconds
>> imap4/log: up (pid 2931) 442 seconds
>> imap4-ssl/log: up (pid 2940) 442 seconds
>> pop3/log: up (pid 2933) 442 seconds
>> pop3-ssl/log: up (pid 2936) 442 seconds
>> send/log: up (pid 2928) 442 seconds
>> smtp/log: up (pid 2930) 442 seconds
>> spamd/log: up (pid 2925) 442 seconds
>> submission/log: up (pid 2923) 442 seconds
>>
>>
>> On 6/3/07, slamp slamp <[EMAIL PROTECTED]> wrote:
>>
>>> how did you manage to update? my toaster broke after upgrading to 
the

>>> new clamav 0.90.3.
>>>
>>> 2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
>>> 2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
>>> 2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
>>> 2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
>>> 2007-06-03 22:06:14.902173500 tcpserver: ok 4399
>>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
>>> 2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt <> : sender
>>> accepted
>>> 2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt
>>> <[EMAIL PROTECTED]> : found existing recipient
>>> 2007-06-03 22:06:15.294420500 connect(): No such file or directory
>>> 2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail 
server
>>> temporarily rejected message (#4.3.0)): 
MAILFROM:<[EMAIL PROTECTED]>

>>> RCPTTO:[EMAIL PROTECTED]
>>> 2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
>>> 2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
>>> 2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
>>> 2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
>>> 2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 
167.206.4.199

>>> 2007-06-03 22:12:17.737210500 tcpserver: ok 22314
>>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
>>> 2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt <> : sender
>>> accepted
>>> 2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt
>>> <[EMAIL PROTECTED]> : found existing recipient
>>> 2007-06-03 22:12:17.807075500 connect(): No such file or directory
>>> 2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail 
server
>>> temporarily rejected message (#4.3.0)): 
MAILFROM:<[EMAIL PROTECTED]>

>>> RCPTTO:[EMAIL PROTECTED]
>>> 2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
>>> 2007-06-03 22:12:17.826076500 tcpserver: status: 0/100
>>>
>>> On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
>>>
 service qmail cdb

 Erik

 On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> 
wrote:


> Well I've just been able to update with the ClamAV 0.90.3 package
>
>>> (on a
>>>
> CentOS 4.5 box) and all is well so far. could anyone tell me the
>
>>> command
>>>
> to run to get Simscan to see show the newer version in email
>
>>> headers?
>>>
> Thanks,
> Chas.
>
>
> 
-

>  QmailToaster hosted by: VR Hosted 
> 
-

> To unsubscribe, e-mail:
>
>>> [EMAIL PROTECTED]
>>>
> For additional commands, e-mail:
>
>>> [EMAIL PROTECTED]
>>>
>
 
--

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[Erik A. Espinoza]

Remove, rebuild, and reinstall simscan after you install clamav-toaster.

Erik

On 6/4/07, Philip <[EMAIL PROTECTED]> wrote:

Hey
I had that same issue with the

connect(): No such file or directory

looks like clamd got delayed somehow when it was supposed to start
but it worked fine after

And that 90.3 fixes the problem with the connection dying I had on many 
machines with the 90.2

Hopefully simscan will have the feature in next version not to just reject a 
mail if a scanner is down like clamd

-P





[EMAIL PROTECTED] wrote:
> Since you rebooted and clamd was running I really don't know what to say
> on that one. As long as you did the 'rebuild' thing first and then the rpm
> install. Maybe someone else knows?
>
> Chas.
>
>
>> forgot to mention that machine was rebooted. clamd was running. i
>> reverted to the old version and things are working again.
>>
>> # qmailctl stat
>> authlib: up (pid 2935) 442 seconds
>> clamd: up (pid 2934) 442 seconds
>> imap4: up (pid 2924) 442 seconds
>> imap4-ssl: up (pid 2938) 442 seconds
>> pop3: up (pid 2927) 442 seconds
>> pop3-ssl: up (pid 2937) 442 seconds
>> send: up (pid 2959) 442 seconds
>> smtp: up (pid 2922) 442 seconds
>> spamd: up (pid 2926) 442 seconds
>> submission: up (pid 2929) 442 seconds
>> authlib/log: up (pid 2939) 442 seconds
>> clamd/log: up (pid 2932) 442 seconds
>> imap4/log: up (pid 2931) 442 seconds
>> imap4-ssl/log: up (pid 2940) 442 seconds
>> pop3/log: up (pid 2933) 442 seconds
>> pop3-ssl/log: up (pid 2936) 442 seconds
>> send/log: up (pid 2928) 442 seconds
>> smtp/log: up (pid 2930) 442 seconds
>> spamd/log: up (pid 2925) 442 seconds
>> submission/log: up (pid 2923) 442 seconds
>>
>>
>> On 6/3/07, slamp slamp <[EMAIL PROTECTED]> wrote:
>>
>>> how did you manage to update? my toaster broke after upgrading to the
>>> new clamav 0.90.3.
>>>
>>> 2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
>>> 2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
>>> 2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
>>> 2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
>>> 2007-06-03 22:06:14.902173500 tcpserver: ok 4399
>>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
>>> 2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt <> : sender
>>> accepted
>>> 2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt
>>> <[EMAIL PROTECTED]> : found existing recipient
>>> 2007-06-03 22:06:15.294420500 connect(): No such file or directory
>>> 2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
>>> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
>>> RCPTTO:[EMAIL PROTECTED]
>>> 2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
>>> 2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
>>> 2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
>>> 2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
>>> 2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
>>> 2007-06-03 22:12:17.737210500 tcpserver: ok 22314
>>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
>>> 2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt <> : sender
>>> accepted
>>> 2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
>>> <[EMAIL PROTECTED]::> remote
>>>  rcpt
>>> <[EMAIL PROTECTED]> : found existing recipient
>>> 2007-06-03 22:12:17.807075500 connect(): No such file or directory
>>> 2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
>>> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
>>> RCPTTO:[EMAIL PROTECTED]
>>> 2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
>>> 2007-06-03 22:12:17.826076500 tcpserver: status: 0/100
>>>
>>> On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
>>>
 service qmail cdb

 Erik

 On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> Well I've just been able to update with the ClamAV 0.90.3 package
>
>>> (on a
>>>
> CentOS 4.5 box) and all is well so far. could anyone tell me the
>
>>> command
>>>
> to run to get Simscan to see show the newer version in email
>
>>> headers?
>>>
> Thanks,
> Chas.
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail:
>
>>> [EMAIL PROTECTED]
>>>
> For additional commands, e-mail:
>
>>> [EMAIL PROTECTED]
>>>
>
 -
  QmailToaster hosted by: VR Hosted 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail:

>>> [EMAIL PROTECTED

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[Philip]

Hey
I had that same issue with the

connect(): No such file or directory

looks like clamd got delayed somehow when it was supposed to start
but it worked fine after

And that 90.3 fixes the problem with the connection dying I had on many 
machines with the 90.2

Hopefully simscan will have the feature in next version not to just reject a 
mail if a scanner is down like clamd

-P





[EMAIL PROTECTED] wrote:

Since you rebooted and clamd was running I really don't know what to say
on that one. As long as you did the 'rebuild' thing first and then the rpm
install. Maybe someone else knows?

Chas.

  

forgot to mention that machine was rebooted. clamd was running. i
reverted to the old version and things are working again.

# qmailctl stat
authlib: up (pid 2935) 442 seconds
clamd: up (pid 2934) 442 seconds
imap4: up (pid 2924) 442 seconds
imap4-ssl: up (pid 2938) 442 seconds
pop3: up (pid 2927) 442 seconds
pop3-ssl: up (pid 2937) 442 seconds
send: up (pid 2959) 442 seconds
smtp: up (pid 2922) 442 seconds
spamd: up (pid 2926) 442 seconds
submission: up (pid 2929) 442 seconds
authlib/log: up (pid 2939) 442 seconds
clamd/log: up (pid 2932) 442 seconds
imap4/log: up (pid 2931) 442 seconds
imap4-ssl/log: up (pid 2940) 442 seconds
pop3/log: up (pid 2933) 442 seconds
pop3-ssl/log: up (pid 2936) 442 seconds
send/log: up (pid 2928) 442 seconds
smtp/log: up (pid 2930) 442 seconds
spamd/log: up (pid 2925) 442 seconds
submission/log: up (pid 2923) 442 seconds


On 6/3/07, slamp slamp <[EMAIL PROTECTED]> wrote:


how did you manage to update? my toaster broke after upgrading to the
new clamav 0.90.3.

2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
2007-06-03 22:06:14.902173500 tcpserver: ok 4399
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:06:15.294420500 connect(): No such file or directory
2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
2007-06-03 22:12:17.737210500 tcpserver: ok 22314
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:12:17.807075500 connect(): No such file or directory
2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
2007-06-03 22:12:17.826076500 tcpserver: status: 0/100

On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
  

service qmail cdb

Erik

On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:


Well I've just been able to update with the ClamAV 0.90.3 package
  

(on a
  

CentOS 4.5 box) and all is well so far. could anyone tell me the
  

command
  

to run to get Simscan to see show the newer version in email
  

headers?
  

Thanks,
Chas.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail:
  

[EMAIL PROTECTED]
  

For additional commands, e-mail:
  

[EMAIL PROTECTED]
  
  

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:


[EMAIL PROTECTED]
  


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







-
 QmailToaster hosted by: VR Hosted 

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[chas]

Since you rebooted and clamd was running I really don't know what to say
on that one. As long as you did the 'rebuild' thing first and then the rpm
install. Maybe someone else knows?

Chas.

> forgot to mention that machine was rebooted. clamd was running. i
> reverted to the old version and things are working again.
>
> # qmailctl stat
> authlib: up (pid 2935) 442 seconds
> clamd: up (pid 2934) 442 seconds
> imap4: up (pid 2924) 442 seconds
> imap4-ssl: up (pid 2938) 442 seconds
> pop3: up (pid 2927) 442 seconds
> pop3-ssl: up (pid 2937) 442 seconds
> send: up (pid 2959) 442 seconds
> smtp: up (pid 2922) 442 seconds
> spamd: up (pid 2926) 442 seconds
> submission: up (pid 2929) 442 seconds
> authlib/log: up (pid 2939) 442 seconds
> clamd/log: up (pid 2932) 442 seconds
> imap4/log: up (pid 2931) 442 seconds
> imap4-ssl/log: up (pid 2940) 442 seconds
> pop3/log: up (pid 2933) 442 seconds
> pop3-ssl/log: up (pid 2936) 442 seconds
> send/log: up (pid 2928) 442 seconds
> smtp/log: up (pid 2930) 442 seconds
> spamd/log: up (pid 2925) 442 seconds
> submission/log: up (pid 2923) 442 seconds
>
>
> On 6/3/07, slamp slamp <[EMAIL PROTECTED]> wrote:
>> how did you manage to update? my toaster broke after upgrading to the
>> new clamav 0.90.3.
>>
>> 2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
>> 2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
>> 2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
>> 2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
>> 2007-06-03 22:06:14.902173500 tcpserver: ok 4399
>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
>> 2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
>> <[EMAIL PROTECTED]::> remote
>>  rcpt <> : sender
>> accepted
>> 2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
>> <[EMAIL PROTECTED]::> remote
>>  rcpt
>> <[EMAIL PROTECTED]> : found existing recipient
>> 2007-06-03 22:06:15.294420500 connect(): No such file or directory
>> 2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
>> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
>> RCPTTO:[EMAIL PROTECTED]
>> 2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
>> 2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
>> 2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
>> 2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
>> 2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
>> 2007-06-03 22:12:17.737210500 tcpserver: ok 22314
>> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
>> 2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
>> <[EMAIL PROTECTED]::> remote
>>  rcpt <> : sender
>> accepted
>> 2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
>> <[EMAIL PROTECTED]::> remote
>>  rcpt
>> <[EMAIL PROTECTED]> : found existing recipient
>> 2007-06-03 22:12:17.807075500 connect(): No such file or directory
>> 2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
>> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
>> RCPTTO:[EMAIL PROTECTED]
>> 2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
>> 2007-06-03 22:12:17.826076500 tcpserver: status: 0/100
>>
>> On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
>> > service qmail cdb
>> >
>> > Erik
>> >
>> > On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> > > Well I've just been able to update with the ClamAV 0.90.3 package
>> (on a
>> > > CentOS 4.5 box) and all is well so far. could anyone tell me the
>> command
>> > > to run to get Simscan to see show the newer version in email
>> headers?
>> > >
>> > > Thanks,
>> > > Chas.
>> > >
>> > >
>> > > -
>> > >  QmailToaster hosted by: VR Hosted 
>> > > -
>> > > To unsubscribe, e-mail:
>> [EMAIL PROTECTED]
>> > > For additional commands, e-mail:
>> [EMAIL PROTECTED]
>> > >
>> > >
>> >
>> > -
>> >  QmailToaster hosted by: VR Hosted 
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail:
>> [EMAIL PROTECTED]
>> >
>> >
>>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[chas]

Hmmm, mine was a recent full instal where I built it with the latest
clamav and squirellmail packages, so I was only upgrading from clamav
0.90.2 to the newer 0.90.3.

I did these comamnds;

qmailctl stop
rpmbuild --rebuild --with cnt40 clamav-toaster-0.90.3
cd /usr/src/redhat/RPMS/i386/
rpm -Uvh clamav-toaster-0.90.3-1.3.13.i386.rpm
qmailctl start
(and per Erik)
service qmail cdb

Works fine now, headers and all.

You might want to make sure clamav is running;

ps -ef | grep clamd  (or clamav)

Should say something like;

root  5199  5174  0 22:36 pts/000:00:00 supervise clamd
clamav5220  5199  3 22:36 pts/000:00:26 /usr/sbin/clamd
qmaill5221  5200  0 22:36 pts/000:00:00 /usr/bin/multilog t
s100 n100 /var/log/qmail/clamd

if you don't see the proper output there may be something wrong. I vaguely
remember having to fix a clamav.conf file once that got overwritten on
another install (may not have been a 'toaster' install though).

Chas.


> how did you manage to update? my toaster broke after upgrading to the
> new clamav 0.90.3.
>
> 2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
> 2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
> 2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
> 2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
> 2007-06-03 22:06:14.902173500 tcpserver: ok 4399
> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
> 2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-03 22:06:15.294420500 connect(): No such file or directory
> 2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
> RCPTTO:[EMAIL PROTECTED]
> 2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
> 2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
> 2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
> 2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
> 2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
> 2007-06-03 22:12:17.737210500 tcpserver: ok 22314
> mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
> 2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
> <[EMAIL PROTECTED]::> remote
>  rcpt <> : sender
> accepted
> 2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
> <[EMAIL PROTECTED]::> remote
>  rcpt
> <[EMAIL PROTECTED]> : found existing recipient
> 2007-06-03 22:12:17.807075500 connect(): No such file or directory
> 2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
> temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
> RCPTTO:[EMAIL PROTECTED]
> 2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
> 2007-06-03 22:12:17.826076500 tcpserver: status: 0/100
>
> On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
>> service qmail cdb
>>
>> Erik
>>
>> On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> > Well I've just been able to update with the ClamAV 0.90.3 package (on
>> a
>> > CentOS 4.5 box) and all is well so far. could anyone tell me the
>> command
>> > to run to get Simscan to see show the newer version in email headers?
>> >
>> > Thanks,
>> > Chas.
>> >
>> >
>> > -
>> >  QmailToaster hosted by: VR Hosted 
>> > -
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail:
>> [EMAIL PROTECTED]
>> >
>> >
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[slamp slamp]

forgot to mention that machine was rebooted. clamd was running. i
reverted to the old version and things are working again.

# qmailctl stat
authlib: up (pid 2935) 442 seconds
clamd: up (pid 2934) 442 seconds
imap4: up (pid 2924) 442 seconds
imap4-ssl: up (pid 2938) 442 seconds
pop3: up (pid 2927) 442 seconds
pop3-ssl: up (pid 2937) 442 seconds
send: up (pid 2959) 442 seconds
smtp: up (pid 2922) 442 seconds
spamd: up (pid 2926) 442 seconds
submission: up (pid 2929) 442 seconds
authlib/log: up (pid 2939) 442 seconds
clamd/log: up (pid 2932) 442 seconds
imap4/log: up (pid 2931) 442 seconds
imap4-ssl/log: up (pid 2940) 442 seconds
pop3/log: up (pid 2933) 442 seconds
pop3-ssl/log: up (pid 2936) 442 seconds
send/log: up (pid 2928) 442 seconds
smtp/log: up (pid 2930) 442 seconds
spamd/log: up (pid 2925) 442 seconds
submission/log: up (pid 2923) 442 seconds


On 6/3/07, slamp slamp <[EMAIL PROTECTED]> wrote:

how did you manage to update? my toaster broke after upgrading to the
new clamav 0.90.3.

2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
2007-06-03 22:06:14.902173500 tcpserver: ok 4399
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:06:15.294420500 connect(): No such file or directory
2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
2007-06-03 22:12:17.737210500 tcpserver: ok 22314
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:12:17.807075500 connect(): No such file or directory
2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
2007-06-03 22:12:17.826076500 tcpserver: status: 0/100

On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:
> service qmail cdb
>
> Erik
>
> On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > Well I've just been able to update with the ClamAV 0.90.3 package (on a
> > CentOS 4.5 box) and all is well so far. could anyone tell me the command
> > to run to get Simscan to see show the newer version in email headers?
> >
> > Thanks,
> > Chas.
> >
> >
> > -
> >  QmailToaster hosted by: VR Hosted 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[chas]

That's got it, thanks.

Chas.

> service qmail cdb
>
> Erik
>
> On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> Well I've just been able to update with the ClamAV 0.90.3 package (on a
>> CentOS 4.5 box) and all is well so far. could anyone tell me the command
>> to run to get Simscan to see show the newer version in email headers?
>>
>> Thanks,
>> Chas.
>>
>>
>> -
>>  QmailToaster hosted by: VR Hosted 
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[slamp slamp]

how did you manage to update? my toaster broke after upgrading to the
new clamav 0.90.3.

2007-06-03 21:59:51.388989500 tcpserver: status: 0/100
2007-06-03 22:04:27.781227500 tcpserver: status: 0/100
2007-06-03 22:06:14.848932500 tcpserver: status: 1/100
2007-06-03 22:06:14.848938500 tcpserver: pid 4399 from 167.206.4.199
2007-06-03 22:06:14.902173500 tcpserver: ok 4399
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::64785
2007-06-03 22:06:15.121824500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:06:15.192784500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:06:15.294420500 connect(): No such file or directory
2007-06-03 22:06:15.295600500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:06:15.308939500 tcpserver: end 4399 status 256
2007-06-03 22:06:15.308945500 tcpserver: status: 0/100
2007-06-03 22:11:41.211648500 tcpserver: status: 0/100
2007-06-03 22:12:17.737201500 tcpserver: status: 1/100
2007-06-03 22:12:17.737207500 tcpserver: pid 22314 from 167.206.4.199
2007-06-03 22:12:17.737210500 tcpserver: ok 22314
mail.mydomain.com:172.16.133.4:25 :167.206.4.199::34602
2007-06-03 22:12:17.763705500 CHKUSER accepted sender: from
<[EMAIL PROTECTED]::> remote
 rcpt <> : sender
accepted
2007-06-03 22:12:17.783909500 CHKUSER accepted rcpt: from
<[EMAIL PROTECTED]::> remote
 rcpt
<[EMAIL PROTECTED]> : found existing recipient
2007-06-03 22:12:17.807075500 connect(): No such file or directory
2007-06-03 22:12:17.808201500 qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<[EMAIL PROTECTED]>
RCPTTO:[EMAIL PROTECTED]
2007-06-03 22:12:17.826070500 tcpserver: end 22314 status 256
2007-06-03 22:12:17.826076500 tcpserver: status: 0/100

On 6/3/07, Erik A. Espinoza <[EMAIL PROTECTED]> wrote:

service qmail cdb

Erik

On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Well I've just been able to update with the ClamAV 0.90.3 package (on a
> CentOS 4.5 box) and all is well so far. could anyone tell me the command
> to run to get Simscan to see show the newer version in email headers?
>
> Thanks,
> Chas.
>
>
> -
>  QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] Clamav upgrade to 0.90.3

[Erik A. Espinoza]

service qmail cdb

Erik

On 6/3/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

Well I've just been able to update with the ClamAV 0.90.3 package (on a
CentOS 4.5 box) and all is well so far. could anyone tell me the command
to run to get Simscan to see show the newer version in email headers?

Thanks,
Chas.


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Staff Polesine Innovazione]

I'm working with QmailToaster Virtual Appliance (CentOS 4.4) and I had same 
problem. After reading the Thread and updated the packages with those in devel 
branch I solved the question! Thanks!
Byez
Davide

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Erik A. Espinoza]

It wasn't that hard. The hard work was done by the ClamAV group.

Erik

On 3/5/07, Peter Peltonen <[EMAIL PROTECTED]> wrote:

I'll mention at this thread too, that upgrading to
clamav-toaster-0.90.1-1.3.11 from the
devel site seemed to fix my problems.

Consider this long thread closed :) Thanks for ES and EE for working
so hard to get this issue
solved.

Cheers,
Peter

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

I'll mention at this thread too, that upgrading to
clamav-toaster-0.90.1-1.3.11 from the
devel site seemed to fix my problems.

Consider this long thread closed :) Thanks for ES and EE for working
so hard to get this issue
solved.

Cheers,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Regarding duplicated clamd log messages, the fix is to comment out "LogFile
stderr" in /etc/clamd.conf (and stop/start). EE will be releasing a fixed
toaster version very soon that does this and also removes the stderr patch.

I can't speak to the other issues.

A M wrote:
> Hi all,
> 
> I've watching clamd 0.90 for some time and found a few strange things:
> 
>  every line in the logs are duplicated (wonder if this has something to
> do with new clamd logging support for syslog and a log file?)
>  in 64bits system (Intel) clamd crashes quite often (haven't had that
> problem in AMD based systems)
>  sometimes after an freshclam automated update clamd gets a stale socket
> (setting "FixStaleSocket yes" in /etc/clamd.conf seems to fix it)
> 
> these are the things i've found hope it helps
> 
> AM
> [EMAIL PROTECTED] 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[A M]

Hi all,

I've watching clamd 0.90 for some time and found a few strange things:

every line in the logs are duplicated (wonder if this has something to do
with new clamd logging support for syslog and a log file?)
in 64bits system (Intel) clamd crashes quite often (haven't had that
problem in AMD based systems)
sometimes after an freshclam automated update clamd gets a stale socket
(setting "FixStaleSocket yes" in /etc/clamd.conf seems to fix it)

these are the things i've found hope it helps

AM
[EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

On 2/28/07, Philip Nix Guru <[EMAIL PROTECTED]> wrote:

Hi Peter
32645 is the only pid you should see

did you by any chance try to rebuild the rpm ?
Yes Pentium D, Core Duo and Xenon 5130 machines all with smp kernels

What's your distrib Peter (sorry if you already mentioned it :))


I have not seen such phantom PIDs before either...

I am running CentOS 3.8.

I haven't tried rebuilding the rpm. It was actually built on another
CentOS 3 box. I'll have to try that too.

We are resolving the issue at #QmailToaster channel at freenode irc
server with Eric at the moment. If you have time, join us?

Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip Nix Guru]

Hi Peter
32645 is the only pid you should see

did you by any chance try to rebuild the rpm ?
Yes Pentium D, Core Duo and Xenon 5130 machines all with smp kernels

What's your distrib Peter (sorry if you already mentioned it :))


Peter Peltonen wrote:

On 2/28/07, Peter Peltonen <[EMAIL PROTECTED]> wrote:

After enabling clamav for one domain and sending an email with
attachment to it I see:

 PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
17742 clamav25   0 47588  42M  1444 R50.1  4.2   1:00   1 clamd
20466 clamav15   0  1624 1624  1256 S 0.0  0.1   0:00   1 
freshclam

32645 clamav19   0 47588  42M  1444 S 0.0  4.2   0:06   1 clamd
17739 clamav20   0   572  572   356 S 0.0  0.0   0:00   1 
simscan
17741 clamav24   0  1152 1152   920 S 0.0  0.1   0:00   1 
clamdscan


I enabled the PPID field in top and saw that the parent for the 17742
process was 32624, which was:

# ps -ef |grep 32624
root 32624 32603  0 00:45 pts/200:00:00 supervise clamd
clamav   32645 32624  1 00:45 pts/200:21:01 /usr/sbin/clamd

Now I noticed that I had another "phantom" clamd process with PID
19309 (PPID being also
32624). Together they ate 100 % of my cpu. This also happened
yesterday: the phantom processes seem to work in pairs, probably due
to the hyperthreaded nature of my CPU.

When the other is killed the other disappears also:

I killed 19309 which apparently terminated 17742 too (at least it
disappeared from top) and I got my emails delivered. In double (which
also happened yesterday).

So supervise is doing something funny with clamav...

BTW Philip, are those qmailtoasters of yours
multiprocessor/hyperthreaded/multicore systems?

Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

On 2/28/07, Peter Peltonen <[EMAIL PROTECTED]> wrote:

After enabling clamav for one domain and sending an email with
attachment to it I see:

 PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
17742 clamav25   0 47588  42M  1444 R50.1  4.2   1:00   1 clamd
20466 clamav15   0  1624 1624  1256 S 0.0  0.1   0:00   1 freshclam
32645 clamav19   0 47588  42M  1444 S 0.0  4.2   0:06   1 clamd
17739 clamav20   0   572  572   356 S 0.0  0.0   0:00   1 simscan
17741 clamav24   0  1152 1152   920 S 0.0  0.1   0:00   1 clamdscan


I enabled the PPID field in top and saw that the parent for the 17742
process was 32624, which was:

# ps -ef |grep 32624
root 32624 32603  0 00:45 pts/200:00:00 supervise clamd
clamav   32645 32624  1 00:45 pts/200:21:01 /usr/sbin/clamd

Now I noticed that I had another "phantom" clamd process with PID
19309 (PPID being also
32624). Together they ate 100 % of my cpu. This also happened
yesterday: the phantom processes seem to work in pairs, probably due
to the hyperthreaded nature of my CPU.

When the other is killed the other disappears also:

I killed 19309 which apparently terminated 17742 too (at least it
disappeared from top) and I got my emails delivered. In double (which
also happened yesterday).

So supervise is doing something funny with clamav...

BTW Philip, are those qmailtoasters of yours
multiprocessor/hyperthreaded/multicore systems?

Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

Hi,

On 2/28/07, Philip <[EMAIL PROTECTED]> wrote:

Try launching a top -u clamav

you should have 1 clamd, 1 freshclam, a few spamc and multiple simscan
commands
clamd and freshclam should have the same PID while you monitor with top


This is what I get. I follow user clamav's processes in top and this
is what I see before
I have enabled any domains to be scanned with clamav:

 PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
20466 clamav15   0  1624 1624  1256 S 0.0  0.1   0:00   1 freshclam
32645 clamav25   0 23936  18M   844 S 0.0  1.8   0:02   0 clamd

After enabling clamav for one domain and sending an email with
attachment to it I see:

PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
17742 clamav25   0 47588  42M  1444 R50.1  4.2   1:00   1 clamd
20466 clamav15   0  1624 1624  1256 S 0.0  0.1   0:00   1 freshclam
32645 clamav19   0 47588  42M  1444 S 0.0  4.2   0:06   1 clamd
17739 clamav20   0   572  572   356 S 0.0  0.0   0:00   1 simscan
17741 clamav24   0  1152 1152   920 S 0.0  0.1   0:00   1 clamdscan

the first clamd process seen by top is new and cannot been seen with ps:

# ps -ef |grep clam
clamav   20466 1  0 Feb27 ?00:00:00 /usr/bin/freshclam -d
-p /var/run/clamav/freshclam.pid
root 32624 32603  0 00:45 pts/200:00:00 supervise clamd
clamav   32645 32624  0 00:45 pts/200:02:51 /usr/sbin/clamd
qmaill   32646 32625  0 00:45 pts/200:00:00 /usr/bin/multilog t
s100 n100 /var/log/qmail/clamd
clamav   17739 17737  0 18:07 pts/200:00:00 /var/qmail/bin/simscan
clamav   17741 17739  0 18:07 pts/200:00:00 clamdscan --stdout
root 18129  7112  0 18:10 pts/200:00:00 grep clam

As it's PID is +1 to the clamdscan process, one might think that it is
created by it?

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip]

Hi
The pid of your clamd (user clamav) shouldnt change and be listed as 
21988 (in your exemple)

as long as you dont restart it of course, and nothign else

I have fc5 and centos4.4 boxes
on very busy machines. I dont have those problems at all

Try launching a top -u clamav

you should have 1 clamd, 1 freshclam, a few spamc and multiple simscan 
commands

clamd and freshclam should have the same PID while you monitor with top
Let us know

Cheers
-Philip






Peter Peltonen wrote:

This is what me and Eric found out yesterday:

If we start my toaster with clamav scanning one domain and feed it a
message with an attachment, we get a "phantom" clamd processes eating
all of my p4 2,8GHz HT CPU. Example:

Top shows:
PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
24177 clamav25   0 25020  21M  1532 R47.9  2.1  11:03   1 clamd
22492 clamav25   0 25020  21M  1532 R45.3  2.1  20:54   1 clamd

Why are those processes "phantom"?`Because ps does not see them! ps 
-ef says:


root 20192 20172  0 Feb27 pts/200:00:00 supervise clamd
qmaill   20215 20193  0 Feb27 pts/200:00:00 /usr/bin/multilog t
s100 n100 /var/log/
clamav   21988 20192 99 Feb27 pts/200:47:07 /usr/sbin/clamd
clamav   22491 22489  0 Feb27 pts/200:00:00 clamdscan --stdout
clamav   24176 24174  0 Feb27 pts/200:00:00 clamdscan --stdout

As you can see, no clamd processes with PIDs 24177 or 22492. Their
PIDs are +1 to the
clamdscan processes, which seem to be stuck.

If we kill one of those clamdscan processes, then the phantom
processes seem to disappear
and the other clamdscan process disappears also. Messages get delivered.

Are other people having this problem seeing this phantom process
behaviour also? And what
kind of systems are you using?

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

This is what me and Eric found out yesterday:

If we start my toaster with clamav scanning one domain and feed it a
message with an attachment, we get a "phantom" clamd processes eating
all of my p4 2,8GHz HT CPU. Example:

Top shows:
PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
24177 clamav25   0 25020  21M  1532 R47.9  2.1  11:03   1 clamd
22492 clamav25   0 25020  21M  1532 R45.3  2.1  20:54   1 clamd

Why are those processes "phantom"?`Because ps does not see them! ps -ef says:

root 20192 20172  0 Feb27 pts/200:00:00 supervise clamd
qmaill   20215 20193  0 Feb27 pts/200:00:00 /usr/bin/multilog t
s100 n100 /var/log/
clamav   21988 20192 99 Feb27 pts/200:47:07 /usr/sbin/clamd
clamav   22491 22489  0 Feb27 pts/200:00:00 clamdscan --stdout
clamav   24176 24174  0 Feb27 pts/200:00:00 clamdscan --stdout

As you can see, no clamd processes with PIDs 24177 or 22492. Their
PIDs are +1 to the
clamdscan processes, which seem to be stuck.

If we kill one of those clamdscan processes, then the phantom
processes seem to disappear
and the other clamdscan process disappears also. Messages get delivered.

Are other people having this problem seeing this phantom process
behaviour also? And what
kind of systems are you using?

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Hey Peter,

How'd it go today? Ready to try adding more domains to clamav?
Let's chat at #QmailToaster.

Peter Peltonen wrote:
> After a restart last evening I've now kept my clamav running over the
> night scanning one
> domain only. Everything seems to be ok and no strange processes visible:
> 
> $ ps ax |grep clam
> 26991 pts/2S  0:00 supervise clamd
> 26999 pts/2S  0:00 /usr/bin/multilog t s100 n100
> /var/log/qmail/clamd
> 2933 pts/2S  0:09 /usr/sbin/clamd
> 18482 pts/12   S  0:00 grep clam
> 
> Regards,
> Peter
> 

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

After a restart last evening I've now kept my clamav running over the
night scanning one
domain only. Everything seems to be ok and no strange processes visible:

$ ps ax |grep clam
26991 pts/2S  0:00 supervise clamd
26999 pts/2S  0:00 /usr/bin/multilog t s100 n100
/var/log/qmail/clamd
2933 pts/2S  0:09 /usr/sbin/clamd
18482 pts/12   S  0:00 grep clam

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] clamav upgrade problem with supervise/lock

[Fernando Azevedo]

Hey Eric,
 
I guess that this mess with the conf file is justified with a previous post I 
made during the week-end or maybe last week: when I Upgraded to 0.90 with a rpm 
-Uvh it did not automatically remove the 0.88.7. I had manually de-install it 
with a rpm -e --nodeps...
 
It looks everything is OK now, though... but I'll keep a close eye on this for 
the next few days.
 
 
Fernando



De: Eric "Shubes" [mailto:[EMAIL PROTECTED]
Enviada: seg 26-02-2007 22:53
Para: qmailtoaster-list@qmailtoaster.com
Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock



Hey Fernando,

You're right. The clamd.conf.rpmsave would have been created when you
removed the old clamd. The clamd.conf.rpmnew would have been created by the
upgrade if there was already a clam.conf file. How you ended up with an
rpmnew and no clamd.conf, I'm not quite sure. I'd try using the rpmnew file,
and as per earlier post, comment out the "LogFile stderr" line. The stop and
start qmail again. supervise should start up clamd for you then.

Let us know how you make out. I'm thinking that with the relatively low
volume on that server you're not likely to have a problem.

Fernando Azevedo wrote:
> Hello Eric,
> 
> This thing has triggered for some other strange things...
> 
> I believe that clamav is not running at all in the machine I used for the log 
> bellow...
> 
> I've just sent an EICAR test for it, /var/log/qmail/clamav/current says 
> nothing... and oddly enough I get this line in /var/log/qmail/spamd/current: 
> 2007-02-26 22:22:20.303894500 [2326] info: spamd: clean message (-4.4/5.0) 
> for clamav:89 in 5.2 seconds, 992 bytes.
> 
> I think I was supposed to have something like 2007-02-26 22:18:16.326169500 
> /var/qmail/simscan/1172528296.321131.24114/msg.1172528296.321131.24114: 
> Eicar-Test-Signature FOUND
> 
> Also, /etc/clamd.conf has disappeared... instead I have 
> /etc/clamd.conf.rpmnew and /etc/clamd.conf.rpmsave... I guess my old config 
> file is the rpmsave one, but when I rename it to /etc/clamd.conf  clamav 
> refuses to start :(
> 
> This is a "test" server with a low message volume +/- 20,000/month.
> 
> In other production servers with 200,000+ messages/monhI have 
> clamav-toaster-0.88.7-1.3.7 running without any issues. I was in fact 
> preparing to upgrade clamav because I had noticed nothing in this machine.
> 
> I will however immediatelly check if this is not just a conf file problem and 
> I will report ASAP.
> 
> 
> Fernando
> 
> 
>
> ____________
>
> De: Eric "Shubes" [mailto:[EMAIL PROTECTED]
> Enviada: seg 26-02-2007 18:22
> Para: qmailtoaster-list@qmailtoaster.com
> Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock
>
>
>
> Hey FA,
>
> Are you seeing any duplicate messages in your clamd log?
> Is your volume of messages very high?
>
> Thanks.
>
> Fernando Azevedo wrote:
>> Hi list,
>>
>> Hope this is of help:
>>
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
>> error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, 
>> key ID 4f2a6fd2
>> autorespond-toaster-2.0.4-1.3.2
>> clamav-toaster-0.90-1.3.10
>> control-panel-toaster-0.5-1.3.3
>> courier-authlib-toaster-0.58-1.3.1
>> courier-imap-toaster-4.1.2-1.3.6
>> daemontools-toaster-0.76-1.3.2
>> ezmlm-cgi-toaster-0.53.324-1.3.2
>> ezmlm-toaster-0.53.324-1.3.2
>> isoqlog-toaster-2.1-1.3.2
>> libdomainkeys-toaster-0.68-1.3.2
>> libsrs2-toaster-1.0.18-1.3.2
>> maildrop-toaster-2.0.3-1.3.4
>> maildrop-toaster-devel-2.0.3-1.3.4
>> qmailadmin-toaster-1.2.9-1.3.3
>> qmailmrtg-toaster-4.2-1.3.2
>> qmail-pop3d-toaster-1.03-1.3.13
>> qmail-toaster-1.03-1.3.13
>> ripmime-toaster-1.4.0.6-1.3.2
>> simscan-toaster-1.3.1-1.3.4
>> spamassassin-toaster-3.1.7-1.3.6
>> squirrelmail-toaster-1.4.9a-1.3.5
>> ucspi-tcp-toaster-0.88-1.3.4
>> vpopmail-toaster-5.4.13-1.3.3
>> vqadmin-toaster-2.3.4-1.3.2
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]# uname -a
>> Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 
>> 2007 i686 i686 i386 GNU/Linux
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>>
>>
>> I'm not having any problem whatsoever. If you need any further info from my 
>> system, please let me know.
>>
>>
>> Best regards,
>> Fernando
>>
>>
>
>
> --
> -Eric 

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Hey Fernando,

You're right. The clamd.conf.rpmsave would have been created when you
removed the old clamd. The clamd.conf.rpmnew would have been created by the
upgrade if there was already a clam.conf file. How you ended up with an
rpmnew and no clamd.conf, I'm not quite sure. I'd try using the rpmnew file,
and as per earlier post, comment out the "LogFile stderr" line. The stop and
start qmail again. supervise should start up clamd for you then.

Let us know how you make out. I'm thinking that with the relatively low
volume on that server you're not likely to have a problem.

Fernando Azevedo wrote:
> Hello Eric,
>  
> This thing has triggered for some other strange things...
>  
> I believe that clamav is not running at all in the machine I used for the log 
> bellow...
>  
> I've just sent an EICAR test for it, /var/log/qmail/clamav/current says 
> nothing... and oddly enough I get this line in /var/log/qmail/spamd/current: 
> 2007-02-26 22:22:20.303894500 [2326] info: spamd: clean message (-4.4/5.0) 
> for clamav:89 in 5.2 seconds, 992 bytes.
>  
> I think I was supposed to have something like 2007-02-26 22:18:16.326169500 
> /var/qmail/simscan/1172528296.321131.24114/msg.1172528296.321131.24114: 
> Eicar-Test-Signature FOUND
>  
> Also, /etc/clamd.conf has disappeared... instead I have 
> /etc/clamd.conf.rpmnew and /etc/clamd.conf.rpmsave... I guess my old config 
> file is the rpmsave one, but when I rename it to /etc/clamd.conf  clamav 
> refuses to start :(
>  
> This is a "test" server with a low message volume +/- 20,000/month.
>  
> In other production servers with 200,000+ messages/monhI have 
> clamav-toaster-0.88.7-1.3.7 running without any issues. I was in fact 
> preparing to upgrade clamav because I had noticed nothing in this machine.
>  
> I will however immediatelly check if this is not just a conf file problem and 
> I will report ASAP.
>  
>  
> Fernando
>  
>  
> 
> ____________
> 
> De: Eric "Shubes" [mailto:[EMAIL PROTECTED]
> Enviada: seg 26-02-2007 18:22
> Para: qmailtoaster-list@qmailtoaster.com
> Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock
> 
> 
> 
> Hey FA,
> 
> Are you seeing any duplicate messages in your clamd log?
> Is your volume of messages very high?
> 
> Thanks.
> 
> Fernando Azevedo wrote:
>> Hi list,
>>
>> Hope this is of help:
>>
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
>> error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, 
>> key ID 4f2a6fd2
>> autorespond-toaster-2.0.4-1.3.2
>> clamav-toaster-0.90-1.3.10
>> control-panel-toaster-0.5-1.3.3
>> courier-authlib-toaster-0.58-1.3.1
>> courier-imap-toaster-4.1.2-1.3.6
>> daemontools-toaster-0.76-1.3.2
>> ezmlm-cgi-toaster-0.53.324-1.3.2
>> ezmlm-toaster-0.53.324-1.3.2
>> isoqlog-toaster-2.1-1.3.2
>> libdomainkeys-toaster-0.68-1.3.2
>> libsrs2-toaster-1.0.18-1.3.2
>> maildrop-toaster-2.0.3-1.3.4
>> maildrop-toaster-devel-2.0.3-1.3.4
>> qmailadmin-toaster-1.2.9-1.3.3
>> qmailmrtg-toaster-4.2-1.3.2
>> qmail-pop3d-toaster-1.03-1.3.13
>> qmail-toaster-1.03-1.3.13
>> ripmime-toaster-1.4.0.6-1.3.2
>> simscan-toaster-1.3.1-1.3.4
>> spamassassin-toaster-3.1.7-1.3.6
>> squirrelmail-toaster-1.4.9a-1.3.5
>> ucspi-tcp-toaster-0.88-1.3.4
>> vpopmail-toaster-5.4.13-1.3.3
>> vqadmin-toaster-2.3.4-1.3.2
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]# uname -a
>> Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 
>> 2007 i686 i686 i386 GNU/Linux
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>> [EMAIL PROTECTED] ~]#
>>
>>
>> I'm not having any problem whatsoever. If you need any further info from my 
>> system, please let me know.
>>
>>
>> Best regards,
>> Fernando
>>
>>
> 
> 
> --
> -Eric 'shubes'
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] clamav upgrade problem with supervise/lock

[Fernando Azevedo]

Hello Eric (and list),
 
After coorecting the conf file (as suspected) clamav is running without any 
problems: just got :2007-02-26 22:52:14.767787500 qmail-smtpd: qq hard reject 
(Your email was rejected because it contains the Eicar-Test-Signature virus): 
MAILFROM:<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > RCPTTO:[EMAIL 
PROTECTED]
 
So... everything appear normal now... :)
 
 



De: Fernando Azevedo [mailto:[EMAIL PROTECTED]
Enviada: seg 26-02-2007 22:40
Para: qmailtoaster-list@qmailtoaster.com
Assunto: RE: [qmailtoaster] clamav upgrade problem with supervise/lock


Hello Eric,
 
This thing has triggered for some other strange things...
 
I believe that clamav is not running at all in the machine I used for the log 
bellow...
 
I've just sent an EICAR test for it, /var/log/qmail/clamav/current says 
nothing... and oddly enough I get this line in /var/log/qmail/spamd/current: 
2007-02-26 22:22:20.303894500 [2326] info: spamd: clean message (-4.4/5.0) for 
clamav:89 in 5.2 seconds, 992 bytes.
 
I think I was supposed to have something like 2007-02-26 22:18:16.326169500 
/var/qmail/simscan/1172528296.321131.24114/msg.1172528296.321131.24114: 
Eicar-Test-Signature FOUND
 
Also, /etc/clamd.conf has disappeared... instead I have /etc/clamd.conf.rpmnew 
and /etc/clamd.conf.rpmsave... I guess my old config file is the rpmsave one, 
but when I rename it to /etc/clamd.conf  clamav refuses to start :(
 
This is a "test" server with a low message volume +/- 20,000/month.
 
In other production servers with 200,000+ messages/monhI have 
clamav-toaster-0.88.7-1.3.7 running without any issues. I was in fact preparing 
to upgrade clamav because I had noticed nothing in this machine.
 
I will however immediatelly check if this is not just a conf file problem and I 
will report ASAP.
 
 
Fernando
 
 



De: Eric "Shubes" [mailto:[EMAIL PROTECTED]
Enviada: seg 26-02-2007 18:22
Para: qmailtoaster-list@qmailtoaster.com
Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock



Hey FA,

Are you seeing any duplicate messages in your clamd log?
Is your volume of messages very high?

Thanks.

Fernando Azevedo wrote:
> Hi list,
> 
> Hope this is of help:
> 
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
> error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, 
> key ID 4f2a6fd2
> autorespond-toaster-2.0.4-1.3.2
> clamav-toaster-0.90-1.3.10
> control-panel-toaster-0.5-1.3.3
> courier-authlib-toaster-0.58-1.3.1
> courier-imap-toaster-4.1.2-1.3.6
> daemontools-toaster-0.76-1.3.2
> ezmlm-cgi-toaster-0.53.324-1.3.2
> ezmlm-toaster-0.53.324-1.3.2
> isoqlog-toaster-2.1-1.3.2
> libdomainkeys-toaster-0.68-1.3.2
> libsrs2-toaster-1.0.18-1.3.2
> maildrop-toaster-2.0.3-1.3.4
> maildrop-toaster-devel-2.0.3-1.3.4
> qmailadmin-toaster-1.2.9-1.3.3
> qmailmrtg-toaster-4.2-1.3.2
> qmail-pop3d-toaster-1.03-1.3.13
> qmail-toaster-1.03-1.3.13
> ripmime-toaster-1.4.0.6-1.3.2
> simscan-toaster-1.3.1-1.3.4
> spamassassin-toaster-3.1.7-1.3.6
> squirrelmail-toaster-1.4.9a-1.3.5
> ucspi-tcp-toaster-0.88-1.3.4
> vpopmail-toaster-5.4.13-1.3.3
> vqadmin-toaster-2.3.4-1.3.2
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]# uname -a
> Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 
> 2007 i686 i686 i386 GNU/Linux
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> 
> 
> I'm not having any problem whatsoever. If you need any further info from my 
> system, please let me know.
> 
> 
> Best regards,
> Fernando
> 
> 


--
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org <http://www.vr.org/> >
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



<>-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Good news: I found out why messages are being duplicated.

The new output.c module in clamav has a new logg_foreground setting (enabled
in the toaster) which sends log output to stdout. The toaster used to use a
patched capability (still in there) which allows for specifying "stderr" as
the log file name, which instead of going to a file goes to stderr. Thus,
messages are going via both stdout and stderr to the log. Changing
/etc/clamav.conf to comment out the "LogFile stderr" line fixes the
duplication in the log. I've filed a bug report.

Bad news: I still don't know why clamd is hanging on occasion, as this is
unrelated to duplicate log messages. I have not been able to recreate this
on my machine(s), so I'll work with Peter (and anyone else who has this
problem) tomorrow on this to see if we can't get a resolution.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] clamav upgrade problem with supervise/lock

[Fernando Azevedo]

Hello Eric,
 
This thing has triggered for some other strange things...
 
I believe that clamav is not running at all in the machine I used for the log 
bellow...
 
I've just sent an EICAR test for it, /var/log/qmail/clamav/current says 
nothing... and oddly enough I get this line in /var/log/qmail/spamd/current: 
2007-02-26 22:22:20.303894500 [2326] info: spamd: clean message (-4.4/5.0) for 
clamav:89 in 5.2 seconds, 992 bytes.
 
I think I was supposed to have something like 2007-02-26 22:18:16.326169500 
/var/qmail/simscan/1172528296.321131.24114/msg.1172528296.321131.24114: 
Eicar-Test-Signature FOUND
 
Also, /etc/clamd.conf has disappeared... instead I have /etc/clamd.conf.rpmnew 
and /etc/clamd.conf.rpmsave... I guess my old config file is the rpmsave one, 
but when I rename it to /etc/clamd.conf  clamav refuses to start :(
 
This is a "test" server with a low message volume +/- 20,000/month.
 
In other production servers with 200,000+ messages/monhI have 
clamav-toaster-0.88.7-1.3.7 running without any issues. I was in fact preparing 
to upgrade clamav because I had noticed nothing in this machine.
 
I will however immediatelly check if this is not just a conf file problem and I 
will report ASAP.
 
 
Fernando
 
 



De: Eric "Shubes" [mailto:[EMAIL PROTECTED]
Enviada: seg 26-02-2007 18:22
Para: qmailtoaster-list@qmailtoaster.com
Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock



Hey FA,

Are you seeing any duplicate messages in your clamd log?
Is your volume of messages very high?

Thanks.

Fernando Azevedo wrote:
> Hi list,
> 
> Hope this is of help:
> 
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
> error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, 
> key ID 4f2a6fd2
> autorespond-toaster-2.0.4-1.3.2
> clamav-toaster-0.90-1.3.10
> control-panel-toaster-0.5-1.3.3
> courier-authlib-toaster-0.58-1.3.1
> courier-imap-toaster-4.1.2-1.3.6
> daemontools-toaster-0.76-1.3.2
> ezmlm-cgi-toaster-0.53.324-1.3.2
> ezmlm-toaster-0.53.324-1.3.2
> isoqlog-toaster-2.1-1.3.2
> libdomainkeys-toaster-0.68-1.3.2
> libsrs2-toaster-1.0.18-1.3.2
> maildrop-toaster-2.0.3-1.3.4
> maildrop-toaster-devel-2.0.3-1.3.4
> qmailadmin-toaster-1.2.9-1.3.3
> qmailmrtg-toaster-4.2-1.3.2
> qmail-pop3d-toaster-1.03-1.3.13
> qmail-toaster-1.03-1.3.13
> ripmime-toaster-1.4.0.6-1.3.2
> simscan-toaster-1.3.1-1.3.4
> spamassassin-toaster-3.1.7-1.3.6
> squirrelmail-toaster-1.4.9a-1.3.5
> ucspi-tcp-toaster-0.88-1.3.4
> vpopmail-toaster-5.4.13-1.3.3
> vqadmin-toaster-2.3.4-1.3.2
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]# uname -a
> Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 
> 2007 i686 i686 i386 GNU/Linux
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> [EMAIL PROTECTED] ~]#
> 
> 
> I'm not having any problem whatsoever. If you need any further info from my 
> system, please let me know.
> 
> 
> Best regards,
> Fernando
> 
> 


--
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org <http://www.vr.org/> >
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



<>-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Thanks, slamp.

Me too. I'd love to hear some suggestions, even if they're just SWAGs!

slamp slamp wrote:
> I have clamav-toaster-0.90-1.3.10 with no problems either. this was an
> upgrade from the rc. but i do see duplicates in my log. the oldest i
> have for logs are from 2/14. i am curious as to why the logs are duplicated.
> 

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[slamp slamp]

I have clamav-toaster-0.90-1.3.10 with no problems either. this was an
upgrade from the rc. but i do see duplicates in my log. the oldest i have
for logs are from 2/14. i am curious as to why the logs are duplicated.

On 2/26/07, Philip Nix Guru <[EMAIL PROTECTED]> wrote:


Eric "Shubes" wrote:
> Philip Nix Guru wrote:
>
>> Eric "Shubes" wrote:
>>
>>> Philip Nix Guru wrote:
>>>
>>>
 Eric "Shubes" wrote:


> Philip Nix Guru wrote:
>
>
>
>> Eric "Shubes" wrote:
>>
>>
>>> We're trying to get a handle on this problem. If anyone is using
>>> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem,
will
>>> you
>>> kindly reply and let us know?
>>>
>>> Thanks.
>>>
>>>
>>>
>> Hello
>> I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
>> 2 x FC5 and 1 x Centos 4.4
>> No problem ..
>>
>> But I am not using default simscan,  I added configure option
>> --enable-dropmsg
>> which shouldnt change anything to clamd's behavior
>>
>> -P
>>
>>
>>
> Hey PNG,
>
> I've got a few questions for you.
>
> .) Are you seeing duplicated messages in clamd log?
> .) Were these upgrades or new installs?
>
> If upgrades,
> .) had you upgraded to RC version(s) first?
> .) what version did you upgrade from?
> .) manual upgrade or qtp-newmodel?
> .) any other packages upgraded at the same time?
>
>
>
 Hello

 Yes I see  duplicated messages in clamd log

 It was an upgrade

 I had clamav-toaster-0.90rc2-1.3.8.src.rpm
 then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
 then to clamav-toaster-0.90-1.3.10.src.rpm

 manual upgrade

 No other packages upgraded at the same time



>>> Thanks, PNG.
>>>
>>> Can you tell with which version the duplicated messages began? (by
>>> looking
>>> through the logs?)
>>>
>>>
>>>
>> Hey Eric
>> I did check the logs, unfortunatly those are busy servers , logs from
>> earlier versions arent accessible anymore (I dont backup clamd logs)
>> sorry cant help much there ...
>>
>>
>
> That's ok. Just curious about that.
>
> It's starting to look like the problem might only rear it's head when
there
> are concurrent scans happening. Can you tell if you've had two messages
> being scanned at once?
>
>
Checked a few things,
never had 2 messages scanned at once ...  as far as I know :)
will check source later and upgrade another server I have (not a toaster
but running clamav 0.88.x)


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip Nix Guru]

Eric "Shubes" wrote:

Philip Nix Guru wrote:
  

Eric "Shubes" wrote:


Philip Nix Guru wrote:
 
  

Eric "Shubes" wrote:
   


Philip Nix Guru wrote:
 
 
  

Eric "Shubes" wrote:
  


We're trying to get a handle on this problem. If anyone is using
clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will
you
kindly reply and let us know?

Thanks.

  
  

Hello
I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
2 x FC5 and 1 x Centos 4.4
No problem ..

But I am not using default simscan,  I added configure option
--enable-dropmsg
which shouldnt change anything to clamd's behavior

-P




Hey PNG,

I've got a few questions for you.

.) Are you seeing duplicated messages in clamd log?
.) Were these upgrades or new installs?

If upgrades,
.) had you upgraded to RC version(s) first?
.) what version did you upgrade from?
.) manual upgrade or qtp-newmodel?
.) any other packages upgraded at the same time?


  

Hello

Yes I see  duplicated messages in clamd log

It was an upgrade

I had clamav-toaster-0.90rc2-1.3.8.src.rpm
then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
then to clamav-toaster-0.90-1.3.10.src.rpm

manual upgrade

No other packages upgraded at the same time




Thanks, PNG.

Can you tell with which version the duplicated messages began? (by
looking
through the logs?)

  
  

Hey Eric
I did check the logs, unfortunatly those are busy servers , logs from
earlier versions arent accessible anymore (I dont backup clamd logs)
sorry cant help much there ...




That's ok. Just curious about that.

It's starting to look like the problem might only rear it's head when there
are concurrent scans happening. Can you tell if you've had two messages
being scanned at once?

  

Checked a few things,
never had 2 messages scanned at once ...  as far as I know :)
will check source later and upgrade another server I have (not a toaster 
but running clamav 0.88.x)



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

That would be a "yes". ;)

Glenn Remstedt wrote:
> a output from my /var/log/qmail/clamd/current
> 
> .
> .
> .
> 
> @400045e2d66333c0c974 
> /var/qmail/simscan/1172493913.298866.2941/textfile1:OK
> @400045e2fccb37f785b4 No stats for Database check - forcing reload
> @400045e2fccb37f80e6c No stats for Database check - forcing reload
> @400045e2fccb37f8163c Reading databases from /usr/share/clamav
> @400045e2fccb37f81e0c Reading databases from /usr/share/clamav
> @400045e2fccb3849f344 
> /var/qmail/simscan/1172503745.861771.5086/textfile0:OK
> @400045e2fccb384ab2ac 
> /var/qmail/simscan/1172503745.861771.5086/textfile0:OK
> @400045e2fccb38a86adc 
> /var/qmail/simscan/1172503745.861771.5086/msg.1172503745.861771.5086:OK
> @400045e2fccb38a91aa4 
> /var/qmail/simscan/1172503745.861771.5086/msg.1172503745.861771.5086:OK
> @400045e2fccb38deb54c 
> /var/qmail/simscan/1172503745.861771.5086/addr.1172503745.861771.5086:OK
> @400045e2fccb38df3e04 
> /var/qmail/simscan/1172503745.861771.5086/addr.1172503745.861771.5086:OK
> @400045e2fccd2d0e37c4 Database correctly reloaded (94742 signatures)
> @400045e2fccd2d0f1284 Database correctly reloaded (94742 signatures)
> @400045e31ac42374c64c +++ Started at Mon Feb 26 18:36:58 2007
> @400045e31ac42374d204 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
> CPU: i386)
> @400045e31ac42374d9d4 Log file size limited to 1048576 bytes.
> @400045e31ac42374e1a4 Reading databases from /usr/share/clamav
> @400045e31ac705c2ad94 Loaded 94742 signatures.
> @400045e31ac706299554 Unix socket file /tmp/clamd
> @400045e31ac7062a163c Unix socket file /tmp/clamd
> @400045e31ac7062a1a24 Setting connection queue length to 15
> @400045e31ac7062a5c8c Setting connection queue length to 15
> @400045e31ac7062a9ef4 Listening daemon: PID: 7040
> @400045e31ac7062aa6c4 Listening daemon: PID: 7040
> @400045e31ac7062b086c Archive: Archived file size limit set to
> 10485760 bytes.
> @400045e31ac7062b103c Archive: Archived file size limit set to
> 10485760 bytes.
> @400045e31ac7062b180c Archive: Recursion level limit set to 8.
> @400045e31ac7062b568c Archive: Recursion level limit set to 8.
> @400045e31ac7062b5e5c Archive: Files limit set to 1000.
> @400045e31ac7062b6244 Archive: Files limit set to 1000.
> @400045e31ac7062ba0c4 Archive: Compression ratio limit set to 250.
> @400045e31ac7062ba894 Archive: Compression ratio limit set to 250.
> @400045e31ac7062bb064 Archive support enabled.
> @400045e31ac7062beafc Archive support enabled.
> @400045e31ac7062bf2cc Algorithmic detection enabled.
> @400045e31ac7062bf6b4 Algorithmic detection enabled.
> @400045e31ac7062c3534 Portable Executable support enabled.
> @400045e31ac7062c391c Portable Executable support enabled.
> @400045e31ac7062c40ec ELF support enabled.
> .
> .
> .
> 
> On Mon, 2007-02-26 at 10:50 -0700, Eric "Shubes" wrote:
>> Thanks Glenn.
>>
>> Any duplicated messages in the clamd log?
>>
>> Glenn Remstedt wrote:
>>> hi,
>>>
>>> I've the clamav-toaster-0.90-1.3.10 just installed yesterday on a FC5,
>>> do not see any problem. But do let me know what you need to see - any
>>> log-files ...?
>>>
>>> G. 
>>>
>>> On Mon, 2007-02-26 at 10:01 -0700, Eric "Shubes" wrote:
 We're trying to get a handle on this problem. If anyone is using
 clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
 kindly reply and let us know?

 Thanks.



-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Hey FA,

Are you seeing any duplicate messages in your clamd log?
Is your volume of messages very high?

Thanks.

Fernando Azevedo wrote:
> Hi list,
>  
> Hope this is of help:
>  
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
> error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, 
> key ID 4f2a6fd2
> autorespond-toaster-2.0.4-1.3.2
> clamav-toaster-0.90-1.3.10
> control-panel-toaster-0.5-1.3.3
> courier-authlib-toaster-0.58-1.3.1
> courier-imap-toaster-4.1.2-1.3.6
> daemontools-toaster-0.76-1.3.2
> ezmlm-cgi-toaster-0.53.324-1.3.2
> ezmlm-toaster-0.53.324-1.3.2
> isoqlog-toaster-2.1-1.3.2
> libdomainkeys-toaster-0.68-1.3.2
> libsrs2-toaster-1.0.18-1.3.2
> maildrop-toaster-2.0.3-1.3.4
> maildrop-toaster-devel-2.0.3-1.3.4
> qmailadmin-toaster-1.2.9-1.3.3
> qmailmrtg-toaster-4.2-1.3.2
> qmail-pop3d-toaster-1.03-1.3.13
> qmail-toaster-1.03-1.3.13
> ripmime-toaster-1.4.0.6-1.3.2
> simscan-toaster-1.3.1-1.3.4
> spamassassin-toaster-3.1.7-1.3.6
> squirrelmail-toaster-1.4.9a-1.3.5
> ucspi-tcp-toaster-0.88-1.3.4
> vpopmail-toaster-5.4.13-1.3.3
> vqadmin-toaster-2.3.4-1.3.2
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# uname -a
> Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 
> 2007 i686 i686 i386 GNU/Linux
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# 
> [EMAIL PROTECTED] ~]# 
>  
>  
> I'm not having any problem whatsoever. If you need any further info from my 
> system, please let me know.
>  
>  
> Best regards,
> Fernando
>  
>  


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Philip Nix Guru wrote:
> Eric "Shubes" wrote:
>> Philip Nix Guru wrote:
>>  
>>> Eric "Shubes" wrote:
>>>
 Philip Nix Guru wrote:
  
  
> Eric "Shubes" wrote:
>   
>> We're trying to get a handle on this problem. If anyone is using
>> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will
>> you
>> kindly reply and let us know?
>>
>> Thanks.
>>
>>   
> Hello
> I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
> 2 x FC5 and 1 x Centos 4.4
> No problem ..
>
> But I am not using default simscan,  I added configure option
> --enable-dropmsg
> which shouldnt change anything to clamd's behavior
>
> -P
>
> 
 Hey PNG,

 I've got a few questions for you.

 .) Are you seeing duplicated messages in clamd log?
 .) Were these upgrades or new installs?

 If upgrades,
 .) had you upgraded to RC version(s) first?
 .) what version did you upgrade from?
 .) manual upgrade or qtp-newmodel?
 .) any other packages upgraded at the same time?

 
>>> Hello
>>>
>>> Yes I see  duplicated messages in clamd log
>>>
>>> It was an upgrade
>>>
>>> I had clamav-toaster-0.90rc2-1.3.8.src.rpm
>>> then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
>>> then to clamav-toaster-0.90-1.3.10.src.rpm
>>>
>>> manual upgrade
>>>
>>> No other packages upgraded at the same time
>>>
>>> 
>>
>> Thanks, PNG.
>>
>> Can you tell with which version the duplicated messages began? (by
>> looking
>> through the logs?)
>>
>>   
> Hey Eric
> I did check the logs, unfortunatly those are busy servers , logs from
> earlier versions arent accessible anymore (I dont backup clamd logs)
> sorry cant help much there ...
> 

That's ok. Just curious about that.

It's starting to look like the problem might only rear it's head when there
are concurrent scans happening. Can you tell if you've had two messages
being scanned at once?

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] clamav upgrade problem with supervise/lock

[Fernando Azevedo]

Hi list,
 
Hope this is of help:
 
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# rpm -qa | grep toaster | sort
error: rpmdbNextIterator: skipping h#1503 Header V3 DSA signature: BAD, key 
ID 4f2a6fd2
autorespond-toaster-2.0.4-1.3.2
clamav-toaster-0.90-1.3.10
control-panel-toaster-0.5-1.3.3
courier-authlib-toaster-0.58-1.3.1
courier-imap-toaster-4.1.2-1.3.6
daemontools-toaster-0.76-1.3.2
ezmlm-cgi-toaster-0.53.324-1.3.2
ezmlm-toaster-0.53.324-1.3.2
isoqlog-toaster-2.1-1.3.2
libdomainkeys-toaster-0.68-1.3.2
libsrs2-toaster-1.0.18-1.3.2
maildrop-toaster-2.0.3-1.3.4
maildrop-toaster-devel-2.0.3-1.3.4
qmailadmin-toaster-1.2.9-1.3.3
qmailmrtg-toaster-4.2-1.3.2
qmail-pop3d-toaster-1.03-1.3.13
qmail-toaster-1.03-1.3.13
ripmime-toaster-1.4.0.6-1.3.2
simscan-toaster-1.3.1-1.3.4
spamassassin-toaster-3.1.7-1.3.6
squirrelmail-toaster-1.4.9a-1.3.5
ucspi-tcp-toaster-0.88-1.3.4
vpopmail-toaster-5.4.13-1.3.3
vqadmin-toaster-2.3.4-1.3.2
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# uname -a
Linux kalimero.netlandia.net 2.6.19-1.2288.fc5 #1 Sat Feb 10 14:52:17 EST 2007 
i686 i686 i386 GNU/Linux
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# 
[EMAIL PROTECTED] ~]# 
 
 
I'm not having any problem whatsoever. If you need any further info from my 
system, please let me know.
 
 
Best regards,
Fernando
 
 



De: Philip Nix Guru [mailto:[EMAIL PROTECTED]
Enviada: seg 26-02-2007 17:54
Para: qmailtoaster-list@qmailtoaster.com
Assunto: Re: [qmailtoaster] clamav upgrade problem with supervise/lock



Eric "Shubes" wrote:
> Philip Nix Guru wrote:
>  
>> Eric "Shubes" wrote:
>>
>>> Philip Nix Guru wrote:
>>> 
>>>  
>>>> Eric "Shubes" wrote:
>>>>   
>>>>
>>>>> We're trying to get a handle on this problem. If anyone is using
>>>>> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will
>>>>> you
>>>>> kindly reply and let us know?
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>>>>>  
>>>> Hello
>>>> I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
>>>> 2 x FC5 and 1 x Centos 4.4
>>>> No problem ..
>>>>
>>>> But I am not using default simscan,  I added configure option
>>>> --enable-dropmsg
>>>> which shouldnt change anything to clamd's behavior
>>>>
>>>> -P
>>>>
>>>>
>>>>
>>> Hey PNG,
>>>
>>> I've got a few questions for you.
>>>
>>> .) Are you seeing duplicated messages in clamd log?
>>> .) Were these upgrades or new installs?
>>>
>>> If upgrades,
>>> .) had you upgraded to RC version(s) first?
>>> .) what version did you upgrade from?
>>> .) manual upgrade or qtp-newmodel?
>>> .) any other packages upgraded at the same time?
>>>
>>>  
>>>  
>> Hello
>>
>> Yes I see  duplicated messages in clamd log
>>
>> It was an upgrade
>>
>> I had clamav-toaster-0.90rc2-1.3.8.src.rpm
>> then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
>> then to clamav-toaster-0.90-1.3.10.src.rpm
>>
>> manual upgrade
>>
>> No other packages upgraded at the same time
>>
>>
>
> Thanks, PNG.
>
> Can you tell with which version the duplicated messages began? (by looking
> through the logs?)
>
>  
Hey Eric
I did check the logs, unfortunatly those are busy servers , logs from
earlier versions arent accessible anymore (I dont backup clamd logs)
sorry cant help much there ...


-
 QmailToaster hosted by: VR Hosted <http://www.vr.org <http://www.vr.org/> >
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



<>-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Glenn Remstedt]

a output from my /var/log/qmail/clamd/current

.
.
.

@400045e2d66333c0c974 /var/qmail/simscan/1172493913.298866.2941/textfile1:OK
@400045e2fccb37f785b4 No stats for Database check - forcing reload
@400045e2fccb37f80e6c No stats for Database check - forcing reload
@400045e2fccb37f8163c Reading databases from /usr/share/clamav
@400045e2fccb37f81e0c Reading databases from /usr/share/clamav
@400045e2fccb3849f344 /var/qmail/simscan/1172503745.861771.5086/textfile0:OK
@400045e2fccb384ab2ac /var/qmail/simscan/1172503745.861771.5086/textfile0:OK
@400045e2fccb38a86adc 
/var/qmail/simscan/1172503745.861771.5086/msg.1172503745.861771.5086:OK
@400045e2fccb38a91aa4 
/var/qmail/simscan/1172503745.861771.5086/msg.1172503745.861771.5086:OK
@400045e2fccb38deb54c 
/var/qmail/simscan/1172503745.861771.5086/addr.1172503745.861771.5086:OK
@400045e2fccb38df3e04 
/var/qmail/simscan/1172503745.861771.5086/addr.1172503745.861771.5086:OK
@400045e2fccd2d0e37c4 Database correctly reloaded (94742 signatures)
@400045e2fccd2d0f1284 Database correctly reloaded (94742 signatures)
@400045e31ac42374c64c +++ Started at Mon Feb 26 18:36:58 2007
@400045e31ac42374d204 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
CPU: i386)
@400045e31ac42374d9d4 Log file size limited to 1048576 bytes.
@400045e31ac42374e1a4 Reading databases from /usr/share/clamav
@400045e31ac705c2ad94 Loaded 94742 signatures.
@400045e31ac706299554 Unix socket file /tmp/clamd
@400045e31ac7062a163c Unix socket file /tmp/clamd
@400045e31ac7062a1a24 Setting connection queue length to 15
@400045e31ac7062a5c8c Setting connection queue length to 15
@400045e31ac7062a9ef4 Listening daemon: PID: 7040
@400045e31ac7062aa6c4 Listening daemon: PID: 7040
@400045e31ac7062b086c Archive: Archived file size limit set to
10485760 bytes.
@400045e31ac7062b103c Archive: Archived file size limit set to
10485760 bytes.
@400045e31ac7062b180c Archive: Recursion level limit set to 8.
@400045e31ac7062b568c Archive: Recursion level limit set to 8.
@400045e31ac7062b5e5c Archive: Files limit set to 1000.
@400045e31ac7062b6244 Archive: Files limit set to 1000.
@400045e31ac7062ba0c4 Archive: Compression ratio limit set to 250.
@400045e31ac7062ba894 Archive: Compression ratio limit set to 250.
@400045e31ac7062bb064 Archive support enabled.
@400045e31ac7062beafc Archive support enabled.
@400045e31ac7062bf2cc Algorithmic detection enabled.
@400045e31ac7062bf6b4 Algorithmic detection enabled.
@400045e31ac7062c3534 Portable Executable support enabled.
@400045e31ac7062c391c Portable Executable support enabled.
@400045e31ac7062c40ec ELF support enabled.
.
.
.

On Mon, 2007-02-26 at 10:50 -0700, Eric "Shubes" wrote:
> Thanks Glenn.
> 
> Any duplicated messages in the clamd log?
> 
> Glenn Remstedt wrote:
> > hi,
> > 
> > I've the clamav-toaster-0.90-1.3.10 just installed yesterday on a FC5,
> > do not see any problem. But do let me know what you need to see - any
> > log-files ...?
> > 
> > G. 
> > 
> > On Mon, 2007-02-26 at 10:01 -0700, Eric "Shubes" wrote:
> >> We're trying to get a handle on this problem. If anyone is using
> >> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
> >> kindly reply and let us know?
> >>
> >> Thanks.
> >>
> 
> 


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip Nix Guru]

Eric "Shubes" wrote:

Philip Nix Guru wrote:
  

Eric "Shubes" wrote:


Philip Nix Guru wrote:
 
  

Eric "Shubes" wrote:
   


We're trying to get a handle on this problem. If anyone is using
clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will
you
kindly reply and let us know?

Thanks.


  

Hello
I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
2 x FC5 and 1 x Centos 4.4
No problem ..

But I am not using default simscan,  I added configure option
--enable-dropmsg
which shouldnt change anything to clamd's behavior

-P




Hey PNG,

I've got a few questions for you.

.) Are you seeing duplicated messages in clamd log?
.) Were these upgrades or new installs?

If upgrades,
.) had you upgraded to RC version(s) first?
.) what version did you upgrade from?
.) manual upgrade or qtp-newmodel?
.) any other packages upgraded at the same time?

  
  

Hello

Yes I see  duplicated messages in clamd log

It was an upgrade

I had clamav-toaster-0.90rc2-1.3.8.src.rpm
then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
then to clamav-toaster-0.90-1.3.10.src.rpm

manual upgrade

No other packages upgraded at the same time




Thanks, PNG.

Can you tell with which version the duplicated messages began? (by looking
through the logs?)

  

Hey Eric
I did check the logs, unfortunatly those are busy servers , logs from 
earlier versions arent accessible anymore (I dont backup clamd logs)

sorry cant help much there ...


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Thanks Glenn.

Any duplicated messages in the clamd log?

Glenn Remstedt wrote:
> hi,
> 
> I've the clamav-toaster-0.90-1.3.10 just installed yesterday on a FC5,
> do not see any problem. But do let me know what you need to see - any
> log-files ...?
> 
> G. 
> 
> On Mon, 2007-02-26 at 10:01 -0700, Eric "Shubes" wrote:
>> We're trying to get a handle on this problem. If anyone is using
>> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
>> kindly reply and let us know?
>>
>> Thanks.
>>


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Glenn Remstedt]

hi,

I've the clamav-toaster-0.90-1.3.10 just installed yesterday on a FC5,
do not see any problem. But do let me know what you need to see - any
log-files ...?

G. 

On Mon, 2007-02-26 at 10:01 -0700, Eric "Shubes" wrote:
> We're trying to get a handle on this problem. If anyone is using
> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
> kindly reply and let us know?
> 
> Thanks.
> 


-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Philip Nix Guru wrote:
> Eric "Shubes" wrote:
>> Philip Nix Guru wrote:
>>  
>>> Eric "Shubes" wrote:
>>>
 We're trying to get a handle on this problem. If anyone is using
 clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will
 you
 kindly reply and let us know?

 Thanks.

 
>>> Hello
>>> I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
>>> 2 x FC5 and 1 x Centos 4.4
>>> No problem ..
>>>
>>> But I am not using default simscan,  I added configure option
>>> --enable-dropmsg
>>> which shouldnt change anything to clamd's behavior
>>>
>>> -P
>>>
>>> 
>>
>> Hey PNG,
>>
>> I've got a few questions for you.
>>
>> .) Are you seeing duplicated messages in clamd log?
>> .) Were these upgrades or new installs?
>>
>> If upgrades,
>> .) had you upgraded to RC version(s) first?
>> .) what version did you upgrade from?
>> .) manual upgrade or qtp-newmodel?
>> .) any other packages upgraded at the same time?
>>
>>   
> Hello
> 
> Yes I see  duplicated messages in clamd log
> 
> It was an upgrade
> 
> I had clamav-toaster-0.90rc2-1.3.8.src.rpm
> then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
> then to clamav-toaster-0.90-1.3.10.src.rpm
> 
> manual upgrade
> 
> No other packages upgraded at the same time
> 

Thanks, PNG.

Can you tell with which version the duplicated messages began? (by looking
through the logs?)

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip Nix Guru]

Eric "Shubes" wrote:

Philip Nix Guru wrote:
  

Eric "Shubes" wrote:


We're trying to get a handle on this problem. If anyone is using
clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
kindly reply and let us know?

Thanks.

  
  

Hello
I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
2 x FC5 and 1 x Centos 4.4
No problem ..

But I am not using default simscan,  I added configure option
--enable-dropmsg
which shouldnt change anything to clamd's behavior

-P




Hey PNG,

I've got a few questions for you.

.) Are you seeing duplicated messages in clamd log?
.) Were these upgrades or new installs?

If upgrades,
.) had you upgraded to RC version(s) first?
.) what version did you upgrade from?
.) manual upgrade or qtp-newmodel?
.) any other packages upgraded at the same time?

  

Hello

Yes I see  duplicated messages in clamd log

It was an upgrade

I had clamav-toaster-0.90rc2-1.3.8.src.rpm
then upgraded to clamav-toaster-0.90rc3-1.3.9.src.rpm
then to clamav-toaster-0.90-1.3.10.src.rpm

manual upgrade

No other packages upgraded at the same time


-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Philip Nix Guru wrote:
> Eric "Shubes" wrote:
>> We're trying to get a handle on this problem. If anyone is using
>> clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
>> kindly reply and let us know?
>>
>> Thanks.
>>
>>   
> Hello
> I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
> 2 x FC5 and 1 x Centos 4.4
> No problem ..
> 
> But I am not using default simscan,  I added configure option
> --enable-dropmsg
> which shouldnt change anything to clamd's behavior
> 
> -P
> 

Hey PNG,

I've got a few questions for you.

.) Are you seeing duplicated messages in clamd log?
.) Were these upgrades or new installs?

If upgrades,
.) had you upgraded to RC version(s) first?
.) what version did you upgrade from?
.) manual upgrade or qtp-newmodel?
.) any other packages upgraded at the same time?

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Philip Nix Guru]

Eric "Shubes" wrote:

We're trying to get a handle on this problem. If anyone is using
clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
kindly reply and let us know?

Thanks.

  

Hello
I am using  clamav-toaster-0.90-1.3.10 on 3 diff systems
2 x FC5 and 1 x Centos 4.4
No problem ..

But I am not using default simscan,  I added configure option 
--enable-dropmsg

which shouldnt change anything to clamd's behavior

-P



-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

We're trying to get a handle on this problem. If anyone is using
clamav-toaster-0.90-1.3.10 and is *not* experiencing a problem, will you
kindly reply and let us know?

Thanks.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Peter Peltonen wrote:
> On 2/26/07, Eric Shubes <[EMAIL PROTECTED]> wrote:
>> Any news on your situation? Can you tell if the scans that hung up were
>> incoming or outgoing?
> 
> I have no idea. I can switch my clamd back on, so we can find out. But
> how do I get more information about the scans that are hanging?
> 
> Regards,
> Peter
> 

I don't know at this point. We'll need to narrow things down.

Anyone who is having this clamav problem with the 0.90 release, please hop
on the #QmailToaster channel at FreeNode IRC so we can communicate more timely.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Peter Peltonen wrote:
> BTW: Maybe `service qmail restart` should sighup *all* the
> qmailtoaster related processes?

I've often thought the same thing.

> Is there a reason it does not do so at the moment?

I don't honestly know why it is done the way it is. I'd like to see some
enhancements done in this area to simplify things a bit. I haven't yet
thought things through enough to figure a simple and logical way for it to work.

> Thanks. If the problem can't be resolved I could definetly take
> downgrading as an option.

I have a new toaster going online in 3 days, so if we can't get it fixed
soon, like today, I'll probably downgrade tomorrow.

> I've now opened a new task for this in the bug tracker:
> http://devel.qmailtoaster.com/flyspray/?do=details&task_id=8

Good.

> I did this because I thought I could upload my clamd log as an
> attachment to that task,
> but it seems the tracker does not allow this?

Apparently not. I don't know if flyspray can be configured for that or not.
It'd be a good thing to have (imho).

> I'm no expert in interpreting clad logs, but I'd say that these last
> clamd log entries show, that messages are being scanned and get
> through ok:
> 
> 007-02-26 13:05:28.409066500
> /var/qmail/simscan/1172487926.905757.12053/msg.1172487926.905757.12053:
> OK
> 2007-02-26 13:05:28.409141500
> /var/qmail/simscan/1172487926.905757.12053/msg.1172487926.905757.12053:
> OK
> 2007-02-26 13:05:28.413249500
> /var/qmail/simscan/1172487926.905757.12053/addr.1172487926.905757.12053:
> OK
> 2007-02-26 13:05:28.413297500
> /var/qmail/simscan/1172487926.905757.12053/addr.1172487926.905757.12053:
> OK
> 2007-02-26 13:05:28.413368500
> /var/qmail/simscan/1172487926.905757.12053/textfile0: OK
> 2007-02-26 13:05:28.413410500
> /var/qmail/simscan/1172487926.905757.12053/textfile0: OK
> 2007-02-26 13:05:28.425787500
> /var/qmail/simscan/1172487926.905757.12053/textfile1: OK
> 2007-02-26 13:05:28.425820500
> /var/qmail/simscan/1172487926.905757.12053/textfile1: OK
> 2007-02-26 13:05:33.818660500
> /var/qmail/simscan/1172487932.879123.12087/msg.1172487932.879123.12087:
> OK
> 2007-02-26 13:05:33.818738500
> /var/qmail/simscan/1172487932.879123.12087/msg.1172487932.879123.12087:
> OK
> 2007-02-26 13:05:33.823468500
> /var/qmail/simscan/1172487932.879123.12087/addr.1172487932.879123.12087:
> OK
> 2007-02-26 13:05:33.823471500
> /var/qmail/simscan/1172487932.879123.12087/addr.1172487932.879123.12087:
> OK
> 2007-02-26 13:05:33.823506500
> /var/qmail/simscan/1172487932.879123.12087/textfile0: OK
> 2007-02-26 13:05:33.823526500
> /var/qmail/simscan/1172487932.879123.12087/textfile0: OK
> 2007-02-26 13:05:33.836111500
> /var/qmail/simscan/1172487932.879123.12087/textfile1: OK
> 2007-02-26 13:05:33.836154500
> /var/qmail/simscan/1172487932.879123.12087/textfile1: OK
> 2007-02-26 13:07:00.243048500
> /var/qmail/simscan/1172488018.86476.12352/msg.1172488018.86476.12352:
> OK
> 2007-02-26 13:07:00.243089500
> /var/qmail/simscan/1172488018.86476.12352/msg.1172488018.86476.12352:
> OK
> 2007-02-26 13:07:00.247147500
> /var/qmail/simscan/1172488018.86476.12352/addr.1172488018.86476.12352:
> OK
> 2007-02-26 13:07:00.247170500
> /var/qmail/simscan/1172488018.86476.12352/addr.1172488018.86476.12352:
> OK
> 2007-02-26 13:07:00.247199500
> /var/qmail/simscan/1172488018.86476.12352/textfile0: OK
> 2007-02-26 13:07:00.247201500
> /var/qmail/simscan/1172488018.86476.12352/textfile0: OK
> 2007-02-26 13:07:00.253917500
> /var/qmail/simscan/1172488018.86476.12352/textfile1: OK
> 2007-02-26 13:07:00.253943500
> /var/qmail/simscan/1172488018.86476.12352/textfile1: OK
> 2007-02-26 13:07:00.807336500
> /var/qmail/simscan/1172488018.86476.12352/textfile2: OK
> 2007-02-26 13:07:00.807436500
> /var/qmail/simscan/1172488018.86476.12352/textfile2: OK
> 2007-02-26 13:09:04.310381500 SelfCheck: Database modification
> detected. Forcing reload.
> 2007-02-26 13:09:04.310385500 SelfCheck: Database modification
> detected. Forcing reload.
> 2007-02-26 13:09:04.310387500 Reading databases from /usr/share/clamav
> 2007-02-26 13:09:04.310389500 Reading databases from /usr/share/clamav
> 2007-02-26 13:09:11.251511500 Database correctly reloaded (94742
> signatures)
> 2007-02-26 13:09:11.251580500 Database correctly reloaded (94742
> signatures)
> 2007-02-26 13:25:27.830833500 SIGHUP caught: re-opening log file.
> 2007-02-26 13:25:27.830879500 SIGHUP caught: re-opening log file.

It appears to me too that some are getting through. *All* messages though
appear to be duplicating. I'm beginning to think that the duplicated
messages aren't necessarily related to the problem of clamdscan going loopy.

I'm going to poke around the code some now, and see if I can tell what might
be going on (although my C's a bit rusty). The duplicated messages (at
least) should be fairly easy to find, as I'm not seeing duplication of
processes when it's running.

> I can send you the whole log if you want.

I don't think that's necessary yet.

Keep posting anything that

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

On 2/26/07, Eric Shubes <[EMAIL PROTECTED]> wrote:

Any news on your situation? Can you tell if the scans that hung up were
incoming or outgoing?


I have no idea. I can switch my clamd back on, so we can find out. But
how do I get more information about the scans that are hanging?

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

On 2/26/07, Eric Shubes <[EMAIL PROTECTED]> wrote:

Thanks for the report, Peter. I'm sure it'll help with tracking this problem
down.


You are welcome.


Restarting qmail (via qmailctl restart or service qmail restart, they're the
same thing) does not restart *everything*. It only recycles qmail-smtp and
qmail-send. To recycle everything (including clamav), you should
.) qmailctl stop
.) qmailctl status
I'm not positive that this will show if there are zombies or not. You should
probably do a few 'ps' commands to see if you can find any stragglers. If
there are still any processes still running, especially zombies, you should
hunt them down and kill them.
.) qmailctl start


That is how I've done it normally. This time I forgot to check
zombies. So it is possible that first time I had multiple clamd
processes running. Second time though I had killed all clam related,
so it should not have been the issue.

BTW: Maybe `service qmail restart` should sighup *all* the
qmailtoaster related processes?
Is there a reason it does not do so at the moment?



You seem to have disabled clamav effectively for the time being, so email is
flowing but not being scanned by clamav. I wouldn't want to run in that
state for an extended period. If anyone needs
clamav-toaster-0.88.7-1.3.7.src.rpm to restore to for the time being, let me
know and I'll make it available.


Thanks. If the problem can't be resolved I could definetly take
downgrading as an option.



clamdscan appears to be getting into an infinite-loop kind of state. Peter,
can you verify from your logs whether or not any emails were scanned to
completion? I'd like to know if this is happening on all emails or just some
of them.


I've now opened a new task for this in the bug tracker:
http://devel.qmailtoaster.com/flyspray/?do=details&task_id=8

I did this because I thoght I could upload my clamd log as an
attachment to that task,
but it seems the tracker does not allow this?

I'm no expert in interpreting clad logs, but I'd say that these last
clamd log entries show, that messages are being scanned and get
through ok:

007-02-26 13:05:28.409066500
/var/qmail/simscan/1172487926.905757.12053/msg.1172487926.905757.12053:
OK
2007-02-26 13:05:28.409141500
/var/qmail/simscan/1172487926.905757.12053/msg.1172487926.905757.12053:
OK
2007-02-26 13:05:28.413249500
/var/qmail/simscan/1172487926.905757.12053/addr.1172487926.905757.12053:
OK
2007-02-26 13:05:28.413297500
/var/qmail/simscan/1172487926.905757.12053/addr.1172487926.905757.12053:
OK
2007-02-26 13:05:28.413368500
/var/qmail/simscan/1172487926.905757.12053/textfile0: OK
2007-02-26 13:05:28.413410500
/var/qmail/simscan/1172487926.905757.12053/textfile0: OK
2007-02-26 13:05:28.425787500
/var/qmail/simscan/1172487926.905757.12053/textfile1: OK
2007-02-26 13:05:28.425820500
/var/qmail/simscan/1172487926.905757.12053/textfile1: OK
2007-02-26 13:05:33.818660500
/var/qmail/simscan/1172487932.879123.12087/msg.1172487932.879123.12087:
OK
2007-02-26 13:05:33.818738500
/var/qmail/simscan/1172487932.879123.12087/msg.1172487932.879123.12087:
OK
2007-02-26 13:05:33.823468500
/var/qmail/simscan/1172487932.879123.12087/addr.1172487932.879123.12087:
OK
2007-02-26 13:05:33.823471500
/var/qmail/simscan/1172487932.879123.12087/addr.1172487932.879123.12087:
OK
2007-02-26 13:05:33.823506500
/var/qmail/simscan/1172487932.879123.12087/textfile0: OK
2007-02-26 13:05:33.823526500
/var/qmail/simscan/1172487932.879123.12087/textfile0: OK
2007-02-26 13:05:33.836111500
/var/qmail/simscan/1172487932.879123.12087/textfile1: OK
2007-02-26 13:05:33.836154500
/var/qmail/simscan/1172487932.879123.12087/textfile1: OK
2007-02-26 13:07:00.243048500
/var/qmail/simscan/1172488018.86476.12352/msg.1172488018.86476.12352:
OK
2007-02-26 13:07:00.243089500
/var/qmail/simscan/1172488018.86476.12352/msg.1172488018.86476.12352:
OK
2007-02-26 13:07:00.247147500
/var/qmail/simscan/1172488018.86476.12352/addr.1172488018.86476.12352:
OK
2007-02-26 13:07:00.247170500
/var/qmail/simscan/1172488018.86476.12352/addr.1172488018.86476.12352:
OK
2007-02-26 13:07:00.247199500
/var/qmail/simscan/1172488018.86476.12352/textfile0: OK
2007-02-26 13:07:00.247201500
/var/qmail/simscan/1172488018.86476.12352/textfile0: OK
2007-02-26 13:07:00.253917500
/var/qmail/simscan/1172488018.86476.12352/textfile1: OK
2007-02-26 13:07:00.253943500
/var/qmail/simscan/1172488018.86476.12352/textfile1: OK
2007-02-26 13:07:00.807336500
/var/qmail/simscan/1172488018.86476.12352/textfile2: OK
2007-02-26 13:07:00.807436500
/var/qmail/simscan/1172488018.86476.12352/textfile2: OK
2007-02-26 13:09:04.310381500 SelfCheck: Database modification
detected. Forcing reload.
2007-02-26 13:09:04.310385500 SelfCheck: Database modification
detected. Forcing reload.
2007-02-26 13:09:04.310387500 Reading databases from /usr/share/clamav
2007-02-26 13:09:04.310389500 Reading databases from /usr/share/clamav
2007-02-26 13:09:11.251511500 Database correctly reloaded (94742 signatures)
2007-02-26 13:09:11.251580500 Da

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Peter (and others with this problem),

I've done some testing on the new toaster I just built. The only symptom
I've seen is the duplicated clamd log messages. Inbound messages have
scanned ok, and clamdscan terminated normally (afaict).

Any news on your situation? Can you tell if the scans that hung up were
incoming or outgoing?

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Peter,

One more thing. If at all possible, it'd be great if you could refrain from
backing off the update for a little bit. That way if the fix ends up being a
relatively simply tweak, we'll have a machine to try it out on right away.

Thanks.

-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Thanks for the report, Peter. I'm sure it'll help with tracking this problem
down.

A few thoughts come to mind (first thing in the morning, so I hope I'm awake!):

Restarting qmail (via qmailctl restart or service qmail restart, they're the
same thing) does not restart *everything*. It only recycles qmail-smtp and
qmail-send. To recycle everything (including clamav), you should
.) qmailctl stop
.) qmailctl status
I'm not positive that this will show if there are zombies or not. You should
probably do a few 'ps' commands to see if you can find any stragglers. If
there are still any processes still running, especially zombies, you should
hunt them down and kill them.
.) qmailctl start

You seem to have disabled clamav effectively for the time being, so email is
flowing but not being scanned by clamav. I wouldn't want to run in that
state for an extended period. If anyone needs
clamav-toaster-0.88.7-1.3.7.src.rpm to restore to for the time being, let me
know and I'll make it available.

clamdscan appears to be getting into an infinite-loop kind of state. Peter,
can you verify from your logs whether or not any emails were scanned to
completion? I'd like to know if this is happening on all emails or just some
of them.

My thinking at this point is that the clamd log messages that are doubling
up are likly pointing to the problem. The doubling messages are not normal,
and if there are indeed two processes running somehow, they might be
stepping on each other, causing the lock-up.

I'll continue to try and figure this out.

Peter Peltonen wrote:
> At 12:50 the situation is: 8 clamdscan processes eating 100 % cpu
> 
> I notice that freshclam is not running:
> 
> # service freshclam status
> freshclam dead but subsys locked
> 
> All I see in freshclam log are messages like this:
> 
> Received signal: wake up
> ClamAV update process started at Mon Feb 26 10:40:41 2007
> main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder:
> tkojm)
> daily.inc is up to date (version: 2654, sigs: 10790, f-level: 13,
> builder: ccordes)
> 
> I restarted it:
> 
> # service freshclam stop
> Stopping freshclam:[FAILED]
> 
> # service freshclam start
> Starting freshclam:[  OK  ]
> 
> And the log says:
> 
> freshclam daemon 0.90 (OS: linux-gnu, ARCH: i386, CPU: i386)
> ClamAV update process started at Mon Feb 26 13:01:47 2007
> main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder:
> tkojm)
> Downloading daily-2655.cdiff [100%]
> daily.inc updated (version: 2655, sigs: 10791, f-level: 13, builder:
> ccordes)
> Database updated (94742 signatures) from db.fi.clamav.net (IP:
> 62.236.254.228)
> 
> [EMAIL PROTECTED] root]# service freshclam status
> freshclam (pid 11365) is running...
> 
> Any effect on clamdscan? Nope:
> 
> At 13:05 the situation is: 9 clamdscan processes eating 100 % cpu
> 
> After that I tried a testing procedure that I found at
> http://wiki.clamav.net/Main/SimScan
> 
> which did not go quite well:
> 
> # QMAILQUEUE=/var/qmail/bin/simscan SIMSCAN_DEBUG=2 \
> /var/qmail/bin/qmail-inject [EMAIL PROTECTED] < testmail.txt
> qmail-inject: fatal: qq crashed (#4.3.0)
> 
> I found out that no email is going through again... I also see now 19
> clamscan
> processes.
> 
> When looking at the log I see that a reload has been issued before my
> test (because of freshclam restart I suppose?):
> 
> 2007-02-26 13:09:04.310381500 SelfCheck: Database modification detected.
> Forcing
> reload.
> 2007-02-26 13:09:04.310385500 SelfCheck: Database modification detected.
> Forcing
> reload.
> 2007-02-26 13:09:04.310387500 Reading databases from /usr/share/clamav
> 2007-02-26 13:09:04.310389500 Reading databases from /usr/share/clamav
> 2007-02-26 13:09:11.251511500 Database correctly reloaded (94742
> signatures)
> 2007-02-26 13:09:11.251580500 Database correctly reloaded (94742
> signatures)
> 
> I disable clam for all domains in /var/qmail/control/simcontrol and
> rebuild the
> cdb:
> 
> [EMAIL PROTECTED] root]# service qmail cdb
> 
> Then I restart clamd:
> 
> root]# svc -h /var/qmail/supervise/clamd
> 
> The logs say:
> 
> 2007-02-26 13:25:27.830833500 SIGHUP caught: re-opening log file.
> 2007-02-26 13:25:27.830879500 SIGHUP caught: re-opening log file.
> 
> Email seems to go through now. No effect on the clamscan processes
> though. Ok,
> let's shutdown clamav totally:
> 
> svc -d /var/qmail/supervise/clamd
> svc -t /var/qmail/supervise/clamd
> 
> Nothing happens, the processes still stay there, nothing in the logs.
> `service
> qmail stat` says:
> 
> clamd: up (pid 26992) 6896 seconds, want down
> 
> After a few minutes this is still the issue. There are now 21
> clamdscan processes
> spawned by qmail-smtpd and simscan, at least pstree reports me the
> processes like
> this:
> 
> |-qmail-smtpd(31206)---simscan(31209)---clamdscan(31223)
> |-qmail-smtpd(1462)---simscan(1465)---clamdscan(1468)
> 
> I kill the clamdscan proces

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Natalio Gatti]

On 2/26/07, Peter Peltonen <[EMAIL PROTECTED]> wrote:

At 12:50 the situation is: 8 clamdscan processes eating 100 % cpu

I notice that freshclam is not running:

# service freshclam status
freshclam dead but subsys locked

All I see in freshclam log are messages like this:

Received signal: wake up
ClamAV update process started at Mon Feb 26 10:40:41 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder: tkojm)
daily.inc is up to date (version: 2654, sigs: 10790, f-level: 13,
builder: ccordes)

I restarted it:

# service freshclam stop
Stopping freshclam:[FAILED]

# service freshclam start
Starting freshclam:[  OK  ]

And the log says:

freshclam daemon 0.90 (OS: linux-gnu, ARCH: i386, CPU: i386)
ClamAV update process started at Mon Feb 26 13:01:47 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder: tkojm)
Downloading daily-2655.cdiff [100%]
daily.inc updated (version: 2655, sigs: 10791, f-level: 13, builder: ccordes)
Database updated (94742 signatures) from db.fi.clamav.net (IP: 62.236.254.228)

[EMAIL PROTECTED] root]# service freshclam status
freshclam (pid 11365) is running...

Any effect on clamdscan? Nope:

At 13:05 the situation is: 9 clamdscan processes eating 100 % cpu

After that I tried a testing procedure that I found at
http://wiki.clamav.net/Main/SimScan

which did not go quite well:

# QMAILQUEUE=/var/qmail/bin/simscan SIMSCAN_DEBUG=2 \
/var/qmail/bin/qmail-inject [EMAIL PROTECTED] < testmail.txt
qmail-inject: fatal: qq crashed (#4.3.0)

I found out that no email is going through again... I also see now 19 clamscan
processes.

When looking at the log I see that a reload has been issued before my
test (because of freshclam restart I suppose?):

2007-02-26 13:09:04.310381500 SelfCheck: Database modification detected. Forcing
reload.
2007-02-26 13:09:04.310385500 SelfCheck: Database modification detected. Forcing
reload.
2007-02-26 13:09:04.310387500 Reading databases from /usr/share/clamav
2007-02-26 13:09:04.310389500 Reading databases from /usr/share/clamav
2007-02-26 13:09:11.251511500 Database correctly reloaded (94742 signatures)
2007-02-26 13:09:11.251580500 Database correctly reloaded (94742 signatures)

I disable clam for all domains in /var/qmail/control/simcontrol and rebuild the
cdb:

[EMAIL PROTECTED] root]# service qmail cdb

Then I restart clamd:

root]# svc -h /var/qmail/supervise/clamd

The logs say:

2007-02-26 13:25:27.830833500 SIGHUP caught: re-opening log file.
2007-02-26 13:25:27.830879500 SIGHUP caught: re-opening log file.

Email seems to go through now. No effect on the clamscan processes though. Ok,
let's shutdown clamav totally:

svc -d /var/qmail/supervise/clamd
svc -t /var/qmail/supervise/clamd

Nothing happens, the processes still stay there, nothing in the logs. `service
qmail stat` says:

clamd: up (pid 26992) 6896 seconds, want down

After a few minutes this is still the issue. There are now 21
clamdscan processes
spawned by qmail-smtpd and simscan, at least pstree reports me the
processes like
this:

|-qmail-smtpd(31206)---simscan(31209)---clamdscan(31223)
|-qmail-smtpd(1462)---simscan(1465)---clamdscan(1468)

I kill the clamdscan processes with `kill -9` and the processes
disappear (also the
related qmail-smtpd processes). Clamd still won't shut itself down, I
have to kill
it also.

Mail seems to go through normally so I suppose I do not have to have the clamd
process running when no domains use it.

As this is a production server I'll stop my testing here... I hope it
gets resolved. I tried
to peek at ClamAV bugtracker / mailing list, but did not see any
similiar reports.

Regards,
Peter


I had the same problem in a FC4. I downgrade to the prior clamav
version and I´m waiting for a new update.

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

At 12:50 the situation is: 8 clamdscan processes eating 100 % cpu

I notice that freshclam is not running:

# service freshclam status
freshclam dead but subsys locked

All I see in freshclam log are messages like this:

Received signal: wake up
ClamAV update process started at Mon Feb 26 10:40:41 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder: tkojm)
daily.inc is up to date (version: 2654, sigs: 10790, f-level: 13,
builder: ccordes)

I restarted it:

# service freshclam stop
Stopping freshclam:[FAILED]

# service freshclam start
Starting freshclam:[  OK  ]

And the log says:

freshclam daemon 0.90 (OS: linux-gnu, ARCH: i386, CPU: i386)
ClamAV update process started at Mon Feb 26 13:01:47 2007
main.cvd is up to date (version: 42, sigs: 83951, f-level: 10, builder: tkojm)
Downloading daily-2655.cdiff [100%]
daily.inc updated (version: 2655, sigs: 10791, f-level: 13, builder: ccordes)
Database updated (94742 signatures) from db.fi.clamav.net (IP: 62.236.254.228)

[EMAIL PROTECTED] root]# service freshclam status
freshclam (pid 11365) is running...

Any effect on clamdscan? Nope:

At 13:05 the situation is: 9 clamdscan processes eating 100 % cpu

After that I tried a testing procedure that I found at
http://wiki.clamav.net/Main/SimScan

which did not go quite well:

# QMAILQUEUE=/var/qmail/bin/simscan SIMSCAN_DEBUG=2 \
/var/qmail/bin/qmail-inject [EMAIL PROTECTED] < testmail.txt
qmail-inject: fatal: qq crashed (#4.3.0)

I found out that no email is going through again... I also see now 19 clamscan
processes.

When looking at the log I see that a reload has been issued before my
test (because of freshclam restart I suppose?):

2007-02-26 13:09:04.310381500 SelfCheck: Database modification detected. Forcing
reload.
2007-02-26 13:09:04.310385500 SelfCheck: Database modification detected. Forcing
reload.
2007-02-26 13:09:04.310387500 Reading databases from /usr/share/clamav
2007-02-26 13:09:04.310389500 Reading databases from /usr/share/clamav
2007-02-26 13:09:11.251511500 Database correctly reloaded (94742 signatures)
2007-02-26 13:09:11.251580500 Database correctly reloaded (94742 signatures)

I disable clam for all domains in /var/qmail/control/simcontrol and rebuild the
cdb:

[EMAIL PROTECTED] root]# service qmail cdb

Then I restart clamd:

root]# svc -h /var/qmail/supervise/clamd

The logs say:

2007-02-26 13:25:27.830833500 SIGHUP caught: re-opening log file.
2007-02-26 13:25:27.830879500 SIGHUP caught: re-opening log file.

Email seems to go through now. No effect on the clamscan processes though. Ok,
let's shutdown clamav totally:

svc -d /var/qmail/supervise/clamd
svc -t /var/qmail/supervise/clamd

Nothing happens, the processes still stay there, nothing in the logs. `service
qmail stat` says:

clamd: up (pid 26992) 6896 seconds, want down

After a few minutes this is still the issue. There are now 21
clamdscan processes
spawned by qmail-smtpd and simscan, at least pstree reports me the
processes like
this:

|-qmail-smtpd(31206)---simscan(31209)---clamdscan(31223)
|-qmail-smtpd(1462)---simscan(1465)---clamdscan(1468)

I kill the clamdscan processes with `kill -9` and the processes
disappear (also the
related qmail-smtpd processes). Clamd still won't shut itself down, I
have to kill
it also.

Mail seems to go through normally so I suppose I do not have to have the clamd
process running when no domains use it.

As this is a production server I'll stop my testing here... I hope it
gets resolved. I tried
to peek at ClamAV bugtracker / mailing list, but did not see any
similiar reports.

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

After restart I have now experienced that clamd processes are eating
up all CPU (2,8GHz HT P4):

PID USER PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
1321 clamav25   0 49292  46M  1616 R30.1  4.7   2:08   0 clamd
31064 clamav25   0 49292  46M  1616 R29.1  4.7  13:06   0 clamd
28678 clamav25   0 49292  46M  1616 R22.7  4.7  23:39   0 clamd

Maybe it's having hard time with the queue that had formated in the
morning. If it does not go away soon I'll have to stop it somehow.

Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Peter Peltonen]

I seem to have similiar problems with the new clamav which I've been
running for a few days now. This morning I found out that my mail
server was not responding: no new emails came through, and nothing was
in smtp logs.

When checking process list, I saw tens and tens of clamav processes like this:

16604 pts/2S  0:00 clamdscan --stdout
16764 pts/2S  0:00 clamdscan --stdout
16785 pts/2S  0:00 clamdscan --stdout
16895 pts/2S  0:00 clamdscan --stdout

I tried sending an email to a domain that had no clamav scanning done
but this message did not go through either.

I did `service qmail stop` which did not end the clamav processes.
Some qmail processes were hanging too. I gave `kill -9` as long as
they all had been killed and then started qmail again and all was fine
again.

In freshclam log were these messages before my restart:

2007-02-26 07:52:14.476478500
/var/qmail/simscan/1172469132.417507.27573/textfile2: OK
2007-02-26 07:52:14.479218500
/var/qmail/simscan/1172469132.417507.27573/centrifugal.gif: O
K
2007-02-26 07:52:14.479276500
/var/qmail/simscan/1172469132.417507.27573/centrifugal.gif: O
K
2007-02-26 08:15:07.506750500 SelfCheck: Database status OK.
2007-02-26 08:15:07.506754500 SelfCheck: Database status OK.
2007-02-26 08:46:30.407870500 SelfCheck: Database modification
detected. Forcing reload.
2007-02-26 08:46:30.407912500 SelfCheck: Database modification
detected. Forcing reload.
2007-02-26 08:46:30.407914500 Reading databases from /usr/share/clamav
2007-02-26 08:46:30.407916500 Reading databases from /usr/share/clamav
2007-02-26 08:46:37.446231500 Database correctly reloaded (94741 signatures)
2007-02-26 08:46:37.446308500 Database correctly reloaded (94741 signatures)
2007-02-26 09:20:27.517258500 SelfCheck: Database status OK.
2007-02-26 09:20:27.517262500 SelfCheck: Database status OK.
2007-02-26 09:51:40.603764500 SelfCheck: Database status OK.
2007-02-26 09:51:40.603810500 SelfCheck: Database status OK.
2007-02-26 10:21:55.917559500 SelfCheck: Database status OK.
2007-02-26 11:36:42.462342500 +++ Started at Mon Feb 26 11:36:42 2007
2007-02-26 11:36:42.462346500 clamd daemon 0.90 (OS: linux-gnu, ARCH:
i386, CPU: i386)
2007-02-26 11:36:42.462348500 Log file size limited to 1048576 bytes.
2007-02-26 11:36:42.462349500 Reading databases from /usr/share/clamav
2007-02-26 11:36:47.176711500 Loaded 94741 signatures.
2007-02-26 11:36:47.187157500 WARNING: Socket file /tmp/clamd exists.
Unclean shutdown? Rem
oving...
2007-02-26 11:36:47.187264500 WARNING: Socket file /tmp/clamd exists.
Unclean shutdown? Rem
oving...
2007-02-26 11:36:47.187393500 Unix socket file /tmp/clamd
2007-02-26 11:36:47.187465500 Unix socket file /tmp/clamd

I did the restart at 11:36. Why did clamav force a reload in the
morning, is that normal behaviour?

Now after running 30 minutes I have two clamdscan processes running.

Could this be happening if in upgrading all cladscan processes did not
die normally after issuing `service qmail restart`? I did the upgrade
manually (not with qtp) and did not
check if all processes went away or not...

I will leave clamav now running. If this happens again, I'll disable
it. What's the best way to do that? Comment it away from simcontrol
for all domains and restart qmail?

Regards,
Peter

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Erik Grammer]

I believe there are.  And the simscan/clamav pairs seem to be 
multiplying as a new check of processes returns:


vpopmail  2870  0.0  0.1   6468  1340 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav2892  0.0  0.0   1800   644 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav2894  0.0  0.0   5980   896 ?SFeb25   0:00 
clamdscan --stdout
root  2907  0.0  0.1   4684  1372 ?SFeb25   0:00 
/usr/bin/couriertls -server -tcpd /usr/sbin/imaplogin /usr/bin/imapd Maildir
vpopmail  2908  0.0  0.0   3820   720 ?SFeb25   0:00 
/usr/bin/imapd Maildir
vpopmail  3035  0.0  0.1   6468  1344 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav3076  0.0  0.0   1800   648 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav3078  0.0  0.0   5984   900 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  3618  0.0  0.1   6468  1336 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav3619  0.0  0.0   1792   636 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav3673  0.0  0.0   5980   896 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  5408  0.0  0.1   6464  1336 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
vpopmail  5409  0.0  0.1   6464  1332 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav5411  0.0  0.0   2692   652 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5412  0.0  0.0   2696   652 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5414  0.0  0.0   5088   892 ?SFeb25   0:00 
clamdscan --stdout
clamav5417  0.0  0.0   5088   896 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  5665  0.0  0.1   6464  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
vpopmail  5666  0.0  0.1   6464  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav5678  0.0  0.0   1804   648 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5679  0.0  0.0   1792   636 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5681  0.0  0.0   5984   896 ?SFeb25   0:00 
clamdscan --stdout
clamav5683  0.0  0.0   5980   896 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  5920  0.0  0.1   6468  1332 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
vpopmail  5921  0.0  0.1   5572  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav5923  0.0  0.0   2692   652 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5924  0.0  0.0   1800   640 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav5926  0.0  0.0   5984   900 ?SFeb25   0:00 
clamdscan --stdout
clamav5929  0.0  0.0   5984   900 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  6259  0.0  0.1   5572  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
vpopmail  6260  0.0  0.1   5572  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav6267  0.0  0.0   1792   640 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav6268  0.0  0.0   2688   652 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav6270  0.0  0.0   5980   896 ?SFeb25   0:00 
clamdscan --stdout
clamav6273  0.0  0.0   5984   900 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  6318  0.0  0.1   6468  1336 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav6320  0.0  0.0   1792   636 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav6322  0.0  0.0   5092   900 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  6409  0.0  0.1   5572  1328 ?SFeb25   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav6410  0.0  0.0   1800   648 ?SFeb25   0:00 
/var/qmail/bin/simscan
clamav6412  0.0  0.0   5984   900 ?SFeb25   0:00 
clamdscan --stdout
vpopmail  6472  0.0  0.1   6468  1336 ?S00:03   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav6473  0.0  0.0   1796   648 ?S00:04   0:00 
/var/qmail/bin/simscan
clamav6475  0.0  0.0   5984   900 ?S00:04   0:00 
clamdscan --stdout
vpopmail  6476  0.0  0.1   5576  1912 ?S00:04   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/bin/vchkpw /bin/true
clamav6517  0.0  0.0   2684   640 ?S00:05   0:00 
/var/qmail/bin/simscan
clamav6519  0.0  0.0   5988   896 ?S00:05   0:00 
clamdscan --stdout
vpopmail  6565  0.0  0.1   5572  1328 ?S00:10   0:00 
/var/qmail/bin/qmail-smtpd /home/vpopmail/

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

These almost-duplicate messages indeed look odd. I don't have them in an
older clamav-toaster version, but I do see them in a new toaster I just
built. I can't get into it any more tonight, but will be looking into it
first thing tomorrow. There appears to be some sort of problem with the
latest clamav-toaster all right.

Erik Grammer wrote:
> Here is a snippet that suggests to me that there are multiple clamd
> processes running but I don't know how to get rid of the duplicate (if
> in fact that is the problem.)  I feel out of my league here and
> appreciate the help!
> 
> 
> 
> clamd log:
> 
> +++ Started at Sun Feb 25 19:11:35 2007
> @400045e24ff135bb071c clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
> CPU: i686)
> @400045e24ff135bb0eec Log file size limited to 1048576 bytes.
> @400045e24ff135bb1aa4 Reading databases from /usr/share/clamav
> @400045e24ff507a9f3c4 Loaded 94737 signatures.
> @400045e24ff508206be4 WARNING: Socket file /tmp/clamd exists.
> Unclean shutdown? Removing...
> @400045e24ff50821b404 WARNING: Socket file /tmp/clamd exists.
> Unclean shutdown? Removing...
> @400045e24ff509fcfbe4 Unix socket file /tmp/clamd
> @400045e24ff509fdda8c Unix socket file /tmp/clamd
> @400045e24ff509fe578c Setting connection queue length to 15
> @400045e24ff509fec4ec Setting connection queue length to 15
> @400045e24ff509ff5d44 Listening daemon: PID: 2232
> @400045e24ff509ffce8c Listening daemon: PID: 2232
> @400045e24ff50a00535c Archive: Archived file size limit set to
> 10485760 bytes.
> @400045e24ff50a00c4a4 Archive: Archived file size limit set to
> 10485760 bytes.
> @400045e24ff50a0135ec Archive: Recursion level limit set to 8.
> @400045e24ff50a01a34c Archive: Recursion level limit set to 8.
> @400045e24ff50a0210ac Archive: Files limit set to 1000.
> @400045e24ff50a0281f4 Archive: Files limit set to 1000.
> @400045e24ff50a02ef54 Archive: Compression ratio limit set to 250.
> @400045e24ff50a035cb4 Archive: Compression ratio limit set to 250.
> @400045e24ff50a03cdfc Archive support enabled.
> @400045e24ff50a043774 Archive support enabled.
> @400045e24ff50a04b08c Algorithmic detection enabled.
> @400045e24ff50a051a04 Algorithmic detection enabled.
> @400045e24ff50a061404 Portable Executable support enabled.
> @400045e24ff50a068164 Portable Executable support enabled.
> @400045e24ff50a06eec4 ELF support enabled.
> @400045e24ff50a07583c ELF support enabled.
> @400045e24ff50a07cd6c Mail files support enabled.
> @400045e24ff50a0836e4 Mail files support enabled.
> @400045e24ff50a08ac14 Mail: Recursion level limit set to 64.
> @400045e24ff50a091974 Mail: Recursion level limit set to 64.
> @400045e24ff50a0986d4 OLE2 support enabled.
> @400045e24ff50a09f04c OLE2 support enabled.
> @400045e24ff50a0a5dac HTML support enabled.
> @400045e24ff50a0ac724 HTML support enabled.
> @400045e24ff50a0b403c Self checking every 1800 seconds.
> @400045e24ff50a0bad9c Self checking every 1800 seconds.
> @400045e251bf2dda1efc
> /var/qmail/simscan/1172459957.86416.2873/addr.1172459957.86416.2873: OK
> @400045e251bf2ddb3c24
> /var/qmail/simscan/1172459957.86416.2873/addr.1172459957.86416.2873: OK
> @400045e251bf2e30842c
> /var/qmail/simscan/1172459957.86416.2873/textfile1: OK
> @400045e251bf2e3162d4
> /var/qmail/simscan/1172459957.86416.2873/textfile1: OK
> @400045e251bf301adf6c
> /var/qmail/simscan/1172459957.86416.2873/textfile2: OK
> @400045e251bf301bba2c
> /var/qmail/simscan/1172459957.86416.2873/textfile2: OK
> @400045e252d60da2e9d4 +++ Started at Sun Feb 25 19:23:55 2007
> @400045e252d60da2f974 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
> CPU: i686)
> @400045e252d60da3052c Log file size limited to 1048576 bytes.
> @400045e252d60da30cfc Reading databases from /usr/share/clamav
> @400045e252db23f55c44 Loaded 94737 signatures.
> @400045e252db2468175c ERROR: Socket file /tmp/clamd is in use by
> another process.
> @400045e252db2469386c ERROR: Socket file /tmp/clamd is in use by
> another process.
> @400045e252db2777a91c +++ Started at Sun Feb 25 19:24:01 2007
> @400045e252db2777bca4 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
> CPU: i686)
> @400045e252db2777c474 Log file size limited to 1048576 bytes.
> @400045e252db2777d02c Reading databases from /usr/share/clamav
> @400045e252e0090b067c Loaded 94737 signatures.
> @400045e252e00985281c ERROR: Socket file /tmp/clamd is in use by
> another process.
> @400045e252e009864544 ERROR: Socket file /tmp/clamd is in use by
> another process.
> @400045e252e01708a8ec +++ Started at Sun Feb 25 19:24:06 2007
> @400045e252e01708bc74 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386,
> CPU: i686)
> @400045e252e01708c444 Log file size limited to 1048576 bytes.
> @400045e252e01708cffc Reading databases from /usr/share/clamav
> @400045e252e5065bfbac Loade

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Some of these simscan/clamav pairs seem to not be terminating normally. Are
there any smtp processes still active too (which would correspond to the
still-active simscans)?

Erik Grammer wrote:
> Thought this might be useful... a list of the clamd/clamav processes
> currently running:
> 
> root  2188  0.0  0.0   1420   236 ?S19:31   0:00
> supervise clamd
> 
> clamav2196 94.9  4.6  93948 47820 ?Sl   19:31 116:18
> /usr/sbin/clamd
> 
> qmaill2206  0.0  0.0   1432   244 ?S19:31   0:00
> /usr/bin/multilog t s100 n100 /var/log/qmail/clamd
> 
> clamav2892  0.0  0.0   1800   644 ?S19:36   0:00
> /var/qmail/bin/simscan
> 
> clamav2894  0.0  0.0   5980   896 ?S19:36   0:00
> clamdscan --stdout
> 
> clamav3076  0.0  0.0   1800   648 ?S19:45   0:00
> /var/qmail/bin/simscan
> 
> clamav3078  0.0  0.0   5984   900 ?S19:45   0:00
> clamdscan --stdout
> 
> clamav3619  0.0  0.0   1792   636 ?S20:24   0:00
> /var/qmail/bin/simscan
> 
> clamav3673  0.0  0.0   5980   896 ?S20:25   0:00
> clamdscan --stdout
> 
> Thanks,
> -Erik G.
> 
> 
> Eric "Shubes" wrote:
>> Does clamd log show anything?
>>
>> Erik Grammer wrote:
>>> When I reboot the server and then run: ps -el | grep 'Z' I get nothing.
>>>I have to stop, then start qmail to replicate the problem.  Then I
>>> get-
>>>
>>> ps -el | grep 'Z' returns:
>>> F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY  TIME CMD
>>> 4 Z 0  3441  3391  0  81   0 - 0 exit   pts/100:00:00
>>> supervise 
>>>
>>> # ps -aux |more returns:
>>> root  3605  0.0  0.0  0 0 pts/1Z18:56   0:00
>>> [supervise] 
>>>
>>>
>>> not sure what to do with that.  When I bring down qmail I get nothing
>>> from ps -el | grep 'Z'  It only shows a zombie when I stop and then
>>> start qmail.  But this also happens when I am not manually
>>> stopping/starting qmail so I'm not sure what is causing the problem.
>>>
>>> Thanks,
>>> -Erik G.
>>>
>>>
>>> Eric "Shubes" wrote:
 It sounds like you have a zombie clamd running. If pid 3282 is still
 running, kill it, and supervise should start it back up again.

 If it doesn't restart on its own, bring down qmail, check for any
 zombies,
 then restart qmail.

 HTH.

 Erik Grammer wrote:
> Hi all,
>
> Running fully updated toaster (as of 2/23/07) on fedora 4.  Prior
> to the
> full update I manually updated clamav with the devel package on Erik's
> site and started receiving the following error on restarting qmail:
>
> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
> failure
>
> I removed the clamav package and then went to a full update using
> 'qtp-newmodel' Everything went smoothly with the updates and outgoing
> mail is fine and incoming works after a server reboot but somewhere
> along the line mail stops coming in.  Restarting qmail returns:
>
> Starting qmail-toaster: svscan.
>
> and then:
>
> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
> failure
>
> qmailctl stat returns:
>
> authlib: up (pid 437) 8 seconds
> clamd: up (pid 3282) 88511 seconds, want down
> imap4: up (pid 419) 9 seconds
> imap4-ssl: up (pid 431) 6 seconds
> pop3: up (pid 403) 9 seconds
> pop3-ssl: up (pid 494) 4 seconds
> send: up (pid 425) 9 seconds
> smtp: up (pid 459) 7 seconds
> spamd: up (pid 413) 9 seconds
> submission: up (pid 445) 8 seconds
> authlib/log: up (pid 442) 8 seconds
> clamd/log: up (pid 455) 7 seconds
> imap4/log: up (pid 422) 9 seconds
> imap4-ssl/log: up (pid 433) 8 seconds
> pop3/log: up (pid 406) 9 seconds
> pop3-ssl/log: up (pid 472) 5 seconds
> send/log: up (pid 411) 8 seconds
> smtp/log: up (pid 462) 6 seconds
> spamd/log: up (pid 415) 9 seconds
> submission/log: up (pid 452) 5 seconds
>
> I thought I had seen an email on the list from Erik about a bug in the
> Clamav package that had been fixed but I can't find the email and
> am now
> at a loss.  Any help would be appreciated.
>
> Thanks,
> -Erik G.
>


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Erik Grammer]

Thought this might be useful... a list of the clamd/clamav processes 
currently running:


root  2188  0.0  0.0   1420   236 ?S19:31   0:00 
supervise clamd


clamav2196 94.9  4.6  93948 47820 ?Sl   19:31 116:18 
/usr/sbin/clamd


qmaill2206  0.0  0.0   1432   244 ?S19:31   0:00 
/usr/bin/multilog t s100 n100 /var/log/qmail/clamd


clamav2892  0.0  0.0   1800   644 ?S19:36   0:00 
/var/qmail/bin/simscan


clamav2894  0.0  0.0   5980   896 ?S19:36   0:00 
clamdscan --stdout


clamav3076  0.0  0.0   1800   648 ?S19:45   0:00 
/var/qmail/bin/simscan


clamav3078  0.0  0.0   5984   900 ?S19:45   0:00 
clamdscan --stdout


clamav3619  0.0  0.0   1792   636 ?S20:24   0:00 
/var/qmail/bin/simscan


clamav3673  0.0  0.0   5980   896 ?S20:25   0:00 
clamdscan --stdout


Thanks,
-Erik G.


Eric "Shubes" wrote:

Does clamd log show anything?

Erik Grammer wrote:

When I reboot the server and then run: ps -el | grep 'Z' I get nothing.
   I have to stop, then start qmail to replicate the problem.  Then I get-

ps -el | grep 'Z' returns:
F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY  TIME CMD
4 Z 0  3441  3391  0  81   0 - 0 exit   pts/100:00:00
supervise 

# ps -aux |more returns:
root  3605  0.0  0.0  0 0 pts/1Z18:56   0:00
[supervise] 


not sure what to do with that.  When I bring down qmail I get nothing
from ps -el | grep 'Z'  It only shows a zombie when I stop and then
start qmail.  But this also happens when I am not manually
stopping/starting qmail so I'm not sure what is causing the problem.

Thanks,
-Erik G.


Eric "Shubes" wrote:

It sounds like you have a zombie clamd running. If pid 3282 is still
running, kill it, and supervise should start it back up again.

If it doesn't restart on its own, bring down qmail, check for any
zombies,
then restart qmail.

HTH.

Erik Grammer wrote:

Hi all,

Running fully updated toaster (as of 2/23/07) on fedora 4.  Prior to the
full update I manually updated clamav with the devel package on Erik's
site and started receiving the following error on restarting qmail:

# supervise: fatal: unable to acquire clamd/supervise/lock: temporary
failure

I removed the clamav package and then went to a full update using
'qtp-newmodel' Everything went smoothly with the updates and outgoing
mail is fine and incoming works after a server reboot but somewhere
along the line mail stops coming in.  Restarting qmail returns:

Starting qmail-toaster: svscan.

and then:

# supervise: fatal: unable to acquire clamd/supervise/lock: temporary
failure

qmailctl stat returns:

authlib: up (pid 437) 8 seconds
clamd: up (pid 3282) 88511 seconds, want down
imap4: up (pid 419) 9 seconds
imap4-ssl: up (pid 431) 6 seconds
pop3: up (pid 403) 9 seconds
pop3-ssl: up (pid 494) 4 seconds
send: up (pid 425) 9 seconds
smtp: up (pid 459) 7 seconds
spamd: up (pid 413) 9 seconds
submission: up (pid 445) 8 seconds
authlib/log: up (pid 442) 8 seconds
clamd/log: up (pid 455) 7 seconds
imap4/log: up (pid 422) 9 seconds
imap4-ssl/log: up (pid 433) 8 seconds
pop3/log: up (pid 406) 9 seconds
pop3-ssl/log: up (pid 472) 5 seconds
send/log: up (pid 411) 8 seconds
smtp/log: up (pid 462) 6 seconds
spamd/log: up (pid 415) 9 seconds
submission/log: up (pid 452) 5 seconds

I thought I had seen an email on the list from Erik about a bug in the
Clamav package that had been fixed but I can't find the email and am now
at a loss.  Any help would be appreciated.

Thanks,
-Erik G.





-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]








-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Erik Grammer]

Here is a snippet that suggests to me that there are multiple clamd 
processes running but I don't know how to get rid of the duplicate (if 
in fact that is the problem.)  I feel out of my league here and 
appreciate the help!




clamd log:

+++ Started at Sun Feb 25 19:11:35 2007
@400045e24ff135bb071c clamd daemon 0.90 (OS: linux-gnu, ARCH: i386, 
CPU: i686)

@400045e24ff135bb0eec Log file size limited to 1048576 bytes.
@400045e24ff135bb1aa4 Reading databases from /usr/share/clamav
@400045e24ff507a9f3c4 Loaded 94737 signatures.
@400045e24ff508206be4 WARNING: Socket file /tmp/clamd exists. 
Unclean shutdown? Removing...
@400045e24ff50821b404 WARNING: Socket file /tmp/clamd exists. 
Unclean shutdown? Removing...

@400045e24ff509fcfbe4 Unix socket file /tmp/clamd
@400045e24ff509fdda8c Unix socket file /tmp/clamd
@400045e24ff509fe578c Setting connection queue length to 15
@400045e24ff509fec4ec Setting connection queue length to 15
@400045e24ff509ff5d44 Listening daemon: PID: 2232
@400045e24ff509ffce8c Listening daemon: PID: 2232
@400045e24ff50a00535c Archive: Archived file size limit set to 
10485760 bytes.
@400045e24ff50a00c4a4 Archive: Archived file size limit set to 
10485760 bytes.

@400045e24ff50a0135ec Archive: Recursion level limit set to 8.
@400045e24ff50a01a34c Archive: Recursion level limit set to 8.
@400045e24ff50a0210ac Archive: Files limit set to 1000.
@400045e24ff50a0281f4 Archive: Files limit set to 1000.
@400045e24ff50a02ef54 Archive: Compression ratio limit set to 250.
@400045e24ff50a035cb4 Archive: Compression ratio limit set to 250.
@400045e24ff50a03cdfc Archive support enabled.
@400045e24ff50a043774 Archive support enabled.
@400045e24ff50a04b08c Algorithmic detection enabled.
@400045e24ff50a051a04 Algorithmic detection enabled.
@400045e24ff50a061404 Portable Executable support enabled.
@400045e24ff50a068164 Portable Executable support enabled.
@400045e24ff50a06eec4 ELF support enabled.
@400045e24ff50a07583c ELF support enabled.
@400045e24ff50a07cd6c Mail files support enabled.
@400045e24ff50a0836e4 Mail files support enabled.
@400045e24ff50a08ac14 Mail: Recursion level limit set to 64.
@400045e24ff50a091974 Mail: Recursion level limit set to 64.
@400045e24ff50a0986d4 OLE2 support enabled.
@400045e24ff50a09f04c OLE2 support enabled.
@400045e24ff50a0a5dac HTML support enabled.
@400045e24ff50a0ac724 HTML support enabled.
@400045e24ff50a0b403c Self checking every 1800 seconds.
@400045e24ff50a0bad9c Self checking every 1800 seconds.
@400045e251bf2dda1efc 
/var/qmail/simscan/1172459957.86416.2873/addr.1172459957.86416.2873: OK
@400045e251bf2ddb3c24 
/var/qmail/simscan/1172459957.86416.2873/addr.1172459957.86416.2873: OK
@400045e251bf2e30842c 
/var/qmail/simscan/1172459957.86416.2873/textfile1: OK
@400045e251bf2e3162d4 
/var/qmail/simscan/1172459957.86416.2873/textfile1: OK
@400045e251bf301adf6c 
/var/qmail/simscan/1172459957.86416.2873/textfile2: OK
@400045e251bf301bba2c 
/var/qmail/simscan/1172459957.86416.2873/textfile2: OK

@400045e252d60da2e9d4 +++ Started at Sun Feb 25 19:23:55 2007
@400045e252d60da2f974 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386, 
CPU: i686)

@400045e252d60da3052c Log file size limited to 1048576 bytes.
@400045e252d60da30cfc Reading databases from /usr/share/clamav
@400045e252db23f55c44 Loaded 94737 signatures.
@400045e252db2468175c ERROR: Socket file /tmp/clamd is in use by 
another process.
@400045e252db2469386c ERROR: Socket file /tmp/clamd is in use by 
another process.

@400045e252db2777a91c +++ Started at Sun Feb 25 19:24:01 2007
@400045e252db2777bca4 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386, 
CPU: i686)

@400045e252db2777c474 Log file size limited to 1048576 bytes.
@400045e252db2777d02c Reading databases from /usr/share/clamav
@400045e252e0090b067c Loaded 94737 signatures.
@400045e252e00985281c ERROR: Socket file /tmp/clamd is in use by 
another process.
@400045e252e009864544 ERROR: Socket file /tmp/clamd is in use by 
another process.

@400045e252e01708a8ec +++ Started at Sun Feb 25 19:24:06 2007
@400045e252e01708bc74 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386, 
CPU: i686)

@400045e252e01708c444 Log file size limited to 1048576 bytes.
@400045e252e01708cffc Reading databases from /usr/share/clamav
@400045e252e5065bfbac Loaded 94737 signatures.
@400045e252e506d0e55c ERROR: Socket file /tmp/clamd is in use by 
another process.
@400045e252e506d2066c ERROR: Socket file /tmp/clamd is in use by 
another process.

@400045e252e5078d99f4 +++ Started at Sun Feb 25 19:24:11 2007
@400045e252e5078db164 clamd daemon 0.90 (OS: linux-gnu, ARCH: i386, 
CPU: i686)

@400045e252e5078db934 Log file size limited to 1048576 bytes.
@400045e252e5078dc4ec Reading databases from /usr/share/clamav
@400045e252e

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

Does clamd log show anything?

Erik Grammer wrote:
> When I reboot the server and then run: ps -el | grep 'Z' I get nothing.
>I have to stop, then start qmail to replicate the problem.  Then I get-
> 
> ps -el | grep 'Z' returns:
> F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY  TIME CMD
> 4 Z 0  3441  3391  0  81   0 - 0 exit   pts/100:00:00
> supervise 
> 
> # ps -aux |more returns:
> root  3605  0.0  0.0  0 0 pts/1Z18:56   0:00
> [supervise] 
> 
> 
> not sure what to do with that.  When I bring down qmail I get nothing
> from ps -el | grep 'Z'  It only shows a zombie when I stop and then
> start qmail.  But this also happens when I am not manually
> stopping/starting qmail so I'm not sure what is causing the problem.
> 
> Thanks,
> -Erik G.
> 
> 
> Eric "Shubes" wrote:
>> It sounds like you have a zombie clamd running. If pid 3282 is still
>> running, kill it, and supervise should start it back up again.
>>
>> If it doesn't restart on its own, bring down qmail, check for any
>> zombies,
>> then restart qmail.
>>
>> HTH.
>>
>> Erik Grammer wrote:
>>> Hi all,
>>>
>>> Running fully updated toaster (as of 2/23/07) on fedora 4.  Prior to the
>>> full update I manually updated clamav with the devel package on Erik's
>>> site and started receiving the following error on restarting qmail:
>>>
>>> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
>>> failure
>>>
>>> I removed the clamav package and then went to a full update using
>>> 'qtp-newmodel' Everything went smoothly with the updates and outgoing
>>> mail is fine and incoming works after a server reboot but somewhere
>>> along the line mail stops coming in.  Restarting qmail returns:
>>>
>>> Starting qmail-toaster: svscan.
>>>
>>> and then:
>>>
>>> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
>>> failure
>>>
>>> qmailctl stat returns:
>>>
>>> authlib: up (pid 437) 8 seconds
>>> clamd: up (pid 3282) 88511 seconds, want down
>>> imap4: up (pid 419) 9 seconds
>>> imap4-ssl: up (pid 431) 6 seconds
>>> pop3: up (pid 403) 9 seconds
>>> pop3-ssl: up (pid 494) 4 seconds
>>> send: up (pid 425) 9 seconds
>>> smtp: up (pid 459) 7 seconds
>>> spamd: up (pid 413) 9 seconds
>>> submission: up (pid 445) 8 seconds
>>> authlib/log: up (pid 442) 8 seconds
>>> clamd/log: up (pid 455) 7 seconds
>>> imap4/log: up (pid 422) 9 seconds
>>> imap4-ssl/log: up (pid 433) 8 seconds
>>> pop3/log: up (pid 406) 9 seconds
>>> pop3-ssl/log: up (pid 472) 5 seconds
>>> send/log: up (pid 411) 8 seconds
>>> smtp/log: up (pid 462) 6 seconds
>>> spamd/log: up (pid 415) 9 seconds
>>> submission/log: up (pid 452) 5 seconds
>>>
>>> I thought I had seen an email on the list from Erik about a bug in the
>>> Clamav package that had been fixed but I can't find the email and am now
>>> at a loss.  Any help would be appreciated.
>>>
>>> Thanks,
>>> -Erik G.
>>>
>>
>>
> 
> 
> -
> QmailToaster hosted by: VR Hosted 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Erik Grammer]

When I reboot the server and then run: ps -el | grep 'Z' I get nothing. 
   I have to stop, then start qmail to replicate the problem.  Then I get-


ps -el | grep 'Z'   returns:
F S   UID   PID  PPID  C PRI  NI ADDR SZ WCHAN  TTY  TIME CMD
4 Z 0  3441  3391  0  81   0 - 0 exit   pts/100:00:00 
supervise 


# ps -aux |more returns:
root  3605  0.0  0.0  0 0 pts/1Z18:56   0:00 
[supervise] 



not sure what to do with that.  When I bring down qmail I get nothing 
from ps -el | grep 'Z'  It only shows a zombie when I stop and then 
start qmail.  But this also happens when I am not manually 
stopping/starting qmail so I'm not sure what is causing the problem.


Thanks,
-Erik G.


Eric "Shubes" wrote:

It sounds like you have a zombie clamd running. If pid 3282 is still
running, kill it, and supervise should start it back up again.

If it doesn't restart on its own, bring down qmail, check for any zombies,
then restart qmail.

HTH.

Erik Grammer wrote:

Hi all,

Running fully updated toaster (as of 2/23/07) on fedora 4.  Prior to the
full update I manually updated clamav with the devel package on Erik's
site and started receiving the following error on restarting qmail:

# supervise: fatal: unable to acquire clamd/supervise/lock: temporary
failure

I removed the clamav package and then went to a full update using
'qtp-newmodel' Everything went smoothly with the updates and outgoing
mail is fine and incoming works after a server reboot but somewhere
along the line mail stops coming in.  Restarting qmail returns:

Starting qmail-toaster: svscan.

and then:

# supervise: fatal: unable to acquire clamd/supervise/lock: temporary
failure

qmailctl stat returns:

authlib: up (pid 437) 8 seconds
clamd: up (pid 3282) 88511 seconds, want down
imap4: up (pid 419) 9 seconds
imap4-ssl: up (pid 431) 6 seconds
pop3: up (pid 403) 9 seconds
pop3-ssl: up (pid 494) 4 seconds
send: up (pid 425) 9 seconds
smtp: up (pid 459) 7 seconds
spamd: up (pid 413) 9 seconds
submission: up (pid 445) 8 seconds
authlib/log: up (pid 442) 8 seconds
clamd/log: up (pid 455) 7 seconds
imap4/log: up (pid 422) 9 seconds
imap4-ssl/log: up (pid 433) 8 seconds
pop3/log: up (pid 406) 9 seconds
pop3-ssl/log: up (pid 472) 5 seconds
send/log: up (pid 411) 8 seconds
smtp/log: up (pid 462) 6 seconds
spamd/log: up (pid 415) 9 seconds
submission/log: up (pid 452) 5 seconds

I thought I had seen an email on the list from Erik about a bug in the
Clamav package that had been fixed but I can't find the email and am now
at a loss.  Any help would be appreciated.

Thanks,
-Erik G.







-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] clamav upgrade problem with supervise/lock

[Eric \"Shubes\"]

It sounds like you have a zombie clamd running. If pid 3282 is still
running, kill it, and supervise should start it back up again.

If it doesn't restart on its own, bring down qmail, check for any zombies,
then restart qmail.

HTH.

Erik Grammer wrote:
> Hi all,
> 
> Running fully updated toaster (as of 2/23/07) on fedora 4.  Prior to the
> full update I manually updated clamav with the devel package on Erik's
> site and started receiving the following error on restarting qmail:
> 
> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
> failure
> 
> I removed the clamav package and then went to a full update using
> 'qtp-newmodel' Everything went smoothly with the updates and outgoing
> mail is fine and incoming works after a server reboot but somewhere
> along the line mail stops coming in.  Restarting qmail returns:
> 
> Starting qmail-toaster: svscan.
> 
> and then:
> 
> # supervise: fatal: unable to acquire clamd/supervise/lock: temporary
> failure
> 
> qmailctl stat returns:
> 
> authlib: up (pid 437) 8 seconds
> clamd: up (pid 3282) 88511 seconds, want down
> imap4: up (pid 419) 9 seconds
> imap4-ssl: up (pid 431) 6 seconds
> pop3: up (pid 403) 9 seconds
> pop3-ssl: up (pid 494) 4 seconds
> send: up (pid 425) 9 seconds
> smtp: up (pid 459) 7 seconds
> spamd: up (pid 413) 9 seconds
> submission: up (pid 445) 8 seconds
> authlib/log: up (pid 442) 8 seconds
> clamd/log: up (pid 455) 7 seconds
> imap4/log: up (pid 422) 9 seconds
> imap4-ssl/log: up (pid 433) 8 seconds
> pop3/log: up (pid 406) 9 seconds
> pop3-ssl/log: up (pid 472) 5 seconds
> send/log: up (pid 411) 8 seconds
> smtp/log: up (pid 462) 6 seconds
> spamd/log: up (pid 415) 9 seconds
> submission/log: up (pid 452) 5 seconds
> 
> I thought I had seen an email on the list from Erik about a bug in the
> Clamav package that had been fixed but I can't find the email and am now
> at a loss.  Any help would be appreciated.
> 
> Thanks,
> -Erik G.
> 


-- 
-Eric 'shubes'

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: [qmailtoaster] ClamAV upgrade

[Carrigan, Jeremy]

Ray, you fixed my problem.  Much appreciated.

Jeremy

-Original Message-
From: Ray Van Dolson [mailto:[EMAIL PROTECTED] 
Sent: Friday, April 14, 2006 2:27 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] ClamAV upgrade

On Fri, Apr 14, 2006 at 02:19:26PM -0400, Carrigan, Jeremy wrote:
> I upgraded ClamAV to version 0.88.1 yet when I view the e-mail header
it still
> shows 0.87.1 as follows:
> 
> Received: by simscan 1.1.0 ppid: 8736, pid: 8737, t: 2.8075s
> 
>  scanners: clamav: 0.87.1/m:36/d:1365 spam: 3.1.1
> 
> X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on qmail
> 
> X-Spam-Level:
> 
> X-Spam-Status: No, score=-2.0 required=4.0 tests=BAYES_00,
> 
> MSGID_FROM_MTA_HEADER autolearn=ham version=3.1.1
> 
> Is there a way I can change this?

You probably need to run /var/qmail/bin/simscanmk -g

Ray

-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
 QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [qmailtoaster] ClamAV upgrade

[Ray Van Dolson]

On Fri, Apr 14, 2006 at 02:19:26PM -0400, Carrigan, Jeremy wrote:
> I upgraded ClamAV to version 0.88.1 yet when I view the e-mail header it still
> shows 0.87.1 as follows:
> 
> Received: by simscan 1.1.0 ppid: 8736, pid: 8737, t: 2.8075s
> 
>  scanners: clamav: 0.87.1/m:36/d:1365 spam: 3.1.1
> 
> X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on qmail
> 
> X-Spam-Level:
> 
> X-Spam-Status: No, score=-2.0 required=4.0 tests=BAYES_00,
> 
> MSGID_FROM_MTA_HEADER autolearn=ham version=3.1.1
> 
> Is there a way I can change this?

You probably need to run /var/qmail/bin/simscanmk -g

Ray

-
 QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]