© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
I think Jim's idea is a good one. Maybe we can trap the error then run `netstat -lnp` in devstack-gate. This should help us catch whatever process is listening on keystone's port.