Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

PROBLEM RESOLVED.

The fact is that's not about AMQP problems, but about cinder-volume & cinder-scheduler that are not working, as I said before.

To see in real time what's going on during an instance creation on RabbitMQ, I've seen in real time logs by using the command tail -f /var/log/rabbitmq/rabbit@openstack.log (logs for RMQ are located here). And there's no "ERROR" log during the execution of instance creation. Here's what I got :

=INFO REPORT==== 25-Apr-2017::09:48:52 ===
accepting AMQP connection <0.13986.0> (192.168.30.155:53962 -> 192.168.30.155:5672)

As Bernd said before, the problem is somewhere else. So I decided to see if there's services in execution about Cinder by executing the command ps -an | grep cinder and I saw that there's no cinder-scheduler & cinder-volume service in running state.

I've tried to find if there's a path to execute these services in order to revive correctly Cinder. By using the command head -n 10 for c-sch.log and c-vol.log, I've found the anwser to my question.

/usr/local/bin/cinder-volume --config-file /etc/cinder/cinder.conf

&

/usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf

By using the screen command, I've created two screens by naming them c-sch and c-vol. According to their names, I've executed the services related to. Detaching from the screens and executing the command openstack volume service list and I can see that there are now working !

+------------------+-----------------------+------+---------+-------+----------------------------+
| Binary           | Host                  | Zone | Status  | State | Updated At                 |
+------------------+-----------------------+------+---------+-------+----------------------------+
| cinder-scheduler | openstack             | nova | enabled | up    | 2017-04-25T08:49:01.000000 |
| cinder-volume    | openstack@lvmdriver-1 | nova | enabled | up    | 2017-04-25T08:49:01.000000 |
+------------------+-----------------------+------+---------+-------+----------------------------+

I don't know if it's the good way to resolve this issue but now, I can create volumes without doubt and attach them to my instances.

PROBLEM RESOLVED.

The fact is that's not about AMQP problems, but about cinder-volume & cinder-scheduler that are not working, as I said before.

To see in real time what's going on during an instance creation on RabbitMQ, I've seen in real time logs by using the command tail -f /var/log/rabbitmq/rabbit@openstack.log (logs for RMQ are located here). And there's no "ERROR" log during the execution of instance creation. Here's what I got :

=INFO REPORT==== 25-Apr-2017::09:48:52 ===
accepting AMQP connection <0.13986.0> (192.168.30.155:53962 -> 192.168.30.155:5672)

As Bernd said before, the problem is somewhere else. So I decided to see if there's services in execution about Cinder by executing the command ps -an | grep cinder and I saw that there's no cinder-scheduler & cinder-volume service in running state.

I've tried to find if there's a path to execute these services in order to revive correctly Cinder. By using the command head -n 10 for c-sch.log and c-vol.log, I've found the anwser to my question.

/usr/local/bin/cinder-volume --config-file /etc/cinder/cinder.conf

&

/usr/local/bin/cinder-scheduler --config-file /etc/cinder/cinder.conf

By using the screen command, I've created two screens by naming them c-sch and c-vol.

1) screen -S c-sch

2) Then execute the services related to as shown below and let the magic operate

3) Ctrl-A + D for being detached from the screen

4) Do the same thing for c-vol

According to their names, I've executed the services related to. Detaching from the screens and executing the command openstack volume service list and I can see that there are now working !

+------------------+-----------------------+------+---------+-------+----------------------------+
| Binary           | Host                  | Zone | Status  | State | Updated At                 |
+------------------+-----------------------+------+---------+-------+----------------------------+
| cinder-scheduler | openstack             | nova | enabled | up    | 2017-04-25T08:49:01.000000 |
| cinder-volume    | openstack@lvmdriver-1 | nova | enabled | up    | 2017-04-25T08:49:01.000000 |
+------------------+-----------------------+------+---------+-------+----------------------------+

I don't know if it's the good way to resolve this issue but now, I can create volumes without doubt and attach them to my instances.