SECOND GENERATION CLOUD SQL CANNT CONNECT VIA TOAD/HEIDI & RESTART SHOWING ERROR

[DJ]

Hi,

I created second generation cloud sql. I gave my ip to authorized networks.

And restarted the instance. Restart DONE but this msg showing 

An unknown error occurred

Also i tried to access cloud sql via TOAD & HEIDI.

I changed the root pwd also.

But i cannt access via cloud sql. Plz refer the attached image.

Plz help me to solve this

[Danny Xu]

Hi, could you check if your client IP address (the address shows up on the website ip4.me) is added to "Authorized networks" of the CloudSQL instance. If you notice that your client IP keeps changing. You could try the subnet address (e.g. 117.218.0.0/16).

[DJ]

Thanks for your reply Danny Xu,

1. We have added all CLIENT IP's(STATIC IP) in the allowed networks section already.
2. In fact using the same client, we can successfully  connect to the FIRST GEN CL SQL instance.
3. Also, why we got an err message , when we restart the instance?

Plz help urgently, as we are billed fr this instance fr the past 3Days!

[DJ]

I m waiting for some one reply.this is urgent. Plz reply. 

[Lee Schumacher]

I'll take a look when I get in around 9am.

--
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-d...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-cloud-sql-discuss/3fee5be1-f824-4fc0-9960-1e9a0479e63d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Danny Xu]

Hi, I noticed that you changed the ActivationPolicy from ALWAYS to NEVER. This will shutdown your MYSQL so that you're not able to connect to your instance I think. Since the ActivationPolicy is NEVER, we prevent you to restart the instance.

I've put your instance ActivationPolicy to ALWAYS, would you try to connect again?

Meanwhile, I'll walk through our public document to see if the behavior above is explained well. Sorry about the late reply.

[DJ]

Thanks You Danny Xu,

Now i can connect via toad!

[Danny Xu]

Hi DJ,

Our public document doesn't catch up with out dev progress. So if you put the activation policy to NEVER, it will shutdown the compute resource (stop MYSQL) to save you $$ but you still have to pay the storage. You definitely won't be able to connect to the instance if the policy is NEVER.

I'll make sure the behavior above showing up in our public document soon.

[DJ]

Thanks Danny Xu,

I can create tables, procedures. but i cannt create trigger in 2nd GEN CLSQL.

I got this error " You do not have the SUPER privilege and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable)”.

using this i tried to fix "set global log_bin_trust_function_creators=1;"

But i got the below error

Setting this variable “Access denied; you need (at least one of) the SUPER privilege(s) for this operation”

But i saw mysql.user SUPER privilege = Y.

Plz help me i cannt create trigger in 2nd GEN CLSQL

[Danny Xu]

Hi DJ,

For security and some other purposes, we don't allow users to change mysql flags from your client (we do it for you.). You can add the mysql flag "log_bin_trust_function_creators" from UI Edit page.

If you are still not able to create triggers, could you send me the sql commands you use to create tables and triggers for further investigation? Thank you.