Running AMaViSd-new 2.6.3 (it was 2.6.1 until today--upgrading to 2.6.3
did not fix the issue), FreeBSD 7.0-RELEASE, perl 5.8.8.

Yesterday, my machine up and started having these issues (copied latest
crash):

(The getswapspace error repeats oh.. 6703 times total. I am cutting 6702
of them to save space:)
Jul  1 20:51:01 caduceus kernel: swap_pager_getswapspace(12): failed
(It always ends with this line (varying PIDs of course:)
Jul  1 20:51:01 caduceus kernel: pid 36486 (perl), uid 2020, was killed:
out of swap space

Now... I have a machine with 4G of RAM, and 12G of swap space.

(output of freecolor:)

                 total       used       free     shared    buffers    
cached
Mem:          4086       3737        348          0          0          8
Swap:        12288      11014       1273
Total:       16374 = (   14752 (used) +     1630 (free))

Here's the output of top when it gets ready to crash:

Last pid: 49047;  load averages:  0.39,  0.44,  0.40    up 0+05:01:13 
21:03:12
251 processes: 2 running, 239 sleeping, 1 zombie, 9 waiting
CPU states:  3.9% user,  0.0% nice,  1.9% system,  0.2% interrupt, 94.0%
idle
Mem: 3240M Active, 343M Inact, 326M Wired, 8984K Cache, 214M Buf, 6844K Free
Swap: 12G Total, 12G Used, 161M Free, 98% Inuse, 224K In, 3008K Out

  PID USERNAME       THR PRI NICE   SIZE    RES STATE  C   TIME   WCPU
COMMAND
36489 vscan            1  76    0  5838M   688M pfault 1   0:49 18.07% perl
36487 vscan            1  76    0  9935M   695M pfault 1   1:07  0.00% perl
36420 vscan            1  44    0   647M     0K WAIT   1   0:40  0.00%
<perl>
36485 vscan            1  76    0   647M 76428K pfault 1   0:18  0.00% perl
36488 vscan            1  76    0   647M 75164K pfault 1   0:18  0.00% perl
38628 vscan            1  76    0   647M 75012K pfault 0   0:08  0.00% perl

I don't understand why would this suddenly start happening, after
*years* of running AMaViSd-new. When the daemon crashes and respawns,
the machine is taken almost to the point of unusability.

Has anyone else noticed this? Is there any kind of workaround? :-/ I'm
supposed to be leaving for a road trip in the AM and I guess the
Critical Circuit<tm> decided to trip. ;-)

Thanks in advance, everyone...

Best,
--Glenn

-- 
...destination is merely a byproduct of the journey
           --Eric Hansen


------------------------------------------------------------------------------
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/amavis-user 
 AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 
 AMaViS-HowTos:http://www.amavis.org/howto/ 

Reply via email to