Looking at another occurence, I decided to look further into "There is still an active connection"
May 19 09:50:45 akoblovMbp com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.syspolicyd.195): Failed to bootstrap path: path = /usr/libexec/syspolicyd, error = 108: Invalid path
May 19 09:50:46 akoblovMbp Installer Progress[158]: Setting window alpha values to 1.0
May 19 09:51:17 --- last message repeated 1 time ---
May 19 09:51:34 akoblovMbp loginwindow[213]: There is still an active connection
May 19 09:51:34 akoblovMbp loginwindow[213]: There is still an active connection
May 19 09:51:35 --- last message repeated 1 time ---
May 19 09:51:35 akoblovMbp com.apple.xpc.launchd[1] (com.apple.xpc.launchd.domain.pid.parentalcontrolsd.415): Failed to bootstrap path: path = /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/Resources/parentalcontrolsd, error = 2: No such file or directory
May 19 09:51:35 akoblovMbp Installer Progress[158]: Progress Updated: currentPhase = "loginwindow Boot", phase progress = 50.000, total progress = 98.843
Notice -- 40 seconds delay and "There is still an active connection" in loginwindow
I collected all logs via `sudo log collect --start "2020-05-19 09:50:40" --size 1000m`
Opened system_logs.logarchive and searched for loginwindow process messages. I found following:
213 default 2020-05-19 09:51:34.245866 +0300 loginwindow There is still an active connection
213 default 2020-05-19 09:51:35.610407 +0300 loginwindow -[SessionAgentCom SACBeginLoginTransition:reply:] | Enter, sent by pid: 363, name: SecurityAgent
213 default 2020-05-19 09:51:35.610408 +0300 loginwindow -[SessionAgentCom SACBeginLoginTransition:reply:] | calling to transition code to signal ready
213 default 2020-05-19 09:51:35.610882 +0300 loginwindow -[LoginTransition externalBeginLoginTransition:] | dispatch_sync to main thread for other transition options
213 default 2020-05-19 09:51:35.610882 +0300 loginwindow -[LoginTransition externalBeginLoginTransition:] | Enter. MainThread (should be 0): 0
So, active connection was held by process 363.
I looked for messages for only this PID and found following:
363 default 2020-05-19 09:50:40.619760 +0300 SecurityAgent Network wasn't ready for mobile user "akoblov" autologin. Try again in three seconds.
363 default 2020-05-19 09:50:43.616205 +0300 SecurityAgent Network wasn't ready for mobile user "akoblov" autologin. Try again in three seconds.
363 default 2020-05-19 09:50:46.616436 +0300 SecurityAgent Network wasn't ready for mobile user "akoblov" autologin. Try again in three seconds.
Or, some more details:
272 default 2020-05-19 09:51:33.955746 +0300 mDNSResponder [R796] DNSServiceCreateConnection START PID[363](SecurityAgent)
272 default 2020-05-19 09:51:33.956001 +0300 mDNSResponder [R800] DNSServiceGetAddrInfo(C000D000, 0, 0, <private>) START PID[363](SecurityAgent)
272 default 2020-05-19 09:51:33.980624 +0300 mDNSResponder [R796] DNSServiceCreateConnection STOP PID[363](SecurityAgent)
272 default 2020-05-19 09:51:33.980628 +0300 mDNSResponder [R800] DNSServiceGetAddrInfo(<private>) STOP PID[363](SecurityAgent)
363 default 2020-05-19 09:51:34.616069 +0300 SecurityAgent Network wasn't ready for mobile user "akoblov" autologin. Timeout reached.
Right, the problem has to do that my account is mobile account. Now I wonder how to decrease this timeout or skip the check that SecurityAgent does at all.