Tuesday, February 11, 2020

[google-cloud-sql-discuss] MySql Second Generation instance restarting with no error message

Hi,

I have a MySql Second Generation db-n1-standard-8 instance that has been restarting by itself with no explanation in the error logs. It doesn't seem to be related to CPU usage or # of network connections. Are there any known issues or situations where this could happen? Does anyone have tips on debugging? I was trying to figure out if it's an OOM issue but since I don't see it in the SQL error logs, I need to look in the Linux system logs, and (correct me if I'm wrong) Google Cloud SQL doesn't give you access to the underlying machine.

The very first line in the logs that is related to the restart is just the beginning of the restart itself: + ROOT=/mysql
And then during the startup process:
[Note] InnoDB: Database was not shutdown normally!
[Note] InnoDB: Starting crash recovery.

This has been happening up to several times a day.

--
You received this message because you are subscribed to the Google Groups "Google Cloud SQL discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-cloud-sql-discuss+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/2674b64f-4cec-4591-933a-a96d5c559125%40googlegroups.com.

No comments:

Post a Comment