For the past week when I try to open up goth.net I get a 503 Service Temporarily Unavailable notice, yet usually if I refresh the page a couple of times it works- other times it doesn't.

It has been happening more frequently than normal the past few days (why I haven't really been posting) and was wondering if it was the website or if it might be my computer.

It's the site. I've been having the same problem.

Yeah it's the site, happens for me to.

I know why this was happening now, and I've fixed it.

This happens when the server gets too busy, and it was getting too busy because for some reason previous month's log files were not getting archived properly, so a program I have that creates statistics about the website (number of visitors, and such) kept having to re-process all the previous months data as well as this month's and it was taking a long time and using a lot of CPU.

This should be fixed now. Not to say the server can't get too busy again, but it should not happen as frequently.

Thanks for explaining it, Prez, and working so adamantly to solve the problem!

I thought this was just becoming a more popular site and overloading at times. Other forums I'm on do the same things, sometimes.

Just becoming popular. Goth.net is first on the list if you type "goth" on Google which usually means it gets the most hits. I knew about this place for years and compared to other goth forums, it constantly keeps traffic instead of dying out. So, I'm guessing that because of so many goth forums dying, Goth.net has become the main online goth hangout with only VampireFreaks.com as competition, resulting in these time out messages.

Whenever that message comes up, I refresh about 4 or 5 times and if that still doesn't work I just close out the browser and restart it then it works. Having taken classes on database and web servers, I have new found appreciation for sites like this and how much work it takes to maintain them. I've also learned in the computer field that you need to have some level of patience no matter how frustrated you get.

Hate to dredge this back up, but I have been getting 503 errors like crazy for the past few days. Still a log issue or are we getting blasted?

~spidey

I've also been getting this error more frequently again.

How's everyone doing with this? Still getting that message?

-- Nephele

Very often, actually.