Yahoo Forum Archive
This is an archive of the MEFA Yahoo Group, which was shut down by Yahoo in 2019. The archive can be sorted by month and by topic ID. You can use your browser to search by keyword within the month or topic you have open.
Jan | Feb | Mar | Apr | May | Jun | Jul | Aug | Sep | Oct | Nov | Dec | |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 | - | - | - | 182 | 1042 | 655 | 89 | 25 | 263 | 362 | 316 | 285 |
2005 | 189 | 56 | 107 | 538 | 347 | 446 | 97 | 276 | 194 | 358 | 565 | 136 |
2006 | 231 | 66 | 27 | 76 | 117 | 139 | 127 | 56 | 67 | 66 | 159 | 79 |
2007 | 20 | 25 | 7 | - | 29 | 72 | 99 | 143 | 3 | 185 | 83 | 103 |
2008 | 56 | 13 | 3 | 54 | 240 | 141 | 274 | 77 | 51 | 60 | 90 | 106 |
2009 | 28 | 3 | - | 39 | 194 | 101 | 72 | 27 | 22 | 15 | 36 | 24 |
2010 | 67 | - | 1 | 4 | 103 | 138 | 129 | 32 | 13 | 16 | 3 | 30 |
2011 | 1 | - | 17 | 2 | 6 | 25 | 90 | 61 | 32 | 7 | 5 | 8 |
2012 | 30 | - | - | - | 8 | 122 | 76 | - | - | - | - | - |
2013 | - | - | - | - | - | - | - | - | - | - | - | - |
2014 | - | - | - | - | - | - | - | - | - | 1 | - | 2 |
2015 | - | - | - | - | - | - | - | - | - | - | - | - |
2016 | - | - | - | - | - | - | - | - | - | - | - | - |
2017 | - | - | - | - | - | - | - | - | - | - | - | - |
2018 | - | - | - | - | - | - | - | - | - | - | - | - |
2019 | - | - | - | - | - | - | - | - | - | 1 | - | - |
Msg# 9294
I just got the following notice Posted by Barbara Rich July 23, 2008 - 19:33:47 Topic ID# 9294When I tried to access the site. I did wait and try again, and got it a
second time. While I'm guessing it's just high traffic, thought I'd better
mention it:
This is the notice--
Please contact this site's webmaster.
Wait a few minutes and use your browser's "Back" button or click
here<javascript:history.go(-1)>to try again.
------------------------------
If you are the webmaster, your account may have gotten this error for one or
more of the following reasons:
- Your account has used more than its share of the cpu in the past 60
second sliding window.
- Your account has too many concurrent processes running simultanously.
- Your account has consumed too much memory.
- Your site was recently very busy trying to run inefficient scripts.
The solution would be to optimize your applications to use less CPU.
Adding appropriate indeces to your SQL tables can often help reduce CPU.
Using static .html documents instead of painful .php scripts will
practically eliminate CPU usage.
[Non-text portions of this message have been removed]
second time. While I'm guessing it's just high traffic, thought I'd better
mention it:
This is the notice--
Please contact this site's webmaster.
Wait a few minutes and use your browser's "Back" button or click
here<javascript:history.go(-1)>to try again.
------------------------------
If you are the webmaster, your account may have gotten this error for one or
more of the following reasons:
- Your account has used more than its share of the cpu in the past 60
second sliding window.
- Your account has too many concurrent processes running simultanously.
- Your account has consumed too much memory.
- Your site was recently very busy trying to run inefficient scripts.
The solution would be to optimize your applications to use less CPU.
Adding appropriate indeces to your SQL tables can often help reduce CPU.
Using static .html documents instead of painful .php scripts will
practically eliminate CPU usage.
[Non-text portions of this message have been removed]
Msg# 9297
Re: I just got the following notice Posted by Aranel Took July 23, 2008 - 20:50:49 Topic ID# 9294Hi Barbara,
Thanks for the heads-up.
Sometimes it may take longer for the site to come back up, depending on
traffic.
Sorry for the inconvenience,
Aranel
Thanks for the heads-up.
Sometimes it may take longer for the site to come back up, depending on
traffic.
Sorry for the inconvenience,
Aranel
On Wed, Jul 23, 2008 at 7:33 PM, Barbara Rich <aelfwina@gmail.com> wrote:
> When I tried to access the site. I did wait and try again, and got it a
> second time. While I'm guessing it's just high traffic, thought I'd better
> mention it:
>
> This is the notice--
>
> Please contact this site's webmaster.
>
> Wait a few minutes and use your browser's "Back" button or click
> here<javascript:history.go(-1)>to try again.
>
> ------------------------------
> If you are the webmaster, your account may have gotten this error for one
> or
> more of the following reasons:
>
> - Your account has used more than its share of the cpu in the past 60
> second sliding window.
> - Your account has too many concurrent processes running simultanously.
> - Your account has consumed too much memory.
> - Your site was recently very busy trying to run inefficient scripts.
>
> The solution would be to optimize your applications to use less CPU.
> Adding appropriate indeces to your SQL tables can often help reduce CPU.
> Using static .html documents instead of painful .php scripts will
> practically eliminate CPU usage.
>
>
> [Non-text portions of this message have been removed]
>
>
> ------------------------------------
>
> Visit our website: http://www.mefawards.net/MEFA2008/Yahoo! Groups Links
>
>
>
>
[Non-text portions of this message have been removed]
This has happened to me before; though I was able to access the site
again shortly. But today, or at least in the last four hours, it
happened quite frequently - for a few hours, I couldn't return to the
MEFA site; and when I finally made it there, and was working on a
review, the darned message came up again, and I couldn't get back to
the site. At the time this has happened to me, I have no difficulty
getting to other websites.
I don't mind it happening occasionally, but when I get bounced out of
the MEFA site in the middle of writing a review, it's annoying.
RAKSHA, feeling cranky
<<<<<<--- In MEFAwards@yahoogroups.com, "Aranel Took"
<araneltook@...> wrote:
again shortly. But today, or at least in the last four hours, it
happened quite frequently - for a few hours, I couldn't return to the
MEFA site; and when I finally made it there, and was working on a
review, the darned message came up again, and I couldn't get back to
the site. At the time this has happened to me, I have no difficulty
getting to other websites.
I don't mind it happening occasionally, but when I get bounced out of
the MEFA site in the middle of writing a review, it's annoying.
RAKSHA, feeling cranky
<<<<<<--- In MEFAwards@yahoogroups.com, "Aranel Took"
<araneltook@...> wrote:
>depending on
> Hi Barbara,
> Thanks for the heads-up.
>
> Sometimes it may take longer for the site to come back up,
> traffic.got it a
>
> Sorry for the inconvenience,
>
> Aranel
>
> On Wed, Jul 23, 2008 at 7:33 PM, Barbara Rich <aelfwina@...> wrote:
>
> > When I tried to access the site. I did wait and try again, and
> > second time. While I'm guessing it's just high traffic, thoughtI'd better
> > mention it:for one
> >
> > This is the notice--
> >
> > Please contact this site's webmaster.
> >
> > Wait a few minutes and use your browser's "Back" button or click
> > here<javascript:history.go(-1)>to try again.
> >
> > ------------------------------
> > If you are the webmaster, your account may have gotten this error
> > orpast 60
> > more of the following reasons:
> >
> > - Your account has used more than its share of the cpu in the
> > second sliding window.simultanously.
> > - Your account has too many concurrent processes running
> > - Your account has consumed too much memory.scripts.
> > - Your site was recently very busy trying to run inefficient
> >CPU.
> > The solution would be to optimize your applications to use less
> > Adding appropriate indeces to your SQL tables can often helpreduce CPU.
> > Using static .html documents instead of painful .php scripts willGroups Links
> > practically eliminate CPU usage.
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> > ------------------------------------
> >
> > Visit our website: http://www.mefawards.net/MEFA2008/Yahoo!
> >
>>>>>>>>>
Msg# 9300
Re: I just got the following notice Posted by heartofoshun@aol.com July 23, 2008 - 23:12:18 Topic ID# 9294Awww! Poor Raksha--patting you on the head. I've been there myself. I try to
cut-and-paste longer reviews, because I would cry if I lost a long one, but
sometimes I just want to do a quick one on something and it is frustrating.
**************Get fantasy football with free live scoring. Sign up for
FanHouse Fantasy Football today.
(http://www.fanhouse.com/fantasyaffair?ncid=aolspr00050000000020)
[Non-text portions of this message have been removed]
cut-and-paste longer reviews, because I would cry if I lost a long one, but
sometimes I just want to do a quick one on something and it is frustrating.
**************Get fantasy football with free live scoring. Sign up for
FanHouse Fantasy Football today.
(http://www.fanhouse.com/fantasyaffair?ncid=aolspr00050000000020)
[Non-text portions of this message have been removed]
Hi Raksha,
I'm very sorry for the frustration that you (and everyone!) has been
going through. It *always* stinks to lose a review that you spent time
constructing, and I'm sorry anyone has to do that.
These CPU errors that everyone's been experiencing are kind of a new
problem this year. I won't say it never happened to anyone in past years
(I just don't know for sure one way or the other), but it does seem
like it's happening a lot more this year. I've been working with Aranel
and Tanaqui all day today to try to figure out why we're suddenly having
this problem.
We're keeping a firm eye on the problem and are trying out several
approaches to fix the situation. I won't go into technical details, but
hopefully you all will see a lot less of those CPU error messages soon.
In the mean time, it's probably a good idea for the next few days to be
careful when composing your reviews. Maybe type them up in something
other than the website and copy-and-paste it into the form. Or even just
copy what you've typed to your clipboard (so you can paste it into some
other program in case the website gives you problems) before you
preview/submit your review. Like I said, I am cautiously optimistic that
you guys will see a lot less of those error messages really soon - but
I'd hate for anyone to lose a review if it can be avoided. Better to be
reviewing other stories!
And thank you, everyone - both for participating to begin with and
bearing with us as we (by which I mostly mean our intrepid technical
volunteers) sort all this out.
Marta
PGF wrote:
I'm very sorry for the frustration that you (and everyone!) has been
going through. It *always* stinks to lose a review that you spent time
constructing, and I'm sorry anyone has to do that.
These CPU errors that everyone's been experiencing are kind of a new
problem this year. I won't say it never happened to anyone in past years
(I just don't know for sure one way or the other), but it does seem
like it's happening a lot more this year. I've been working with Aranel
and Tanaqui all day today to try to figure out why we're suddenly having
this problem.
We're keeping a firm eye on the problem and are trying out several
approaches to fix the situation. I won't go into technical details, but
hopefully you all will see a lot less of those CPU error messages soon.
In the mean time, it's probably a good idea for the next few days to be
careful when composing your reviews. Maybe type them up in something
other than the website and copy-and-paste it into the form. Or even just
copy what you've typed to your clipboard (so you can paste it into some
other program in case the website gives you problems) before you
preview/submit your review. Like I said, I am cautiously optimistic that
you guys will see a lot less of those error messages really soon - but
I'd hate for anyone to lose a review if it can be avoided. Better to be
reviewing other stories!
And thank you, everyone - both for participating to begin with and
bearing with us as we (by which I mostly mean our intrepid technical
volunteers) sort all this out.
Marta
PGF wrote:
>
>
> This has happened to me before; though I was able to access the site
> again shortly. But today, or at least in the last four hours, it
> happened quite frequently - for a few hours, I couldn't return to the
> MEFA site; and when I finally made it there, and was working on a
> review, the darned message came up again, and I couldn't get back to
> the site. At the time this has happened to me, I have no difficulty
> getting to other websites.
>
> I don't mind it happening occasionally, but when I get bounced out of
> the MEFA site in the middle of writing a review, it's annoying.
>
> RAKSHA, feeling cranky
>
If you have any questions about the archive, or would like to report a technical problem, please contact Aranel (former MEFA Tech Support and current Keeper of the Archive) at araneltook@mefawards.org or at the MEFA Archive group..