This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.
This is the blog of Adam Kalsey. Unusual depth and complexity. Rich, full body with a hint of nutty earthiness.
26 Feb 2007
ServerBeach is a dedicated hosting provider that’s popular among the web 2.0 crowd. Companies like Automattic, TailRank, YouTube, Dogster, and MyBlogLog all have servers there*. That’s where Feed Crier’s servers are, and several other startups I’m involved in are there too.
Starting this morning, Feed Crier started behaving oddly. A few minutes ago, all the bots went offline. The front page of the Web site stopped showing the blog items, essentially meaning that the page can’t find the blog’s RSS feed. I can see the feed. I can log into the Jabber server. But applications on Feed Crier’s servers can’t find other Feed Crier servers.
What’s more the server can’t do DNS lookups on sites like security.debian.org, even though those servers are obviously up and running.
I headed over to Server Beach to report the problem, and I got this:
Until these issues are resolved, expect some intermittent uptime from Feed Crier.
(* Or did in the past. I would imagine that YouTube has been moved to Google’s datacenters and MyBlogLog is probably moving as well.)
Adam Kalsey
Mobile: 916.600.2497
Email: adam AT kalsey.com
AIM or Skype: akalsey
©1999-2008 Adam Kalsey.
Content management by Movable Type.
Justin Shattuck
March 22, 2007 2:02 PM
Adam,
This may not be a concern to you, but you might consider taking your image you uploaded and blurring the content of the mysql_error(s) message you are displaying. The paths and contents of that image could very well be a major risk for serverbeach.
The absolute paths gives a malicious user exactly what they require to perform some vulnerability assessments on server beach. Just in my opinion, I would remove it and let serverbeach know they should stop outputting their error messages. I would recommend everyone stop outputting their errors.
My two cents.