|
SA Bugzilla – Full Text Bug Listing |
Summary: | Memory & CPU hogging on network outage | ||
---|---|---|---|
Product: | Spamassassin | Reporter: | Matthias Andree <matthias.andree> |
Component: | spamc/spamd | Assignee: | SpamAssassin Developer Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jjlin |
Priority: | P5 | Keywords: | dns |
Version: | 2.41 | ||
Target Milestone: | 2.50 | ||
Hardware: | PC | ||
OS: | Linux | ||
Whiteboard: |
Description
Matthias Andree
2002-09-16 02:07:29 UTC
Ummm... I just checked in a possible fix for this. Could you check the latest CVS (HEAD branch) and try to reproduce? This does NOT fix the problem for me, regretfully. I am seeing a similiar problem with SA on Debian. I'm running version 2.41 on Debian sarge. SA is invoked through maildrop's xfilter command. Normally, things work just fine. However, from time to time, an SA process hangs around and grows to a little over 200 megs in memory usage (as reported by top) and ~100% CPU usage. Might this perchance be related to bug 1151 (http://www.hughes- family.org/bugzilla/show_bug.cgi?id=1151)? Do you have Razor1 or Razor2 enabled? Does the problem go away if you disable one or both? I don't have either Razor version activated, so there is nothing to disable here. I'm also seeing a problem like this on Solaris. According to my procmail log, this morning at about 6:30 am, procmail started reporting procmail: Timeout, terminating "/opt/really-local/bin/spamc" and by 6:50 am, it was saying procmail: Program failure (74) of "/opt/really-local/bin/spamc" for most incoming messages. By 3pm or so, when I first checked mail today, the various unterminated spamd processes were using 800 MB. This isn't the first time this has happened. I think it's happened about 3 other times, and I had thought it might have to do with the auto-whitelisting database getting pretty large (~5 MB), but I restarted spamd on 1/5 without -a, and the problem showed up just 4 days later (it usually seemed to happen about once a month or so). > I don't have either Razor version activated, so there is nothing to disable here.
Huh. Same for you, Jeremy? Other than Razor, the main ones that have had problems
recently are orbs.dorkslayers.com (RCVD_IN_ORBS) and relays.osirusoft.com (any
number of ones). And this is just with spamc/spamd? I'm wondering if socket
problems may be happening with spamd.
-Allen
Actually, no. I do have remote tests, and spamd just stopped working for several hours today. Using -L to use only local tests seems to fix the problem, so it might be that what I experienced doesn't apply to this bug after all. Will have to see if something like this happens again with the -L. Jeremy:
> Actually, no. I do have remote tests,
I'm sorry, I evidently wasn't clear enough. Do you have Razor/Razor2 going or not,
as opposed to other remote tests (DNS/RBL, DCC, Pyzor...)?
Thanks,
-Allen
Allen, yes, I have Razor1. Jeremy: > Allen, yes, I have Razor1. Hmm... that makes it uncertain whether you're having Razor (Bug 1151) or DNS problems causing this, unfortunately. Any error messages about Razor (or DNS/RBL)? -Allen Any updates on this? It looks as if the issue was caused by Razor1 going haywire. Thanks. Assuming the disabling of RAzor1 will have fixed this. If not, the reporter can reopen the bug ;) |