Cloud SQL error messages

Check for the following conditions:

• The application did not call mysql_close() before exiting.
• Communication errors.
• The application might have been sleeping more than the number of seconds specified in `wait_timeout` or `interactive_timeout` without issuing any requests to the server. See Section 5.1.7, Server System Variables.
• The application ended abruptly in the middle of a data transfer.
• The max_allowed_packet variable value might be too small or queries require more memory than the allocated for mysqld. This can be resolved by raising the max_allowed_packet flag to a much larger number.

Update the definer in the external databases, for example from root@localhost to root@% or a non-superuser. See Stored Object Access Control for more information.

• The username (or password) is incorrect.
• The user is connecting from a URL other than @XXX.
• The user doesn't have the correct privileges for the database they're trying to connect to.

Try these things ...

• Verify the username and corresponding password.
• Check the origin of the connection to see if it matches the URL where the user has access privileges.
• Check the user's grant privileges in the database.

You need to modify the private connection. Use the following command, and make sure to use the --force argument:

gcloud services vpc-peerings update \
--network=VPC_NETWORK \
--ranges=ALLOCATED_RANGES \
--service=servicenetworking.googleapis.com \
--force

Try this:

1. Connect to the database (for example, using Cloud Shell) and login as root.
2. Execute USE mysql;.
3. Grant the following permissions using the syntax:

   GRANT PERMISSION_1,PERMISSION_2 ON *.* TO 'root' WITH GRANT OPTION;
      

   • SELECT
   • INSERT
   • UPDATE
   • DELETE
   • CREATE
   • DROP
   • RELOAD
   • SHUTDOWN
   • PROCESS
   • REFERENCES
   • INDEX
   • ALTER
   • SHOW DATABASES
   • CREATE TEMPORARY TABLES
   • LOCK TABLES
   • EXECUTE
   • REPLICATION SLAVE
   • REPLICATION CLIENT
   • CREATE VIEW
   • SHOW VIEW
   • CREATE ROUTINE
   • ALTER ROUTINE
   • CREATE USER
   • EVENT
   • TRIGGER
   • CREATE TABLESPACE
4. Execute USE 'Database_Name'; where Database_Name is the database where you're creating the views.
5. Execute all create views in the session and commit.

For Illegal Argument, check the request to make sure each argument is permissible and each value for the argument is valid. For all other causes, check the log files to see if there is more information there.

You need to modify the private connection. Use the following command, and make sure to use the --force argument:

gcloud services vpc-peerings update \
--network=VPC_NETWORK \
--ranges=ALLOCATED_RANGES \
--service=servicenetworking.googleapis.com \
--force

If you're trying to perform an export and Cloud Storage doesn't receive any data within a certain timeframe, then the connection resets.

Try a manual export using pg_dump.

Remove all Authorized Networks entries from the Cloud SQL instance if you can. Otherwise, create a replica without any Authorized Networks entries.

Use the sp_helpdb command to get information about the database.

Consider the following solutions:

• Manually expand the disk space or reduce the data in the database.
• Ensure that Automatic storage increase is enabled for the database instance.
• Add more filegroups and move data into them.
• Ensure that growth is not limited. Use the ALTER DATABASE command to enable autogrowth, if it is not already enabled, and to increase the maximum file size.
• Manage tempdb files. Use the DBCC OPENTRAN and DBCC SQLPERFcommands to check for open transactions that can cause the tempdb file or the transaction log to grow.

Connect with the default user and then change users.

Edit the primary instance to upgrade it to a larger disk size.

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:

• The size of the allocated IP range for the private service connection is smaller than /24.
• The size of the allocated IP range for the private service connection is too small for the number of Cloud SQL instances.
• The requirement on the size of allocated IP range will be larger if instances are created in multiple regions. See allocated range size

For each of the previously listed 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

Connecting from Cloud Shell to an instance with only a private IP address isn't supported.

Use mysqldump with the max_allowed_packet option.

To learn more about using mysqldump flags for managed import migration, see Allowed and default initial sync flags

Check that your OS and file system support files of this size. Check that the disk isn't full or out of disk quota. You can request an increase to your quotas from the Google Cloud console or edit the instance to upgrade it to a larger disk size.

To repair service permissions, disable the Service Networking API, wait five minutes and then re-enable it.

Enable the Service Networking API in your project. If you see this error when you're trying to assign a private IP address to a Cloud SQL instance, and you're using a Shared VPC, you also need to enable the Service Networking API for the host project.

Find the process that locked the table and stop it:

1. Diagnose with: sql> show processlist;

   The first item in the list might be the one holding the lock, which the following items are waiting on.

2. The SHOW INNODB STATUS command can also be helpful.
3. Run the command KILL <var>PID</var>.

Enable the Service Networking API in your project. If you see this error when you're trying to assign a private IP address to a Cloud SQL instance, and you're using a Shared VPC, you also need to enable the Service Networking API for the host project.

Wait for the previous operation to finish before beginning another.