’s servers are going down for a few hours today as developer Bungie performs maintenance and releases a new patch. ET, at which point nobody could sign in if they hadn’t already been playing .At noon ET, Bungie will boot all remaining players out of the game.That has only worked on one AP130 so far - the other 6 are still offline.
In addition to the v1.0.6 patch on all platforms, Bungie will release hotfix 18.104.22.168 on PC.
Also, I have a lot of systems that will not run recon as specified in policies.
I also have logged a support ticket with JAMF as well and due to the nature of the problem being so randmon. We did look at the system log file at the time of the occurance and did note the error message which is May 12 XXXXXX kernel: AFP_VFS afpfs_unmount: /Volumes/Casper Share, flags 0, pid 7486May 12 XXXXXX kernel: ASP_TCP Disconnect: triggering reconnect by bumping reconn Trigger from curr value 0 on so 0xffffff8013d8eb80May 12 XXXXXX kernel: ASP_TCP Detach: Reply queue not empty?
using version 9.3 I'm seeing the same thing here.
Error running recon: Connection failure: "The host org is not accessible." If it was a network issue I would assume that the package would fail to install as well. I'm not sure, but it's still happening often. What do you get when you try to check the connection to the jss on that machine? I also started seeing quite a lot of errors with clients failing to connect to http distribution points and failing over to afp, which works ok. Error message is: Error running recon: Connection failure: "The request timed out." I also tested a manual recon by ssh-ing in and running "sudo jamf recon -verbose" on a workstation that failed to run a recon after a policy. Finally, I am getting this a lot now: Just to chime in. I'm wondering if the network connection is dropping during recon or maybe the user is unplugging their network cable.