The error log aggregates all the errors from our 100 web servers into one place. Errors range form simple warnings to fatal errors that causes the program to crash.
The worst kind of errors are memory errors where a process eats up so much memory that the server aborts the process as it is probably not optimized, and not shutting down these processes just leads to the site going down.
So I've been consistently tracking down these fatal errors and fixing them when I take breaks from the building features or fixing other bugs. Some are caused by runaway notifications stacking up, some are caused by bad search terms, some by simply having large inventories, some from the inventory worth calculator, and the arranger also had a hand in causing memory errors.
Today I finally fixed the last of these memory errors. So most the random 500 errors or the random white screens should go away now!
Time for a little victory dance before I crawl back to fixing other bugs. blaugh
Here's a sample of what the error log looks like. With memory errors that hopefully we'll never see again.
