Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988

Strict Standards: getdate(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/20/d268022878/htdocs/forum/viewtopic.php on line 988
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4284: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4286: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4287: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4288: Cannot modify header information - headers already sent by (output started at /viewtopic.php:988)
FAROO Forum • View topic - Corrupt database - once again!

Corrupt database - once again!

Bug reports

Corrupt database - once again!

Postby TomHH » Sun Mar 20, 2011 12:53 pm

My PC did not wake up correctly after entering hibernation mode.
When I restarted Faroo, the database was corrupt and always starts with 0 indexed words after a rescan of the database.
This is the third time that I ran into a corrupt database since January, and the second time within 9 days. :x

Please look into this problem. I would really appreciate you feedback in this case.
For me it does not make sense to run the Faroo client as long as this situation is not fixed, because I do not want to start from scratch every other week. :cry:
TomHH
 
Posts: 40
Joined: Sat Dec 18, 2010 5:37 am

Re: Corrupt database - once again!

Postby TomHH » Mon May 30, 2011 7:51 pm

73 Zugriffe und keine Antwort wert?
Ich frage mich so langsam, warum ich das immer noch (und immer wieder von vorn!) laufen lasse. :geek:

Oder gibt's bei boinc Punkte für indizierte Wörter, oder vielleicht sogar für korrupte Datenbanken? :evil:
TomHH
 
Posts: 40
Joined: Sat Dec 18, 2010 5:37 am

Re: Corrupt database - once again!

Postby Wolf » Wed Jun 15, 2011 11:46 am

Sorry für die späte Antwort. In unseren Tests war das Problem nicht replizierbar, dashalb ist es schwer der eigentlichen Ursache auf den Grund zu gehen.
Wir nehmen das natürlich ernst und haben den Datenbank-Layer neu geschrieben. Er unterstützt jetzt Logging and Crash Recovery.
Gegenwärtig nehmen wir umfangreiche Änderungen am Ranking und Crawling vor. Deshalb gibt es z.Zt. leider noch keine neue lauffähige Version.
Wolf
Site Admin
 
Posts: 130
Joined: Wed Dec 17, 2008 12:28 pm

Re: Corrupt database - once again!

Postby TomHH » Sat Jul 09, 2011 6:43 am

Gibt es denn schon einen ungefähren Termin, zu dem die neue Version fertig sein soll?
TomHH
 
Posts: 40
Joined: Sat Dec 18, 2010 5:37 am


Return to Bugs

Who is online

Users browsing this forum: No registered users and 1 guest

cron