The conversation for this thread is being combined into a master thread, as the root cause is the same. Please see this thread for more information: https://goo.gl/6LSRH5
Cheers, Josh On Monday, November 7, 2016 at 12:57:56 PM UTC-8, Mike Lucente wrote: > > They are (or were) part of the same project. I've since reverted to mysql > v1 which works fine. I've removed the v2 instance since then but could > easily recreate it if I thought it might work. > > I did notice that my project did NOT have an @appspot.gserviceaccount.com > service account. I've added it by hand but don't know if that might help(?) > > I was hoping that it would help to resolve yet another app engine/storage > issue that I've recently encountered -- I'm unable to upload to the > blobstore with my old app. I get an HTTP 503 as soon as I hit the upload > button and the logs record nothing. If I try the same upload in a new > project it works fine. Adding the @appspot.gserviceaccount.com entry did > not help with this issue. > > There's something not right with my project and I appear to have no > ability to fix it. Appreciate your help. > > On Sunday, November 6, 2016 at 4:14:53 PM UTC-5, Adam (Cloud Platform > Support) wrote: >> >> I noticed you mentioned that the App Engine app and Cloud SQL instance >> are in the same region, but are they part of the same project? >> >> If they are in the same project, no authorization is needed, otherwise >> you still need to go to 'Access control' -> 'Authorization' -> 'App Engine >> authorization' in the instance details and follow the steps to add the App >> Engine default service account for the App Engine project as an Editor in >> the Cloud SQL instance project. >> >> Even if they're in the same project, you may still have a problem if the >> App Engine default service account is missing from the 'IAM & Admin' >> section of the project. If it was deleted, usually you need to recreate the >> project. However, there's a workaround which you can try >> <https://code.google.com/p/googleappengine/issues/detail?id=13085> to >> recover it in the Cloud Console. >> >> On Friday, November 4, 2016 at 3:40:09 PM UTC-4, Mike Lucente wrote: >>> >>> I'm getting the following when trying to connect to Cloud SQL from app >>> engine using python: >>> >>> super(Connection, self).*init*(*args, **kwargs2) OperationalError: >>> (2013, "Lost connection to MySQL server at 'reading initial communication >>> packet', system error: 38") >>> >>> >>> I've posted this on stackoverflow: >>> >>> >>> http://stackoverflow.com/questions/40425349/unable-to-connect-to-cloud-sql-from-app-engine-python >>> >>> >>> No luck so far. My appengine app is a few years old and I'm concerned >>> that google may need to get involved. Unfortunately I'm a bronze customer >>> and have no way to ask for technical support. >>> >>> >>> Thought I'd drop it in here too in case someone has an answer. If I'm >>> unable to resolve I may have set up my database elsewhere. >>> >>> >>> Hoping someone has a solution. >>> >>> >>> Thanks. >>> >> -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/06a31437-9016-4332-be9f-f680a232ee90%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
