Same issue here, now every day I have to restart dspam.
Jan 31 00:35:57 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:42:33 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:44:31 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:47:49 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:49:22 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:50:54 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:52:42 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:54:35 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:56:07 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 00:57:11 localhost dspam[2833]: Thread creation failed: Cannot allocate
memory
Jan 31 01:16:06 localhost postfix/qmgr[2935]: fatal: watchdog timeout
--On Monday, December 18, 2006 3:20 PM +0000 Samuel Clough <[EMAIL PROTECTED]>
wrote:
Most systems limit threads per process. Perhaps you've exceeded that limit?
HP-UX, for example, IIRC sets that limit fairly low initially.
On Mon, 18 Dec 2006 15:56:21 +0100, Matteo Sgalaberni <[EMAIL PROTECTED]> wrote:
Hi,
I have a problem with dspam(dspam3.6.8)
It's configured with TOE and with the pgsql driver. I have a db of about
13 gigabyte.
the problem is:
24958: [12/18/2006 13:15:17] Thread creation failed: Cannot allocate
memory
but the server does not seem to have the memory exhausted.
I made a vacuum analyze and seems that there are
not dead rows in the db, so the database it's efficient and consistent,
the vacuum process is making its work.
Have you some ideas ?
Thanks
Matteo
