Link: https://openstack.nimeyo.com/31835/?show=68695#c68695
From: buptzhoutian
The most likely reason : You configured your mysql connection in the [api_database] , not [database]
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinf
I can confirm. Following docs here:
http://docs.openstack.org/juno/install-guide/install/yum/content/ch_nova.html#nova-controller-install
I removed the distro nova.conf and created a new and added this content,
replacing it with the settings pertenant to my environment an it is now
working.
Subject: Re: [Openstack] Nova DB sync Operational error
Well created a new controller on a whole new machine and get all the way up
until compute and get same error again. I have to think it something with my
nova.conf but I cant figure it out. Ive pasted here so if anyone can take a
look and see
Ok well figured it out!!!
I guess its either me or the documentation. I basically got rid of the
original nova.conf (that comes with the distro) and then I just made a new
nova.conf with only the changes that are listed in the documentation (ie I
created [database] [DEFAULT] etc sections listed th
Hi,
this is a (mostly) working Juno nova.conf (up to end of chapter 8, block
storage, on CentOS 7): http://paste.openstack.org/show/139106/
I'm currently struggling with Neutron issues but database connection is
working fine.
Hope this helps,
Uwe
Am 26.11.2014 um 22:56 schrieb Amit A
Well created a new controller on a whole new machine and get all the way up
until compute and get same error again. I have to think it something with
my nova.conf but I cant figure it out. Ive pasted here so if anyone can
take a look and see maybe what Im doing incorrect I would appreciate it...
h
Im going to try building a new controller on a whole new nuc see if I get
the same I will keep yall abreast if it works or not. In any case thank you
very much for all your help!!!
On Wed, Nov 26, 2014 at 3:56 PM, Amit Anand wrote:
>
> Password is viimed1
>
>
>
> On Wed, Nov 26, 2014 at 3:55 PM,
George
Thanks. Yeah there no other nova.conf I went as far as to do a find in case
I put somewhere nothing turned up except the proper one. I did have a
nova.conf.orig (I always make a backup so i can always start over) and was
hoping maybe you hit the nail on the head so I moved that out to my
/
Password is viimed1
On Wed, Nov 26, 2014 at 3:55 PM, Amit Anand wrote:
> George
>
> Thanks. Yeah there no other nova.conf I went as far as to do a find in
> case I put somewhere nothing turned up except the proper one. I did have a
> nova.conf.orig (I always make a backup so i can always start
Amit,
Please tell me whats the real password?
On Thu, Nov 27, 2014 at 2:12 AM, Amit Anand wrote:
> Geo
>
> Error logs are here:
>
> http://paste.openstack.org/show/139035/
>
> When I run your command with password nova it fails - when I run it with
> the real password it works fine
>
> [root@co
Jay,
So this is the command that u sent, works just fine connect to Nova DB:
[root@controller nova]# mysql -unova -hlocalhost -p -Dnova
Enter password:
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 8
Server version: 5.5.40-MariaDB MariaDB Server
Copyri
Geo
Error logs are here:
http://paste.openstack.org/show/139035/
When I run your command with password nova it fails - when I run it with
the real password it works fine
[root@controller ~]# mysql -u nova -p -h controller nova
Enter password:
I entered nova here
ERROR 1045 (28000): Access denie
Make sure that nova.conf you edited it's actually being used, if you have a
nova.conf in your root directory it will be used before the one in
"/etc/nova/".
You could start the db sync with strace and see what config file is
actually used just to make sure. Also, if the nova.conf has wrong
permiss
Also verify from controller node
mysql -u nova -p -h controller nova
is working with password => nova
On Thu, Nov 27, 2014 at 1:42 AM, Amit Anand wrote:
> I tried and still same errors. I dont see how that would fix in any case
> as the guide says I need to put the password into the connection
On 11/26/2014 03:36 PM, Amit Anand wrote:
I also took a look at a command you ran and I tried it, would this be
correct output (notice I didnt specify a DB in command)?
Yep, that all looks correct to me. I'm a little unsure what else to
investigate, frankly, Amit :( There's got to be *somethi
Amit,
It should work. actually we have to give it like this.
I faced this error earlier and fixed it by changing like this.
can you paste the exact error here?
On Thu, Nov 27, 2014 at 1:42 AM, Amit Anand wrote:
> I tried and still same errors. I dont see how that would fix in any case
> as th
Try this
connection=mysql://nova:nova@controller/nova
This will fix the issue.
On Thu, Nov 27, 2014 at 1:06 AM, Amit Anand wrote:
> Same error - also tried with 127.0.0.1. Even crazier I removed all
> keystone nova (user, service, etc) and dropped the nova DB and recreated
> that, then recreat
On 11/26/2014 02:36 PM, Amit Anand wrote:
Same error - also tried with 127.0.0.1. Even crazier I removed all
keystone nova (user, service, etc) and dropped the nova DB and recreated
that, then recreated keystone nova with a new different password,
updated nova.conf with new password and still get
I tried and still same errors. I dont see how that would fix in any case as
the guide says I need to put the password into the connection config?
Tried below and same error:
# The SQLAlchemy connection string used to connect to the
# bare-metal database (string value)
connection=mysql://nova:nova
HI Geo - Pasted above in the email chain but here it is again:
# The SQLAlchemy connection string used to connect to the
# bare-metal database (string value)
connection=mysql://nova:PASSWORD@localhost/nova
On Wed, Nov 26, 2014 at 2:17 PM, Geo Varghese wrote:
> Hi Amit,
>
> Please open => /etc/
Hi Jay - I believe so below is the part that is in the nova.conf
# The SQLAlchemy connection string used to connect to the
# bare-metal database (string value)
connection=mysql://nova:PASSWORD@controller/nova
The PASSWORD is exactly the same what I have in the conf file and what I
have in the nov
Same error - also tried with 127.0.0.1. Even crazier I removed all keystone
nova (user, service, etc) and dropped the nova DB and recreated that, then
recreated keystone nova with a new different password, updated nova.conf
with new password and still get the same error (notice below now nova has
t
I mean it is exactly the same in nova.conf and the command line
On Wed, Nov 26, 2014 at 2:21 PM, Amit Anand wrote:
> Hi Jay - I believe so below is the part that is in the nova.conf
>
> # The SQLAlchemy connection string used to connect to the
> # bare-metal database (string value)
> connection
Hi Amit,
Please open => /etc/nova/nova.conf
Find a line with starting with "connection = "
Please paste it here. That will help us to fix the issue.
On Wed, Nov 26, 2014 at 11:55 PM, Jay Pipes wrote:
> On 11/25/2014 05:10 PM, Amit Anand wrote:
>
>> Hi all,
>>
>> Setup: 3 node, one controller,
On 11/26/2014 02:21 PM, Amit Anand wrote:
Hi Jay - I believe so below is the part that is in the nova.conf
# The SQLAlchemy connection string used to connect to the
# bare-metal database (string value)
connection=mysql://nova:PASSWORD@controller/nova
The PASSWORD is exactly the same what I have
On 11/25/2014 05:10 PM, Amit Anand wrote:
Hi all,
Setup: 3 node, one controller, one compute and one network all separate
machines. Juno install.
Recreating my Juno install and this is the second time Ive gotten this
error whne running "su -s /bin/sh -c "nova-manage db sync" nova" ( I got
in in
Hi all,
Setup: 3 node, one controller, one compute and one network all separate
machines. Juno install.
Recreating my Juno install and this is the second time Ive gotten this
error whne running "su -s /bin/sh -c "nova-manage db sync" nova" ( I got in
in another install so I started over):
2014-1
27 matches
Mail list logo
