• Status New
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System pentium4
  • Severity Low
  • Priority Medium
  • Reported Version
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Arch Linux 32
Opened by Andreas Baumann - 06.11.2020

FS#116 - Race causes iptables not to be ready after startup

Nov 06 08:04:01 eurohp1 systemd[1]: Starting IPv4 Packet Filtering Framework… Nov 06 08:04:01 eurohp1 iptables-restore[287]: Another app is currently holding the xtables lock. Perhap>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Main process exited, code=exited, status=4/NOPERMI>
Nov 06 08:04:01 eurohp1 systemd[1]: iptables.service: Failed with result ‘exit-code’.
Nov 06 08:04:01 eurohp1 systemd[1]: Failed to start IPv4 Packet Filtering Framework.

Works when starting iptables later manually.

This is security relevant as not having a firewall after startup puts the system at risk.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing