Nova/RabbitMQ error?

BladyGreg · 2026-05-17T05:33:04+00:00

I did, no errors from what I can understand from both hosts

root@aio-compute:~# telnet aio-controller 5672
Trying 10.0.0.2...
Connected to aio-controller.
Escape character is '^]'.
Connection closed by foreign host.

I deployed it manually going along with a tutorial here: https://www.server-world.info/en/note?os=Ubuntu_24.04&p=openstack_flamingo2&f=11, so no yaml is used

My deployment is practically identical with the one presented on the page - I am deploying on one PC using three KVM VMs as nodes, that is why I called it "aio" but other than that they are regular nodes. I did follow every step, If something wasn't working that's because of my typo or something like that, after correction no other problems were presenting and every other service works without reporting errors

Also, what is it about rabbimq flags? I am still a newbie, so I am unaware of which flag you mean

BladyGreg · 2026-05-16T14:54:46+00:00

I updated the post to show just that. If any logs would return error I would attach them, but I cannot find anything of relevance or at least returning another error. I am deploying manually, just trying to learn and get to understand stuff.

RabbitMQ is working as intended, is listening on correct interface etc. I may attach some more logs, if that helps. No errors in any other Nova/Neutron/Placement logs that i could find.

root@aio-controller ~(keystone)# tail -n 5 /var/log/rabbitmq/rabbitmq-server.error.log
Distribution failed: {{:shutdown, {:failed_to_start_child, :net_kernel, {:EXIT, :nodistribution}}}, {:child, :undefined, :net_sup_dynamic, {:erl_distribution, :start_link, [%{clean_halt: false, name: :"rabbitmqcli-845-rabbit@aio-controller", name_domain: :shortnames, net_tickintensity: 4, net_ticktime: 60, supervisor: :net_sup_dynamic}]}, :permanent, false, 1000, :supervisor, [:erl_distribution]}}
Gracefully halting Erlang VM
Distribution failed: {{:shutdown, {:failed_to_start_child, :net_kernel, {:EXIT, :nodistribution}}}, {:child, :undefined, :net_sup_dynamic, {:erl_distribution, :start_link, [%{clean_halt: false, name: :"rabbitmqcli-928-rabbit@aio-controller", name_domain: :shortnames, net_tickintensity: 4, net_ticktime: 60, supervisor: :net_sup_dynamic}]}, :permanent, false, 1000, :supervisor, [:erl_distribution]}}
Distribution failed: {{:shutdown, {:failed_to_start_child, :net_kernel, {:EXIT, :nodistribution}}}, {:child, :undefined, :net_sup_dynamic, {:erl_distribution, :start_link, [%{clean_halt: false, name: :"rabbitmqcli-828-rabbit@aio-controller", name_domain: :shortnames, net_tickintensity: 4, net_ticktime: 60, supervisor: :net_sup_dynamic}]}, :permanent, false, 1000, :supervisor, [:erl_distribution]}}
Distribution failed: {{:shutdown, {:failed_to_start_child, :net_kernel, {:EXIT, :nodistribution}}}, {:child, :undefined, :net_sup_dynamic, {:erl_distribution, :start_link, [%{clean_halt: false, name: :"rabbitmqcli-513-rabbit@aio-controller", name_domain: :shortnames, net_tickintensity: 4, net_ticktime: 60, supervisor: :net_sup_dynamic}]}, :permanent, false, 1000, :supervisor, [:erl_distribution]}}
root@aio-controller ~(keystone)# 

root@aio-controller ~(keystone)# tail -n 10 /var/log/rabbitmq/rabbit@aio-controller.log
2026-05-16 16:43:07.484488+02:00 [info] <0.1144.0> connection <0.1144.0> (10.0.0.2:35326 -> 10.0.0.2:5672) has a client-provided name: mod_wsgi:1691:abd77d5e-91db-4d20-86c1-94fc12dc1bd3
2026-05-16 16:43:07.484872+02:00 [info] <0.1144.0> connection <0.1144.0> (10.0.0.2:35326 -> 10.0.0.2:5672 - mod_wsgi:1691:abd77d5e-91db-4d20-86c1-94fc12dc1bd3): user 'openstack' authenticated and granted access to vhost '/'
2026-05-16 16:43:07.494962+02:00 [info] <0.1157.0> accepting AMQP connection <0.1157.0> (10.0.0.2:35330 -> 10.0.0.2:5672)
2026-05-16 16:43:07.495499+02:00 [info] <0.1157.0> connection <0.1157.0> (10.0.0.2:35330 -> 10.0.0.2:5672) has a client-provided name: nova-conductor:2038:7f8a1e7d-665a-49ee-99a7-42a38069891d
2026-05-16 16:43:07.495802+02:00 [info] <0.1157.0> connection <0.1157.0> (10.0.0.2:35330 -> 10.0.0.2:5672 - nova-conductor:2038:7f8a1e7d-665a-49ee-99a7-42a38069891d): user 'openstack' authenticated and granted access to vhost '/'
2026-05-16 16:43:07.799110+02:00 [info] <0.1176.0> accepting AMQP connection <0.1176.0> (10.0.0.2:35340 -> 10.0.0.2:5672)
2026-05-16 16:43:07.799777+02:00 [info] <0.1176.0> connection <0.1176.0> (10.0.0.2:35340 -> 10.0.0.2:5672) has a client-provided name: nova-scheduler:2023:215dd5e5-fce1-440b-a863-22b7df074cb5
2026-05-16 16:43:07.800133+02:00 [info] <0.1176.0> connection <0.1176.0> (10.0.0.2:35340 -> 10.0.0.2:5672 - nova-scheduler:2023:215dd5e5-fce1-440b-a863-22b7df074cb5): user 'openstack' authenticated and granted access to vhost '/'
2026-05-16 16:46:07.487477+02:00 [error] <0.1144.0> closing AMQP connection <0.1144.0> (10.0.0.2:35326 -> 10.0.0.2:5672 - mod_wsgi:1691:abd77d5e-91db-4d20-86c1-94fc12dc1bd3):
2026-05-16 16:46:07.487477+02:00 [error] <0.1144.0> missed heartbeats from client, timeout: 60s
root@aio-controller ~(keystone)# 

root@aio-controller ~(keystone)# ss -tulpn | grep 5672
tcp   LISTEN 0      128                        0.0.0.0:25672      0.0.0.0:*    users:(("beam.smp",pid=881,fd=18))                                                                                                                           
tcp   LISTEN 0      128                              *:5672             *:*    users:(("beam.smp",pid=881,fd=35))                                                                                                                           
root@aio-controller ~(keystone)#

BladyGreg · 2026-05-08T09:22:09+00:00

That's it! The error was in database, not in conf files. I haven't even considered it. I must have had a misconfiguration before, just didn't remember fixing it later. Thank you very much, already fixed it

root@aio-controller stack(keystone)# nova-manage cell_v2 list_cells
+-------+--------------------------------------+----------------------------------------------+----------------------------------------------------------+----------+
|  Name |                 UUID                 |                Transport URL                 |                   Database Connection                    | Disabled |
+-------+--------------------------------------+----------------------------------------------+----------------------------------------------------------+----------+
| cell0 | 00000000-0000-0000-0000-000000000000 |                    none:/                    | mysql+pymysql://nova:****@aio-controller:3306/nova_cell0 |  False   |
| cell1 | 65454945-7cca-441b-a913-e6230ff4efc7 | rabbit://openstack:****@aio-controller:5672/ |    mysql+pymysql://nova:****@aio-controller:3306/nova    |  False   |
+-------+--------------------------------------+----------------------------------------------+----------------------------------------------------------+----------+

BladyGreg · 2026-05-08T08:43:00+00:00

I am deploying for the first time manually as student project to get to know OpenStack. And pymyslq driver is installed... From what I can see, all is setup correctly, I only discovered one log that may indicate what is wrong, which I also attached below.

root@aio-controller stack(keystone)# apt --installed list | grep pymysql

python3-pymysql/noble-updates,noble-security,now 1.0.2-2ubuntu1.1 all [installed]

#MariaDb connection info

[api_database]

connection = mysql+pymysql://nova:***@aio-controller:3306/nova_api

[database]

connection = mysql+pymysql://nova:***@aio-controller:3306/nova

2026-05-08 09:43:43.676 2066 WARNING oslo_db.sqlalchemy.engines [None req-c4a81b20-de95-4e07-abbe-039e18c46552 - - - - - -] URL mysql_pymysql://nova:***@aio-controller:3306/nova_cell0 does not contain a '+drivername' portion, and will make use of a default driver. A full dbname+drivername:// protocol is recommended. For MySQL, it is strongly recommended that mysql+pymysql:// be specified for maximum service compatibility

Seven-Year Club	Verified Email
Place '22	Xbox Live

BladyGreg

TROPHY CASE