Project

General

Profile

Tâche #17678

Scénario #17455: Traitement express MEN (42-44)

Erreur de démarrage de bastion au reconfigure et au boot sur le module Hâpy

Added by Joël Cuissinat about 3 years ago. Updated about 3 years ago.

Status:
Fermé
Priority:
Normal
Start date:
11/02/2016
Due date:
% Done:

100%

Estimated time:
2.00 h
Spent time:
Remaining (hours):
0.0

Description

Service opennebula is running                                                                                                                                                                               [  OK  ]
Service libvirt-bin is running                                                                                                                                                                              [  OK  ]
Service bastion is not running                                                                                                                                                                              [  KO  ]
Service opennebula-sunstone is running                                                                                                                                                                      [  OK  ]
Service z_stats is running                                                                                                                                                                                  [  OK  ]
root@hapy:~# service bastion status
● bastion.service - Bastion firewall manager
   Loaded: loaded (/lib/systemd/system/bastion.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since mer. 2016-11-02 15:31:44 CET; 45s ago
  Process: 14948 ExecStart=/usr/sbin/bastion start (code=exited, status=1/FAILURE)
 Main PID: 14948 (code=exited, status=1/FAILURE)

nov. 02 15:31:44 hapy systemd[1]: Starting Bastion firewall manager...
nov. 02 15:31:44 hapy bastion[14948]:  * Restauration des règles de pare-feu en cache
nov. 02 15:31:44 hapy bastion[14948]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
nov. 02 15:31:44 hapy bastion[14948]:  * Erreur iptables, vérifiez le noyau Linux utilisé par le serveur
nov. 02 15:31:44 hapy bastion[14948]:    ...fail!
nov. 02 15:31:44 hapy systemd[1]: bastion.service: Main process exited, code=exited, status=1/FAILURE
nov. 02 15:31:44 hapy systemd[1]: Failed to start Bastion firewall manager.
nov. 02 15:31:44 hapy systemd[1]: bastion.service: Unit entered failed state.
nov. 02 15:31:44 hapy systemd[1]: bastion.service: Failed with result 'exit-code'.

Évidemment l'erreur n'est pas systématique :(

J'ai également obtenu l'erreur après un redémarrage et visiblement Jenkins aussi :
http://jenkins.eole.lan/jenkins/job/test-checkinstance-hapy-2.6.0-amd64/lastFailedBuild/console


Related issues

Related to EOLE OpenNebula - Tâche #16848: Erreur au reconfigure Fermé 05/23/2016

Associated revisions

Revision 757295b5 (diff)
Added by Fabrice Barconnière about 3 years ago

Override systemd de libvirt-bin pour démarrer avant bastion

ref #17678 @1h

Revision ef486863 (diff)
Added by Fabrice Barconnière about 3 years ago

Reload de systemd pour la prise en compte de l'override de libbirt-bin

ref #17678 @15m

History

#1 Updated by Joël Cuissinat about 3 years ago

  • Subject changed from Erreur de démarrage de bastion au reconfigure sur un module Hâpy to Erreur de démarrage de bastion au reconfigure et au boot sur le module Hâpy

#2 Updated by Joël Cuissinat about 3 years ago

  • Description updated (diff)

#3 Updated by Joël Cuissinat about 3 years ago

  • Assigned To set to Joël Cuissinat

#4 Updated by Joël Cuissinat about 3 years ago

  • Status changed from Nouveau to En cours

#5 Updated by Joël Cuissinat about 3 years ago

  • Status changed from En cours to Nouveau

#6 Updated by Joël Cuissinat about 3 years ago

  • Assigned To deleted (Joël Cuissinat)

#7 Updated by Fabrice Barconnière about 3 years ago

  • Status changed from Nouveau to En cours
  • % Done changed from 0 to 100
  • Remaining (hours) changed from 2.0 to 0.5

Pas facile à reproduire.
Avec le Before=bastion.service, on s'assure que libvirt-bin est complètement lancé avant de démarrer bastion pour éviter le holding the xtables lock.

#8 Updated by Fabrice Barconnière about 3 years ago

  • Assigned To set to Fabrice Barconnière

#9 Updated by Fabrice Barconnière about 3 years ago

  • Status changed from En cours to Résolu

#10 Updated by Joël Cuissinat about 3 years ago

  • Status changed from Résolu to Fermé
  • Remaining (hours) changed from 0.5 to 0.0

Also available in: Atom PDF