Process terminated because the request deadline was exceeded. (Error code 123)

1,386 views
Skip to first unread message

Мария Кокаия

unread,
May 17, 2016, 7:54:45 AM5/17/16
to Google App Engine
All requests to the Google Cloud SQL are returning instant errors: "Process terminated because the request deadline was exceeded. (Error code 123)". We have only 1 active connection to Cloud SQL. We tried to restart SQL instance, no matter. It doesn't work

Osman AKTAS

unread,
May 17, 2016, 8:04:18 AM5/17/16
to Google App Engine
I have same problem. what should i do . Please help :(

17 Mayıs 2016 Salı 14:54:45 UTC+3 tarihinde Мария Кокаия yazdı:

bFlood

unread,
May 17, 2016, 8:10:18 AM5/17/16
to Google App Engine
this is causing major headaches, anything google?

Aditya Agarwalla

unread,
May 17, 2016, 8:10:45 AM5/17/16
to Google App Engine
Likewise. Have had it now for 50 minutes.

Леонтьев Пётр

unread,
May 17, 2016, 8:11:43 AM5/17/16
to Google App Engine
It seems that SQL server only accepts connections but it DOES NOT close it. Why does it happen. When we noticed this problem, our main server has something like 3.500.000 opened connections. It's not fun at all

вторник, 17 мая 2016 г., 15:04:18 UTC+3 пользователь Osman AKTAS написал:

Nithin G

unread,
May 17, 2016, 8:21:19 AM5/17/16
to Google App Engine


On Tuesday, May 17, 2016 at 5:24:45 PM UTC+5:30, Мария Кокаия wrote:
All requests to the Google Cloud SQL are returning instant errors: "Process terminated because the request deadline was exceeded. (Error code 123)". We have only 1 active connection to Cloud SQL. We tried to restart SQL instance, no matter. It doesn't work

Same here. Down for 50 minutes across 3 apps with the same error message

Carlos Vieira

unread,
May 17, 2016, 8:33:43 AM5/17/16
to Google App Engine
I'm experiencing the same problem...

Brian Flood

unread,
May 17, 2016, 8:34:59 AM5/17/16
to google-a...@googlegroups.com

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/-yrM5IXHoaQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@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/c57dc84d-2434-49d8-a8e6-17794373168f%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Baik JoongWon

unread,
May 17, 2016, 8:45:47 AM5/17/16
to Google App Engine
I have same problem.. 
please resolve this problem asap.

2016년 5월 17일 화요일 오후 8시 54분 45초 UTC+9, Мария Кокаия 님의 말:

Леонтьев Пётр

unread,
May 17, 2016, 9:02:01 AM5/17/16
to Google App Engine

The issue is confirmed to affect a subset of Cloud SQL First Generation instances. All further updates will be provided here:

https://status.cloud.google.com/incident/cloud-sql/17010

It seems that it is an internal link... 

Kevin Liu

unread,
May 17, 2016, 9:15:02 AM5/17/16
to Google App Engine
Indeed. Google, that link redirects to the screenshotted page...

Osman AKTAS

unread,
May 17, 2016, 9:18:26 AM5/17/16
to google-a...@googlegroups.com
finally i found soliton :D

First backup and export your currently database. After that create new mysql instance and import all backup to new database . Re define your config file of your application. 

thats all ;)

--
You received this message because you are subscribed to a topic in the Google Groups "Google App Engine" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-appengine/-yrM5IXHoaQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-appengi...@googlegroups.com.
To post to this group, send email to google-a...@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.

Aditya Agarwalla

unread,
May 17, 2016, 9:24:08 AM5/17/16
to Google App Engine
Its back up. Here's the latest from the Status page of Google.


On Tuesday, May 17, 2016 at 5:24:45 PM UTC+5:30, Мария Кокаия wrote:
Screenshot 2016-05-17 18.52.46.png

Nick (Cloud Platform Support)

unread,
May 17, 2016, 10:01:55 AM5/17/16
to Google App Engine
Hey Folks,

Yes, this was indeed a platform issue. We'll have an incident report posted here

bFlood

unread,
May 17, 2016, 11:37:21 AM5/17/16
to Google App Engine
I'm seeing these errors again, did something else break?

Леонтьев Пётр

unread,
May 17, 2016, 11:50:30 AM5/17/16
to Google App Engine
We had small batch or errors too. It took roughly 5-10 minutes. 

вторник, 17 мая 2016 г., 14:54:45 UTC+3 пользователь Мария Кокаия написал:

bFlood

unread,
May 17, 2016, 11:51:53 AM5/17/16
to Google App Engine
yea, its back working again now but that's a little disconcerting considering they closed the incident report earlier today
Reply all
Reply to author
Forward
0 new messages