Unfortunately there's something wrong with my logging configuration. Nova-api
doesn't log anything after it starts up. I've got debug enabled, and
verbose=true. But once it finished binding that last port.. Nothing. I've tried
grabbing the sample logging.conf and using that, but it doesn't get
Hey Folks,
Any idea why 'nova flavor-list' (among other things) would fail with a 503 but
'nova-manage flavor list' succeeds?
bash-4.1$ sudo nova-manage flavor list
Password:
m1.medium: Memory: 4096MB, VCPUS: 2, Root: 10GB, Ephemeral: 40Gb, FlavorID: 3,
Swap: 0MB, RXTX Factor: 1.0
m1.large:
Is there a traceback from nova-api?
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Sorry, forgot to include that:
bash-4.1$ nova —debug image-list
connect: (127.0.0.1, 5000)
send: 'POST /v2.0/tokens HTTP/1.1\r\nHost: 127.0.0.1:5000\r\nAccept-Encoding:
identity\r\nContent-Length: 101\r\ncontent-type: application/json\r\naccept:
application/json\r\nuser-agent:
That's the traceback from novaclient. If you're getting a 503, there's likely
a traceback in the nova-api service logs.
- Chris
On May 9, 2012, at 5:38 PM, James R Penick pen...@yahoo-inc.com wrote:
Sorry, forgot to include that:
bash-4.1$ nova —debug image-list
connect: (127.0.0.1,
5 matches
Mail list logo