NES Cart DB down again

You can talk about almost anything that you want to on this board.

Moderator: Moderators

User avatar
FitzRoy
Posts: 144
Joined: Wed Oct 22, 2008 9:27 pm
Contact:

Re: NES Cart DB down again

Post by FitzRoy »

I'm curious to know the status of the as yet undumped list of Famicom carts. There doesn't seem to be much progress on getting those bought and dumped? Are they too expensive or something?
User avatar
Myask
Posts: 965
Joined: Sat Jul 12, 2014 3:04 pm

Re: NES Cart DB down again

Post by Myask »

I assume it's still volunteer ad-hoc community work, and we haven't got a member in Japan with money to burn, motivation, and equipment.
tepples
Posts: 22705
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Re: NES Cart DB down again

Post by tepples »

Down again, with "access denied" all over the place.
User avatar
Myask
Posts: 965
Joined: Sat Jul 12, 2014 3:04 pm

Re: NES Cart DB down again

Post by Myask »

tepples wrote:Down again, with "access denied" all over the place.
WFM
Revenant
Posts: 462
Joined: Sat Apr 25, 2015 1:47 pm
Location: FL

Re: NES Cart DB down again

Post by Revenant »

Seems fine on my end as well. Maybe it was just being a little sporadic earlier?
tepples
Posts: 22705
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Re: NES Cart DB down again

Post by tepples »

tepples wrote:Down again, with "access denied" all over the place.
It was reported to me, through a channel that I don't remember with certainty but was most probably #nesdev on EFnet, that NesCartDB was broken. I checked it out, and the site was having issues with its MySQL database: the application server was getting "access denied" from the database server when trying to SELECT from various tables. It appeared as "access denied" because the application server was set up to echo PHP warning messages to output instead of logging them privately or converting them to exceptions. This problem was present at the time I posted the previous comment but has since cleared up.
BootGod
Posts: 359
Joined: Wed Jul 13, 2005 3:14 pm

Re: NES Cart DB down again

Post by BootGod »

FitzRoy wrote:I'm curious to know the status of the as yet undumped list of Famicom carts. There doesn't seem to be much progress on getting those bought and dumped? Are they too expensive or something?
It's mostly a money thing for me, I don't have quite as much disposable income as I used too. Also, when I first started dumping FC stuff, I was buying large bulk lots for very cheap, at this point I pretty much have to get them individually which adds up quick.
tepples wrote:Down again, with "access denied" all over the place.
I'm aware this happens occasionally, I think it has something with concurrent connections to DB being maxed out because for some reason some sessions aren't closing properly. The problem fixes itself when the rouge sessions timeout. Could anyone who has experienced this error tell me how long the problem persisted?
tepples
Posts: 22705
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Re: NES Cart DB down again

Post by tepples »

BootGod wrote:
tepples wrote:Down again, with "access denied" all over the place.
I'm aware this happens occasionally, I think it has something with concurrent connections to DB being maxed out because for some reason some sessions aren't closing properly. The problem fixes itself when the rouge sessions timeout. Could anyone who has experienced this error tell me how long the problem persisted?
Here are a couple things you can try to make these problems occur less often.

Nowadays it's best practice to convert all PHP warnings to ErrorException:

Code: Select all

function exception_error_handler($severity, $message, $file, $line) {
  if (error_reporting() & $severity) {
    throw new ErrorException($message, 0, $severity, $file, $line);
  }
}
set_error_handler("exception_error_handler");
This way, failed connections will cause errors that you can catch. Failing fast reduces how much load a failed connection puts on the database before it times out.

Another is testing the database connection before trying to render anything. Often you can test the connection by trying a simple query that should always work, such as looking up global settings for the application or data associated with a user session. If this fails, raise an appropriate HTTP status code such as 503 Service Unavailable. More generally, getting in the habit of doing all the database access before producing any output will help you separate functions that access data from functions that render it for display, which can make the architecture cleaner and easier to maintain.
tepples
Posts: 22705
Joined: Sun Sep 19, 2004 11:12 pm
Location: NE Indiana, USA (NTSC)
Contact:

Re: NES Cart DB down again

Post by tepples »

Discuss the latest downtime in #16325
Locked