>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.
; From: [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.25
>I know scott needs this declude debug file...
The .gp1/.gp2 files are the only reliable way we can take care of a problem
when Declude crashes and those files are created. So you are right, we do
need those files when they are created.
>but when declude crashes our system, yes it just happe
>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 repo
> >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
>wi
are http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q142676
and http://support.microsoft.com/directory/article.asp?ID=kb;en-us;Q126962 .
Thanks Scott, I know you are only trying to help and I commend your efforts on helping
us through this situation. If you remember, I was the
il server
once 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 si
>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
01 8:15 AM
To: [EMAIL PROTECTED]
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
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
>My server decided to behave for nearly a week, then last night one
>locked. Running a log level of high this is the only entries the offending
>process made:
>
>09/12/2001 20:03:36 Q05e6040 000276 Start
>09/12/2001 20:03:36 Q05e6040 000276 Locking d:\spool\Q05e6040.SMD.
>09/12/2001 20:03:36 Q05
OTECTED]
Subject: RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>My server decided to behave for nearly a week, then last night one
>locked. Running a log level of high this is the only entries the offending
>process made:
>
>09/12/2001 20:03:36 Q05e6040 000276 Start
]
[mailto:[EMAIL PROTECTED]]On Behalf Of Charles Frolick
Sent: Friday, September 14, 2001 11:36 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
I am running the console, I also have a Hijack license. With 1.20 I don't
recall ever having a lockup.
Her
riginal Message -
From: "R. Scott Perry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 12, 2001 6:58 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>
> >I know scott needs this declude debug file...
>
> The .gp1/.
>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 .
> v1.25a always crashes more than 3 to 4 times a day since we loaded
> this. We've NEVER had a Declude
>lockup prior to v1.25a and we have the ",512
.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jack Taugher
> Sent: Sunday, September 16, 2001 4:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>
>
> Where can we fin
>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
wha
half Of R. Scott Perry
> Sent: Monday, September 17, 2001 3:56 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>
>
>
> >My problems also began after upgrading to 1.25a, before the upgrade
> >Declude never crashed. Now I
t; <[EMAIL PROTECTED]>
To: <[EMAIL 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://
>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
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
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
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 t
>I downgraded from v1.25a to v1.24. This morning, 20 minutes ago, Declude
>was at 99% utilization.
FYI, this is our number #1 priority right now. It appears to only be
happening with Declude JunkMail (not with the other Declude programs,
unless Declude JunkMail is running as well). We are t
lt;[EMAIL PROTECTED]>
Sent: Friday, September 21, 2001 2:51 PM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>
> >I downgraded from v1.25a to v1.24. This morning, 20 minutes ago, Declude
> >was at 99% utilization.
>
> FYI, this is our number #1
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 fi
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
[E
>What are the major differences between 1.23 and 1.24+
>
>If 1.23 fixes our problem, then I want to downgrade.
You can find the release notes at http://www.declude.com/relnotes.htm to
see the differences. FYI, 1.23 is an older beta version that is
technically unsupported (which really means t
I've got a PID for you. Declude was running at 95% for 8hrs 12mins.
I am running v1.26. We are using McAfee's Command Line Interface Scanner.
> Please be aware that it is very unlikely that the 99% CPU issue will go
> away until one of the people experiencing it runs the interim (or later)
>
>I've got a PID for you. Declude was running at 95% for 8hrs 12mins.
Thanks. That will help quite a bit in tracking down the problem. It looks
like it may be within the DNS engine.
Would it be possible to look at the IMail \IMail\spool\sys0924.txt log
file, and look at around 1:09AM to see
[Declude.JunkMail] Declude crashing and taking up 99% CPU
> >I've got a PID for you. Declude was running at 95% for 8hrs 12mins.
>
> Thanks. That will help quite a bit in tracking down the problem. It
looks
> like it may be within the DNS engine.
>
> Would it be possib
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 thin
>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 declude.
EMAIL 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
I stand corrected, but the purpose is the same.
Thanks,
_M
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]]On Behalf Of R. Scott Perry
| Sent: Tuesday, September 25, 2001 11:16 AM
| To: [EMAIL PROTECTED]
| Subject: RE: [Declude.JunkMail] Declude crashing and
a helpful glimpse.
Sorry for rambling.
_M
| -Original Message-
| From: [EMAIL PROTECTED]
| [mailto:[EMAIL PROTECTED]]On Behalf Of Charles Frolick
| Sent: Tuesday, September 25, 2001 11:16 AM
| To: [EMAIL PROTECTED]
| Subject: RE: [Declude.JunkMail] Declude crashing and taking up 99%
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 du
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
>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
unsubscrib
process (or
wouldn't exit - couldn't tell which).
- Original Message -
From: "R. Scott Perry" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 25, 2001 10:45 AM
Subject: Re: [Declude.JunkMail] Declude crashing and taking up 99% CPU
>
&
>I now have seen it with version 1.23.
That may actually be good news, combined with not having any reports yet of
the interim release doing this (although it is too early to tell if the
interim release fixes the problem, since it can't be reproduced on
demand). I say it is good news because
43 matches
Mail list logo
