[google-appengine] Re: Can't access my application
Hi all, This is a known issue and we're looking into it now. It appears to be affecting some users accessing applications served off of custom dasher domains: http://mail.google.com/support/bin/answer.py?hl=enanswer=46346#403 We're working to lessen the impact that these problems can have on App Engine applications, and to provide a CAPTCHA mechanism for users who see this response. Pete Koomen, App Engine Team On Sun, Mar 22, 2009 at 8:43 AM, B.J. bjp...@gmail.com wrote: Some of my users are reporting the same problem. Anyone know what is going on? On Mar 22, 2:37 am, WallyDD shaneb...@gmail.com wrote: I can't do much more than try again another day... Good ol google;http://code.google.com/status/appengine On Mar 22, 3:18 am, baytiger troels...@gmail.com wrote: Same problem for me, many of my users are complaining they see the same. It's been going on for more than 24 hours now. Google can you please fix this? There has been _a lot_ of outages the past month, it's not particularly credible for user-experience :( On 22 Mar., 07:56, Brandon Thomson gra...@gmail.com wrote: I fixed it temporarily by going to a neighbor's house for internet connection... but it is working on my original connection again now? I am confused what is the cause... On Mar 22, 2:13 am, WallyDD shaneb...@gmail.com wrote: Where do I get my membership badge? I have the same webpage :( On Mar 22, 2:00 am, William searchmon...@gmail.com wrote: I'm also getting this message on my app now. )-: On Mar 21, 5:14 am, Brandon Thomson gra...@gmail.com wrote: When I try to access my application I get the following message: We'resorry... ... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, we can't process your request right now. We'll restore your access as quickly as possible, so try again soon. In the meantime, if you suspect that your computer or network has been infected, you might want to run a virus checker or spyware remover to make sure that your systems are free of viruses and other spurious software. If you're continually receiving this error, you may be able to resolve the problem by deleting your Google cookie and revisiting Google. For browser-specific instructions, please consult your browser's online support center. If your entire network is affected, more information is available in the Google Web Search Help Center. We apologize for the inconvenience, and hope we'll see you again on Google. What is the cause and how can this be fixed? -- Pete --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Can't access my application
Sorry: this appears to be affecting some users accessing applications served off of custom *Google Apps* domains: On Sun, Mar 22, 2009 at 11:01 AM, Pete Koomen pkoo...@google.com wrote: Hi all, This is a known issue and we're looking into it now. It appears to be affecting some users accessing applications served off of custom dasher domains: http://mail.google.com/support/bin/answer.py?hl=enanswer=46346#403 We're working to lessen the impact that these problems can have on App Engine applications, and to provide a CAPTCHA mechanism for users who see this response. Pete Koomen, App Engine Team On Sun, Mar 22, 2009 at 8:43 AM, B.J. bjp...@gmail.com wrote: Some of my users are reporting the same problem. Anyone know what is going on? On Mar 22, 2:37 am, WallyDD shaneb...@gmail.com wrote: I can't do much more than try again another day... Good ol google;http://code.google.com/status/appengine On Mar 22, 3:18 am, baytiger troels...@gmail.com wrote: Same problem for me, many of my users are complaining they see the same. It's been going on for more than 24 hours now. Google can you please fix this? There has been _a lot_ of outages the past month, it's not particularly credible for user-experience :( On 22 Mar., 07:56, Brandon Thomson gra...@gmail.com wrote: I fixed it temporarily by going to a neighbor's house for internet connection... but it is working on my original connection again now? I am confused what is the cause... On Mar 22, 2:13 am, WallyDD shaneb...@gmail.com wrote: Where do I get my membership badge? I have the same webpage :( On Mar 22, 2:00 am, William searchmon...@gmail.com wrote: I'm also getting this message on my app now. )-: On Mar 21, 5:14 am, Brandon Thomson gra...@gmail.com wrote: When I try to access my application I get the following message: We'resorry... ... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, we can't process your request right now. We'll restore your access as quickly as possible, so try again soon. In the meantime, if you suspect that your computer or network has been infected, you might want to run a virus checker or spyware remover to make sure that your systems are free of viruses and other spurious software. If you're continually receiving this error, you may be able to resolve the problem by deleting your Google cookie and revisiting Google. For browser-specific instructions, please consult your browser's online support center. If your entire network is affected, more information is available in the Google Web Search Help Center. We apologize for the inconvenience, and hope we'll see you again on Google. What is the cause and how can this be fixed? -- Pete -- Pete --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Latency Issue - More Feedback!
Hi Greg, We're listening, and we feel your pain. The App Engine team has been working very hard to resolve this and we'll post updates as soon as we have them. I'll try to address what I can right now: 1. The latency issues are related to the planned maintenance on Monday night. They were unexpected, and we are working on infrastructure improvements to ensure this won't happens again. If you'd like more data on serving and API latency and error rate, you can look at our own live monitoring data here http://code.google.com/status/appengine 2) We expect a fix to be in place by EOD to fix the issues you are currently seeing. We will keep you updated if this is not the case. When these issues are fixed, you should only see a small difference (possibly 10-20%) in the performance of your application as compared to earlier this week. However, one way or the other, we will return our previous configuration by Monday 3/9. Thanks for your patience through this. Pete, App Engine Team On Mar 4, 12:18 pm, Greg g.fawc...@gmail.com wrote: Please can we have more information about the current latency issue. Pointing us tohttp://groups.google.com/group/google-appengine-downtime-notify doesn't help when the last post there is two days old. Specifically: 1. Cloudstatus.com shows very clearly that everything went to hell in handbasket after the upgrade earlier this week. Can Google confirm this is the cause of the latency? 2. Is the scheduled maintenence next week likely to cure the problem (then please bring it forward) or make it worse (then please delay it)? I'm sure the lack of information is because the engineers who know what is happening are so busy trying to resolve the issue that they can't post. Or maybe they are all smoking joints while watching Lost, snickering about all the poor muppets out there struggling to find ways of streamlining their apps to make them work. Without feedback we don't know... This is severely denting our (paying) customers confidence in my app, and likewise our confidence in Appengine. We spent yesterday wringing the last ounce of performance out of our app, and if I don't hear any more, today (it's morning in New Zealand) will be spent investigating how big a deal it will be to migrate it to a dedicated mod_python/ PostgreSQL system. Other appengine developers - please star this message so we get a response from Google. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: 502 Server Errors after upgrade?
Hi all, Some apps are still seeing inreased latencies--we're working hard to isolate this. We'll keep you updated as we do. Pete On Mar 3, 11:22 am, Arun Shanker Prasad arunshankerpra...@gmail.com wrote: Hi, My app still seems to be experiencing this problem.. I seem to get 502 - Bad Gateway error at random, also the the serving of the app is very slow. Writes are the most expensive, timing out randomly.. Thanks, Arun Shanker Prasad. On Mar 4, 12:18 am, Sylvain sylvain.viv...@gmail.com wrote: Yes I don't know why but today the main request is 1000 ms-cpu higher than yesterday. So the CPU Quota is higher than usual. Regards On 3 mar, 20:08, Brandon Thomson gra...@gmail.com wrote: Ditto. Datastore performance is very bad too. On Mar 3, 2:04 pm, Brenton toonscr...@nvbell.net wrote: It still feels down to me. Our app keeps timing out. Friends' apps too. 208 - try again in 30 secs. Same as last night. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: New Terms of Service :-(
Hi, The sections that have changed in our new terms of service are Section 4 and Section 10.3. We added some language around billing and payments, and also a clause that prevents users from using multiple cloned free applications to avoid usage charges that would have otherwise been incurred by single app. The admin console does not currently provide developers with a way to delete applications. You can effectively delete an app by deploying an empty app using the same verison number that is currently live. Deployment does not require acceptance of our terms. Thanks, Pete Koomen, App Engine Team On Feb 28, 5:10 am, KillIEbrowser davide.rogn...@gmail.com wrote: Follow the steps: 1. Sign-in: Google App Engine 2. Appears: Accept New Terms of Servicehttp://appengine.google.com/start/newtos 3. Press: [Cancel] 4. Redirect to:http://code.google.com/appengine/ 4. Now I can not delete my apps... On Feb 28, 1:56 pm, Barry Hunter barrybhun...@googlemail.com wrote: Considering they are refering to Billing, which was only just introduced, its a fair bet that its new. What specificly do you object to in that quote? On 28/02/2009, KillIEbrowser davide.rogn...@gmail.com wrote: For example, is this a new Term? 4.2. A bill will be issued to your online account for all charges accrued in excess of the Fee Threshold. For use of the Service in excess of any portion of the Fee Threshold, you shall be responsible for all charges up to the amount set in your online account, and shall pay all charges in U.S. Dollars or in such other currency as agreed to in writing by the parties. Unless agreed to by the parties in writing, you shall pay all charges in accordance with the payment terms in the Service FAQ. Late payments may bear interest at the rate of 1.5% per month (or the highest rate permitted by law, if less). Charges are exclusive of taxes. You are responsible for paying all taxes and government charges, and all reasonable expenses and attorneys fees Google incurs collecting late amounts. To the fullest extent permitted by law, you waive all claims relating to charges unless claimed within 60 days after the charge (this does not affect your credit card issuer rights). Charges are solely based on Google's measurements of your use of the Service, unless otherwise agreed to in writing. To the fullest extent permitted by law, refunds (if any) are at the discretion of Google and only in the form of credit for the Service. Nothing in these Terms obligates Google to extend credit to any party. You acknowledge and agree that any credit card and related billing and payment information that you provide to Google may be shared by Google with companies who work on Google's behalf, such as payment processors and/or credit agencies, solely for the purposes of checking credit, effecting payment to Google and servicing your account. Google may also provide information in response to valid legal process, such as subpoenas, search warrants and court orders, or to establish or exercise its legal rights or defend against legal claims. Google shall not be liable for any use or disclosure of such information by such third parties. Google reserves the right to discontinue the provision of the Service to you for any late payments. 4.3. Google may change its fees and payment policies for the Service with ninety (90) days prior notice. However, Google may change the Fee Threshold limits at its discretion. Changes to the fees or payment policies will be posted in the Service FAQ or at http://code.google.com/appengine/terms.html(orsuch other URL Google may provide from time to time). Any outstanding balance becomes immediately due and payable upon termination of the Terms for any reason. On Feb 27, 8:40 pm, KillIEbrowser davide.rogn...@gmail.com wrote: Why I must accept the New Terms of Service ? What is the delta? /\ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: 502 Server Errors after upgrade?
Hi all, we'll continue posting updates about this issue to our status site and downtime-notify group as we continue investigating: http://code.google.com/status/appengine http://groups.google.com/group/google-appengine-downtime-notify Thanks for your patience, we're still working hard on this one. Pete On Mar 3, 3:07 pm, Brandon Thomson gra...@gmail.com wrote: I think my errors are gone now. Thank you Google! On Mar 3, 1:44 pm, Artem p.ar...@gmail.com wrote: I am still getting 502s in our App (which is an instance of Rietveld without any changes except securing it with a password). app id is: wsl-codereview We have changed nothing. Problems started last night, but now every request is a 502. Artem On Mar 3, 1:25 pm, Brett Slatkin brett-appeng...@google.com wrote: Hi Nick, On Tue, Mar 3, 2009 at 8:55 AM, Nick Winter livel...@gmail.com wrote: http://code.google.com/status/appengine/detail/serving/2009/03/03#ae-... Just about every day for the past several weeks, there's been elevated latency like this, usually at similar times of day. It was unfortunate and frustrating before, but since last night our development is stalled because every part of App Engine is too slow to do any testing or data manipulation right now. 5 seconds per request? I'm confident that the App Engine team will get a handle on the performance and everything will be shiny once more, but it'd be nice to hear some word as to what's going on. Are the servers just overloaded? Did something go wrong with the maintenance last night? Is anomaly-yellow serving to be expected? We had some unexpected issues during the maintenance last night which caused elevated latencies and errors for all applications. We resolved the issue around 8:45pm last night and things have returned to normal since. Please let me know if you're still seeing any problems. As for the elevated latency for the dynamic request metric (that you linked to), this is primarily a product of alert tolerances. We're still tuning our status site metrics to match real-world expectations of App Engine performance. You'll notice today that we've raised some of these tolerances by a little bit, causing many of the lines to go back to a blue color (i.e., everything OK). -Brett --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: scheduled maintenance
Hi all, Thanks very much for your posts--we're definitely reading. Regarding the timing of our scheduled maintenance, we try our best to pick times that will have the smallest effect on our developers. This isn't easy and, as you've pointed out, it's never going to work seamlessly for everyone. Regarding the existence of scheduled maintenance--we completely agree. We're working on eliminating the need for these and will keep you posted on our progress. For now, you can subscribe to our downtime-notify group: http://groups.google.com/group/google-appengine-downtime-notify and monitor our system status page: http://code.google.com/status/appengine for updates. Thanks, Pete Koomen, App Engine Team On Mar 2, 8:11 pm, GregF g.fawc...@gmail.com wrote: My rant about the same thing here... http://groups.google.com/group/google-appengine/browse_thread/thread/... --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Annoucement: you may now purchase additional computing resources
Hi Matija, The per-minute CPU limit is independent of the number of active requests you can run. Let's assume your requests were taking on average 200ms of CPU time and completed in 200ms wall clock time, to keep things simple. There are at least three limits that come into play here. Looking at the free quotas (for apps that *do not* have billing enabled): Per-minute quota on CPU Time: 15min/min = 900,000ms/min = 4500 req/ min = 75 req/sec Per-minute quota on HTTP Requests: 7400 req/min = ~123req/sec 30 active simultaneous requests: (1000ms/sec / 200ms/req) * 30 = 150req/sec In this case, the per-minute CPU Time quota is the limiting factor. If you were to halve the CPU wall time of each requests, then the per-minute HTTP Request quota would become the limiting factor. Does this make sense? Keep in mind, the free quotas will be changing on May 25th, 2009. See http://code.google.com/appengine/docs/quotas.html#Free_Changes for more details. Pete f each of your requests takes 200ms of CPU time on average, you'd have enough CPU per minute to handle roughly 75 requests per second On Feb 25, 4:17 am, Matija matija.jerko...@gmail.com wrote: How can '...An application operating entirely within the free quotas can process around 30 active dynamic requests at any given moment...' if maximum rate for CPU time within free default quota is 15 CPU-min/ min ? Should you correct that statement to 15 active dynamic requests ? Pozdrav, MATijA. On Feb 24, 10:30 pm, Jeff S j...@google.com wrote: Hi all, We've just announced that it is now possible to purchase additional quota for your application. To borrow from our blog post, We're psyched to announce that developers can now purchase additional computing resources on App Engine, enabling apps to scale beyond our free quotas. This has been our most requested improvement to App Engine and we're thrilled to deliver it, as promised. You can now set a daily budget for your app that represents the maximum amount you're willing to pay for computing resources each day. You allocate this budget across CPU, bandwidth, storage, and email, and you pay for only what your app consumes beyond the free thresholds... More details are available at the following locations: Blog post:http://googleappengine.blogspot.com/2009/02/new-grow-your-app-beyond-... Updated quota documentation page:http://code.google.com/appengine/docs/quotas.html Documentation on purchasing additional quota:http://code.google.com/appengine/docs/billing.html Billing FAQs:http://code.google.com/appengine/kb/billing.html Questions? Comments? :-) Happy coding, Jeff --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Announcing: System Status Dashboard, Quota Details Page, and a Preview of Billing
Hi Thomas--this is correct. The quotas not marked as adjustable will be raised considerably when Billing is released. Pete On Mon, Dec 22, 2008 at 2:02 PM, Thomas Johansson prenc...@gmail.comwrote: It's 1.3 million currently, meaning about 15.42 req/s for the *entire* day. It's been growing over time though. I believe the hard limit until very recently was 650.000. My guess is that the request limit and a lot of other quotas will get adjusted based on the payable ones. The request limit for example will probably rise with bandwidth allotment. On Dec 22, 4:34 pm, bFlood bflood...@gmail.com wrote: I noticed in the new quotas page that number of requests is not adjustable. so no matter what, if a site gets a spike in traffic that is larger then the default request limit, it will be shutdown? this seems odd to me, althought maybe I really need to examine how large the cap is first cheers brian On Dec 21, 2:10 pm, Thomas Johansson prenc...@gmail.com wrote: The docs are fine, I was referring to the billing of the other quotas. Or will they rise proportionally to CPU usage, storage and bandwidth? - Thomas On Dec 21, 7:56 pm, Dan Sanderson dansander...@google.com wrote: On Sat, Dec 20, 2008 at 11:06 PM, Thomas Johansson prenc...@gmail.comwrote: Speaking of the billing, perhaps you can elaborate on the other quotas in place, like sending emails, urlfetch and so forth? The best sources of info on the quotas right now are the Quotas section of the Admin Console, and the new section in the documentation: http://code.google.com/appengine/docs/quotas.html The docs have the definitions, and the Console has the precise amounts for your application (the free levels) and how much your app has used in the past 24 hours. Please let me know if you have any further questions after looking at these pages, so we can improve the docs. -- Dan -- Pete --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Memcache API Timing out
Hi Gayle, Would you mind sending either your app_id or a stack trace to [EMAIL PROTECTED] We haven't seen this globally and would like to look into it. Thanks! Pete, App Engine Team On Nov 13, 9:29 am, Gayle Laakmann [EMAIL PROTECTED] wrote: Despite what the post at the link below says, memcache is actually timing out and throwing a DeadlineExceededError. Furthermore, it hardly seems accurate to say that our apps should continue serving normally. The quota limits are so ridiculously low that we CAN'T serve pages without caching. http://groups.google.com/group/google-appengine-downtime-notify/brows... We will be taking memcache offline tomorrow morning from 9-10am PST (GMT-8) for routine maintenance. Calls to the memcache API will *not* throw exceptions but will instead return false for set() calls and None for get() calls (just like any other cache miss.) Your app should continue serving normally during this period, and we'll keep you updated on our progress. Additonally, I'd like to make two suggestions: 1. If you're going to take down memcache, wouldn't it make sense to remove the quota limits? It hardly seems fair to penalized for exceeding quota when caching is disabled. 2. If you have to take down our apps for an hour, can you pick something like 2am - 3am? I know you don't want to go to work at 2am, but it's not really ok to take down our apps for an hour during prime- time. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Google App Engine group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
