--0-243897229-1207493105=:39436
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

For sake of completeness I would like to send out the solution to this, in case anyone else is also having the same porblem.
It seems like there is a problem with forking on FreeBSD 6.3:
http://www.freebsd.org/cgi/query-pr.cgi?pr=119920

The solution to fix this problem is to edit the file /etc/libmap.conf (create it if it doesn't exist) and add the following line to it:

libpthread.so.2 libthr.so.2

This will globally map libpthread to libthr.

You have to restart all the processes that link against libpthread.so.2 in order for the libmap.conf change to take effect.

Thanks to Lawrence Stewart for the above solution.

Aflatoon


Aflatoon Aflatooni wrote:
Here is anothe occurance of this problem:

Mar 2 14:40:22 sara sm-mta[85764]: m22JeJxE085764: from=, size=1678, class=0, nrcpts=1, msgid=<108401c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar 2 14:40:22 sara sm-mta[85765]: m22JeJEu085765: from=, size=1629, class=0, nrcpts=1, msgid=<108501c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar 2 14:40:22 sara sm-mta[85766]: m22JeJ8l085766: from=, size=1553, class=0, nrcpts=1, msgid=<108601c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar 2 14:40:22 sara sm-mta[85767]: m22JeJh2085767: from=, size=1574, class=0, nrcpts=1, msgid=<108701c87c9d$0baf59d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar 2 14:40:22 sara spamd[64309]: spamd: connection from localhost [127.0.0.1] at port 53850
Mar 2 14:40:22 sara spamd[64309]: spamd: processing message <108701c87c9d$0baf59d0$391e8f56@Eve> for root:58
Mar 2 14:40:27 sara spamd[64309]: spamd: identified spam (22.1/5.0) for root:58 in 4.9 seconds, 1944 bytes.

I am using spamassassin version 3.2.3 on FreeBSD 6.3.
It looks like if similar messages are checked through spam-milter it causes a problem and the spam-milter goes to 99% cpu utilization.
Is this a bug? has anyone else encountered this?

Thanks


Aflatoon Aflatooni wrote:
Hi,
I have installed spamassassin on my freebsd 6.3 and everything works great but after some time (it could be couple of days, or hours) the CPU utilization on spamass-milter goes to almost 100%.
I have discovered that the following messages cause the 100% utilization:

Feb 29 04:22:32 sara sm-mta[27844]: m1T9MQ2W027844: from=, size=1721, class=0, nrcpts=1, msgid=, proto=SMTP, daemon=IPv4, relay=[58.137.142.102]
Feb 29 04:22:32 sara sm-mta[27845]: m1T9MQgb027845: from=, size=1737, class=0, nrcpts=1, msgid=, proto=SMTP, daemon=IPv4, relay=[58.137.142.102]
Feb 29 04:22:32 sara spamd[27027]: spamd: connection from localhost [127.0.0.1] at port 61494
Feb 29 04:22:32 sara spamd[27027]: spamd: processing message for root:58


Notice that sendmail receives two messages from the same relay by the same person with almost the same msgid, one is a057... and the other one is a056...
You see from the log that the second one is processed by spamd, but the first one causes the high cpu utilization in spam-milter. Since it is spam-milter and not sendmail that is having problem I am thinking that there is something in that message that is not liked by SpamAssassin.
How can I get more information logged about the message so I can find the root-cause? Has anyone else come across this problem?

I have also posted this problem on bsdforums, because I wasn't sure if it is a problem with freebsd:
http://www.bsdforums.org/forums/show...253#post289253

Many thanks
Aflatoon

---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.


---------------------------------
Looking for last minute shopping deals? Find them fast with Yahoo! Search.



---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
--0-243897229-1207493105=:39436
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

For sake of completeness I would like to send out the solution to this, in case anyone else is also having the same porblem.
It seems like there is a problem with forking on FreeBSD 6.3:
 
The solution to fix this problem is to edit the file /etc/libmap.conf (create it if it doesn't exist) and add the following line to it:
 
libpthread.so.2 libthr.so.2
This will globally map libpthread to libthr.

You have to restart all the processes that link against libpthread.so.2 in order for the libmap.conf change to take effect.
Thanks to Lawrence Stewart for the above solution.
 
Aflatoon


Aflatoon Aflatooni <aaflatooni@yahoo.com> wrote:
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
Here is anothe occurance of this problem:
 
Mar  2 14:40:22 sara sm-mta[85764]: m22JeJxE085764: from=<jr@waldorf.edu>, size=1678, class=0, nrcpts=1, msgid=<108401c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar  2 14:40:22 sara sm-mta[85765]: m22JeJEu085765: from=<jr@waldorf.edu>, size=1629, class=0, nrcpts=1, msgid=<108501c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar  2 14:40:22 sara sm-mta[85766]: m22JeJ8l085766: from=<jr@waldorf.edu>,
size=1553, class=0, nrcpts=1, msgid=<108601c87c9d$0bace8d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar  2 14:40:22 sara sm-mta[85767]: m22JeJh2085767: from=<jr@waldorf.edu>, size=1574, class=0, nrcpts=1, msgid=<108701c87c9d$0baf59d0$391e8f56@Eve>, proto=SMTP, daemon=IPv4, relay=host86-143-30-57.range86-143.btcentralplus.com [86.143.30.57]
Mar  2 14:40:22 sara spamd[64309]: spamd: connection from localhost [127.0.0.1] at port 53850
Mar  2 14:40:22 sara spamd[64309]: spamd: processing message <108701c87c9d$0baf59d0$391e8f56@Eve> for root:58
Mar  2 14:40:27 sara spamd[64309]: spamd: identified spam (22.1/5.0) for root:58 in 4.9 seconds, 1944
bytes.
I am using spamassassin version 3.2.3 on FreeBSD 6.3.
It looks like if similar messages are checked through spam-milter it causes a problem and the spam-milter goes to 99% cpu utilization.
Is this a bug? has anyone else encountered this?

Thanks
 

Aflatoon Aflatooni  wrote:
Hi,
I have installed spamassassin on my freebsd 6.3 and everything works great but after some time (it could be couple of days, or hours) the CPU utilization on spamass-milter goes to almost 100%.
I have discovered that the following messages cause the 100% utilization:
 
Feb 29 04:22:32 sara sm-mta[27844]: m1T9MQ2W027844: from=<jramirez@central.unicor.gov>, size=1721, class=0, nrcpts=1,
msgid=<a05701c87ab4$75e14a60$c0a80c59@Quinn>, proto=SMTP, daemon=IPv4, relay=[58.137.142.102]
Feb 29 04:22:32 sara sm-mta[27845]: m1T9MQgb027845: from=<jramirez@central.unicor.gov>, size=1737, class=0, nrcpts=1, msgid=<a05601c87ab4$75e14a60$c0a80c59@Quinn>, proto=SMTP, daemon=IPv4, relay=[58.137.142.102]
Feb 29 04:22:32 sara spamd[27027]: spamd: connection from localhost [127.0.0.1] at port 61494
Feb 29 04:22:32 sara spamd[27027]: spamd: processing message <a05601c87ab4$75e14a60$c0a80c59@Quinn> for root:58
 
 
Notice that sendmail receives two messages from the same relay by the same person with almost the same msgid, one is a057... and the other one is a056...
You see from the log that the second one is processed by spamd, but the first one causes the high cpu utilization in spam-milter. Since it is spam-milter and not sendmail that is having problem I am thinking that there is something in
that message that is not liked by SpamAssassin.
How can I get more information logged about the message so I can find the root-cause? Has anyone else come across this problem?
 
I have also posted this problem on bsdforums, because I wasn't sure if it is a problem with freebsd:
 
Many thanks
Aflatoon

Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now.


Looking for last minute shopping deals? Find them fast with
Yahoo! Search.




You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.
--0-243897229-1207493105=:39436--