This page discusses some of the error messages encountered in Cloud SQL.
Overview
Error messages in Cloud SQL come from many sources and appear in many places. Some error messages come from the database engines themselves, some from the Cloud SQL service, some from client applications, and some are returned by calls to the Cloud SQL Admin API.
This page includes some of the most common errors seen in Cloud SQL. If you do not find the error code or message you are looking for here, you can look for source reference material here:
If you don't find the reference material for the error message that you're seeing, you can also search in some of these places where other users may have relevant experience:
- Cloud SQL questions on Stack Overflow
- Public issue tracker for Cloud SQL
- DBA Stack Exchange
- Cloud SQL discuss group
- Google Cloud Slack community
- Google Cloud on Reddit
Operational errors
A | B | C | D | E | F | G | I | L | M | N | O | P | Q | R | S | T | U | W
Error message | Troubleshooting |
---|---|
Access denied for user 'XXX'@'XXX' (using password: XXX) | There could be several causes, including:
Try these things ...
|
Allocated IP range not found in network. | VPC peerings were not updated after an allocated range was modified
or removed.
You need to
modify the private connection. Use the following command, and make
sure to use the gcloud services vpc-peerings update \ --network=VPC_NETWORK \ --ranges=ALLOCATED_RANGES \ --service=servicenetworking.googleapis.com \ --force |
Error message | Troubleshooting |
---|---|
Bad request. | This message can have many causes. Illegal Argument is one
of the most common. In this case, the request is using either the wrong
argument or an invalid value for the argument. For the many other
causes, the error message might contain a useful hint.
For |
Error message | Troubleshooting |
---|---|
Cannot modify allocated ranges in CreateConnection. Please use UpdateConnection. | VPC peerings were not updated after an allocated range was modified or removed.
You need to modify the private connection.
Use the following command, and make sure to use the gcloud services vpc-peerings update \ --network=VPC_NETWORK \ --ranges=ALLOCATED_RANGES \ --service=servicenetworking.googleapis.com \ --force |
Constraints/sql.restrictAuthorizedNetworks. | The cloning operation is blocked by the
Authorized Networks configuration. Authorized Networks
are configured for public IP addresses in the Connectivity section of
the Google Cloud console, and cloning isn't permitted due to
security considerations.
Remove all |
Could not allocate a new page for database database_name
because of insufficient disk space in filegroup PRIMARY . |
The PRIMARY filegroup, which is the main and default filegroup in a
database, has run out of space.
Use the Consider the following solutions:
|
Error message | Troubleshooting |
---|---|
Disk is full. | The primary instance disk size can become full during replica creation.
Edit the primary instance to upgrade it to a larger disk size. |
Error message | Troubleshooting |
---|---|
Failed to create subnetwork. | No more available addresses in the IP range.
Couldn't find free blocks in allocated IP ranges. Please allocate new ranges for this service provider. There are no more available addresses in the allocated IP range. Consider these possible scenarios:
For each of the above scenarios, you can elect to either expand the existing or allocate an additional IP range to the private service connection. If you're allocating a new range, take care to not create an allocation that overlaps with any existing allocations. After creating a new IP range, update the VPC peering with the following command: gcloud services vpc-peerings update \ --service=servicenetworking.googleapis.com --ranges=OLD_RESERVED_RANGE_NAME,NEW_RESERVED_RANGE_NAME \ --network=VPC_NETWORK --project=PROJECT_ID \ --force If you're expanding an existing allocation, take care to only increase the allocation range and not decrease it. For example, if the original allocation was 10.0.10.0/24, make the new allocation at least 10.0.10.0/23. In general, if starting from a /24 allocation, decrementing the /mask by 1 for each condition (additional instance type group, additional region) is a good rule of thumb. For example, if trying to create both instance type groups on the same allocation, going from /24 to /23 is enough. After expanding an existing IP range, update the vpc peering with following command: gcloud services vpc-peerings update \ --service=servicenetworking.googleapis.com --ranges=RESERVED_RANGE_NAME \ --network=VPC_NETWORK \ --project=PROJECT_ID \ --force |
Error message | Troubleshooting |
---|---|
Internal error. | The project could be missing the Service Networking service account
required for this feature.
To repair service permissions, disable the
|
Invalid request: Incorrect Service Networking config for instance. | Service Networking API isn't enabled in the project.
Enable the |
Error message | Troubleshooting |
---|---|
Network association failed. | The Service Networking API isn't enabled in the project.
Enable the |
Error message | Troubleshooting |
---|---|
Operation failed because another operation was already in progress. | Most operations in Cloud SQL are synchronous. You can
run only one at a time.
Wait for the previous operation to finish before beginning another. |
Operation isn't valid for this instance. | This error is returned from an API call to instances.restoreBackup ,
and it means that you cannot restore from backup to an instance with a storage size
(XX GB) smaller than the backup size (YY GB).
Edit the target instance to increase its storage size. |
Error message | Troubleshooting |
---|---|
Quota exceeded. | You reached the limit of your per-minute or daily quota. Review the
quotas and limits for Cloud SQL.
Request an increase to your quotas from the Google Cloud console. |
Error message | Troubleshooting |
---|---|
SSL error: invalid padding. | Server certificate error.
Create a new server certificate and rotate. |
System error occurred. |
Try these things ...
|
Error message | Troubleshooting |
---|---|
Table definition changed. | During the export process a change occurred in the table.
The dump transaction can fail if you use the following statements during the export operation:
Remove any of these statements from the dump operation. |
Temporary file size exceeds temp_file_limit. | The temp_file_limit flag is set too low for your database usage.
Increase the |
Error message | Troubleshooting | |
---|---|---|
x509: certificate isn't valid for any names. | Known issue: The
Cloud SQL Proxy Dialer isn't compatible with Go 1.15 at this time.
Until fixed, see this discussion on GitHub, which includes a workaround. |
Operation | The issue might be... | Things to try... |
---|---|---|
Add user | If the user already exists in the database, this error can occur when you try to add them. | Check to make sure the user doesn't already exist in the database. |
Backup | If you see this during automated or manual backups, it's likely the instance disk is full. | If the temporary file size is taking up too much space, you can restart the instance to remove the file and free up the disk space. Otherwise, you might need to upgrade your instance to a larger disk size. |
Clone | This can occur when there is a shortage of resources in the selected zone. | Try another zone in the region, or wait and try again later. |
Create instance |
|
|
Export | If you see this while trying to export a database to a Cloud Storage bucket, the transfer may be failing due to a bandwidth issue. | The Cloud SQL instance may be located in a different region than the Cloud Storage bucket. Reading and writing data from one continent to another involves a lot of network usage, and can cause intermittent issues like this. |
Failover (automatic) | An automatic failover operation can produce this error message when the service detects that the primary instance is still responsive. | There is nothing to be done in this case. The failover won't occur because it isn't needed. |
Import | The import file may contain statements which require the superuser role. | Edit the file to remove any statements which require the superuser role. |
Cloud SQL also uses some third-party binaries (for example,
mysqld
), which can generate unknown error messages. Such errors are
internal to the third-party binaries and are outside the scope of Cloud SQL.
However, sometimes a more specific error can be found in the
Cloud SQL log files at around the same
time.
Also, sometimes it is an error code that is unknown. In this case,
the complete message can be Unknown Error Code
.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-10-30 UTC.