Colin,
Mike reported the same yesterday. The code changes have not solved the
problem. Try to use the workaround with 'delaySameIPorHelo' for some time
- let's see.
Jun-04-12 23:37:59 m1-42278-05809 [Worker_2] 173.231.177.84 ...
Message-Score: added -1 for 173.231.177 in griplist (0.19), total score
for this message is now -1
Jun-04-12 23:37:59 m1-42278-08953 [Worker_4] 173.231.177.84 ...
Message-Score: added -1 for 173.231.177 in griplist (0.19), total score
for this message is now -1
Jun-04-12 23:38:02 m1-42278-08953 [Worker_4] 173.231.177.84 ...
Message-Score: added -1 (spfpValencePB) for SPF pass, total score for this
message is now -2
Jun-04-12 23:38:02 m1-42278-05809 [Worker_2] 173.231.177.84 ...
Message-Score: added -1 (spfpValencePB) for SPF pass, total score for this
message is now -2
This shows, the Worker_4 was running a bit faster than Worker_2 - this is
normal and could happen. In this case the serialization of the workers in
some code parts does'nt help.
It is strange - I've done some stress tests running two or more threads,
which accessing the same shared variables and/or BerkeleyDB entries over
some minutes.
All results were like expected. I saw no crash. I think that this issue is
somehow related to the OS and/or perl in sum - it also explains why I
never had this issue in assp.
For this reason it makes IMHO no sense to try the serialization of the
workers anywhere in the middle of the code.
If the workaround with the 'delaySameIPorHelo' works, I'll make this quick
and dirty code much more better.
All of you, who had this problem, please add the following lines to the
file ../lib/CorrectASSPcfg.pm and use at least assp 2.2.2 build 12151.
$main::delaySameIPorHelo = 5;
&main::mlog(0,"info: delaySameIPorHelo is set to 5 ");
Thank you.
Thomas
Von: Colin <[email protected]>
An: ASSP development mailing list <[email protected]>,
Datum: 05.06.2012 22:53
Betreff: [Assp-test] Crashes on multiple connections
Hi all,
Just an update on the issue, I have had less problems (possibly due to
the long bank holiday meaning there is less traffic) but it still
appears to be happening. ASSP has bailed out a couple of times over the
last few days with two similar threads being handled from the same IP.
Any more info that can help with the continued troubleshooting?
All the best,
Colin.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
