Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

at last I found the solution..

cinder RuntimeError: Could not bind to 0.0.0.0:8776 after trying for 30 seconds

the above error is due to the fact that another cinder api process is running in the cluster and you need to kill that mannually.. use netstat to check whether another process is running with port 8776. And kill that process and restart cinder service will solve this issue

netstat -tupln | grep 8776 // identify the proc-id
kill -9 proc-id  // proc-id using 8776

Then the next error

Stderr: u'iscsiadm: No session found.\n'

For me this error was caused by the miss configuration someone did with my management IP's in the cinder /etc/cinder/cinder.conf file in controller node.. I changed that to my proper management IP and now I can attach volumes..

my_ip = your proper management IP

at last I found the solution..

cinder RuntimeError: Could not bind to 0.0.0.0:8776 after trying for 30 seconds

the above error is due to the fact that another cinder api process is running in the cluster with port 8776 and you need to kill that mannually.. use netstat to check whether another process is running with port 8776. And kill that process and restart cinder service will solve this issue

netstat -tupln | grep 8776 // identify the proc-id
kill -9 proc-id  // proc-id using 8776

Then the next error

Stderr: u'iscsiadm: No session found.\n'

For me this error was caused by the miss configuration someone did with my management IP's in the cinder /etc/cinder/cinder.conf file in controller node.. I changed that to my proper management IP and now I can attach volumes..

my_ip = your proper management IP