Hello,
have someone any idea why it happens ??

bye
Ralf

here ist the log :


Okt-29-09 03:56:00 [Worker_10000] Downloading Griplist via direct HTTP 
connection
Okt-29-09 03:56:04 [Worker_10000] Griplist download completed
Okt-29-09 03:56:04 [Worker_10000] Info: next Griplist download in 12 hours 0 
mins 
Okt-29-09 03:56:04 [Worker_10000] Griplist download completed: binary download 
721168 bytes
Okt-29-09 03:56:04 [Worker_10000] Griplist - starting binary to text conversion 
for Griplist
Okt-29-09 03:56:16 [Worker_10000] Griplist binary read OK: 
/var/db/assp/griplist.tmp, 180289 IPv4 addresses
Okt-29-09 03:56:16 [Worker_10000] Writing merged Griplist binary
Okt-29-09 03:56:16 [Worker_10000] Writing merged Griplist binary finished
Okt-29-09 03:56:16 [Worker_10000] Griplist update uses BerkeleyDB for temporary 
hashes
Okt-29-09 03:57:30 [Worker_10000] Griplist - finished adding/updating 180289 
new records
Okt-29-09 03:57:30 [Worker_10000] Griplist - start remove old records after 
full download
Okt-29-09 03:57:30 [Worker_10000] Griplist - finished removing 0 old records
Okt-29-09 03:57:31 [Worker_10000] Griplist update complete: 180289 IPv4 
addresses
Okt-29-09 03:57:32 [Main_Thread] Saving config
Okt-29-09 03:57:32 [Main_Thread] Finished saving config
Okt-29-09 03:57:32 [Worker_4] BerkeleyDB-CRT-ENV-ERROR Griplist: 
BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_4] BerkeleyDB-ENV-ERROR Griplist: Can't call method 
"set_timeout" on an undefined value at (eval 798) line 12.
     - BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_4] Error: Worker_4: Can't call method "set_timeout" 
on an undefined value at (eval 798) line 12.

Okt-29-09 03:57:32 [Worker_3] BerkeleyDB-CRT-ENV-ERROR Griplist: 
BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_3] BerkeleyDB-ENV-ERROR Griplist: Can't call method 
"set_timeout" on an undefined value at (eval 798) line 12.
     - BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_4] Worker_4 finished
Okt-29-09 03:57:32 [Worker_1] BerkeleyDB-CRT-ENV-ERROR Griplist: 
BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_3] Error: Worker_3: Can't call method "set_timeout" 
on an undefined value at (eval 798) line 12.

Okt-29-09 03:57:32 [Worker_1] BerkeleyDB-ENV-ERROR Griplist: Can't call method 
"set_timeout" on an undefined value at (eval 803) line 12.
     - BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_3] Worker_3 finished
Okt-29-09 03:57:32 [Worker_1] Error: Worker_1: Can't call method "set_timeout" 
on an undefined value at (eval 803) line 12.

Okt-29-09 03:57:32 [Worker_2] BerkeleyDB-CRT-ENV-ERROR Griplist: 
BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_1] Worker_1 finished
Okt-29-09 03:57:32 [Worker_2] BerkeleyDB-ENV-ERROR Griplist: Can't call method 
"set_timeout" on an undefined value at (eval 798) line 12.
     - BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:32 [Worker_2] Error: Worker_2: Can't call method "set_timeout" 
on an undefined value at (eval 798) line 12.

Okt-29-09 03:57:32 [Worker_2] Worker_2 finished
Okt-29-09 03:57:33 [Worker_5] BerkeleyDB-CRT-ENV-ERROR Griplist: 
BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:33 [Worker_5] BerkeleyDB-ENV-ERROR Griplist: Can't call method 
"set_timeout" on an undefined value at (eval 798) line 12.
     - BDB:DB_RUNRECOVERY: Fatal error, run database recovery
Okt-29-09 03:57:33 [Worker_5] Error: Worker_5: Can't call method "set_timeout" 
on an undefined value at (eval 798) line 12.

Okt-29-09 03:57:33 [Worker_5] Worker_5 finished
Okt-29-09 03:57:36 [Worker_10000] BerkeleyDB-TIE-ERROR Griplist:  - BDB:PANIC: 
fatal region error detected; run recovery
Okt-29-09 03:57:36 [Worker_10000] Error: Worker_10000: 
Okt-29-09 03:57:36 [Worker_10000] Worker_10000 finished
Okt-29-09 05:05:00 [Main_Thread] Warning: Main_Thread is unable to transfer 
connection to any worker - try again!
Okt-29-09 05:05:31 [Main_Thread] Warning: Main_Thread is unable to transfer 
connection to any worker - try again!
Okt-29-09 05:06:02 [Main_Thread] Warning: Main_Thread is unable to transfer 
connection to any worker - try again!
Okt-29-09 05:06:33 [Main_Thread] Warning: Main_Thread is unable to transfer 
connection to any worker - try again!
Okt-29-09 05:06:33 [Main_Thread] Error: Main_Thread is unable to transfer 
connection to any worker within 120 seconds - restart ASSP!
Okt-29-09 05:06:33 [Main_Thread] Info: removing all SMTP and Proxy listeners
Okt-29-09 05:06:33 [Main_Thread] Waiting for high Workers to be finished
Okt-29-09 05:06:35 [Worker_10001] Worker_10001 finished
Okt-29-09 05:06:36 [Main_Thread] High workers finished work
Okt-29-09 05:06:36 [Main_Thread] Info: saving Stats in file asspstats.sav
Okt-29-09 05:06:36 [Main_Thread] Waiting for all SMTP-Workers to be finished
Okt-29-09 05:06:36 [Main_Thread] Info: saving Stats in file asspstats.sav
Okt-29-09 05:06:36 [Main_Thread] ASSP finished work
Okt-29-09 05:06:36 [Main_Thread] Info: removing all WEB listeners
Okt-29-09 05:06:36 [Main_Thread] Restarting
Okt-29-09 12:15:30 [] Starting in console mode 

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to