openstack-cinder-api failed
Hi guys I tried to start openstack-cinder-api but failed. Please help me to solve this issue. Thank you for your help in advance.
[root@controller1 ~]# cat /etc/centos-release
CentOS Linux release 7.3.1611 (Core)
[root@controller1 ~]# rpm -qa | grep newton
centos-release-openstack-newton-1-1.el7.noarch
[root@controller1 ~]# systemctl start opensack-cinder-api openstack-cinder-scheduler
[root@controller1 ~]# systemctl status openstack-cinder-api
openstack-cinder-api.service - OpenStack Cinder API Server
Loaded: loaded (/usr/lib/systemd/system/openstack-cinder-api.service; disabled; vendor preset: disabled)
Active: active (running) since Sat 2017-02-04 15:53:06 KST; 1ms ago
Main PID: 16352 (systemd)
CGroup: /system.slice/openstack-cinder-api.service
16352 /usr/lib/systemd/systemd --switched-root --system --deserialize 21
Feb 04 15:53:06 controller1.chul.com systemd[1]: openstack-cinder-api.service holdoff time over,...rt.
Feb 04 15:53:06 controller1.chul.com systemd[1]: Started OpenStack Cinder API Server.
[root@controller1 ~]# lsof -i tcp:8776
[root@controller1 ~]# tail -f /var/log/messages
Feb 4 15:54:25 controller1 cinder-api: 2017-02-04 15:54:25.313 16762 WARNING cinder.api [-] The v1 api is deprecated and is not under active development. You should set enable_v1_api=false and enable_v3_api=true in your cinder.conf file.
Feb 4 15:54:25 controller1 kernel: cinder-api[16762]: segfault at 7f414b8eb760 ip 00007f414b8eb760 sp 00007ffca6bc41b8 error 15 in multiarray.so[7f414b8ea000+d000]
Feb 4 15:54:25 controller1 systemd: openstack-cinder-api.service: main process exited, code=killed, status=11/SEGV
Feb 4 15:54:25 controller1 systemd: Unit openstack-cinder-api.service entered failed state.
Feb 4 15:54:25 controller1 systemd: openstack-cinder-api.service failed.
Feb 4 15:54:25 controller1 systemd: openstack-cinder-api.service holdoff time over, scheduling restart.
Feb 4 15:54:25 controller1 systemd: Started OpenStack Cinder API Server.
Feb 4 15:54:25 controller1 systemd: Starting OpenStack Cinder API Server...
Feb 4 15:54:25 controller1 cinder-scheduler: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT".
Feb 4 15:54:25 controller1 cinder-scheduler: 2017-02-04 15:54:25.817 16764 WARNING oslo_reports.guru_meditation_report [-] Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
Feb 4 15:54:26 controller1 kernel: cinder-schedule[16764]: segfault at 7f749a4ba760 ip 00007f749a4ba760 sp 00007fffb21e1168 error 15 in multiarray.so[7f749a4b9000+d000]
Feb 4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service: main process exited, code=killed, status=11/SEGV
Feb 4 15:54:26 controller1 systemd: Unit openstack-cinder-scheduler.service entered failed state.
Feb 4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service failed.
Feb 4 15:54:26 controller1 systemd: openstack-cinder-scheduler.service holdoff time over, scheduling restart.
Feb 4 15:54:26 controller1 systemd: Started OpenStack Cinder Scheduler Server.
Feb 4 15:54:26 controller1 systemd: Starting OpenStack Cinder Scheduler Server...
[root@controller1 ~]# cinder service-list
ERROR: Unable to establish connection to http://192.168.80.3:8776/v2/ba40e0d269db49fda3ab07438f36e1da/os-services (http://192.168.80.3:8776/v2/ba40e0d26...): HTTPConnectionPool(host='192.168.80.3', port=8776): Max retries exceeded with url: /v2/ba40e0d269db49fda3ab07438f36e1da/os-services (Caused by NewConnectionError ...
Any clues in the cinder-scheduler log file?
Looking at the last lines of your messages file, I also wonder if the scheduler runs after all. What's the output of cinder service-list?
Bernd thank you for your comment. This is the process I configured for openstack-cinder-api
[root@controller1 ~]# cinder service-list
ERROR: Unable to establish connection to http://192.168.80.3:8776/v2/ba40e0d269db49fda3ab07438f36e1da/os-services (http://192.168.80.3:8776/v2/ba40e0d26...): HTTPConnectionPool(host='192.168.80.3', port=8776): Max retries exceeded with url: /v2/ba40e0d269db49fda3ab07438f36e1da/os-services (Caused by
However I could not find any error messages from /var/log/cinder/api.log and scheduler.log
Well, connection is refused because Cinder API isn't running. The messages in the syslog are probably repeated because systemd tries to restart the processes.
To me this smells like some incompatibility between Cinder and other software on the system, but I don't have enough insight to help.