cinder-volume status becomes inactive after few seconds automatically after restart

asked 2016-11-11 03:11:42 -0600

basant gravatar image

updated 2016-11-23 12:42:28 -0600

rbowen gravatar image
 root@cinder:~# service cinder-volume start
root@cinder:~# service cinder-volume status

cinder-volume.service - OpenStack Cinder Volume
   Loaded: loaded (/lib/systemd/system/cinder-volume.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2016-11-11 14:36:21 IST; 583ms ago
  Process: 12961 ExecStartPre=/bin/chown cinder:adm /var/log/cinder (code=exited, status=0/SUCCESS)
  Process: 12957 ExecStartPre=/bin/chown cinder:cinder /var/lock/cinder /var/lib/cinder (code=exited, status=0/SUCCESS)
  Process: 12953 ExecStartPre=/bin/mkdir -p /var/lock/cinder /var/log/cinder /var/lib/cinder (code=exited, status=0/SUCCESS)
 Main PID: 12965 (cinder-volume)
    Tasks: 1
   Memory: 86.0M
      CPU: 584ms
   CGroup: /system.slice/cinder-volume.service
           └─12965 /usr/bin/python /usr/bin/cinder-volume --config-file=/etc/cinder/cinder.conf --log-file=/var/log/cinder/cinder-volume.log

Nov 11 14:36:21 cinder systemd[1]: Starting OpenStack Cinder Volume...
Nov 11 14:36:21 cinder systemd[1]: Started OpenStack Cinder Volume.
root@cinder:~# service cinder-volume status

cinder-volume.service - OpenStack Cinder Volume
   Loaded: loaded (/lib/systemd/system/cinder-volume.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Fri 2016-11-11 14:36:26 IST; 5s ago
  Process: 13048 ExecStart=/etc/init.d/cinder-volume systemd-start (code=exited, status=1/FAILURE)
  Process: 13044 ExecStartPre=/bin/chown cinder:adm /var/log/cinder (code=exited, status=0/SUCCESS)
  Process: 13040 ExecStartPre=/bin/chown cinder:cinder /var/lock/cinder /var/lib/cinder (code=exited, status=0/SUCCESS)
  Process: 13037 ExecStartPre=/bin/mkdir -p /var/lock/cinder /var/log/cinder /var/lib/cinder (code=exited, status=0/SUCCESS)
 Main PID: 13048 (code=exited, status=1/FAILURE)

Nov 11 14:36:26 cinder systemd[1]: cinder-volume.service: Unit entered failed state.
Nov 11 14:36:26 cinder systemd[1]: cinder-volume.service: Failed with result 'exit-code'.
Nov 11 14:36:26 cinder systemd[1]: cinder-volume.service: Service hold-off time over, scheduling restart.
Nov 11 14:36:26 cinder systemd[1]: Stopped OpenStack Cinder Volume.
Nov 11 14:36:26 cinder systemd[1]: cinder-volume.service: Start request repeated too quickly.
Nov 11 14:36:26 cinder systemd[1]: Failed to start OpenStack Cinder Volume.

Does anyone has any solution . Feel free to ask extra information . the service becoming inactive after few seconds . The configuration files looks OK to me .

The cinder-volume.log contains

root@cinder:/var/log/cinder# tail -f cinder-volume.log.1 
2016-11-09 12:30:35.642 20314 INFO cinder.service [-] Starting cinder-volume node (version 9.0.0)
2016-11-09 12:30:35.659 20314 INFO cinder.coordination [-] Coordination backend started successfully.
2016-11-09 12:30:35.659 20314 INFO cinder.volume.manager [req-a752f63e-611a-4f23-97d6-e4190653f820 - - - - -] Starting volume driver LVMVolumeDriver (3.0.0)
2016-11-09 12:30:38.321 20314 INFO cinder.volume.manager [req-a752f63e-611a-4f23-97d6-e4190653f820 - - - - -] Driver initialization completed successfully.
2016-11-09 12:30:38.347 20314 INFO cinder.volume.manager [req-a752f63e-611a-4f23-97d6-e4190653f820 - - - - -] Initializing RPC dependent components of volume driver LVMVolumeDriver (3.0.0)
2016-11-09 12:30:38.978 20314 INFO cinder.volume.manager [req-a752f63e-611a-4f23-97d6-e4190653f820 - - - - -] Driver post RPC initialization completed successfully.
2016-11-09 18:59:03.389 20314 WARNING oslo.service.loopingcall [req-12ed5e68-048d-45f1-b7c2-af6d48b3e2d4 - - - - -] Function 'cinder.service.Service.report_state' run ...
(more)
edit retag flag offensive close merge delete

Comments

check the cinder-volume.log for error messages.

Bernd Bausch gravatar imageBernd Bausch ( 2016-11-11 09:19:37 -0600 )edit