The boring life of Jerod Poore, Crazymeds' Chief Citizen Medical Expert.

Brace yourselves

The switch to the new server just happened.  It will take anywhere from one to 48 hours for the DNS to propagate all across teh interwebs, so some of you will still see the old stuff for a day or two.  I unfortunately jumped the gun and reset the forum to full featured mode on the old server, so the only way to tell the difference is to look for an announcement about the site being on a new server.  Although you might be able to get on the new server before I do, especially since I haven't had breakfast yet.


scatha said...

Just FYI: I'm getting an error message on the home page,

Warning: Cannot modify header information - headers already sent by (output started at /var/www/vhosts/ in /var/www/vhosts/ on line 3

Jerod Poore said...

That's been fixed.

th3vil0ne said...

on the off chance that you don't know this, whenever i've tried to access the site all day it has been giving me a page load error message from my browser, saying the server is taking too long to respond, or it gives me a crazymeds error message saying that something is messed up, and check your blog for updates, but is nothing ON your blog...hence this comment.

Jerod Poore said...

Yeah, I changed the permissions on a couple of directories from 0755 to 0775, and that caused some software on the server to totally flip out. And since I couldn't imagine giving a non-public group write permission would cause such a problem, I continued with the various behind-the-scenes stuff I could muddle through. I wasn't aware of the problem until I had to look at something via HTTP.

Now I check the forum whenever I make the slightest change to anything that touches the web server.

Kaliena said...

Any idea when will be back up? I can't even get a proper nslookup response at this point.

Jerod Poore said...

I don't know what happened there. For some reason the server didn't want to automagically deal with the top-level URL without an index.* or anything else for that matter. It didn't even have to be a valid URL. correctly forwarded to the new homepage at , The forum is working and all the new wiki pages were showing up just fine.

I changed all the index.* files from chmod 0664 to 0644 but I have no idea if that fixed it or not, as it was 10 minutes or so before things were working normally. I broke the HTTPD error logging while trying to get log rotation working the way I need it to, so I can't tell why this latest problem really happened.

Jerod Poore said...

I dropped a few words.

If you had nothing past you got the 500 Internal Server Error message. If you had anything after, including total crap, it would forward you to the new home page.

It works either way now.

For some time has been more reliable than, although that might be resolved now that we're on a dedicated server. The forum, though, is married to