I have tried my best to help with this issue, research, testing, etc.
During a normal business day, declude is awesome - working very nicely as
advertised and very reliable. Perhaps, on an email server with less
traffic, some declude customers wouldn't even know of any reliability
issues. I
I have tried my best to help with this issue, research, testing, etc.
During a normal business day, declude is awesome - working very nicely as
advertised and very reliable. Perhaps, on an email server with less
traffic, some declude customers wouldn't even know of any reliability
issues.
, 2001 10:25 AM
| To: [EMAIL PROTECTED]
| Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
|
|
| I have tried my best to help with this issue, research, testing, etc.
| During a normal business day, declude is awesome - working very nicely as
| advertised and very reliable
There is a tweak for this in declude. You can set the maximum number of
decludes that will run at one time. This helps set limits in cases like
this.
Actually, the MAXATONCE option only affects the number of virus scanner
processes that are started. It does not affect the number of
PROTECTED]]On Behalf Of R. Scott Perry
Sent: Tuesday, September 25, 2001 9:45 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
I have tried my best to help with this issue, research, testing, etc.
During a normal business day, declude is awesome
and taking up 99% CPU
|
|
|
| There is a tweak for this in declude. You can set the maximum number of
| decludes that will run at one time. This helps set limits in cases like
| this.
|
| Actually, the MAXATONCE option only affects the number of virus scanner
| processes that are started. It does
We now have a new interim declude.exe online, at
http://www.declude.com/release/126/declude.exe . This one is based on
1.25a, except that the DNS engine has been modified to make sure that
infinite loops are not possible. Right now, the most likely reason for the
99% CPU usage seems to be
should we use this even if we don't have the 99% cpu problem?
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 25, 2001 6:44 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
We now have a new interim
should we use this even if we don't have the 99% cpu problem?
No, you should not. The interim release should only be used by people who
are experiencing that problem.
-Scott
---
This E-mail came from the Declude.JunkMail mailing list. To
What are the major differences between 1.23 and 1.24+
If 1.23 fixes our problem, then I want to downgrade.
Travis
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type unsubscribe Declude.JunkMail. You can E-mail
I downgraded from v1.25a to v1.24. This morning, 20 minutes ago, Declude
was at 99% utilization.
- Original Message -
As I've stated several times: I'm not getting an error message, no files
are
being created and no event log messages. (I'll double check my gigantic
log
files to be
FYI-
We now have an interim release available online at
http://www.declude.com/release/126/declude.exe that adds a new
configuration option PIDDEBUG ON, that should signifcantly help in
tracking down the 99% CPU problem.
When that line is added to the global.cfg file, Declude will save a
Scott,
I don't remember having any problems with 1.24.
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, September 17, 2001 5:13 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
As I've stated several times: I'm
Actually, I take that back. There might be a problem with 1.24 but not with
1.23.
- Original Message -
From: Frank [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, September 18, 2001 9:48 AM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Scott,
I don't
My problems also began after upgrading to 1.25a, before the upgrade
Declude never crashed. Now I need 2 reboots a day to keep my mail working.
Do you recall which version you were running before that? If I can find
out which version introduced this problem, it will be easier to find out
what
PROTECTED]
Sent: Saturday, September 15, 2001 9:53 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Where can we find v1.24 or below of Declude?
You can download the previous public release at
http://www.declude.com/release/120/declude.exe .
---
This E-mail came
As I've stated several times: I'm not getting an error message, no files are
being created and no event log messages. (I'll double check my gigantic log
files to be sure of the first..)
It appears that there are 3 separate issues (you're seeing #1):
[1] 100% CPU usage, that appears to have
a day because of this.
- Original Message -
From: R. Scott Perry [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 10:24 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
other similar information? What *exactly* does the error
If anyone has any further advise, I am eagerly, but patiently, waiting.
It seems like there aren't many (although there are some) programs that
encounter this problem. The real solution would be for Ipswitch not to
start a new process for each E-mail delivery. But, the earliest that could
We are also have a problem with Declude recently. It doesn't crash our
system per say but it causes our system to go to 100% CPU utilization,
memory usage goes way up and SMTP timesout (even though there are a lot of
STMP Declude processes showing up).
We haven't seen that here, but have had
: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry
Sent: Tuesday, September 11, 2001 14:59
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
Hello, since I upgraded to declude 1.25a sometimes the following
happens:
1. Declude
other similar information? What *exactly* does the error message say, the
complete text of it? I can't recall ever seeing NT/2000 report a crash
without at least the memory address that the crash occurred at.
user32.dll is the main text of the message. There is just the pop up
window
Hello, since I upgraded to declude 1.25a sometimes the following happens:
1. Declude logs something like this:
09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb9b1 v1.25a)
09/11/2001 04:18:48 Q743b0de (log part 1 saved as C:\declude.gp1)
09/11/2001 04:18:48 Q743b0de (Error 5 at 77fcb892 v1.25a)
23 matches
Mail list logo
