Daniel,

what are the settings for:

DoOrgWhiting + whiteSenderBase
DoOrgBlocking + blackSenderBase
DoCountryBlocking

CountryCodeBlockedRe
CountryCodeRe

You see I'm stepping in the dark - no clue what happens - and I'm absolute 
unable to reproduce this issue.

Thomas





Von:    "Daniel K. Du Vall" <dduv...@1peter4-10.org>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>, 
Datum:  06.10.2013 02:21
Betreff:        Re: [Assp-test] Antwort:  unable to detect any running 
worker



Thomas here is a link to the log file. 
http://volkswageninsanity.us/Postings/ASSP/maillog.zip


Daniel Du Vall
http://1peter4-10.org
http://volkswageninsanity.us

-----Original Message-----
From: Thomas Eckardt [mailto:thomas.ecka...@thockar.com] 
Sent: Friday, October 4, 2013 10:20 AM
To: ASSP development mailing list
Subject: Re: [Assp-test] Antwort: unable to detect any running worker

This seems not to be a DNS problem - the DNS part has been finished 
because the "sigon" was still processed.
Do you use any DB engine for the SBCACHE ? Check the tablespace. To check 
if the DB is the problem - set 'pbdb' back to the default.

disable all database locking - ignore this if you don't know how to enable 
it check the following regular expressions for loops (eg. back 
references):

whiteSenderBase
blackSenderBase
NoCountryCodeRe
CountryCodeBlockedRe
CountryCodeRe
MyCountryCodeRe

what was the last line written by worker 10 before this happens?

Thomas





Von:    "Daniel K. Du Vall" <dduv...@1peter4-10.org>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>, 
Datum:  04.10.2013 16:56
Betreff:        Re: [Assp-test] Antwort:  unable to detect any running 
worker



OK got the error again and I reduced the workers to 10 and its running on 
ASSP version 2.3.4(13275)

Oct-04-13 00:42:06 [Worker_10000] Backup: 1 records of database table 
AdminUsers to file /var/assp/mysql/dbbackup/adminusers
Oct-04-13 00:42:06 [Worker_10000] Backup: 1 records of database table 
AdminUsers to file /var/assp/adminusers
Oct-04-13 00:42:06 [Worker_10000] Backup: starting backup database table 
AdminUsersRight to file /var/assp/mysql/dbbackup/adminusers.right
Oct-04-13 00:42:06 [Worker_10000] Backup: 0 records of database table 
AdminUsersRight to file /var/assp/mysql/dbbackup/adminusers.right
Oct-04-13 00:42:06 [Worker_10000] Backup: 0 records of database table 
AdminUsersRight to file /var/assp/adminusers.right
Oct-04-13 00:44:59 [Worker_10000] Info: looking for files to (re)send
Oct-04-13 00:49:59 [Worker_10000] Info: looking for files to (re)send
Oct-04-13 00:50:33 [Main_Thread] Info: Main_Thread got connection request
Oct-04-13 00:50:33 [Main_Thread] Info: Main_Thread looks up the best 
Worker for new connection - 408
Oct-04-13 00:50:33 [Main_Thread] Info: try to interrupt worker Worker_10
(2) for new connection
Oct-04-13 00:50:33 [Main_Thread] Info: Main_Thread interrupted Worker_10
(2) to submit the connection
Oct-04-13 00:50:33 [Main_Thread] Info: Loop in Worker_10 was not active 
for 577 seconds
Oct-04-13 00:50:33 [Main_Thread] Info: Worker_10 : last sigoff in main, 
sub main::SenderBaseOK, 3, main::SenderBaseOK_Run, 1, 0, ,  at 13-4-9
0:4057 1380868857.10733 - 36
Oct-04-13 00:50:33 [Main_Thread] Info: Worker_10 : last sigon in main, sub 
main::SenderBaseOK, 3, main::SenderBaseOK_Run, 1, 0, ,  at 13-4-9 0:4057
1380868857.25033 - 48
Oct-04-13 00:50:33 [Main_Thread] Info: Worker_10 : last action was : 
ASSP::Senderbase::Query::
Oct-04-13 00:50:33 [Main_Thread] Warning: try to terminate 
inactive/stucking Worker_10
Oct-04-13 00:50:33 [Main_Thread] Info: Main_Thread will wait (max 30 s) 
for the answer of Worker_10 which handles 2 sockets
Oct-04-13 00:51:04 [Main_Thread] Info: Worker_10 handles 2 sockets and 
does not answer - will try other worker
Oct-04-13 00:51:04 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:51:04 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:51:04 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:51:04 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:51:04 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)

Oct-04-13 00:53:07 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:53:07 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:53:07 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:53:07 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:53:08 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-04-13 00:53:08 [Main_Thread] Info: ConnectionTransferTimeOut (30
seconds) is now reached
Oct-04-13 00:53:08 [Main_Thread] Warning: Main_Thread is unable to 
transfer connection to any worker - try again!

Daniel Du Vall
http://1peter4-10.org
http://volkswageninsanity.us

-----Original Message-----
From: Daniel K. Du Vall
Sent: Wednesday, October 2, 2013 9:37 AM
To: 'ASSP development mailing list'
Subject: RE: [Assp-test] Antwort: unable to detect any running worker

I was running ASSP version 2.3.4(13271) when this happened. I am now 
running the latest release ASSP version 2.3.4(13275).
I will  reduce the number of workers to 10 and watch to see if this 
happens again.

Daniel Du Vall
http://1peter4-10.org
http://volkswageninsanity.us

-----Original Message-----
From: Thomas Eckardt [mailto:thomas.ecka...@thockar.com]
Sent: Wednesday, October 2, 2013 9:16 AM
To: ASSP development mailing list
Subject: [Assp-test] Antwort: unable to detect any running worker

WOW - what a setup - 15 Workers: that's the same like 15 V1 instances 
!????????
Never saw a V2 installation with more than 7 Workers required.
Every number of Workers above 10 produces more overhead than performance 
in a standard installation! Running more than 10 Workers requires special 
system design and assp configuration. 

check your DNS setup - with 15 Workers assp will/can do several hundred 
DNS querys per second (eg URIBL)

What version/build is running?

>fixed in assp 2.3.4 build 13263: 
.....
- the SenderBase querys were running in to a timeout condition (given no
results) too often
  V2 now uses a smarter way to query senderbase.org 

Thomas





Von:    "Daniel K. Du Vall" <dduv...@1peter4-10.org>
An:     "ASSP development mailing list (assp-test@lists.sourceforge.net)" 
<assp-test@lists.sourceforge.net>,
Datum:  02.10.2013 16:54
Betreff:        [Assp-test] unable to detect any running worker



Just an FYI but this has started and I have noticed it in the last few 
builds. If there is anything else you would like to see just let me know.

Oct-01-13 22:40:59 [Main_Thread] Info: Worker_15 : last sigoff in main, 
sub main::SenderBaseOK, 3, main::SenderBaseOK_Run, 1, 0, ,  at 13-1-9
22:369 1380688569.35811 - 36
Oct-01-13 22:40:59 [Main_Thread] Info: Worker_15 : last sigon in main, sub 
main::SenderBaseOK, 3, main::SenderBaseOK_Run, 1, 0, ,  at 13-1-9 22:369
1380688569.58908 - 48
Oct-01-13 22:40:59 [Main_Thread] Info: Worker_15 : last action was : 
ASSP::Senderbase::Query::
Oct-01-13 22:40:59 [Main_Thread] Warning: try to terminate 
inactive/stucking Worker_15
Oct-01-13 22:40:59 [Main_Thread] Info: Main_Thread will wait (max 30 s) 
for the answer of Worker_15 which handles 2 sockets
Oct-01-13 22:41:30 [Main_Thread] Info: Worker_15 handles 2 sockets and 
does not answer - will try other worker
Oct-01-13 22:41:30 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-01-13 22:41:30 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-01-13 22:41:30 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)


Oct-01-13 22:43:33 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-01-13 22:43:34 [Main_Thread] Info: unable to detect any running worker 
for a new connection - wait (max 30 seconds)
Oct-01-13 22:43:34 [Main_Thread] Info: ConnectionTransferTimeOut (30
seconds) is now reached
Oct-01-13 22:43:34 [Main_Thread] Warning: Main_Thread is unable to 
transfer connection to any worker - try again!

Daniel Du Vall
http://1peter4-10.org
http://volkswageninsanity.us

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most 
from the latest Intel processors and coprocessors. See abstracts and 
register > 
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk



_______________________________________________
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!
*******************************************************



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most 
from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk


_______________________________________________
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!
*******************************************************



------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most 
from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk

_______________________________________________
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!
*******************************************************


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to