The Forum > General Discussion > Server error
Server error
- Pages:
-
- 1
- 2
- 3
- ...
- 7
- 8
- 9
- Page 10
- 11
- 12
-
- All
Posted by CJ Morgan, Tuesday, 26 May 2009 7:34:02 PM
| |
I'm still having the same problems as others.
When I attempt to load a post and see that it is taking too long, I stop the browser, go to some other links, then come back and try again - usually this works and I don't feel like I am wasting my time as much as just sitting there and getting that dumb server error message. Posted by Fractelle, Wednesday, 27 May 2009 8:55:15 AM
| |
Ratio of successful requests to server error messages - doesn't seem to matter if you are posting, previewing or looking up a User - has now reached one in four.
Is anyone actually listening, I wonder? Posted by Pericles, Wednesday, 27 May 2009 11:30:20 AM
| |
I don't know whether this post made this morning by Banjo, http://forum.onlineopinion.com.au/thread.asp?article=8954#142254 contains any hint as to where problems encountered by users in posting may be occurring.
It appears as if the timestamp has been applied twice to the one post, with a short interval of around six minutes between applications. Of course it is possible that Banjo may have typed the first, and slightly incomplete, entry himself as part of his post, but such is not normally done by users. I mention this because it is an apparent event that might otherwise be easily overlooked. If the first timestamp entry was not typed by Banjo, then something in the OLO software may not be operating correctly, or worse, some hacker may have found a way to fiddle with timestamps. For what it is worth, since changing ISPs from Bigpond to Internode, I have experienced fewer 'Server error' messages, and generally much quicker page loading on OLO. I do not know whether it is relevant, but I understand that Internode operates a lot of its own 'backbone' transmission cabling independently of that of Bigpond. I just wonder whether some 'server error' messages might not originate from some intermediate switching of traffic over the Bigpond network at times of congestion thereon. Just a non-technical speculation: I don't know whether such a thing could be made to occur in order to disguise inadequacies in Bigpond bandwidth as problems originating from the OLO servers. Do any geeks know whether such can happen? For those wanting to continue watching or posting to this topic, bear in mind that it is due to disappear from the default display of topics for one month back at 4:35 PM either today or tomorrow. You can continue to display it by selecting 'show [drop-down selection] discussions per category, having been started one quarter back' from the right-hand drop-down menu at the top of the General Discussion index page, then clicking the 'display' button. Posted by Forrest Gumpp, Wednesday, 27 May 2009 11:36:13 AM
| |
No Pericles, no-one is listening, but I am reading the thread. I have someone starting on Monday who will hopefully be able to clear this issue up. Forest, you'll find that Banjo copied and pasted the post from another thread where he had incorrectly put it. When he copied the post he copied the date stamp.
BTW, I have been keeping track of my use of the site and error messages. So far today I have had 14 page downloads and no error messages. I'll keep looking for one. Maybe it will happen when I try to post this response. Posted by GrahamY, Wednesday, 27 May 2009 11:56:36 AM
| |
Just ran into an unusual server error at 6:20 PM while attempting to refresh the 'On Line Opinion' page (the page where the new articles for each day are first displayed) which I keep open in a tab in Firefox.
Today's articles were all listed, as was the 'Today's most popular articles' panel. Beside that panel appeared a 'server error' notice, Incident number: 33941-2018. None of the articles for the month preceding were listed. A re-try at refreshing yielded the same result. I did note that the status bar showed 'Waiting for onlineopinion' for around 20 - 30 seconds before any loading progress bar appeared on each of these attempts. An attempt at around 6:30 PM was sucessful at refreshing the complete contents of the page with very little delay before the page commenced loading. Posted by Forrest Gumpp, Wednesday, 27 May 2009 6:41:36 PM
|
Correction:
<<Server Error
Incident number: 14028-3219
The fault has been reported to staff.>>
Bugger!