[Ventura 13.3.1] System.log spam by AMPDeviceDiscoveryAgent every single minute

Question

DerekLeung Author

Level 1

20 points

[Ventura 13.3.1] System.log spam by AMPDeviceDiscoveryAgent every single minute

I am getting these message every single minute in system.log on Ventura 13.3.1. How to stop these spam?

Apr 21 15:27:45 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:15

Apr 21 15:27:46 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:17

Apr 21 15:27:46 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:17

Apr 21 15:27:46 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:17

Apr 21 15:27:46 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:17

Apr 21 15:27:56 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:19

Apr 21 15:27:56 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:19

Apr 21 15:27:56 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:19

Apr 21 15:27:56 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:19

Apr 21 15:27:58 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:18

Apr 21 15:27:58 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:18

Apr 21 15:27:58 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:18

Apr 21 15:27:58 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:18

Apr 21 15:28:18 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:20

Apr 21 15:28:18 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:20

Apr 21 15:28:18 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:20

Apr 21 15:28:18 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:20

Apr 21 15:28:37 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:21

Apr 21 15:28:37 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:21

Apr 21 15:28:37 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:21

Apr 21 15:28:37 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:21

Apr 21 15:28:39 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:22

Apr 21 15:28:39 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:22

Apr 21 15:28:39 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:22

Apr 21 15:28:39 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:22

Apr 21 15:28:53 myhostname MobileDeviceUpdater[634]: Entered:_AMMuxedDeviceDisconnected, mux-device:23

Apr 21 15:28:53 myhostname MobileDeviceUpdater[634]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:23

Apr 21 15:28:53 myhostname AMPDeviceDiscoveryAgent[663]: Entered:_AMMuxedDeviceDisconnected, mux-device:23

Apr 21 15:28:53 myhostname AMPDeviceDiscoveryAgent[663]: Entered:__thr_AMMuxedDeviceDisconnected, mux-device:23

Posted on Apr 21, 2023 7:30 AM

Reply

Answer 1

Dec 6, 2023 10:54 AM in response to Owl-53

The activity of AMPDevicesAgent is normal and expected.

What is NOT normal and expected is for debug-level logging to flood the system log. The system log doesn't record every event that passes over USB, nor is it recording every Bluetooth device that comes in range, and likewise it shouldn't be recording every mux-device event -- that should be reserved for an AMPDevices debug log.

Up until AMPDevicesAgent, you could normally tell when something unusual was happening on your system by quickly checking the system log for a flood of repeat attempts at some action. But AMPDevicesAgent and AMPDeviceDiscoveryAgent legitimately disconnect from nearby mobile devices, sometimes as often as every two seconds. So the system log is being flooded with hundreds of thousands of disconnect notices that not only drown out any other events being recorded, but get written to disk, later to be archived, pushing all the other system events into the archive along with them, accelerating both the archival and deletion process for useful log events.

Reply

Answer 2

Owl-53

Level 10

102,505 points

Apr 21, 2023 7:42 AM in response to DerekLeung

Has the user connected an iPhone to the computer for the purposes of Backing up the iPhone to the computer ?

It is a Normal, Native Apple Process

AMPDevicesAgent

Here are the basic answers:

AMPDevicesAgent is not 3rd party software and it is not caused by a virus (or malware). Actually it is included with macOS Catalina. Apple introduced this with Catalina so it is new:

(/System/Library/PrivateFrameworks/AMPDevices.framework)

You can check this by going to Activity Monitor, it will show up as an Apple process.
This notification is normal, it is expected behavior and you may enter your password. This should not be a cause for concern. When you enter your password, an unknown third party will not have your sensitive info. if your mac is trusted, you may want to check Always Allow.
This new AMPDevicesAgent is apart of the Frameworks in your Library folder to allow Finder to synchronization and backup with iOS & iPadOS devices. Basically, AMPDevicesAgent is a new device manager. It is used for backing up, restoring and updating your devices.

Reply

[Ventura 13.3.1] System.log spam by AMPDeviceDiscoveryAgent every single minute

Similar questions