Google cloudsql down for about 4 hours

已查看 67 次
跳至第一个未读帖子

Ricky Li

未读,
2017年6月9日 09:07:562017/6/9
收件人 Google Cloud SQL discuss
My Google cloudsql located in asia-northeast1 (IP: 35.187.194.229)  have down for about 4 hours. But nobody support for it. What I can do?

Ricky Li

未读,
2017年6月9日 09:07:572017/6/9
收件人 Google Cloud SQL discuss
My Google cloudsql located in asia-northeast1 ( IP: 35.187.194.229) have down for about 4 hours. But nobody support for it. What I can do?

Ricky Li

未读,
2017年6月9日 09:07:572017/6/9
收件人 Google Cloud SQL discuss
My Google cloudsql located in asia-northeast1 ( IP: 35.187.194.229  )have down for about 4 hours. But nobody support for it. What I can do?

Irina (Google Cloud Support)

未读,
2017年6月9日 10:16:372017/6/9
收件人 Google Cloud SQL discuss
I'm able to ping your Cloud SQL IP address. You might have been affected by known network connectivity issue in 'asia-norrtheast1' region which should be resolved by now and can be tracked on Google Cloud Status Dashboard [1].

If you think that this outage is not related to your case, provide any error message you see and other relevant information.

Ricky Li

未读,
2017年6月9日 19:35:052017/6/9
收件人 Google Cloud SQL discuss
I am able to ping it too. But it is a sql server. The php tell me got the following error:

Error!: SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', 




Irina (Google Cloud Support)於 2017年6月9日星期五 UTC+8下午10時16分37秒寫道:

Ricky Li

未读,
2017年6月9日 19:40:032017/6/9
收件人 Google Cloud SQL discuss
How to fix it. Just ping the IP? My php got the following error:
Error!: SQLSTATE[HY000] [2013] Lost connection to MySQL server at 'reading initial communication packet', system error: 0

Ricky Li於 2017年6月10日星期六 UTC+8上午7時35分05秒寫道:

Ricky Li

未读,
2017年6月9日 19:46:192017/6/9
收件人 Google Cloud SQL discuss
If everything OK, why I still complain about it?
If everything OK, why the cloudsql storage is zero ?
If everything OK, why the cloudsql still mark as "maintenance " for about 19 hours ?



Ricky Li於 2017年6月10日星期六 UTC+8上午7時40分03秒寫道:

Ricky Li

未读,
2017年6月9日 19:50:252017/6/9
收件人 Google Cloud SQL discuss
The " Google Cloud Status Dashboard " currently only trace the "mkpcdb-failover", But "mkpcdb" is down.





Ricky Li於 2017年6月10日星期六 UTC+8上午7時46分19秒寫道:

Ricky Li

未读,
2017年6月9日 19:57:242017/6/9
收件人 Google Cloud SQL discuss
Connect by my compute engine ( IP: 35.189.152.193 ) that have the access right. And got the following errror:

mysql -h 35.187.194.229 -u root -p
Enter password: 
ERROR 2003 (HY000): Can't connect to MySQL server on '35.187.194.229' (110)



Ricky Li於 2017年6月10日星期六 UTC+8上午7時50分25秒寫道:

Ricky Li

未读,
2017年6月9日 20:51:352017/6/9
收件人 Google Cloud SQL discuss

Attached with google cloud platform screen:







Ricky Li於 2017年6月10日星期六 UTC+8上午7時57分24秒寫道:
回复全部
回复作者
转发
0 个新帖子