Help:About/archive/server

Current Status

2006-01-03 11:07 EST: The SSL server appears to be down – which means that when you press the "checkout" button, nothing happens for a long time and then your browser tells you that the page cannot be loaded. We are working on this; please check back in an hour or three. If you have items in your cart, they should still be there (we discard inactive carts after a minimum of 48 hours, often longer).

Past Issues

2005-12-28 Things are still settling down after a major server migration on 12/26 (faster server with more RAM and more disk space); domains may not all be pointing to the right places, which may cause occasional error dialogs. Everything seems to be working, however.

2005-12-13 the search engine doesn't seem to be searching artist names. Unfortunately I probably won't have time to work on this until the weekend at the earliest. (This was fixed shortly before 12/25, and I added searching by (title's) catalog number as well, yay!)

2005-11-16 21:43 Unbeknownst to me (because no errors were being generated), the shopping cart data script was broken for about a day in that it was not storing data from customer orders. Everything seemed to be working fine, and even the confirmation emails went out looking correct, but the actual data was missing. Fortunately, I can reconstruct the missing orders from the email confirmations, but unfortunately this does not (for security reasons) include credit card numbers... so I'm having to contact the customers whose orders were dropped and have them send in their information again.

2005-11-08 09:52 The search page and adding-items-to-cart were both generating 500 errors. Solution: deleted all static dbm files so they would get regenerated; apparently they became unwritable for some reason. (Maybe the file data was damaged?)

The shopping cart script has mysteriously started generating Internal Server Errors whenever an item is added (if you just go to the cart page without adding anything, it displays properly). Currently working on this. --Woozle 15:46, 12 Oct 2005 (EDT)

Update #1: Apparently our webhost went and installed FastCGI on the server with no warning, which apparently breaks the Perl DBM hash-writing functions. Currently trying to find out if there's any way around this problem. --Woozle 18:13, 12 Oct 2005 (EDT)

Update #2 (problem resolved): Apparently it was even simpler than that; there was a Perl library file (cgi-lib.pl) which one script library depended on, and either the library itself got moved or else the path got altered. Not sure which. --Woozle 21:32, 12 Oct 2005 (EDT)