Menu
▾
▴
#3015 503 service unavailable
This is related to bug 999591. slashdot.org has been
giving me random 503 service unavailable messeges ever
since that recent upgrade regarding domain updates.
Sometimes I can view slashdot, and sometimes I can't.
I have to reload a few times before I can see the main
page.
I am using IE 6.0, Windows XP.
This problem is not limited to the Yesterday news, and
it's still happening today 8/2/2004.
Logged In: YES
user_id=107247
...and I can get this error messege from home and at work.
Logged In: YES
user_id=107247
...and I can get the same "503 Service Unavailable" messege
from mozilla when I log in.
Logged In: YES
user_id=972667
This happening to me as well... but only wtih firefox. IE
loads it just fine everytime I try (thus far). I'm running
Windows 2000 and FireFox .9
Logged In: YES
user_id=1096175
I've noticed the same problems.
To alleviate the problem, simply delete all of the Slashdot
cookies. Don't know why this works, but it does--hopefully
the info will prove usefull for determining what's going on.
Logged In: YES
user_id=689077
Same for me, I haven't been able to get into slashdot for a day now.
If my browser sends this:
$ telnet slashdot.org 80
Trying 66.35.250.150...
Connected to slashdot.org.
Escape character is '^]'.
GET / HTTP/1.1
Host: slashdot.org
Connection: keep-alive
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/
125.2 (KHTML, like Gecko) Safari/125.8
Accept: */*
Accept-Encoding: gzip, deflate;q=1.0, identity;q=0.5, *;q=0
Accept-Language: en, ja;q=0.75, ja-jp;q=0.88, zh-cn;q=0.62, zh-tw;
q=0.50, zh;q=0.38, ko-kr;q=0.25, ko;q=0.12
Cookie: user=23954::XXXXXX; user=23954::XXXXXX
HTTP/1.0 503 Service Unavailable
Content-Type: text/html
Content-Length: 169
<html><head><title>503 Service Unavailable</title></
head><body><h1>503 Service Unavailable</h1><p>The service is not
available. Please try again later.</p></body></html>Connection closed
by foreign host.
If I take the cookie line out, it works fine.
Logged In: YES
user_id=64005
I think I have tracked down the situation which causes the
problem and I need you guys to confirm this. The problem is
the cookie:
If you have the cookie set then the server tries confirming
your login info and bang you get error 503. I strongly
suspect that nicolae6 never got the issue with IE because
(s)he never logged in with IE. If you delete the cookie for
slashdot.org and then try again you should be able to access
the web site. Try logging in and even IE gives you a 503
error. Hence the problem is caused somewhere between the
cookie and the user details database.
At least that's the way I see it. Hope this helps the
developers.
Logged In: YES
user_id=1096301
I received a 503 myself today at 19:25 EDT.
Logged In: YES
user_id=1096613
I saw it for most of yesterday (2-aug-2004), as an
intermittent problem, once getting the 503 error instead of
one of the ad images inside a page that had otherwise loaded
correctly!
I think the error is intermittent rather than necessarily tied to
a cookie problem, but that's just my 2p worth...
Logged In: YES
user_id=538143
I am using Mozilla FireFox 0.9.2 and I am receving the same
503 error when I attempt to connect to www.slashdot.org but
if I type www.slashdot.com it will resolve to slashdot.org
and will load. /. is my homepage and it loads at startup
with the same 503 error. checked mozillazine and didn't see
an mention of it on their end.
Logged In: YES
user_id=350050
I can verify that the cookie fix is working for me. I get a
503, use firefox to just delete the slashdot cookies,
relogin and as long as my session stays alive, I browse
around fine. If the session dies, and slashdot tries to log
in with the cookie... 503.
For a quick fix, why not simply disable cookies and tell
people its a quickfix to the 503 problems until you can find
a permanent fix for the cookie issue.
Logged In: YES
user_id=350050
Oh, I found a caveat. If you disallow slashdot from writing
cookies, you get a 503. So you shouldn't "stop" slashdot
from writing cookies, just delete them if you get 503s.
Wow, this is a wierd bug.
Logged In: YES
user_id=381516
okay, so following the recommendations here, i removed my
cookie and then tried to log in, only to have the login.pl
script throw me a 503.
can anyone here do anything right???
Logged In: YES
user_id=350050
looks like the login is a bit shaky, now. Logging in sits
until timeout for me, now. Ugh, I thought that was a good
quickfix. Maybe not.
Logged In: YES
user_id=25309
I deleted my cookies, updated to firefox .9.2, and noticed a
"public terminal" check box. If I check this box, I can
login. If not, I can not, 503 error.
Logged In: YES
user_id=25309
I deleted my cookies, updated to firefox .9.2, and noticed a
"public terminal" check box. If I check this box, I can
login. If not, I can not, 503 error.
Logged In: YES
user_id=356483
IT'S NOT ABOUT COOKIES
I don't know what it IS about, but you can get the 503 error
without presenting any cookies. Just visit any /~user link,
for instance http://slashdot.org/~cmdrtaco or
http://slashdot.org/~trollback/journal. Even totally logged
out (or using wget) you'll get the 503 error message half
the time. Also you can get it trying to visit stats
(http://slashdot.org/stats.pl).
HTH, HAND.
Logged In: YES
user_id=751196
I haven't been to slashdot.org in at least a month. I try to
go to the site and the first thing I get is 503. I'm
thinking "did someone slashdot slashdot?".
But apparently not. After several page refresh attempts it
came up, although I had to wait several seconds for some of
those attempts to time out, they weren't all instantaneous.
Other info available upon correctly phrased requests from
verified slashdot personnel. :-)
Logged In: YES
user_id=3660
It is not about cookies. Ignore fortknox, and trust sllort (I can't believe I
just said that :-).
We are working on the problem, and hope to fix it soon.
Logged In: YES
user_id=350050
but.... umm... well I.... if you.... but but but....
*drops head in shame* ;-)
Logged In: YES
user_id=3889
This should be over at least for now ;)