Giving another shot - I saw that the shell prompt shows the localhost
name. Could you try setting a proper hostname (hostname -f returns a
fqdn) and retry?
On Fri, Jan 15, 2016 at 1:48 PM, Javier Pena <
javier.pena@redhat.com> wrote:
> ----- Original Message -----
>
>> Hello Javier,
>
>> Okay, I did what you said. This took some fumbling around. There are 7 files.
>> The two biggest are 13k and 12k , the others are 4k and below. Hope they
>> aren't too big!
>
>> == 1> nova-api.log:=============================
>
> [...snip...]
>
>> c73d477ea608499eb117fb79b28bff80 - - -] Option "sql_connection" from group
>> "DEFAULT" is deprecated. Use option "connection" from group "database".
>> 2016-01-14 14:26:44.407 6099 INFO nova.api.openstack.wsgi
>> [req-fdc4d3ba-9f6b-4b98-85f9-51dfeb5dca84 c2114578a647492c985508e88c06f24b
>> c73d477ea608499eb117fb79b28bff80 - - -] HTTP exception thrown: Keypair data
>> is invalid: failed to generate fingerprint
>> 2016-01-14 14:26:44.408 6099 INFO nova.osapi_compute.wsgi.server
>> [req-fdc4d3ba-9f6b-4b98-85f9-51dfeb5dca84 c2114578a647492c985508e88c06f24b
>> c73d477ea608499eb117fb79b28bff80 - - -] 192.168.1.12 "POST
>> /v2/c73d477ea608499eb117fb79b28bff80/os-keypairs HTTP/1.1" status: 400 len:
>> 319 time: 3.4419072
>
> So this is all the Nova logs show, it is just complaining that the keypair data is not valid.
>
> While we try to get some other ideas, does dmesg show any application segfaulting?
>
> Javier
>
> [... all other logs, snipping ...]
the log issue, let's try this: