Technical: Access to WLDG early in the day.

I frequently find it difficult to access WLDG between 8 and 9 o'clock in the morning European time and on rare occasions until much later."General Error" messages are frequent. Usually after repeated attempts over 30 minutes or so I can get in but the response times remain slow.

Is there a reason for this?

The same does not apply to other sites which I visit regularly.

[David M. Bueker]

You're not the only one. Robin & I have often tried to figure out the true cause, but to little avail.

I have had the same problem. Despite being aself-confessed computer illiterate, I have understood that this was a period of "adjustment" of some sort to the site. I do not find it all that inconvenient because my outage generally lasts no more than 5 - 10 minutes and can be counted on in Israel to take place at between 09:00-09:15.

On the few occasions during which the outage was longer or the message repeating, I simply closed and reopened my internet connection and all was well.

Best
Rogov

I do not find it all that inconvenient because my outage generally lasts no more than 5 - 10 minutes and can be counted on in Israel to take place at between 09:00-09:15.

It is inconvenient to me because we open the bookshop at 11:00 so at 9:00 I am usually drinking coffee and reading wine sites - and almost every day this site shows error messages. And not for 5-10 mins but usually all the way until 10:00 when I have to leave home!

Gladly in the evenings it seems to work fine for me, so it's not that big a deal. Just a minor annoyance.

It hits me in the early evening at about 6:30pm, but generally does not last for too long.

[David M. Bueker]

Because of this issue, one of hte very first things I do when I get up at 5 AM is check the WLDG to see if General SQL is trying to stage a military coup. If he is I notify Robin by PM & he usually can get it fixed pronto.

Is this now happening on a more than occasional basis? I have not seen it for a couple of weeks.

Because of this issue, one of hte very first things I do when I get up at 5 AM is check the WLDG to see if General SQL is trying to stage a military coup. If he is I notify Robin by PM & he usually can get it fixed pronto.

Is this now happening on a more than occasional basis? I have not seen it for a couple of weeks.

By 11 am our time (5am yours, I think), access to WLDG is usually OK, as it is right now. However rare is the day between 8am and 9am our time when it is not "General Error" (or such a wait that I move elsewhere) on first and usually many subsequent tries.

[Robin Garr]

Folks, this is an irritating, but occasional, issue that our server technicians are seeking to pursue. The "too many connections," as the name implies, indicates that the server has become overloaded from excessive use. This is odd because early in the morning, US time, should be a relatively low-traffic period. A mass attack by Asian hackers is certainly possible, but seems unlikely. Bottom line, our techs are looking into it, and yesterday they created a little computer routine to try to log errors and detect exactly what was happening just before "General Error" appeared.

You guys could actually help by posting the EXACT time when you see this. That would help our guy track errors in the log.

Robin, Hi....


For me, daily and religiously between 09:00-09:15 Tel Aviv time (which places it at 02:00-02:15 New York Time)
Personally, I have just taken it in stride.

Best
Rogov

Its 11.17pm MT. No problem getting in.

I just got in on my first try. Has something been done or is it just luck?

Hey guys, Robin asked for the times that it DOES go wrong. Maybe they have sorted it as tonight there were no problems for me. Well done to Robin's hosts if they have caught the baddie!

[Robin Garr]

For me, daily and religiously between 09:00-09:15 Tel Aviv time (which places it at 02:00-02:15 New York Time)
Personally, I have just taken it in stride.

I have discovered, Rogov, that this particular outage - about 10 to 15 minutes around 2 a.m. NY time - is the period when our server is entirely backed up. This is an important process because it ensures that, in case of some disaster like hard-disk failure, we could completely restore all data at least through the daily backup hour. That time is chosen because traffic overall is lowest then, although it's unfortunate that it is business hours in Europe and Israel.

Technically, during that period the forum is not literally down, but the backup requires so many resources that the system runs extremely slow, so much so that your browser is likely to time out and give up before you get to a page. Frustrating, but it should not normally last longer than 10-15 minutes.

The "Too Many Connections - General Error" message is random and sporadic, and we would like reports on exactly what time it happens so we can match occurrences to events in the log.

For me, daily and religiously between 09:00-09:15 Tel Aviv time (which places it at 02:00-02:15 New York Time)
Personally, I have just taken it in stride.

I have discovered, Rogov, that this particular outage - about 10 to 15 minutes around 2 a.m. NY time - is the period when our server is entirely backed up.

That coincides with 6pm to 6.15pm NZ (normal time) - which is when I particulary experience it.

I have discovered, Rogov, that this particular outage - about 10 to 15 minutes around 2 a.m. NY time - is the period when our server is entirely backed up.

That is clearly our problem; between 8 and 8.30 (6 hours ahead of New York) is usually when I switch on. I think that I actually experienced the back up process turning on this morning at about 8.10. I got into the site immediately but when I tried to call up Sue's above post the system blocked.

Got a general failure tonight at about 6:30pm NZ time, which equates to 2:30am EST as far as I can determine. From about 6:15pm I did not get any page served at all. No error message, no page, no nothin'.

[David M. Bueker]

That probably coincides with the backup Neil. We also had a General SQL error yesterday at 6:45 PM EDT, so at least we know it's not you.