Site Issues

My apologies for the numerous site outages and odd mySQL error messages over the past few days. Unfortunately, OTB Media has outgrown its dedicated server. I have entered into an agreement with Rackspace for a much more robust multi-server system. Mark Jaquith will be porting everything over the next couple of days. Please bear with us in the meantime.

FILED UNDER: General
James Joyner
About James Joyner
James Joyner is Professor and Department Head of Security Studies at Marine Corps University's Command and Staff College and a nonresident senior fellow at the Scowcroft Center for Strategy and Security at the Atlantic Council. He's a former Army officer and Desert Storm vet. Views expressed here are his own. Follow James on Twitter @DrJJoyner.

Comments

  1. Michael says:

    Unfortunately, OTB Media has outgrown its dedicated server.

    You’re kidding, right? I’ve never seen php include errors caused by heavy traffic. It looks more like someone or something has screwed up your file permissions. Are you sure your hosting company isn’t trying to sell you an upgrade you don’t need?

  2. Michael says:

    James: My previous post was caught in your spam filter. It was really meant for just you anyway, so if you don’t want to post it that’s fine.

  3. Mark Jaquith says:

    I’ve never seen php include errors caused by heavy traffic

    They weren’t. I found some areas where a PHP include was calling a URL instead of a local file (which means a double hit on the server). You probably saw a cached page from when I was fixing that (made a typo and pointed to the wrong file).

  4. Michael says:

    Warning: main(_features.inc) [function.main]: failed to open stream: Permission denied in /var/www/vhosts/otbmedia.org/httpdocs/index.php on line 41

    Warning: main() [function.include]: Failed opening ‘_features.inc’ for inclusion (include_path=’.:/usr/share/php:/usr/share/pear’) in /var/www/vhosts/otbmedia.org/httpdocs/index.php on line 41

    Is what I’m seeing at http://otbmedia.org, is this a static page, or are these errors being generated every time?