"An unknown error occured" when trying to create a MySQL instace.

60 views
Skip to first unread message

Rodimiro Cerrato Espinal

unread,
Jan 11, 2019, 10:16:06 PM1/11/19
to Google Cloud SQL discuss
In a project called "nth-baton-226021" in my account rod...@gmail.com I am unable to start instance due this "unknown error".

I can retry the operation in the notifications dialog, but the failure is persistent. It shows "The server has encountered a problem. Please try again."

I am appending the logs below. They do not seem to provide conclusive information.


Thanks,
Rodimiro


{
insertId: "nlhnpzc5ne" 
logName: "projects/nth-baton-226021/logs/cloudaudit.googleapis.com%2Factivity" 
operation: {
id: "289451045299570041" 
last: true 
producer: "cloudsql.googleapis.com" 
}
protoPayload: {
authenticationInfo: {
principalEmail: "rod...@gmail.com" 
}
authorizationInfo: [
0: {
granted: true 
permission: "cloudsql.instances.create" 
resource: "instances/nth-baton-226021:dashboard0" 
resourceAttributes: {
}
}
]
methodName: "cloudsql.instances.create" 
requestMetadata: {
callerIp: "190.241.207.39" 
destinationAttributes: {
}
requestAttributes: {
auth: {
}
time: "2019-01-12T00:11:04.695Z" 
}
}
resourceName: "instances/nth-baton-226021:dashboard0" 
response: {
operation: {
insertTime: "1547251864822" 
operationName: {
instanceName: {
fullProjectId: "nth-baton-226021" 
instanceId: "dashboard0" 
}
operationId: "d9381960-aa03-49c2-a3c3-be0a2b07cb4c" 
}
operationType: "CREATE" 
state: "PENDING" 
userEmailAddress: "rod...@gmail.com" 
}
operationId: "d9381960-aa03-49c2-a3c3-be0a2b07cb4c" 
}
serviceName: "cloudsql.googleapis.com" 
status: {
}
}
receiveTimestamp: "2019-01-12T00:11:05.835541910Z" 
resource: {
labels: {
database_id: "nth-baton-226021:dashboard0" 
project_id: "nth-baton-226021" 
region: "us-central" 
}
type: "cloudsql_database" 
}
severity: "NOTICE" 
timestamp: "2019-01-12T00:11:04.686Z" 
}

yka...@google.com

unread,
Jan 19, 2019, 4:01:43 PM1/19/19
to Google Cloud SQL discuss
Hello,

I tried creating an instance in that zone and it worked. This is a transient issue on the network. I suggest trying again and it should work.
Reply all
Reply to author
Forward
0 new messages