This issue is under investigation. It is caused by the DBD::mysql driver 
(-> MySQL-server ??) on some systems (OS - linux).
ASSP crashes if at least two different workers accessing the same DB table 
at exacly the same time.
Normaly this should be no problem, because the MySQL engine locking 
mechanism is designed to manage such cases.

I'm just testing a workaraound for this problem.

Thomas



Von:    Colin <a...@lanternhosting.co.uk>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>, 
Datum:  28.11.2012 17:00
Betreff:        [Assp-test] Recurring Problem 2 - ASSP crash on similar 
connections



Hi again,

There were some changes not too long back that addressed this. 
Unfortunately I am still seeing ASSP crashes every now and then where 
there are two similar connections hitting at the same time.

The first example is a mailing list hitting two different customers on 
different domains at the same time.

The second example is a mailing list hitting two different email 
addresses on the same domain at the same time.

The third example is on of our off site monitoring platforms. It sent us 
5 alerts simultaneously and hit 5 different workers. ASSP didn't even 
get past the MAIL FROM before it died.

Sorry to be the bearer of bad news but the bug has not been completely 
squished!

All the best,
Colin Waring.

2012-11-20 08:30:22 [Main_Thread] Info: Main_Thread got connection request
2012-11-20 08:30:22 [Worker_2] Worker_2 wakes up
2012-11-20 08:30:22 [Worker_2] Info: Worker_2 got connection from 
MainThread
2012-11-20 08:30:22 [Worker_2] Connected: 204.232.163.44:36472 > 
195.88.101.109:25 > 127.0.0.1:125
2012-11-20 08:30:22 [Worker_2] 204.232.163.44 [SMTP Reply] 220 
mail2.smtphost.co.uk ESMTP Exim 4.76 Tue, 20 Nov 2012 08:30:22 +0000
2012-11-20 08:30:22 [Main_Thread] Info: Main_Thread freed by idle 
Worker_2 in 0.060 seconds
2012-11-20 08:30:22 [Worker_1] 204.232.163.44 [SMTP Reply] 250 HELP
2012-11-20 08:30:22 [Worker_2] 204.232.163.44 [SMTP Reply] 250 HELP
2012-11-20 08:30:22 [Worker_1] 204.232.163.44 info: injected STARTTLS 
request to 127.0.0.1
2012-11-20 08:30:22 [Worker_2] 204.232.163.44 info: injected STARTTLS 
request to 127.0.0.1
2012-11-20 08:30:22 m1-00222-13588 [Worker_1] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer1=domain1....@mail44.us1.mcsv.net> 
[SMTP Reply] 250 OK
2012-11-20 08:30:22 m1-00222-09405 [Worker_2] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer2=domain2....@mail44.us1.mcsv.net> 
[SMTP Reply] 250 OK
2012-11-20 08:30:23 m1-00222-13588 [Worker_1] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer1=domain1....@mail44.us1.mcsv.net> 
to: custom...@domain1.tld [SMTP Reply] 250 Accepted
2012-11-20 08:30:23 m1-00222-09405 [Worker_2] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer2=domain2....@mail44.us1.mcsv.net> 
to: custom...@domain2.tld [SMTP Reply] 250 Accepted
2012-11-20 08:30:23 m1-00222-13588 [Worker_1] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer1=domain1....@mail44.us1.mcsv.net> 
to: custom...@domain1.tld [SMTP Reply] 354 Enter message, ending with 
"." on a line by itself
2012-11-20 08:30:23 m1-00222-09405 [Worker_2] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer2=domain2....@mail44.us1.mcsv.net> 
to: custom...@domain2.tld [SMTP Reply] 354 Enter message, ending with 
"." on a line by itself
2012-11-20 08:30:23 m1-00222-13588 [Worker_1] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer1=domain1....@mail44.us1.mcsv.net> 
to: custom...@domain1.tld DKIM-Signature found
2012-11-20 08:30:23 m1-00222-09405 [Worker_2] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer2=domain2....@mail44.us1.mcsv.net> 
to: custom...@domain2.tld DKIM-Signature found
2012-11-20 08:30:23 m1-00222-13588 [Worker_1] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer1=domain1....@mail44.us1.mcsv.net> 
to: custom...@domain1.tld Received-RWL:  from 
(list.dnswl.org->127.0.15.0,trust=0 (category=Email Marketing 
Providers);) - high trust is 0 - client-ip=204.232.163.44
2012-11-20 08:30:23 m1-00222-09405 [Worker_2] [TLS-out] 204.232.163.44 
<bounce-mc.us5_9552969.12581-customer2=domain2....@mail44.us1.mcsv.net> 
to: custom...@domain2.tld Received-RWL:  from 
(list.dnswl.org->127.0.15.0,trust=0 (category=Email Marketing 
Providers);) - high trust is 0 - client-ip=204.232.163.44


2012-11-26 07:47:52 [Worker_3] Disconnected: 81.168.74.225 - processing 
time 1 seconds
2012-11-26 07:47:52 [Worker_3] Worker_3 will sleep now
2012-11-26 07:47:52 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [SMTP Reply] 250 Accepted
2012-11-26 07:47:52 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [SMTP Reply] 250 Accepted
2012-11-26 07:47:52 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [SMTP Reply] 354 Enter message, ending with "." on 
a line by itself
2012-11-26 07:47:52 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [SMTP Reply] 354 Enter message, ending with "." on 
a line by itself
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld DKIM-Signature found
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld DKIM-Signature found
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added -4 for 209.85.219 in griplist 
(0.02), total score for this message is now -4
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added -4 for 209.85.219 in griplist 
(0.02), total score for this message is now -4
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added -10 (spfpValencePB) for SPF 
pass, total score for this message is now -14
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added -10 (spfpValencePB) for SPF 
pass, total score for this message is now -14
2012-11-26 07:47:53 [Worker_2] Info: weighted regex (bombHeaderRe) 
result found for DKIM-Signature - with DKIM-Signature - weight is 0.1
2012-11-26 07:47:53 [Worker_1] Info: weighted regex (bombHeaderRe) 
result found for DKIM-Signature - with DKIM-Signature - weight is 0.1
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Regex:BombHeaderRe 'PB 2: for DKIM-Signature'
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Regex:BombHeaderRe 'PB 2: for DKIM-Signature'
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
[BombHeaderRe] 209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [scoring] (BombHeaderRe 'DKIM-Signature')
2012-11-26 07:47:53 m1-16071-10927 [Worker_2] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykijaehyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added 2 for BombHeaderRe 
'DKIM-Signature', total score for this message is now -12
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
[BombHeaderRe] 209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld [scoring] (BombHeaderRe 'DKIM-Signature')
2012-11-26 07:47:53 m1-16071-09787 [Worker_1] [TLS-in] [TLS-out] 
209.85.219.72 
<3pr6zubekbdojknalhu+baazlnktuckkcha.ykiiwngyknwhldkjao.yk...@feedburner.bounces.google.com>
 

to: ema...@domain.tld Message-Score: added 2 for BombHeaderRe 
'DKIM-Signature', total score for this message is now -12


2012-11-27 22:55:25 [Worker_4] 1.1.1.1 info: sending EHLO instead of 
HELO to 127.0.0.1
2012-11-27 22:55:25 [Worker_1] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:25 [Worker_5] 1.1.1.1 [SMTP Reply] 220 
mail.smtphost.co.uk ESMTP Exim 4.76 Tue, 27 Nov 2012 22:55:25 +0000
2012-11-27 22:55:25 [Worker_3] 1.1.1.1 [SMTP Reply] 250 OK
2012-11-27 22:55:25 [Worker_6] 1.1.1.1 [SMTP Reply] 220 
mail.smtphost.co.uk ESMTP Exim 4.76 Tue, 27 Nov 2012 22:55:25 +0000
2012-11-27 22:55:25 [Worker_2] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:25 [Worker_5] 1.1.1.1 info: sending EHLO instead of 
HELO to 127.0.0.1
2012-11-27 22:55:25 [Worker_6] 1.1.1.1 info: sending EHLO instead of 
HELO to 127.0.0.1
2012-11-27 22:55:25 [Worker_3] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:25 [Worker_5] 1.1.1.1 [SMTP Reply] 250 OK
2012-11-27 22:55:25 [Worker_4] 1.1.1.1 [SMTP Reply] 250 OK
2012-11-27 22:55:25 [Worker_6] 1.1.1.1 [SMTP Reply] 250 OK
2012-11-27 22:55:25 [Worker_5] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:25 [Worker_4] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:25 [Worker_6] 1.1.1.1 info: injected STARTTLS request 
to 127.0.0.1
2012-11-27 22:55:26 m1-56926-00074 [Worker_1] [TLS-out] 1.1.1.1 
<sen...@domain.tld> [SMTP Reply] 250 OK
2012-11-27 22:55:26 m1-56926-09157 [Worker_2] [TLS-out] 1.1.1.1 
<sen...@domain.tld> [SMTP Reply] 250 OK
2012-11-27 22:55:26 m1-56926-09511 [Worker_3] [TLS-out] 1.1.1.1 
<sen...@domain.tld> [SMTP Reply] 250 OK
2012-11-27 22:55:26 m1-56926-06104 [Worker_5] [TLS-out] 1.1.1.1 
<sen...@domain.tld> [SMTP Reply] 250 OK
2012-11-27 22:55:26 m1-56926-12346 [Worker_4] [TLS-out] 1.1.1.1 
<sen...@domain.tld> [SMTP Reply] 250 OK

------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
INSIGHTS What's next for parallel hardware, programming and related areas?
Interviews and blogs by thought leaders keep you ahead of the curve.
http://goparallel.sourceforge.net
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
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!
*******************************************************


------------------------------------------------------------------------------
Keep yourself connected to Go Parallel: 
VERIFY Test and improve your parallel project with help from experts 
and peers. http://goparallel.sourceforge.net
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to