Pirates@Home logo

Pirates@Home

Berkeley Open Infrastructure
BOINC!
for Network Computing
Home Help Status Forums Glossary Account

Database errors

log in

Advanced search

Message boards : Help! : Database errors

Author Message
Profile Martin P.
Send message
Joined: 9 Jun 05
Austria
BOINC@Austria
Credit: 7,073.1
RAC: 0.00
Joined: Jun 9, 2005
Verified: May 11, 2011
Dubloons: 3
Pieces of Eight: 11
Punishment: Mess Duty
Message 7235 - Posted: 28 Feb 2008 | 12:50:36 UTC
Last modified: 28 Feb 2008 | 12:51:14 UTC

Since the crash of the Pirates@Home hard disk on monday this week (which also cost me 400 turk-credits) I have continued problems connecting to the server. I keep getting this error message:

[size=+2] Database unavailable[/size]

Unable to connect to database - please try again later
Error: 1045
Access denied for user 'apache'@'localhost' (using password: NO)


Besides that, the homepage is extremely slow. It often takes 30-40 seconds between a sent turk and the display of the next one.

____________

Profile Wormholio
Captain
Avatar
Send message
Joined: 6 Jun 04
United States
Away
Credit: 4,065.6
RAC: 0.00
Joined: Jun 6, 2004
Verified: Mar 13, 2008
Dubloons: 3
Pieces of Eight: 10
Punishment: Aztec curse
Message 7236 - Posted: 28 Feb 2008 | 13:38:11 UTC - in response to Message 7235.

Martin P. wrote:
Since the crash of the Pirates@Home hard disk on monday this week (which also cost me 400 turk-credits) ...

I hope to get them back to you sometime.

The database problems are due to our current round of testing: trickle messages. It seems they put a very large load on the database.

Now part of that is due to the fact that you need to specifically enable sending messages to the hosts, and I have sometimes left that turned off. In that case they pile up, and when I turn it back on and the messages start being delivered the load goes way up.

But it may just be that trickle down messages always put a significant load on the database. That might be because of problems in the code, or even that trickle down messages bypass the feeder. Or it could be that I'm doing something wrong.

It may also be that keeping messages around after they have been delivered is the problem. After all, even though we are done with them, the database server has to sort through them all when looking for which message to deliver. There is nothing in the sample trickle handler code to delete messages once they have been handled. I'll add something to do that and we'll see what effect that has.

So hang on, it may be a bumpy ride, but again we are testing BOINC to see how well it works, and the result may be finding some bugs, or at least improving documentation and sample code. Thanks to all who stick with it. And appologies to those who's time on the Turk is interrupted. ;-)


____________
-- Eric Myers

"Education is not the filling of a pail, but the lighting of a fire." -- William Butler Yeats

Profile Martin P.
Send message
Joined: 9 Jun 05
Austria
BOINC@Austria
Credit: 7,073.1
RAC: 0.00
Joined: Jun 9, 2005
Verified: May 11, 2011
Dubloons: 3
Pieces of Eight: 11
Punishment: Mess Duty
Message 7238 - Posted: 28 Feb 2008 | 15:02:40 UTC - in response to Message 7236.
Last modified: 28 Feb 2008 | 15:03:11 UTC

Wormholio wrote:
I hope to get them back to you sometime.

The database problems are due to our current round of testing: trickle messages. It seems they put a very large load on the database.

Now part of that is due to the fact that you need to specifically enable sending messages to the hosts, and I have sometimes left that turned off. In that case they pile up, and when I turn it back on and the messages start being delivered the load goes way up.

But it may just be that trickle down messages always put a significant load on the database. That might be because of problems in the code, or even that trickle down messages bypass the feeder. Or it could be that I'm doing something wrong.

It may also be that keeping messages around after they have been delivered is the problem. After all, even though we are done with them, the database server has to sort through them all when looking for which message to deliver. There is nothing in the sample trickle handler code to delete messages once they have been handled. I'll add something to do that and we'll see what effect that has.

So hang on, it may be a bumpy ride, but again we are testing BOINC to see how well it works, and the result may be finding some bugs, or at least improving documentation and sample code. Thanks to all who stick with it. And appologies to those who's time on the Turk is interrupted. ;-)



Thanks a lot for this excellent explaination!

____________

Profile Stan Pleban
Volunteer tester
Avatar
Send message
Joined: 6 Jan 08
United States
Mensa
Credit: 1,340.1
RAC: 0.00
Joined: Jan 6, 2008
Verified: Nov 7, 2011
Dubloons: 3
Pieces of Eight: 10
Punishment: Mess Duty
Message 7295 - Posted: 7 Mar 2008 | 18:45:59 UTC

I am getting the following message...

3/7/2008 1:38:36 PM|Pirates@Home|Message from server: Starting in 24 days and 9 hours, project will require a minimum BOINC core client version of 5.12.0. You are currently using version 5.10.45; please upgrade before this time.


I am using BOINC 5.10.45...which is the latest test version, so who knows???

Profile Scott Brown
Volunteer tester
Avatar
Send message
Joined: 25 Jul 04
United States
Duke University
Credit: 39,692.5
RAC: 0.00
Joined: Jul 25, 2004
Verified: Oct 7, 2011
Dubloons: 3
Pieces of Eight: 11
Punishment: Keel Haul
Message 7296 - Posted: 7 Mar 2008 | 18:52:09 UTC - in response to Message 7295.
Last modified: 7 Mar 2008 | 18:52:20 UTC



see this thread:

http://pirates.spy-hill.net/forum_thread.php?id=789
____________

Post to thread

Message boards : Help! : Database errors

Home Help Status Forums Glossary Account


Return to Pirates@Home main page


Copyright © 2017 Capt. Jack Sparrow