Life In 19x19

I had the problems today between 10AM - 11AM GMT. I tried from Turkey and Germany, same result.

If we are getting Http 503 errors, it is probably not a bandwidth issue. (since the server is able to serve the error at least.) I could not check the HTTP error code in my case since the problem ceased as I began to look into it.

One thing I noticed was that the server would usually serve the last page of a multiple page thread, but would have problems with the previous pages of the same thread. But that is not a statistically verifiable experiment right now.

Oh, also when connecting from Firefox instead of chrome, I got served a 0 byte viewtopic.php file. Your php-mod might also be goofing up or my Firefox might be stupid.

Yes, last night it was really bad again

I had mentioned this odd error message before:

Got java.net.SocketException (Connection reset) [..]

Would anybody please explain what this message means? What does Java have to do with it? Or does “java.net.SocketException” not have anything to do with Java? What is it then?

TIA, Tom

Bonobo wrote:Yes, last night it was really bad again

It seems to be bad every weekend. It seems to go in cycles of about 4-5 days ok, then 2-3 days timeout on threads longer than 15 posts. I can hardly read this forum any more, much less contribute.

Bonobo wrote:I had mentioned this odd error message before:

Got java.net.SocketException (Connection reset) [..]

Would anybody please explain what this message means? What does Java have to do with it? Or does “java.net.SocketException” not have anything to do with Java? What is it then?

At first glance, it looks like the backend server is using java to serve up this php forum. Or its at least one link in the chain somewhere between you and the server.

I don't recall seeing any java specific error messages myself, but I do get lots of connection timeout errors on longer threads.

Seems worse on some days than others, and sometimes one post won't load but others will, but I don't see a pattern.

Claint wrote:I had the problems today between 10AM - 11AM GMT. ...

Here in Southern California, I'm on several times per day between 11:00 and 24:00 GMT or later. I haven't seen a slowdown in weeks.

Joaz Banbeck wrote:

Claint wrote:I had the problems today between 10AM - 11AM GMT. ...

Here in Southern California, I'm on several times per day between 11:00 and 24:00 GMT or later. I haven't seen a slowdown in weeks.

I would report when I have problems, except I can't connect

Joaz Banbeck wrote:

Claint wrote:I had the problems today between 10AM - 11AM GMT. ...

Here in Southern California, I'm on several times per day between 11:00 and 24:00 GMT or later. I haven't seen a slowdown in weeks.

Yesterday at around 5pm GMT I couldn't connect to several threads including this one. The rest of the site worked fine.

I've noticed that limiting the number of posts per page seems to make some threads accessible again.

skydyr wrote:I've noticed that limiting the number of posts per page seems to make some threads accessible again.

(Admin)
If true, that could be the key to fixing the problem. The posts per page figure is easily adjustable.
Can anyone else confirm or refute Skydyr's conjecture?
(/admin)

Joaz Banbeck wrote:

skydyr wrote:I've noticed that limiting the number of posts per page seems to make some threads accessible again.

(Admin)
If true, that could be the key to fixing the problem. The posts per page figure is easily adjustable.
Can anyone else confirm or refute Skydyr's conjecture?
(/admin)

Next time it happens to me I'll test that. My current post per page is 20 for reference.

I had it at 40 b/c I have DSL and we have 2013, and with my life’s remaining time getting shorter (sometimes it seems I’m on Byo-Yomi already) I don’t really have any time to waste waiting for the next page to load <shrug> but now I also set it down to 20 which is really sad, given how fast I read But then again, usually I’m just following threads, not reading several pages of a thread at a time, so it might be less bad than I thought.

Joaz Banbeck wrote:

skydyr wrote:I've noticed that limiting the number of posts per page seems to make some threads accessible again.

(Admin)
If true, that could be the key to fixing the problem. The posts per page figure is easily adjustable.
Can anyone else confirm or refute Skydyr's conjecture?
(/admin)

I got the idea from something someone else had said, but I can't recall who.

Joaz Banbeck wrote:

skydyr wrote:I've noticed that limiting the number of posts per page seems to make some threads accessible again.

(Admin)
If true, that could be the key to fixing the problem. The posts per page figure is easily adjustable.
Can anyone else confirm or refute Skydyr's conjecture?
(/admin)

I used to have mine set at 40, but because of these problems I reduced it to 30. It seemed to reduce the number of timeout connections, but not eliminate them. I really hate the thought of dropping down to 20 or even 10 -- that's so annoying to have to click through so many pages to read the context of a thread.

xed_over wrote:[..] I really hate the thought of dropping down to 20 or even 10 -- that's so annoying to have to click through so many pages to read the context of a thread.

that was exactly my sentiment, too, but now that I thought of it: I’m a regular reader here, so it’s actually quite seldom that I need to read many successive pages of a thread. And if it helps loading pages AT ALL this will for sure be faster that having to wait forever

Joaz Banbeck wrote:

Claint wrote:I had the problems today between 10AM - 11AM GMT. ...

Here in Southern California, I'm on several times per day between 11:00 and 24:00 GMT or later. I haven't seen a slowdown in weeks.

This is strange... I am in southern CA as well and see a lot of timeout issues. True, its much better than it used to be 2-3 weeks ago or so, but the pages still often fail to load on first try. I noticed this is especially bad in the morning, but this is when I mostly do my catching up, so maybe its just coincidence.