[OpenStack-fr] erreur start openstack-nova-compute.service

Sam 2 Jan 22:15:35 UTC 2016

Bonsoir

installation openstack version kilo sur centos 7

Je n'arrive pas à démarrer le service openstack-nova-compute.
Voici l'erreur obtenue lors du démarrage:

[root at srkcomputesrv01 ~]# systemctl start libvirtd.service
openstack-nova-compute.service
Job for openstack-nova-compute.service failed because a timeout was
exceeded. See "systemctl status openstack-nova-compute.service" and
"journalctl -xe" for details.
[root at srkcomputesrv01 ~]#

Voici les infos sur le journalctl:

*[root at srkcomputesrv01 ~]# journalctl -xejanv. 02 22:55:54 srkcomputesrv01
systemd[1]: openstack-nova-compute.service start operation timed out.
Terminating.janv. 02 22:55:54 srkcomputesrv01 systemd[1]: Failed to start
OpenStack Nova Compute Server.-- Subject: L'unité (unit)
openstack-nova-compute.service a échoué-- Defined-By: systemd-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
<http://lists.freedesktop.org/mailman/listinfo/systemd-devel>---- L'unité
(unit) openstack-nova-compute.service a échoué, avec le résultat
failed.janv. 02 22:55:54 srkcomputesrv01 systemd[1]: Unit
openstack-nova-compute.service entered failed state.janv. 02 22:55:54
srkcomputesrv01 systemd[1]: openstack-nova-compute.service failed.janv. 02
22:55:54 srkcomputesrv01 systemd[1]: openstack-nova-compute.service holdoff
time over, scheduling restart.janv. 02 22:55:54 srkcomputesrv01 systemd[1]:
Starting OpenStack Nova Compute Server...-- Subject: L'unité (unit)
openstack-nova-compute.service a commencé à démarrer-- Defined-By:
systemd-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
<http://lists.freedesktop.org/mailman/listinfo/systemd-devel>---- L'unité
(unit) openstack-nova-compute.service a commencé à démarrer.janv. 02
22:55:59 srkcomputesrv01 dhclient[4992]: DHCPDISCOVER on ens20 to
255.255.255.255 port 67 interval 8 (xid=0x7bd9c52)janv. 02 22:56:07
srkcomputesrv01 dhclient[4992]: DHCPDISCOVER on ens20 to 255.255.255.255
port 67 interval 11 (xid=0x7bd9c52)janv. 02 22:56:18 srkcomputesrv01
dhclient[4992]: DHCPDISCOVER on ens20 to 255.255.255.255 port 67 interval
15 (xid=0x7bd9c52)janv. 02 22:56:33 srkcomputesrv01 dhclient[4992]:
DHCPDISCOVER on ens20 to 255.255.255.255 port 67 interval 15
(xid=0x7bd9c52)janv. 02 22:56:36 srkcomputesrv01 NetworkManager[603]:
<warn>  (ens20): DHCPv4 request timed out.janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  (ens20): DHCPv4 state changed unknown ->
timeoutjanv. 02 22:56:36 srkcomputesrv01 NetworkManager[603]: <info>
(ens20): canceled DHCP transaction, DHCP client pid 4992janv. 02 22:56:36
srkcomputesrv01 NetworkManager[603]: <info>  (ens20): DHCPv4 state changed
timeout -> donejanv. 02 22:56:36 srkcomputesrv01 NetworkManager[603]:
<info>  (ens20): device state change: ip-config -> failed (reason
'ip-config-unavailable') [70 120 5]janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <warn>  (ens20): Activation: failed for connection
'Connexion filaire 1'janv. 02 22:56:36 srkcomputesrv01 NetworkManager[603]:
<info>  (ens20): device state change: failed -> disconnected (reason
'none') [120 30 0]janv. 02 22:56:36 srkcomputesrv01 NetworkManager[603]:
<info>  Auto-activating connection 'Connexion filaire 1'.janv. 02 22:56:36
srkcomputesrv01 NetworkManager[603]: <info>  (ens20): Activation: starting
connection 'Connexion filaire 1'
(205d9701-cb36-4590-8207-c1716f4b3ecd)janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  (ens20): device state change: disconnected ->
prepare (reason 'none') [30 40 0]janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  (ens20): device state change: prepare ->
config (reason 'none') [40 50 0]janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  (ens20): device state change: config ->
ip-config (reason 'none') [50 70 0]janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  Activation (ens20) Beginning DHCPv4
transaction (timeout in 45 seconds)janv. 02 22:56:36 srkcomputesrv01
NetworkManager[603]: <info>  dhclient started with pid 5004janv. 02
22:56:36 srkcomputesrv01 dhclient[5004]: DHCPDISCOVER on ens20 to
255.255.255.255 port 67 interval 7 (xid=0x75fa13ae)janv. 02 22:56:37
srkcomputesrv01 ntpd[18666]: Deleting interface #1379 ens20,
fe80::3431:31ff:fe65:6637#123, interface stats: received=0, sent=0,
dropped=0, active_time=88 sejanv. 02 22:56:39 srkcomputesrv01 ntpd[18666]:
Listen normally on 1380 ens20 fe80::3431:31ff:fe65:6637 UDP 123janv. 02
22:56:39 srkcomputesrv01 ntpd[18666]: new interface(s) found: waking up
resolverjanv. 02 22:56:43 srkcomputesrv01 dhclient[5004]: DHCPDISCOVER on
ens20 to 255.255.255.255 port 67 interval 7 (xid=0x75fa13ae)janv. 02
22:56:50 srkcomputesrv01 dhclient[5004]: DHCPDISCOVER on ens20 to
255.255.255.255 port 67 interval 12 (xid=0x75fa13ae)janv. 02 22:57:02
srkcomputesrv01 dhclient[5004]: DHCPDISCOVER on ens20 to 255.255.255.255
port 67 interval 20 (xid=0x75fa13ae)janv. 02 22:57:21 srkcomputesrv01
NetworkManager[603]: <warn>  (ens20): DHCPv4 request timed out.janv. 02
22:57:21 srkcomputesrv01 NetworkManager[603]: <info>  (ens20): DHCPv4 state
changed unknown -> timeoutjanv. 02 22:57:21 srkcomputesrv01
NetworkManager[603]: <info>  (ens20): canceled DHCP transaction, DHCP
client pid 5004janv. 02 22:57:21 srkcomputesrv01 NetworkManager[603]:
<info>  (ens20): DHCPv4 state changed timeout -> donejanv. 02 22:57:21
srkcomputesrv01 NetworkManager[603]: <info>  (ens20): device state change:
ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]janv. 02
22:57:21 srkcomputesrv01 NetworkManager[603]: <info>  Disabling autoconnect
for connection 'Connexion filaire 1'.janv. 02 22:57:21 srkcomputesrv01
NetworkManager[603]: <warn>  (ens20): Activation: failed for connection
'Connexion filaire 1'janv. 02 22:57:21 srkcomputesrv01 NetworkManager[603]:
<info>  (ens20): device state change: failed -> disconnected (reason
'none') [120 30 0]janv. 02 22:57:22 srkcomputesrv01 ntpd[18666]: Deleting
interface #1380 ens20, fe80::3431:31ff:fe65:6637#123, interface stats:
received=0, sent=0, dropped=0, active_time=43 sejanv. 02 22:57:24
srkcomputesrv01 systemd[1]: openstack-nova-compute.service start operation
timed out. Terminating.janv. 02 22:57:24 srkcomputesrv01 systemd[1]: Failed
to start OpenStack Nova Compute Server.-- Subject: L'unité (unit)
openstack-nova-compute.service a échoué-- Defined-By: systemd-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
<http://lists.freedesktop.org/mailman/listinfo/systemd-devel>---- L'unité
(unit) openstack-nova-compute.service a échoué, avec le résultat
failed.janv. 02 22:57:24 srkcomputesrv01 systemd[1]: Unit
openstack-nova-compute.service entered failed state.janv. 02 22:57:24
srkcomputesrv01 systemd[1]: openstack-nova-compute.service failed.janv. 02
22:57:25 srkcomputesrv01 systemd[1]: openstack-nova-compute.service holdoff
time over, scheduling restart.janv. 02 22:57:25 srkcomputesrv01 systemd[1]:
Starting OpenStack Nova Compute Server...-- Subject: L'unité (unit)
openstack-nova-compute.service a commencé à démarrer-- Defined-By:
systemd-- Support:
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
<http://lists.freedesktop.org/mailman/listinfo/systemd-devel>---- L'unité
(unit) openstack-nova-compute.service a commencé à démarrer.lines
1479-1544/1544 (END*)

Auriez-vous une piste svp.
Merci d'avance
-------------- section suivante --------------
Une pièce jointe HTML a été nettoyée...
URL: <http://lists.openstack.org/pipermail/openstack-fr/attachments/20160102/c0287888/attachment.html>