On 16 May 2018 at 21:14, Marek Marczykowski-Górecki < [email protected]> wrote:
... this log is from 20:47:38. > > See for earlier log entries. > You are right. I'm stupid. Here's the relevant log. There was indeed an error: May 16 20:44:47 sys-firewall qubes-iptables[417]: iptables: Applying firewall rules: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? May 16 20:44:47 sys-firewall audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-gui-agent comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' May 16 20:44:47 sys-firewall audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=qubes-iptables comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' May 16 20:44:47 sys-firewall qubes-iptables[417]: FAIL May 16 20:44:47 sys-firewall systemd[1]: Started Qubes GUI Agent. May 16 20:44:47 sys-firewall systemd[1]: qubes-iptables.service: Main process exited, code=exited, status=1/FAILURE May 16 20:44:47 sys-firewall systemd[1]: Failed to start Qubes base firewall settings. May 16 20:44:47 sys-firewall systemd[1]: qubes-iptables.service: Unit entered failed state. May 16 20:44:47 sys-firewall systemd[1]: qubes-iptables.service: Failed with result 'exit-code'. Regards, Elias -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/CADtN0W%2B5_%2B666xfxW3QnSECSsC0SS8bgjebegPkVGRObT8XRhA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
