Open tparchambault opened 1 year ago
Datapoint:
pkttyagent registering on the dbus...
pkttyagent registering on the dbus...
pkttyagent registering on the dbus...
pkttyagent registering on the dbus...
pkttyagent registering on the dbus...
^C
Observed the issue again. Checked if there were any audit.log
or journalctl -f
messages during these dbus comm failures. No output messages observed unfortunately.
This ticket is to capture an observed and known issue. The work-around is to send a SIGINT/Ctrl-C to terminate the registration attempts, and immediately attempt to invoke the
fapolicy-analyzer
again. I don't recall seeing two sequential invocation attempts failing.I occasionally see the following
dbus
registration failure. Anecdotally, it has been observed <5% of the time. The issue may just be inherent in the underlyingdbus
implementation or its libraries, however it may be in the fapolicy-analyzer's wrapper script's interaction with the pkexec program and/or our use of the default authentication agent.