Tuesday, November 29, 2016

[google-cloud-sql-discuss] Re: CloudSQL create replica slave problem (external replication)


Hey Nicholas, 

Yes, I have an external MySQL server and I'm trying to make a replication slave in a CloudSQL instance. 

  • Yes, I created the internal master (step 1 from documentation) without problems. I've exported my authorization token and I'm sure it's working because I've created and deleted a bunch of SQL instances to test this trough cloud sql API. The 403 shows up for the second step. 
  • Yes, credentials are correct for external master.
  • I used the same bucket for importing mysqldump files from web interface and was ok.
  • The Cloud SQL instance isn't created with API when I'm executing the steps from tutorial ? I'm assuming that will go default with first generation right ? 
  • Both MySQL are version 5.6 

Thank you! 

On Tuesday, November 29, 2016 at 7:42:30 PM UTC+2, Nicholas (Google Cloud Support) wrote:
Hey Lisei,

Welcome.  From what I understand, you have an existing MySQL server that you wish to use as the base for replication as Cloud SQL instances.  From your description, I understand that you receive the 403 when attempting to create the replica (step 2 in Creating the external master configuration).  The 403 suggests an authorization issue.  My questions are as follows:
  • Could you successfully create the internal master instance (step 1 in the same guide)?  I ask this because that step should require the same authorization and could in fact be accomplished with the same access token if properly authorized.  It would therefore be quite strange if step 1 succeeded while step 2 failed.
  • Did you use the proper replication user/pass credentials in the request when creating a replica?
  • Do you have proper privileges for the provided Cloud Storage bucket for the dump file?
  • Is the Cloud SQL instance one of the first generation and of the same MySQL version as the existing external MySQL instance?  I doubt this would return a 403 but would not want to disregard the possibility.
Nicholas

On Tuesday, November 29, 2016 at 9:05:25 AM UTC-5, Lisei Andrei wrote:

I'm following this guide here for creating a cloudsql slave for an external mysql database.

I've managed to create an internal master but when i try to create the replica I have this error: 
I'm the project owner of the GCP project. 

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notAuthorized",
    "message": "The client is not authorized to make this request."
   }
  ],
  "code": 403,
  "message": "The client is not authorized to make this request."
 }
}

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/00736ef2-c6e3-4368-8344-4f825e84882c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: CloudSQL create replica slave problem (external replication)

Hey Lisei,

Welcome.  From what I understand, you have an existing MySQL server that you wish to use as the base for replication as Cloud SQL instances.  From your description, I understand that you receive the 403 when attempting to create the replica (step 2 in Creating the external master configuration).  The 403 suggests an authorization issue.  My questions are as follows:
  • Could you successfully create the internal master instance (step 1 in the same guide)?  I ask this because that step should require the same authorization and could in fact be accomplished with the same access token if properly authorized.  It would therefore be quite strange if step 1 succeeded while step 2 failed.
  • Did you use the proper replication user/pass credentials in the request when creating a replica?
  • Do you have proper privileges for the provided Cloud Storage bucket for the dump file?
  • Is the Cloud SQL instance one of the first generation and of the same MySQL version as the existing external MySQL instance?  I doubt this would return a 403 but would not want to disregard the possibility.
Nicholas

On Tuesday, November 29, 2016 at 9:05:25 AM UTC-5, Lisei Andrei wrote:

I'm following this guide here for creating a cloudsql slave for an external mysql database.

I've managed to create an internal master but when i try to create the replica I have this error: 
I'm the project owner of the GCP project. 

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notAuthorized",
    "message": "The client is not authorized to make this request."
   }
  ],
  "code": 403,
  "message": "The client is not authorized to make this request."
 }
}

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/7eb5504d-3d2c-4524-ba33-eb6aac0c086e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Monday, November 28, 2016

[google-cloud-sql-discuss] CloudSQL create replica slave problem (external replication)


I'm following this guide here for creating a cloudsql slave for an external mysql database.

I've managed to create an internal master but when i try to create the replica I have this error: 
I'm the project owner of the GCP project. 

{
 "error": {
  "errors": [
   {
    "domain": "global",
    "reason": "notAuthorized",
    "message": "The client is not authorized to make this request."
   }
  ],
  "code": 403,
  "message": "The client is not authorized to make this request."
 }
}

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/b0ab590b-da6f-438e-a540-d760497a5e9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Google SQL I/O Pricing

We don't charge I/O any more. The page is out of date and we will update it.

On Monday, November 28, 2016 at 6:14:18 AM UTC-8, Brody West wrote:
Hi!

As far as I can tell from the pricing page, 2nd Generation SQL pricing does not charge for I/O calls, while 1st Generation SQL pricing charges $0.2 per million I/O calls in excess of the allotted number of free calls. Am I correct?

Thanks,
Brody

--
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/ca56e3f0-ccde-4fbb-93ba-ad10db15b3a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sunday, November 27, 2016

[google-cloud-sql-discuss] Google SQL I/O Pricing

Hi!

As far as I can tell from the pricing page, 2nd Generation SQL pricing does not charge for I/O calls, while 1st Generation SQL pricing charges $0.2 per million I/O calls in excess of the allotted number of free calls. Am I correct?

Thanks,
Brody

--
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/f91d8434-980f-4d9c-9329-a4e9238f7d2a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Saturday, November 26, 2016

[google-cloud-sql-discuss] Re: SQL Instance stuck on restarting

I see from a recent support interaction that the instance had recovered. Please don't hesitate to reach out again if you experience further issues.

On Friday, November 25, 2016 at 1:26:56 PM UTC-5, Laurens Verspeek wrote:
Our production SQL instance (2nd generation) is stuck on restarting for a few hours. We can't access the backups or do anything else with the instance. Can someone help me fix this critical issue?

--
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/5dbbaf08-98a6-4fff-ad45-7113f1aa3256%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, November 25, 2016

[google-cloud-sql-discuss] Trouble with SQL Transactions + App Engine

Hello! I'm having trouble making MySQL transactions work with App Engine. I'm posting it to this list since I imagine more people here are using App Engine than people on the App Engine list are using Cloud SQL, but please let me know if I should post elsewhere.

TL;DR of what I think its happening: When two App Engine requests in parallel use MySQLdb to connect to Google Cloud SQL (or another MySQL server), if the requests are coming from the same machine then they are not dealt with independently. In particular, locking a row in one request does not prevent the other request from modifying it.


Gist to reproduce:
1. Make a GAE app that connects to Cloud SQL.
2. Write code in two separate admin consoles of the app:
  - One starts a transaction, locks and prints a row, then waits 10 seconds, then prints out the row before ending the transaction.
  - The other updates the row that the first one locked.
3. Run the first console's code, then wait a few seconds and run the second console's code.

Expected result:
The second console waits for several seconds, then terminates (having updated the name).
The first console prints out the row with its original name, twice.

Actual result:
The second console terminates immediately, and updates the row.
The first console prints out the row, first with its original name and second with its updated name.


More detailed steps to reproduce:
1. Create a Google App Engine app that connects to a Google Cloud SQL database. Make sure the app has MySQLdb and an admin console[1] in its app.yaml.
2. Make a 'Products' table with a 'name' column and an 'id' column, and insert something with name 'BoringName' and id 1. [2]
3. Open up two separate browser tabs to the interactive console of the admin console, and enter the following code:

[Console 1]
import time
import my_db_lib
db = my_db_lib.GetConnection()  # [3]
c = my_db_lib.GetCursor(db)
c.execute('START TRANSACTION')
c.execute('SELECT Name FROM Products WHERE ProductId=1 FOR UPDATE')
print c.fetchall()
time.sleep(10.0)
c.execute('SELECT Name FROM Products WHERE ProductId=1')
print c.fetchall()
db.commit()

[Console 2]
import my_db_lib
db = my_db_lib.GetConnection()  # [3]
c = my_db_lib.GetCursor(db)
c.execute('UPDATE Products SET Name="ExcitingName" WHERE ProductId=1')
db.commit()

3. Run the first console's code, then wait a few seconds and run the second console's code.

Expected result:
The second console waits for several seconds, then terminates (having updated the name).
The first console prints out the row with its original name, twice.

Actual result:
The second console terminates immediately, having updated the row.
The first console prints:
({'Name': u'BoringName'},)
({'Name': u'ExcitingName'},)


Other things I've tried
1. The same thing, but on dev_appserver.py (the offline test server for App Engine). Result: The same unexpected result as occurs on the live App Engine servers. [4]
2. Running console 1 from App Engine, and the UPDATE statement from console 2 in Cloud Shell. Result: As expected, the UPDATE statement hangs for several seconds before completing, and console 1 prints 'BoringName' twice.
3. Running the statements from both consoles in separate Cloud Shells. Result: As expected, the UPDATE statement hangs until I commit the transaction.
4. Running the two consoles on different machines [5]. Result: Expected. Console 2 waits for console 1 to complete. Console 1 prints:
({'Name': u'BoringName'},)
({'Name': u'BoringName'},)


Hypothesis

Both live and offline App Engine have issues with transactions when both requests are coming from the same machine.
Live App Engine has no issues with transactions when the requests are coming from different machines.

I hypothesize that when two MySQLdb connections come in to Google Cloud SQL from the same machine in App Engine, they aren't treated as distinct connections by the database. This seems like a bug to me, but I'd love to hear if other people think my hypothesis is correct and if it's indeed a bug.


Thanks!
Bartholomew



Footnotes

[1] Admin console requires the following in app.yaml:
# Admin console.
- url: /some_url
  script: google.appengine.ext.admin.application
  login: admin
  secure: always

[2] Some technical details: I'm using a first-generation CloudSQL instance, and the default InnoDB storage engine.

[3] My db lib just connects as follows:
return MySQLdb.connect(unix_socket='/cloudsql/my-project-name:db', user='root', db=my_db_name, charset='utf8')
And gets a cursor via db.cursor(MySQLdb.cursors.DictCursor).

[4] When on dev_appserver, my db lib connects as follows:
return MySQLdb.connect(host='localhost', user=user_name, passwd=super_secure_password, db=my_db_name, charset='utf8')
It connects to a standard MySQL server.

[5] I uploaded a different version of the app. It had no code differences, but App Engine runs different versions on different machines. So I ran my two consoles on:
https://version1-dot-my-test-app.appspot.com/a/db/interactive
https://version2-dot-my-test-app.appspot.com/a/db/interactive

--
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/eb09b7bb-e903-46f7-b0c0-ba76401f0992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] SQL Instance stuck on restarting

Our production SQL instance (2nd generation) is stuck on restarting for a few hours. We can't access the backups or do anything else with the instance. Can someone help me fix this critical issue?

--
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/1d591473-d778-42fc-bae9-13fe8acbce94%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thursday, November 24, 2016

[google-cloud-sql-discuss] Re: Table creations

Thanks.

On Thursday, November 24, 2016 at 7:56:08 AM UTC-8, Alex (Cloud Platform Support) wrote:

Hi David,


This is a classical topic in web application development: the design and structure of SQL tables. A question like this would have better chances of useful answers if posted on Stack Overflow which we regularly monitor alongside other Stack Exchange sites (see one here specifically for database administration). Posting there would increase your chances to get a comprehensive answer due to the larger audience. This Google forum is more suited to general discussions of Cloud SQL Platform specifically.

--
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/dedea320-bebe-40f5-83ae-b26ebc237573%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Table creations

Hi David,


This is a classical topic in web application development: the design and structure of SQL tables. A question like this would have better chances of useful answers if posted on Stack Overflow which we regularly monitor alongside other Stack Exchange sites (see one here specifically for database administration). Posting there would increase your chances to get a comprehensive answer due to the larger audience. This Google forum is more suited to general discussions of Cloud SQL Platform specifically.

--
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/af2ba97c-a929-420f-8c4c-c563040db7fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Anyway to disable only_full_group_by on 5.7

Thanks it worked. Will it have have any other impact on performance or functionality ?

--
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/029d595c-b118-4b53-a808-5fd202c994f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wednesday, November 23, 2016

[google-cloud-sql-discuss] Table creations

I am writing an app for use with my trucking company. Each user will have the app, where they can store their trip data, and export twice a month to their Cloud Storage. They can then import it to a sheet that will extrapolate the trip data, and payroll data into separate sheets with in the worksheet. 

My question is, how should I set up the tables? I have current trip data that goes onto a trip sheet for handing in, payroll data for the personal info for the driver, app settings data (check boxes etc) for recall with trip info is recalled for updating on route, trip data they select from, payroll data that is pulled according to the drivers selections, vehicle data for the same reason. 

I have worked with SQL in my apps, but as a single table with limited data storage. This is my first bigger use of tables, and I am not sure if I should have one large table with all the data, or smaller tables. I know I am going to use trip data (stored pick up land drop locations) as one table, and the same for vehicle data. How should I set up the other table(s)?

--
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/043929af-d734-427f-87e7-073893c67267%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Stuck in start

Thank for your answer Tianzhou, please do all what you can do.

About the move to 2nd, in my plans, I would start a migration in December this year.

Thank you.

Em quarta-feira, 23 de novembro de 2016 15:25:06 UTC-2, Tianzhou Chen escreveu:
Hi Giuliano,

    There is a failover happened in our datacenter which affects your instance. Your instance is trying to restart but stuck in the crash recovery mode, we tried to rescue your instance, but all failed so far. Are you OK for us to move this instance into maintenance mode so we use extra methods to rescue it?

    Also from looking at your instance history, the instance presents the usage pattern which is not well suited for 1st Gen (We noticed it was down multiple times in the past). Please also consider moving your instance to 2nd Gen, which performs much better and will suit your usage much better.

Thanks
Tianzhou



On Wednesday, November 23, 2016 at 7:59:02 AM UTC-8, Giuliano Ribeiro wrote:
Hi all, since yesterday I have a database stucked.
It is started but I can't connect there:

Looking at the logs I got this:


and the last log is that:


I already restart it many times, but not success to get my database up.

I don't know what to do more.Any ideas?

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/112d2c52-d3c5-4d05-8991-de6409cba5eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Stuck in start

Hi Giuliano,

    There is a failover happened in our datacenter which affects your instance. Your instance is trying to restart but stuck in the crash recovery mode, we tried to rescue your instance, but all failed so far. Are you OK for us to move this instance into maintenance mode so we use extra methods to rescue it?

    Also from looking at your instance history, the instance presents the usage pattern which is not well suited for 1st Gen (We noticed it was down multiple times in the past). Please also consider moving your instance to 2nd Gen, which performs much better and will suit your usage much better.

Thanks
Tianzhou



On Wednesday, November 23, 2016 at 7:59:02 AM UTC-8, Giuliano Ribeiro wrote:
Hi all, since yesterday I have a database stucked.
It is started but I can't connect there:

Looking at the logs I got this:


and the last log is that:


I already restart it many times, but not success to get my database up.

I don't know what to do more.Any ideas?

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/cb8d4afa-aeaa-4d2c-9e7b-58dc917e2147%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Stuck in start

Hi all, since yesterday I have a database stucked.
It is started but I can't connect there:

Looking at the logs I got this:


and the last log is that:


I already restart it many times, but not success to get my database up.

I don't know what to do more.Any ideas?

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/80241029-2b5b-4423-a9b2-002f4a9a2759%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Saturday, November 19, 2016

Re: [google-cloud-sql-discuss] Re: Can not import from storage

When you perform the export, you should specify the databases you want to export.
The issue stems from the fact that the export you have tries to perform DDL changes on the mysql database which we do not allow. 
Alternatively, edit your existing export to remove any statements that modify the mysql database.

On Fri, Nov 18, 2016 at 1:01 PM Rohit Manglik <rohit.manglik@gmail.com> wrote:
Hi,

I am also getting same error. Is there any workaround for this problem?

 ERROR 1227 (42000) at line 22: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I am having a down time because of this error.

Any lead?

On Tuesday, 9 August 2016 22:09:12 UTC+5:30, James McManus wrote:
When I attempt to import a file using the console, to cloud sql, from storage I get the following message when I "Browse" for the file:

Object not available. Either it does not exist or you do not have access. Try browsing for the object instead.

I've done this many times before and have not had this problem. I've tried changing permissions on the file, in storage, but have the same problem. I can also can download the file, directly using a url, so I do not think the problem is with storage. 

If I change the path, to the file, in the cloud sql import "Browse" console to:

danudata/danunews%2F2016%2Flatest_news_feed080916.csv

I no longer get the error message, but it then fails to import the data.

This appears to be a problem with google sql import console. Has anybody else had this problem? Are there solutions?

Thanks
Jim

--
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/ccd228e7-95d4-454f-90e2-91cd34c40998%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/CABDU3p3HJEwfViLtudu4yegW8G3NbqGTmGXr-T89Ypdj0nZ8Tw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: How to Automate Store Procedure Testing in SQL Server

It sounds like your questions are specific to Microsoft SQL Server, is that correct? If so, the Google Cloud SQL discussion forum is probably not the best place to ask, as Cloud SQL is hosted MySQL.

On Friday, November 18, 2016 at 4:01:23 PM UTC-5, Bharat Bhusan Sau wrote:
Hi, I am a newbie in SQL. I use SQL server for database management in my company. I am assigned task to automate the manual testing of business rules/stored procedures. I am searching for a method which is generic for automating any business rule testing (There are hundreds of business rules). Can somebody suggest me which technology is best suited for this ? Also what could be a better choice between TSQL and DBUnit for this task ?

--
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/4e4e134d-03b3-4f9d-b62b-be9eb5b674e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Thursday, November 17, 2016

[google-cloud-sql-discuss] Re: Can not import from storage

Hi,

I am also getting same error. Is there any workaround for this problem?

 ERROR 1227 (42000) at line 22: Access denied; you need (at least one of) the SUPER privilege(s) for this operation

I am having a down time because of this error.

Any lead?

On Tuesday, 9 August 2016 22:09:12 UTC+5:30, James McManus wrote:
When I attempt to import a file using the console, to cloud sql, from storage I get the following message when I "Browse" for the file:

Object not available. Either it does not exist or you do not have access. Try browsing for the object instead.

I've done this many times before and have not had this problem. I've tried changing permissions on the file, in storage, but have the same problem. I can also can download the file, directly using a url, so I do not think the problem is with storage. 

If I change the path, to the file, in the cloud sql import "Browse" console to:

danudata/danunews%2F2016%2Flatest_news_feed080916.csv

I no longer get the error message, but it then fails to import the data.

This appears to be a problem with google sql import console. Has anybody else had this problem? Are there solutions?

Thanks
Jim

--
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/ccd228e7-95d4-454f-90e2-91cd34c40998%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, November 11, 2016

[google-cloud-sql-discuss] Re: New Problem with login using google in OpenID Connect return Invalid Id Token that print invalid payload

What does the raw response look like before you parse out the payload? In the interest of troubleshooting, have you tested the request and response using a plain servlet instead of a form and JSP?

On Tuesday, November 8, 2016 at 2:37:32 PM UTC-5, Carl Andin Michel Sanon wrote:
Hi Adam
            Thanx for your support.
            This is the detail of my process : I have
            1- A jsp for login that contains this form
                   <form action="https://accounts.google.com/o/oauth2/auth" method="get" name="loginForm">
                        <input type="hidden" name="response_type" value="token id_token" />
                        <input type="hidden" name="client_id" value="xxxxxx.apps.googleusercontent.com" />
                        <input type="hidden" name="redirect_uri" value="http://xxxxxxxx.appspot.com/xxxx.jsp" />
                        <input type="hidden" name="scope" value="openid email" />
                        <input type="hidden" name="access_type" value="online" />
                        <input type="hidden" name="approval_prompt" value="auto" />
                        <input type="hidden" name="openid.realm" value="http://xxxxxxxxx.appspot.com/" />
                  </form>
               When we submit the form above I receive the response that contains the id_token in the page xxxx.jsp

             2-  In the page xxxxx.jsp I use this function below to retrieve the email
                  public String getEmailFromURL(String idToken){
                       System.out.println(idToken);
                       String[] jwtParts = idToken.split("\\.");
                       String payload = "";
                      JSONObject json = null;
                      payload = new String( Base64.decode(jwtParts[1].getBytes()));
                      System.out.println(payload);
                      //logger.info("Payload: "+payload);
                      //json = (JSONObject) JSONValue.parse(payload);\
                     String email = getEmail(payload);
                     if(payload!=null)
                     System.out.println(email);
                     //logger.info("Email: "+json.get("email"));   
                      return email;
                }

                 Remember that its worked very well since April 2016, but on October 22, 2016 Its not working, because the id_token is invalid. The statement "System.out.println(payload);" that's print the payload with an ? in the console of the cloud.

Best Regards.

On Monday, November 7, 2016 at 11:15:13 AM UTC-5, Carl Andin Michel Sanon wrote:
Hi Everyone,
                 We have our web application under Appengine server that's worked very well since April 2016, now users can't connect because of invalid id token from google. I try to see what change the developer from google has made, I can't see. Here is a log from google below that's print My payload finish with an "?". Someone has already found this problem?. I need your help please because users can't connect .
Best Regards.

[s~xxxxx/v1-0-4.396821290758257501].<stdout>: {"iss":"accounts.google.com","iat":1478529880,"exp":1478533480,"at_hash":"0gp2l3j9SSSI0cUDuYAJ-w","aud":"xxxxx.apps.googleusercontent.com","sub":"103993690248691064163","email_verified":true,"azp":"xxxxxxxx.apps.googleusercontent.com","hd":"xxxx.gouv.ht","email":"xxx@gmail.com"B'?

--
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/0edd895e-2e71-44ed-9a60-d45f47e5f373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Tuesday, November 8, 2016

[google-cloud-sql-discuss] Re: New Problem with login using google in OpenID Connect return Invalid Id Token that print invalid payload

Hi Adam
            Thanx for your support.
            This is the detail of my process : I have
            1- A jsp for login that contains this form
                   <form action="https://accounts.google.com/o/oauth2/auth" method="get" name="loginForm">
                        <input type="hidden" name="response_type" value="token id_token" />
                        <input type="hidden" name="client_id" value="xxxxxx.apps.googleusercontent.com" />
                        <input type="hidden" name="redirect_uri" value="http://xxxxxxxx.appspot.com/xxxx.jsp" />
                        <input type="hidden" name="scope" value="openid email" />
                        <input type="hidden" name="access_type" value="online" />
                        <input type="hidden" name="approval_prompt" value="auto" />
                        <input type="hidden" name="openid.realm" value="http://xxxxxxxxx.appspot.com/" />
                  </form>
               When we submit the form above I receive the response that contains the id_token in the page xxxx.jsp

             2-  In the page xxxxx.jsp I use this function below to retrieve the email
                  public String getEmailFromURL(String idToken){
                       System.out.println(idToken);
                       String[] jwtParts = idToken.split("\\.");
                       String payload = "";
                      JSONObject json = null;
                      payload = new String( Base64.decode(jwtParts[1].getBytes()));
                      System.out.println(payload);
                      //logger.info("Payload: "+payload);
                      //json = (JSONObject) JSONValue.parse(payload);\
                     String email = getEmail(payload);
                     if(payload!=null)
                     System.out.println(email);
                     //logger.info("Email: "+json.get("email"));   
                      return email;
                }

                 Remember that its worked very well since April 2016, but on October 22, 2016 Its not working, because the id_token is invalid. The statement "System.out.println(payload);" that's print the payload with an ? in the console of the cloud.

Best Regards.

On Monday, November 7, 2016 at 11:15:13 AM UTC-5, Carl Andin Michel Sanon wrote:
Hi Everyone,
                 We have our web application under Appengine server that's worked very well since April 2016, now users can't connect because of invalid id token from google. I try to see what change the developer from google has made, I can't see. Here is a log from google below that's print My payload finish with an "?". Someone has already found this problem?. I need your help please because users can't connect .
Best Regards.

[s~xxxxx/v1-0-4.396821290758257501].<stdout>: {"iss":"accounts.google.com","iat":1478529880,"exp":1478533480,"at_hash":"0gp2l3j9SSSI0cUDuYAJ-w","aud":"xxxxx.apps.googleusercontent.com","sub":"103993690248691064163","email_verified":true,"azp":"xxxxxxxx.apps.googleusercontent.com","hd":"xxxx.gouv.ht","email":"xxx@gmail.com"B'?

--
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/2fc50a5c-75b3-4444-865e-6a6394aa6867%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: New Problem with login using google in OpenID Connect return Invalid Id Token that print invalid payload

Could you share the details about how you're making the request that produces the invalid token?

On Monday, November 7, 2016 at 11:15:13 AM UTC-5, Carl Andin Michel Sanon wrote:
Hi Everyone,
                 We have our web application under Appengine server that's worked very well since April 2016, now users can't connect because of invalid id token from google. I try to see what change the developer from google has made, I can't see. Here is a log from google below that's print My payload finish with an "?". Someone has already found this problem?. I need your help please because users can't connect .
Best Regards.

[s~xxxxx/v1-0-4.396821290758257501].<stdout>: {"iss":"accounts.google.com","iat":1478529880,"exp":1478533480,"at_hash":"0gp2l3j9SSSI0cUDuYAJ-w","aud":"xxxxx.apps.googleusercontent.com","sub":"103993690248691064163","email_verified":true,"azp":"xxxxxxxx.apps.googleusercontent.com","hd":"xxxx.gouv.ht","email":"xxx@gmail.com"B'?

--
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/83fda40c-e474-42e9-9ace-92b49f885a7d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Monday, November 7, 2016

[google-cloud-sql-discuss] New Problem with login using google in OpenID Connect return Invalid Id Token that print invalid payload

Hi Everyone,
                 We have our web application under Appengine server that's worked very well since April 2016, now users can't connect because of invalid id token from google. I try to see what change the developer from google has made, I can't see. Here is a log from google below that's print My payload finish with an "?". Someone has already found this problem?. I need your help please because users can't connect .
Best Regards.

[s~xxxxx/v1-0-4.396821290758257501].<stdout>: {"iss":"accounts.google.com","iat":1478529880,"exp":1478533480,"at_hash":"0gp2l3j9SSSI0cUDuYAJ-w","aud":"xxxxx.apps.googleusercontent.com","sub":"103993690248691064163","email_verified":true,"azp":"xxxxxxxx.apps.googleusercontent.com","hd":"xxxx.gouv.ht","email":"xxx@gmail.com"B'?

--
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/e6aa6fdf-ba6c-4cb8-b116-2b09ae9531ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] How to Automate Store Procedure Testing in SQL Server

Hi, I am a newbie in SQL. I use SQL server for database management in my company. I am assigned task to automate the manual testing of business rules/stored procedures. I am searching for a method which is generic for automating any business rule testing (There are hundreds of business rules). Can somebody suggest me which technology is best suited for this ? Also what could be a better choice between TSQL and DBUnit for this task ?

--
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/bfcb06bb-7531-4b90-950e-15a49852c2e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Friday, November 4, 2016

[google-cloud-sql-discuss] Re: Cannot connect to Cloud SQL 2nd generation

Hey Great Studio,

This should be posted as an issue thread in the Public Issue Tracker for Cloud SQL. However, I'll help by suggesting some paths of investigation to pursue before making an issue report:

1. Error 111 is usually caused by the instance not listening on 3306. Is it possible that the my.cnf file is at issue?

2. You should include your my.cnf file when reporting the issue.

3. Does reverting to the prior my.cnf file resolve the issue?

4. What is the project ID and instance ID?

These details will allow us to properly investigate the issue report once you post it to the Public Issue Tracker for Cloud SQL. This forum is meant for more high-level discussion of the service, design patterns, etc. as opposed to reporting issues. Feel free to ask any questions you may have either before or simultaneously with posting to the Issue Tracker. I'll be happy to assist. 

Cheers,

Nick
Cloud Platform Community Support

On Saturday, October 29, 2016 at 12:05:30 PM UTC-4, Great Studio wrote:
Hi,

I think Google Cloud SQL 2nd generation is inaccessible now.

I tried to connect from GCE instances to Cloud SQL via Cloud SQL Proxy, but I cannot connect.
This happened when I restarted Cloud SQL instance (with changing instance spec) at about June 11, 15:00 UTC (June 12, 00:00 JST).

I updated my.cnf variables and machine specs for several times, and just restarted instance for several times.
It takes so long (5 - 10 mins) to complete restart. I viewed Stackdriver logging page [ https://console.cloud.google.com/logs ] and saw ton of warnings.
In the operations tab [ https://console.cloud.google.com/sql/instances/INSTANCE_NAME/operations ], there are several "An unknown error occurred" logs on restart and update.


Next, I gave up to continue with Google Cloud SQL and get back to our old server instance which is hosted by another cloud vendor.
To keep data, I tried to export current data with export button in the overview page of Cloud SQL instance [ https://console.cloud.google.com/sql/instances/INSTANCE_NAME/overview ]

I saved it in SQL format, but the file is 0 byte and empty.

In the operation page, I found following error message:
mysqldump: Got error: 2002: Can't connect to local MySQL server through socket '/mysql/mysql.sock' (111) when trying to connect


Thanks in advance.

Alison

--
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/0df9f28a-d005-41e3-8970-e889eff2c75c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Sql instance never restarts

Welcome LizBetSoft,

It's not entirely clear from this brief message and PROCESSLIST what is stalling the restart of your Cloud SQL instance.  If you could answer the questions below, we may have a better idea of where to start investigating:
  • Is the status of your instance still "restarting"?
  • Is this instance one of first or second generation?
  • From the Binlog Dump, may I assume that you have Binary Logging enabled?
  • What do the instance logs look like?
  • Have you tried anything else since posting this here?
I look forward to your response.

On Monday, October 31, 2016 at 4:34:52 PM UTC-4, LizBetSoft wrote:
I restarted my sql instance 30 minutes ago and stills "restarting" what can i do?

wen i do show processlist in mysql i see

 1149793 | cloudsqlreplica | 8.34.216.122:53556           | NULL         | Binlog Dump GTID | 2177 | Sending to client | NULL  



--
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/9a716bd3-83de-42d9-b7aa-33ca49bcc879%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Wednesday, November 2, 2016

Re: [google-cloud-sql-discuss] Create Users in Free Trial?

This should work as it is. We have documentation for creating users here [0].

[0] https://cloud.google.com/sql/docs/create-manage-user-mysql#creating

On Wed, Nov 2, 2016 at 2:17 PM, Mike Tickle <mtickle@gmail.com> wrote:
Vishnu, thanks for answering so quickly.

Let me rephrase my question: The root account in MySQL does not have adequate permissions to create users. Is that a result of my account being in the free trial period?

-Mike

On Wednesday, November 2, 2016 at 5:06:31 PM UTC-4, Vishnu Fafat wrote:
Hi Mike,

This feature is currently available in UI/API/GCloud for first generation and in API/GCloud for second generation. We are working on making this available in the UI for second generation as well.

On Wed, Nov 2, 2016 at 1:59 PM, Mike Tickle <mti...@gmail.com> wrote:
Hi everyone,

I am currently evaluating Cloud SQL for my company. I don't seem to be able to create users in the console, MySQL Workbench or Cloud Shell. Is user management not available during the free trial period?

Thanks,
Mike

--
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/09370b78-02d6-4a29-8111-350fd1d6496a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

--
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/6c6204fb-c143-493d-b8f9-a0819e68932d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

--
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/CAPVxmMDZy26Ai-Dae3WfntyKYqpWOoGEk9ywAy-gTH9mo1qfqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Create Users in Free Trial?

Vishnu, thanks for answering so quickly.

Let me rephrase my question: The root account in MySQL does not have adequate permissions to create users. Is that a result of my account being in the free trial period?

-Mike

On Wednesday, November 2, 2016 at 5:06:31 PM UTC-4, Vishnu Fafat wrote:
Hi Mike,

This feature is currently available in UI/API/GCloud for first generation and in API/GCloud for second generation. We are working on making this available in the UI for second generation as well.

On Wed, Nov 2, 2016 at 1:59 PM, Mike Tickle <mti...@gmail.com> wrote:
Hi everyone,

I am currently evaluating Cloud SQL for my company. I don't seem to be able to create users in the console, MySQL Workbench or Cloud Shell. Is user management not available during the free trial period?

Thanks,
Mike

--
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/09370b78-02d6-4a29-8111-350fd1d6496a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

--
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/6c6204fb-c143-493d-b8f9-a0819e68932d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-cloud-sql-discuss] Create Users in Free Trial?

Hi Mike,

This feature is currently available in UI/API/GCloud for first generation and in API/GCloud for second generation. We are working on making this available in the UI for second generation as well.

On Wed, Nov 2, 2016 at 1:59 PM, Mike Tickle <mtickle@gmail.com> wrote:
Hi everyone,

I am currently evaluating Cloud SQL for my company. I don't seem to be able to create users in the console, MySQL Workbench or Cloud Shell. Is user management not available during the free trial period?

Thanks,
Mike

--
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/09370b78-02d6-4a29-8111-350fd1d6496a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Vishnu Fafat

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

[google-cloud-sql-discuss] Create Users in Free Trial?

Hi everyone,

I am currently evaluating Cloud SQL for my company. I don't seem to be able to create users in the console, MySQL Workbench or Cloud Shell. Is user management not available during the free trial period?

Thanks,
Mike

--
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/09370b78-02d6-4a29-8111-350fd1d6496a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-cloud-sql-discuss] Re: Need sql instance un-suspended (due to billing)

Since your payment was processed on November 1st, it may take 48 hours for your Cloud SQL instance to be taken out of the suspended state. In the meantime I have notified the Billing Agent who is investigating your case, and they are working to rectify the suspension state on their end. 

--
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/569dd87a-5635-4916-9c1b-5b5cf28cefa1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.