Scénario #30686
Bastion régulièrement en erreur après un reconfigure sur Scribe 2.8.0
Status:
Terminé (Sprint)
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
09/22/2020
Due date:
10/16/2020
% Done:
100%
Story points:
2.0
Remaining (hours):
0.00 hour
Velocity based estimate:
Release:
Release relationship:
Auto
Description
Sur aca.scribe, le problème se produit au moins une fois sur deux.
root@scribe:~# systemctl status bastion
● bastion.service - Bastion firewall manager
Loaded: loaded (/lib/systemd/system/bastion.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-09-22 11:02:46 CEST; 2min 35s ago
Main PID: 489054 (code=exited, status=1/FAILURE)
sept. 22 11:02:46 scribe systemd[1]: Starting Bastion firewall manager...
sept. 22 11:02:46 scribe bastion[489054]: * Restauration des règles de pare-feu en cache
sept. 22 11:02:46 scribe bastion[489088]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?
sept. 22 11:02:46 scribe bastion[489054]: * Erreur iptables, vérifiez le noyau Linux utilisé par le serveur
sept. 22 11:02:46 scribe bastion[489054]: ...fail!
sept. 22 11:02:46 scribe systemd[1]: bastion.service: Main process exited, code=exited, status=1/FAILURE
sept. 22 11:02:46 scribe systemd[1]: bastion.service: Failed with result 'exit-code'.
sept. 22 11:02:46 scribe systemd[1]: Failed to start Bastion firewall manager.
Subtasks
Related issues
History
#1 Updated by Benjamin Bohard over 2 years ago
- Assigned To set to Emmanuel GARETTE
#2 Updated by Joël Cuissinat over 2 years ago
- Related to Tâche #30795: Validation du scénario Bastion régulièrement en erreur après un reconfigure sur Scribe 2.8.0 added
#3 Updated by Joël Cuissinat over 2 years ago
- Status changed from Nouveau to Terminé (Sprint)