[google-cloud-sql-discuss] cannot CREATE CAST PostgreSQL 9.6

CREATE CAST (text AS smallint) WITH INOUT AS IMPLICIT;

=> ERROR:  must be owner of type text or type smallint

Any alternative or solution to this? 

It's really pushing me back on Google SQL as an alternative.

--
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/249a5c6d-d2f0-4609-a7af-5bf8ea002659%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: unable to connect cloud sql in tableau

Since Tableau is not a Google Cloud Platform product I have little to no insight into its inner functionality and workings. I would recommend that you follow their guide for connecting to a datasource, and consult with their Help Forum for further technical troubleshooting help. 

- Note that Google Groups is reserved for general product discussions and not for technical support. For Cloud SQL support it is recommended to post your detailed questions to Stack Exchange using the supported Cloud tags. 

--
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/7e82fad9-1812-4075-8583-1854bbd7b013%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL instance does not restart

Hello Şimşek,

It appears you have another thread opened for the same. As mentioned, Please submit a private issue report using this link, providing all related information (for example: project number, cloud SQL instance name etc.) for us to verify and assist further. 

On Monday, July 30, 2018 at 6:27:31 PM UTC-4, Şimşek Mert wrote:

I tried to restart the instance but it is stuck. It does not restart. Please help. 

--
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/f8f6ac3c-f47d-4cbb-ad69-06f620e7c1b6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL Instance does not restart

Hello Şimşek,

Please submit a private issue report using this link, providing all related information. For example: Project number, Cloud SQL instance name etc. We will verify and take appropriate steps to resolve. 

On Monday, July 30, 2018 at 6:27:31 PM UTC-4, Şimşek Mert wrote:

I just wanted to restart the instance but it is stuck. It does not restart. And I cannot access as well.

--
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/846fddd5-0867-4fc3-812c-09d4813e3fef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] unable to connect cloud sql in tableau

Hi Team,

I'm trying to connect Cloud SQL server in tableau using predefined cloud sql connector however below error showing.

An error occurred while communicating with Google Cloud SQL.

 

Unable to connect to the server. Check that the server is running and that you have access privileges to the requested database.

Unable to connect to the ODBC Data Source. Check that the necessary drivers are installed and that the connection properties are valid.

[MySQL][ODBC 5.3(w) Driver]Unknown MySQL server host ' Cloud SQL Instance Name' (2)

Unable to connect to the server "Cloud SQL Instance Name". Check that the server is running and that you have access privileges to the requested database.

Kindly help me to resolve this.

Thanks,

Rajesh

--
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/a0745700-a805-4d0d-844b-77cb25662e8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud SQL Instance does not restart

I just wanted to restart the instance but it is stuck. It does not restart. And I cannot access as well.

--
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/8b6ef91a-0bc6-44b3-93b7-ea87adb7856d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Cloud SQL instance does not restart

I tried to restart the instance but it is stuck. It does not restart. Please help. 

--
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/3c185d00-34f9-4a25-b144-ac3e0220810f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Missing database flags

You are right, the list of unsupported features for PostgreSQL in GCP includes any features that require SUPERUSER privileges. An exception to this rule is made for the CREATE EXTENSION statement, but only for supported extensions. You may read more related detail on the "Cloud SQL for PostgreSQL Features" page. 

You state that editing the mentioned parameters by way of the "CREATE DATABASE" command is unsatisfactory. Why do you find this feature unsatisfactory? What new feature implementation would be satisfactory for you, by contrast? How would you describe the desired feature in more detail? A well-described use-case would help, preferably structured in step-by-step manner. 

--
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/0e9abf5d-3334-4a26-96d0-ecb816221573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Migrating Postgresql server to SQL Cloud and SQL_ASCII encoding

Hi Brenden,

There is a likelihood that you have some Windows-1252-encoded text in your old database (0x96 encodes "dash" in that encoding). This issue is already reported to the PostgreSQL Issue tracker and it is recommended that you edit dump file there.

So, I recommend that you change your database encoding first and then follow the steps on Importing Data into Cloud SQL. As noted in your duplicate post, you may find many discussion threads like this one on Stack Overflow [4] on how to change the database encoding.

If the issue persists, you may post your full detailed question to Stack Overflow, using the supported Cloud tags.

--
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/81a2ce0a-baea-44ea-b4c8-354ec94b0032%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Missing database flags

Hi, i've noticed that i can't configure ( server wide ) the following 

Parameters:

1. lc_messages
   
2. lc_monetary
   
3. lc_numeric
   
4. lc_time
   

i can edit them with the common "CREATE DATABASE ... " SQL command, but that is not what i want.

I've also traied to use the "ALTER SYSTEM" SQL command, to change the "postgresql.conf" params, but the user created doesn't have "superuser" rights.

The ability of editing those parameters, is important for us, because whe have all our server with the locale 'es_AR.UTF-8'

Thx and apologies for my english.

--
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/e1288fcf-a8b4-4f51-90e7-9e6442d03cfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Changing Postgres encoding from UTF8 to SQL_ASCII

Hi Brenden,

I should note that, here, we provide support for Google Cloud Platform-end products and not for PostgreSQL, however you may find many discussion threads like this one on Stack Overflow on how to change the database encoding.

--
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/64dead45-c5a9-4cf4-ad61-fb3594dad601%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Restore as New CloudSQL Instance

Hello Arvind, 

Yes, it is possible to restore from the backup to a different/new Cloud SQL instance. You can refer to this documentation link for detailed procedure. Here are the tips and requirements for restoring to a different instance

***Note: The restore process overwrites all the current data on the target instance.

On Friday, July 27, 2018 at 5:42:21 AM UTC-4, Arvind Stutzen wrote:

CloudSQL automated backup is working daily on schedule. We like to test if the backup is correct and will not create any problem while restoring. Without affecting the running instance data is it possible to restore the backup to a new instance so we can test the data in new instance. 

--
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/f61edd01-0db0-4856-b839-c4db0d67c33c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Restore as New CloudSQL Instance

CloudSQL automated backup is working daily on schedule. We like to test if the backup is correct and will not create any problem while restoring. Without affecting the running instance data is it possible to restore the backup to a new instance so we can test the data in new instance. 

--
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/1fa5ad4f-44e8-4aba-81a9-1592a168df69%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Changing Postgres encoding from UTF8 to SQL_ASCII

Hi All,

Hopefully this isn't a duplicate post, i'm not sure where my other post went.

I have a Postgres database server that's existed since the 2000s, and the encoding on all databases is SQL_ASCII.

I've tried a conversion from SQL_ASCII to UTF8 locally and then tried to import into GCP Cloud SQL and i'm getting errors like ERROR:  invalid byte sequence for encoding "UTF8": 0x96

I'm wondering if anyone knows how to convert Cloud SQL (postgres) from UTF8 to SQL_ASCII?

--
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/fc1827d1-8a9d-42fa-863b-2a3711321dc4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Migrating Postgresql server to SQL Cloud and SQL_ASCII encoding

Hi All,

I am attempting to migrate a Postgres database server from our datacentre that's been around since the 90s (its now running  8.1.21) however the encoding type is "SQL_ASCII".

The error I get is:

postgres=>  CREATE DATABASE dbtest  ENCODING = 'SQL_ASCII';

ERROR:  encoding "SQL_ASCII" does not match locale "en_US.UTF8"

DETAIL:  The chosen LC_CTYPE setting requires encoding "UTF8".

Is there anything I can do to enable SQL_ASCII? 

I thought that ASCII was  subset of UTF8 so I was thinking this should be compatible.

I've dumped the DB, and changing the encoding to UTF8 (using sed -i -e 's/SQL_ASCII/UTF8/g' db-prod.sql) as the file is too big to open. 

However this resulted in import errors when copying our production database dump into a development project with things like.

ERROR:  invalid byte sequence for encoding "UTF8": 0x96

Has anyone done this before? 

--
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/27679962-15e0-42fc-ab61-1dfa30d24e6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Unable to connect to Cloud SQL from Node JS

Hi Fabrizio,

What Kenworth posted above is correct, you should only use either host/post to connect via TCP or you should use socketPath to connect with a UnixSocket. For AppEngine Standard you have to use a unix socket, for AppEngine Flex you can choose whichever is better for your situation. 

On Sunday, May 27, 2018 at 8:48:22 AM UTC-7, Lalit Indoria wrote:

Hi

I am trying to connect to node JS from my sails js app that's hosted on App Engine in the same project as Cloud SQL. I have tried multiple combinations but failed every time.

Here' what the log says:

name=AdapterError, adapterMethodName=create, modelIdentity=admin, name=Exception, code=badConnection, exit=badConnection, errorno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, fatal=true, host=35.230.110.241, port=3306, schema=true, adapter=sails-mysql, socketPath=/cloudsql/parsley-dev:us-west1:parsley-dev, user=parsley-dev, password=parsleyDevApi, database=parsley, identity=default, url=mysql://parsley-dev:parsleyDevApi@35.230.110.241:3306/parsley, isOperational=true, adapterMethodName=create, modelIdentity=admin, $ref=$["cause"]["raw"]

My sails JS adapter configuration:

adapter: 'sails-mysql',
socketPath: `/cloudsql/${process.env.INSTANCE_CONNECTION_NAME}`,
user: process.env.SQL_USER,
password: process.env.SQL_PASSWORD,
host: '35.230.110.241',
database: 'parsley'

Would be great if someone can help me.

--
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/2d2b80dc-1b0b-41a8-91e5-4c7e86f908bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Unable to connect to Cloud SQL from Node JS

I have the same problem.

Did you find any solution?

Il giorno domenica 27 maggio 2018 17:48:22 UTC+2, Lalit Indoria ha scritto:

Hi

I am trying to connect to node JS from my sails js app that's hosted on App Engine in the same project as Cloud SQL. I have tried multiple combinations but failed every time.

Here' what the log says:

name=AdapterError, adapterMethodName=create, modelIdentity=admin, name=Exception, code=badConnection, exit=badConnection, errorno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, fatal=true, host=35.230.110.241, port=3306, schema=true, adapter=sails-mysql, socketPath=/cloudsql/parsley-dev:us-west1:parsley-dev, user=parsley-dev, password=parsleyDevApi, database=parsley, identity=default, url=mysql://parsley-dev:parsleyDevApi@35.230.110.241:3306/parsley, isOperational=true, adapterMethodName=create, modelIdentity=admin, $ref=$["cause"]["raw"]

My sails JS adapter configuration:

adapter: 'sails-mysql',
socketPath: `/cloudsql/${process.env.INSTANCE_CONNECTION_NAME}`,
user: process.env.SQL_USER,
password: process.env.SQL_PASSWORD,
host: '35.230.110.241',
database: 'parsley'

Would be great if someone can help me.

--
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/f372bc22-5fc1-4bd2-8733-4259615dfc65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Unable to connect to Cloud SQL from Node JS

Did you find a solution?

Il giorno domenica 27 maggio 2018 17:48:22 UTC+2, Lalit Indoria ha scritto:

Hi

I am trying to connect to node JS from my sails js app that's hosted on App Engine in the same project as Cloud SQL. I have tried multiple combinations but failed every time.

Here' what the log says:

name=AdapterError, adapterMethodName=create, modelIdentity=admin, name=Exception, code=badConnection, exit=badConnection, errorno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, fatal=true, host=35.230.110.241, port=3306, schema=true, adapter=sails-mysql, socketPath=/cloudsql/parsley-dev:us-west1:parsley-dev, user=parsley-dev, password=parsleyDevApi, database=parsley, identity=default, url=mysql://parsley-dev:parsleyDevApi@35.230.110.241:3306/parsley, isOperational=true, adapterMethodName=create, modelIdentity=admin, $ref=$["cause"]["raw"]

My sails JS adapter configuration:

adapter: 'sails-mysql',
socketPath: `/cloudsql/${process.env.INSTANCE_CONNECTION_NAME}`,
user: process.env.SQL_USER,
password: process.env.SQL_PASSWORD,
host: '35.230.110.241',
database: 'parsley'

Would be great if someone can help me.

--
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/aa32314f-e149-4654-94ba-301f294c5a5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Stuck at "1 Read replicas of external source instances are being created and seeded with data"

My pleasure. Your report is being investigated and all further updates should be posted in the report.

--
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/2f728714-ee5d-4013-96a4-81f82546ee07%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Stuck at "1 Read replicas of external source instances are being created and seeded with data"

Thanks Katayoon,

I submitted ticket 111565582. Please help!

On Wednesday, July 18, 2018 at 3:29:12 AM UTC+7, Katayoon (Cloud Platform Support) wrote:

Hi Tai,

If you are still receiving this issue, I recommend that you raise a private report in the Issue Tracker and provide us the project number and the instance ID so that we would be able to investigate the issue efficiently.

--
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/39ae1064-ec6f-4ccb-bb78-d64d4b64cc48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Stuck at "1 Read replicas of external source instances are being created and seeded with data"

Hi Tai,

If you are still receiving this issue, I recommend that you raise a private report in the Issue Tracker and provide us the project number and the instance ID so that we would be able to investigate the issue efficiently.

--
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/dfcfeb18-867b-45a9-ae29-610187fa4da6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Stuck at "1 Read replicas of external source instances are being created and seeded with data"

Hi,

I tried to create cloud sql replicas as this guide https://cloud.google.com/sql/docs/mysql/replication/configure-external-master. The read replica is stuck. I could not delete or do anything. Please see in the attachment.

Thanks,
Tai

--
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/10fef3c1-8a9c-4f19-9da5-decb409e77a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

I can't help you with that so please look elsewhere for help, thanx

On Thu, Jul 12, 2018 at 2:20 AM, <joseo@gencat.cat> wrote:

On Wednesday, July 11, 2018 at 3:19:02 AM UTC+2, Fady (Google Cloud Platform) wrote:

Hello Jose, 

Thank you for the feedback. I believe both cases are different as you are migrating using named pipes/load data infile over the internet, while Mousa is describing heavy write load. In both cases though, the instance itself should not restart. That said, we do appreciate opening the issue tracker for an investigation as it is the platform for discovering defects and improving our products. 

Hello Fady,

the fact that we are using pipes in parallel is just the mechanism. This is what generates heavy write load also in our scenario.

Best,

Jose 

--
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/f0ac28a2-8a52-4f34-9ff7-ee4ccc8c32f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
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/CACHeDUyNhpHTtjhwjG%2BP%3Du8ah8_xpP7RTgb9P8vhkFVR5ACWsw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Problems connecting instance to App Maker

Hi Edward,

I should note that, here we provide support for Google Cloud Platform-end products and it seems that your issue is related to App Maker which is a G Suite product. So I recommend that you double check the steps you have taken via this link and if the issue still persists, you may contact the App Maker support center.

--
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/d558f044-2144-4949-bccb-be266f98bbfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Problems connecting instance to App Maker

First timer here....created an instance of CloudSQL, added it into the App Maker admin settings, when I open up my App Maker project I get this..

Can't figure out what's wrong.

Thoughts?

Thanks!

--
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/f3cffacc-3a7c-4e64-8160-d55cba16aca3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

On Wednesday, July 11, 2018 at 3:19:02 AM UTC+2, Fady (Google Cloud Platform) wrote:

Hello Jose, 

Thank you for the feedback. I believe both cases are different as you are migrating using named pipes/load data infile over the internet, while Mousa is describing heavy write load. In both cases though, the instance itself should not restart. That said, we do appreciate opening the issue tracker for an investigation as it is the platform for discovering defects and improving our products. 

Hello Fady,

the fact that we are using pipes in parallel is just the mechanism. This is what generates heavy write load also in our scenario.

Best,

Jose 

--
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/f0ac28a2-8a52-4f34-9ff7-ee4ccc8c32f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

In fact, Engineering is looking presently at similar Cloud SQL issues. Your issue is likely going to enjoy increased attention, as a consequence. 

--
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/9d2affef-db63-4d01-a13b-3ac0b9f977f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hi,

Thank you for your replies. I have created an issue as suggested by @Fady, but I sill agree with @Jose that we shouldn't worry about server restarts no matter how heavy the read/write load is. We can live with the server getting slower at heavy load times but not it being restarted. We shouldn't be forced to upgrade the machine type if we expect a heavy load in a relatively very short time of the day especially that it is okay for us if the server gets slower responding at these times being planned.

Best,

Mousa

--
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/bc153656-a35a-4ec0-934e-b73977491e73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hello Jose, 

Thank you for the feedback. I believe both cases are different as you are migrating using named pipes/load data infile over the internet, while Mousa is describing heavy write load. In both cases though, the instance itself should not restart. That said, we do appreciate opening the issue tracker for an investigation as it is the platform for discovering defects and improving our products. 

--
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/41cab351-712a-40ea-8abc-c937209294dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Trying to connect to MySQL instance using Scio (Apache Beam)

Scio is not a Google supported API. As per our documentation example, if you are using the standard java.sql.DriverManager this should work for you. If you are having issues with Scio's implementation it is recommended to directly report the issue in their Github Issue Tracker, as Google Groups is reserved for general Google product discussions and not for technical support. 

--
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/a7b2b08c-4f3a-4e39-92ba-82f9e753acc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hi,

to be honest, if they are suffering the same issue as us, I don't think it can be solved by provisioning additional resources. We've tried with a machine configured as db-n1-highmen-32 (32 cpus and 208 GB of RAM), and this issue is still happening. IMHO It doesn't makes sense, neither, to need to worry with service restarts when a vanila MySQL VMWare instance in our premises, with 4 cpus and 8 GB RAM can handle that parallel import task without any problem...

On Tuesday, July 10, 2018 at 12:24:36 AM UTC+2, Fady (Google Cloud Platform) wrote:

Hello Mousa,

From the description it seems like an over-utilized instance, and provisioning additional resources should resolve the issue. However, the instance (VM) itself should not restart but rather the running MySQL server (mysqld). If the instance itself is restarting please open a private issue tracker report including the instance's connection name for inspection.

--
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/4e5f4bd5-3bb5-4b67-9ff9-21d1aac0f1e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Trying to connect to MySQL instance using Scio (Apache Beam)

Hi,

I'm trying to connect to a MySQL instance using the following example from Scio, a library for using Apache Beam with Scala. I'm trying this in DirectRunner (local machine) but I can't get connected to the DB. The JDBC URL I use is the following: "jdbc:mysql://google/dbname?cloudSqlInstance=xxx:us-central1:yyy&socketFactory=com.google.cloud.sql.mysql.SocketFactory". For username and password I use a custom user I made (I tried it with the root user as well but no luck). I also have enabled the SQL API from GCP as well as logged in with the gcloud SDK on my local computer. In addition, I whitelisted the IP from my computer (although it suppose to work without whitelisting if you use the above JDBC URL).  The error I get is the following:

Caused by: java.sql.SQLNonTransientConnectionException: Cannot connect to MySQL server on google:3,306.


Make sure that there is a MySQL server running on the machine/port you are trying to connect to and that the machine this software is running on is able to connect to this host/port (i.e. not firewalled). Also make sure that the server has not been started with the --skip-networking flag.

Any idea why it can't connect?

Thank you

--
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/67c46cb6-79e0-4c96-9180-b5a1da503558%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hello Mousa,

From the description it seems like an over-utilized instance, and provisioning additional resources should resolve the issue. However, the instance (VM) itself should not restart but rather the running MySQL server (mysqld). If the instance itself is restarting please open a private issue tracker report including the instance's connection name for inspection.

--
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/a517fdab-88e1-4e66-950d-d0c920d86f1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: MySQL restarts itself when doing "load data"

Hi,

We are also facing a similar problem with our SQL instance in Google Cloud Platform, it restarts often (2-3) times a day on what we suspect to be a heavy write load. We cannot see enough information in MySQL error logs except the information that MySQL instance was restarted. What could cause instance restarts other than the maintenance and upgrades? Is it possible that a heavy write or even read load causes such restarts?

Many thanks in advance,

Mousa

--
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/e6a325ae-49d4-4276-a1ac-877af2f42ed9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL Proxy encryption and access query

In addition to Pia's response:

1. Currently, I cannot share any road-map of the AES-256 encryption support for Cloud SQL Proxy. However, I would suggest you to open a feature request using Google Cloud issue tracker. 

2. As per the documentation, Cloud SQL proxy automatically encrypts traffic to and from the database using TLS. You can refer to this document link for information on how Cloud SQL Proxy works. 

3. Provided credentials for the Cloud SQL Proxy authenticates the Cloud SQL proxy which enables it to access GCP on behalf of the application, using set of provided Google credentials and this is different from database user authentication. Check this documentation links [1] [2] for more information. 

4. You do not needs to create a separate Cloud SQL Proxy process to set up a connection to the Cloud SQL. As per documentation, "In general, you should run one proxy client process per workstation or virtual machine." You can connect to the multiple Cloud SQL instances using same Cloud SQL proxy client.


On Friday, July 6, 2018 at 12:26:59 PM UTC-4, Pia Chamberlain wrote:

Greetings,

2) The proxy provides TLS encryption.

https://cloud.google.com/sql/docs/mysql/sql-proxy#what_the_proxy_provides

3) Correct.

4) You can connect to multiple instances with the same Proxy client.

https://cloud.google.com/sql/docs/mysql/sql-proxy#multiple-instances

On Tuesday, July 3, 2018 at 9:01:27 AM UTC-7, Shubhanan Bakre wrote:

We had the following queries regarding the proxy:

1)     Proxy client encrypts traffic to the Proxy server using AES128 and NOT AES256. Any plans to support AES 256 in near future?

2)     Per documentation, TLS tunnel can be established for Authorized IPs. Can it be established for CloudSQL Proxy too?

3)     In Cloud Proxy scenario, the "service key" is "only" allowing communication to the Cloud SQL instance. It is NOT used to access to actual data in tables. User/password credentials at database-level are still required to get access to the data in the database.

4) Can we have multiple Proxy clients(one per CloudSQL instance) per VM? Or is it recommended to have a one Proxy Client (for each CloudSQL instance) per VM?

Thanks!

--
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/690d1e12-053d-42f6-9a79-7cb36bd7388a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Cloud SQL Proxy encryption and access query

Greetings,

2) The proxy provides TLS encryption.

https://cloud.google.com/sql/docs/mysql/sql-proxy#what_the_proxy_provides

3) Correct.

4) You can connect to multiple instances with the same Proxy client.

https://cloud.google.com/sql/docs/mysql/sql-proxy#multiple-instances

On Tuesday, July 3, 2018 at 9:01:27 AM UTC-7, Shubhanan Bakre wrote:

We had the following queries regarding the proxy:

1)     Proxy client encrypts traffic to the Proxy server using AES128 and NOT AES256. Any plans to support AES 256 in near future?

2)     Per documentation, TLS tunnel can be established for Authorized IPs. Can it be established for CloudSQL Proxy too?

3)     In Cloud Proxy scenario, the "service key" is "only" allowing communication to the Cloud SQL instance. It is NOT used to access to actual data in tables. User/password credentials at database-level are still required to get access to the data in the database.

4) Can we have multiple Proxy clients(one per CloudSQL instance) per VM? Or is it recommended to have a one Proxy Client (for each CloudSQL instance) per VM?

Thanks!

--
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/d7ea27b5-5815-4053-803a-be8d54dcc435%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: failure to connect to MySQL instance on cloudsql socket (GAE Python flex environment)

Er, nevermind. The settings are correct, but I was trying to open a db connection before the service was completely updated, instead of per request.

On Thursday, July 5, 2018 at 6:15:02 PM UTC-4, Eric G wrote:

Following the instructions here:

https://cloud.google.com/appengine/docs/flexible/python/using-cloud-sql

• I have specified the unix_socket  as /cloudsql/project:location:instance .  (i.e. the instance connection name, not just the instance ID)
  
• I have added it to the beta_settings, cloud_sql_instances in app.yaml.
  
• I am connecting as a db user created through the Google Console from "any host" (%)  -- but it also happens with the root user too
  
• I am connecting using the pymysql library
• This is during deployment to GAE Python flex environment, and the cloudsql instance is in the same project, so the GAE service account should be authorized.

From the traceback (below), it does appear to try to open a socket connection, rather than TCP/IP, but fails with the message "Can't connect to MySQL server on 'localhost' ([Errno 2] No such file or directory)".

--
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/8669aa0e-1995-43e9-89d1-9d89addbae34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.