search

jmac11 / googlecloudsql

Automatically exported from code.google.com/p/googlecloudsql
0 stars 0 forks source link

Root passwords not updating on new D0 instances. #86

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
MySQL said: Access denied for user 'root'@'IP' (using password: YES)

... No matter what password I change the root password to on a freshly created 
instance, it still gives me this connection error. My preexisting databases 
work fine, it's only new ones.

I've tried now to create two separate Cloud SQL instances and they refuse to 
work.

Original issue reported on code.google.com by b...@benguild.com on 1 May 2014 at 11:18

GoogleCodeExporter commented 9 years ago 
I was able to work around this issue by creating a DB in a different region. I 
can confirm that this is still a problem, and it's pretty annoying to not be 
able to get in touch with you guys about critical issues like this.

New DBs in us-central1-b can be accessed but us-central1-a reject the root 
password no matter what currently.

Original comment by b...@benguild.com on 2 May 2014 at 12:40

GoogleCodeExporter commented 9 years ago 
Wow, I'm even getting some Access denied for user 'root'@'... errors just in 
doing updates and configuration changes ....

Original comment by b...@benguild.com on 2 May 2014 at 1:05

GoogleCodeExporter commented 9 years ago 
am also getting same issue.I tried to create a password where am getting a 
message as "Instance busy". But the operation log is mentioned as "inject user 
done " I am not able to deliver my project due to this.Please consider this in 
high priority.

Original comment by phi...@gmail.com on 19 May 2014 at 12:55

GoogleCodeExporter commented 9 years ago 
Are you still experiencing this issue yet ?

Original comment by ju...@google.com on 16 Apr 2015 at 10:31

GoogleCodeExporter commented 9 years ago 
yeah it's still an issue on new instances. `root` is inaccessible remotely, but 
new users created via http://cloud.google.com can be accessed without issue.

Original comment by b...@benguild.com on 17 Apr 2015 at 5:32

GoogleCodeExporter commented 9 years ago 
Hi, Ben

Can you confirm that you have an account associated for the remote host, 
specifically, a "root@remote-host-name" instead of the default "@locahost" 
accounts for your instance ?

Original comment by ju...@google.com on 21 Apr 2015 at 10:12

GoogleCodeExporter commented 9 years ago 
Sure, if you want to give our account some credit for our time/trouble. We're a 
paying customer on multiple projects and ran into this issue almost a year ago 
with little to no response.

    _____________________________
From: googlecloudsql@googlecode.com
Sent: Wednesday, April 22, 2015 7:13 AM
Subject: Re: Issue 86 in googlecloudsql: Root passwords not updating on new D0 
instances.
To:  <ben@benguild.com>

Original comment by b...@benguild.com on 22 Apr 2015 at 5:01

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
@ben 

Thank you for providing your feedback in the public issue tracker. 
Unfortunately, this isn't the correct place to go about asking for any credits 
to your billing account. If you're interested in reading about how to apply for 
a credit if you believe you've been affected by an outage, see [1]. 

As far as the state of this issue, it appears to be working as intended. By 
default, Cloud SQL has no "root@%" user, only "root@localhost". This means 
there is actually no "root" user to login as unless connecting from "localhost" 
(ie. via an App Engine connection), until you create the "root@%" user. 

On the CloudSQL MySQL installation, there are multiple accounts with the same 
name "root" and same root privileges, each with its own possible password, 
depending on the host in "root@host", which differentiates these accounts. If 
you want to set the root password for one of these root accounts, you should 
set it for that one to make sure it takes effect. The "root@%" setting will 
override the other passwords, since it applies for any host, however.

To login as root from a remote host, you can manually add the "root" user to 
your Cloud SQL instance, which will set up "root@%" (the "any-host" notation).

@phisjo

I'm not sure that the issue you bring up is related to this one. If you feel 
you'd still like it to be investigated, I suggest opening a new thread where 
you detail exactly what your situation is.

[1] https://cloud.google.com/appengine/kb/billing#credit

Original comment by ju...@google.com on 22 Apr 2015 at 11:24