1 reply to this topic

[jimdahl]

Warning, tech jargon ahead...

The tech guys say it has something to do with having previously been on a Linux 2.6 kernel, leading to "kernel panics".  We're now happily on a Linux 3.0 kernel, which they're optimistic will resolve the problem.  If you know what that really means and can wear the same shirt at lunch and dinner, you're a better man than I.

I'll continue to remain engaged with the techs until we reach the type of stability to which we were previously accustomed (about a year of continuous uptime until last Thursday).  In an unlikely timing coincidence, I've been unusually distracted by family issues since Thursday evening, leading to atypically poor responsiveness from me.  Sorry for any inconvenience this may have caused.

[jimdahl]

Another problem today, so we tried migrating the database to new hardware.  We'll see if that does the trick.