Tâche #26137
Scénario #26198: Traitement express MEN (50-51)
Horus 2.7.0 : erreur au reconfigure sur bastion
Status:
Ne sera pas résolu
Priority:
Normal
Assigned To:
Target version:
Remaining (hours):
0.0
Description
root@horus:~# systemctl status bastion.service ● bastion.service - Bastion firewall manager Loaded: loaded (/lib/systemd/system/bastion.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2018-12-05 11:56:45 CET; 1min 34s ago Process: 7755 ExecStopPost=/bin/rm -rf /var/lock/bastion (code=exited, status=0/SUCCESS) Process: 7699 ExecStart=/usr/sbin/bastion start --systemd (code=exited, status=1/FAILURE) Main PID: 7699 (code=exited, status=1/FAILURE) déc. 05 11:56:45 horus systemd[1]: Starting Bastion firewall manager... déc. 05 11:56:45 horus bastion[7699]: * Restauration des règles de pare-feu en cache déc. 05 11:56:45 horus bastion[7699]: iptables-restore: line 8 failed déc. 05 11:56:45 horus bastion[7699]: ...fail! déc. 05 11:56:45 horus systemd[1]: bastion.service: Main process exited, code=exited, status=1/FAILURE déc. 05 11:56:45 horus systemd[1]: bastion.service: Failed with result 'exit-code'. déc. 05 11:56:45 horus systemd[1]: Failed to start Bastion firewall manager.
History
#1 Updated by Scrum Master over 2 years ago
- Parent task changed from #25625 to #26198
#2 Updated by Fabrice Barconnière over 2 years ago
- Status changed from Nouveau to En cours
#3 Updated by Fabrice Barconnière over 2 years ago
- Assigned To set to Fabrice Barconnière
#4 Updated by Fabrice Barconnière over 2 years ago
- Status changed from En cours to Ne sera pas résolu
- Remaining (hours) changed from 3.0 to 0.0
Je ne reproduis pas cette situation.
J'ai du me trouver dans une faille temporelle :/