2006-07-27 06:59
The computer running the @Baker Web service failed without warning on July 24 at about 4:51 PM. Web services were restored about 3:40 AM on July 27; database services are still down, the problem is a configuration error by the hosting company which should be corrected presently. You won't be able to use any of the features of @Baker that require database access until they've fixed the problem. (Didn't happen.)
Our Web hosting provider, Assorted Internet, has not given us any explanation for this unplanned, unscheduled downtime.
2006-07-18 08:49
The database appears to be running normally again. I will run some integrity checks later in the day to be sure.
2006-07-18 07:25
The database is Once Again not responding. The whole server appears to have been down for about an hour. It's back. The hosting provider has been notified, but they haven't responded yet.
(Time passes...) 2006-07-18 08:20 Our hosting service provider, Assorted Internet, closed my request for help without checking whether the database process was running and without notifying me, other than to update their own trouble-reporting system. It isn't. I've re-opened the help request.
2006-07-10 21:50
PostgreSQL is once again refusing connections. The hosting provider has been notified.
2006-07-05 05:24
Database locked up. I sent the following to the hosting provider: PLEASE DON'T JUST TELL ME IT IS FIXED. WE NEED TO FIND THE CAUSE OF THIS CONTINUING FAILURE. Their answer? "Postgresql service is now running fine in the server. Could you please have a recheck anb [sic] let us know the details." AAaarrgghh!
Update: 2006-05-11 08:49
Sent to hosting provider: "PostgreSQL is (once again) refusing connections, even though the postmaster process is running. This has happened before, and you were going to research it. See ticket LIJ-94614. Site down. (Again.) "
Update: 2006-04-16 02:03
The hosting company reports that the database is "running fine now," with no explanation of what they did or did not do to fix things. We do have a backup from just before the failure. I have the dreadful spring cold and am going back to bed in a minute; I'll do some serious checks on database integrity when the sun is in the sky, but everything looks OK at the moment. --Bob.
Update: 2006-04-15 11:57
The database system that runs most of @Baker failed between 3:30 and 6:30 EDT this morning. The failure has been reported to our hosting provider and we're waiting for them to respond.
This page will be updated as we find out more. Updates will be at the top of the page so you don't have to read the same stuff over again.