This discussion has been archived.
No new comments can be posted.
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Davidadelong on 06:52 PM February 7th, 2006 EST (#1)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
I read your other post on this. Thanks for the info.
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Dittohd on 08:22 PM February 7th, 2006 EST (#2)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
I've never had this problem, although I've had others.
Seems to me that in the instance mentioned, the "back" button would do just as well.
When I type a post, I always make sure I hit the preview button first to make sure that what I typed is placed into memory before hitting "submit". If you REALLY want to be careful, copy what you typed into RAM memory before hitting the "preview" button by highlighting what you typed and then clicking on "copy" in the menu. At that point, if something happens when you hit "submit", you can revert back to the previous post that you typed. If that doesn't work, you have what you typed in your RAM memory. Just go to a blank post entry screen, place the cursor at the beginning of the post window, and click on "paste". Everything you copied into RAM memory will reappear. Just keep in mind that RAM memory holds one entry at a time. If you do the "copy" maneuver twice on different items, the second entry will replace the first.
Complicated? A little, but it sure beats typing several paragraphs and watching them go up into thin air as though you never typed a thing. This happened to me a few times before I started taking precautions.
Dittohd
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Scott
(scott@mensactivism.org)
on 07:26 AM February 8th, 2006 EST (#3)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
Please let us know if there are other problems with the site. I haven't migrated the web server for www.mensactivism.org to the new dedicated server yet.
I've noticed on a few occassions recently that when trying to get to this site that my initial request would hang, and I'd have to hit reload a couple of times. If other people are experiencing this too, I want to know about it.
Thanks,
Scott
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Thundercloud on 10:22 AM February 8th, 2006 EST (#5)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
Scott-
Yeah, it happens to me some times.
Thundercloud.
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Dittohd on 11:50 AM February 8th, 2006 EST (#6)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
This is the problem I have the most often and it happens very often and has been happening for a long time.
I have noticed that when clicks get processed properly, the transaction gets processed and the response is almost instantaneous... and I have a modem connection. This is probably the fastest-loading site I've seen. When my requests hang, I get a "Your request has timed out..." notice after maybe 10-15 seconds or so. By the way, I use Mozilla rather than Internet Explorer.
Rather than wait for that annoying message, I wait about three or four seconds after clicking and if I don't get my response, I hit the "Stop" button and then hit the "Preview" or "Submit" button again. Oftentimes it works on the second request, other times I have to do this three, four, five, or even six times on occasion until I get the normal "immediate" response. I never lose posts or get double submissions when I do this.
Annoying, but I can't say for sure that this only happens on the MANN site. But definitely far and away the most often here. No other site stands out in my mind concerning this problem like MANN does. I always thought the problem was with my system software or browser.
Dittohd
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by Scott
(scott@mensactivism.org)
on 03:20 PM February 8th, 2006 EST (#7)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
Ok, I've tried restarting the web server process but observed the hanging connection problem happening again after only a few minutes. Then I noticed that my server uptime is over 219 days now without a reboot. Well, time to at least give a reboot a try. :)
Scott
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
![](/images/pix.gif) |
|
![](/images/pix.gif) |
![](/images/pix.gif) |
by dschmidt on 08:08 AM February 8th, 2006 EST (#4)
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
![](/images/pix.gif) |
For several months now I've been getting timeouts for several pages on mensactivism.org.
Sometimes even when first going for the front page, sometimes going into a story and sometimes burrowing down into the comments (I use the threaded view). It doesn't happen what I'd call often. Maybe 2-3 times per day and I check for new postings probably 3-4 times per day on weekdays. It hangs for a while until my firewall times out and says the site is non-responsive or unreachable. Hitting back then trying again usually works on the 2nd try and always by the 3rd.
Never happens with other sites I frequent (slashdot, groups.google.com, gmail) so I don't think it's on my end.
|
|
![](/images/pix.gif) |
![](/images/pix.gif) |
|
[an error occurred while processing this directive]
|