Distribution EOLE

<pre>
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 ]
</pre>

<pre>
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'.
</pre>

É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