Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

VitoBotta

macrumors 65816
Original poster
Dec 2, 2020
1,020
414
Espoo, Finland
Arq backup is failing for me when trying to access ~/Library/Daemon Containers/F68D34A1-3EBA-4C03-B7FD-27B10C2BADE6/Data/com.apple.milod/milo.db-wal.

The weird thing is that Arq has full disk access and that this happens only when the computer is locked with a black screen.

What is milod? I can't find it with Google and also Llama3, Claude Sonnet 3.5 and GPT-4o all give different answers that seem the result of hallucinations.

Can you please check if you have the file milo.db-wal in the same or similar location? I am wondering if it's something new in Sequoia.

Thanks!
 
I forgot to mention that I tried to open the database with sqlite3 and it doesn't allow me due to permissions even if I do it with sudo.
 
With mdfind I found this

/Library/Developer/CommandLineTools/SDKs/MacOSX15.0.sdk/usr/share/man/man8/milod.8

So perhaps it's something to do with the command line tools but not sure if it's just a coincidence
 
Carbon Copy Cloner doesn't fail but logs this

CCE_IVGR| 06/26 18:36:12 DEBUG: SIP prevented access to /private/tmp/16777233@240626183029/Users/vito/Library/Daemon Containers/F68D34A1-3EBA-4C03-B7FD-27B10C2BADE6/Data/com.apple.milod/milo.db-wal
CCE_SIGL| 06/26 18:36:12 🔸 Failed to open source file for reading: /private/tmp/16777233@240626183029/Users/vito/Library/Daemon Containers/F68D34A1-3EBA-4C03-B7FD-27B10C2BADE6/Data/com.apple.milod/milo.db-wal (1)

Why is SIP preventing access to this file?
 
Yes, I have the com.apple.milod folder in similar location. There is also a milod process running in Activity Monitor.
15.0-beta (24A5279h)
 
Yes, I have the com.apple.milod folder in similar location. There is also a milod process running in Activity Monitor.
15.0-beta (24A5279h)
Any idea of what it might be? It's weird that it only causes problems when the computer is locked
 
Maybee the process writes to the file when the computer is locked? I don´t know anything about programming, but you can open the file with a text editor and get some random keywords:

ULRapportMO ULOdometryMO ULModelMO ULMeasurementMO ULLoiMO< ULLoggedEventMO ULLabelMO ULHomeSlamAnalyticEventMO ULCustomLoiMO ULConfigurationMO ULBluetoothIdentityMO ULAssociatedStateMO

So connect the dots... A totally uneducated guess - something bluetooth with a motion sensor?
Maybe so the new head gestures for AirPods Pro will let you answer an incoming FaceTime call by nodding your head?
 
No idea, but I'm glad it's not just on my mac as I was starting to wonder if I had some kind of malware or something. Thanks for checking!
 
Going into Console and filtering by process:milod, looks like it’s related to Bluetooth and micro-location (“milod" is probably “micro-location daemon"). This entry seems to be my HomePod:

Code:
CBDiscovery    CLMiLoLeeching: Device found: CBDevice XXXXXXXXX-E040-5716-550B-XXXXXXXXX, BDA XXXXXXXXX, Nm 'Living Room', Md AudioAccessory1,1, IDS XXXXXXXXX-130D-43F0-898A-XXXXXXXXX, AcID XXXXXXXXXXX@icloud.com, stID CC830B4F-130D-43F0-898A-XXXXXXXXX, DsFl 0x80040 < NearbyInfo NearbyAction >, DvF 0x40000000300 < Family SharedHome Connectable >, RSSI -55, Ch 37, AdTsMC <XXXXXXXXX>, AMfD <4c 00 0f 05 90 00 c5 31 f2 10 02 03 04>, nbAF 0x90 < DeviceClose HasAuthTag >, nbIF 0x100 < WiFiP2P >, CF 0x80200000000 < RSSI Attributes >    milod    com.apple.bluetooth
 
  • Like
Reactions: IngoX
Going into Console and filtering by process:milod, looks like it’s related to Bluetooth and micro-location (“milod" is probably “micro-location daemon"). This entry seems to be my HomePod:

Code:
CBDiscovery    CLMiLoLeeching: Device found: CBDevice XXXXXXXXX-E040-5716-550B-XXXXXXXXX, BDA XXXXXXXXX, Nm 'Living Room', Md AudioAccessory1,1, IDS XXXXXXXXX-130D-43F0-898A-XXXXXXXXX, AcID XXXXXXXXXXX@icloud.com, stID CC830B4F-130D-43F0-898A-XXXXXXXXX, DsFl 0x80040 < NearbyInfo NearbyAction >, DvF 0x40000000300 < Family SharedHome Connectable >, RSSI -55, Ch 37, AdTsMC <XXXXXXXXX>, AMfD <4c 00 0f 05 90 00 c5 31 f2 10 02 03 04>, nbAF 0x90 < DeviceClose HasAuthTag >, nbIF 0x100 < WiFiP2P >, CF 0x80200000000 < RSSI Attributes >    milod    com.apple.bluetooth

Thanks! I didn't think to check the console. I wonder why it's causing problems when the computer is locked if it's something related to BlueTooth. Super weird.
 
I can not add anything but a "same here". MacOS 15.0.1 (24A348) and Arq Version 7.33.1.
 
I'm having this same issue ever since getting a new Bluetooth keyboard.

Did they offer a solution, or you just added it to wildcard exclusions?
 
I think I found the solution to this problem. I went to System Settings -> Privacy & Security -> Full Disk Access and added TimeMachine.app. That seems to have solved it for me.
 
I think I found the solution to this problem. I went to System Settings -> Privacy & Security -> Full Disk Access and added TimeMachine.app. That seems to have solved it for me.
This appeared to have fixed my issue at first, but it did not. When I find the solution, I will post it here.
 
This appeared to have fixed my issue at first, but it did not. When I find the solution, I will post it here.

I fixed this just by adding com.apple.milod as an exclusion. Have not had the issue since doing that last year.
 
Last edited:
I fixed this just by adding com.apple.milod as an exclusion. Have not had the issue since doing that last year.
Yes. Thank you. This is the correct solution. It worked great for me as well. For those of you that don't know how to do this, here are the instructions:

1. The Terminal app will need full disk access in order to do the "tmutil addexclusion -p" command, so add the following entry to System Settings -> Privacy & Security -> Full Disk Access:

/Applications/Utilities/Terminal.app

2. Use this command to get the error messages from Time Machine:

log show --info --style compact --predicate '(subsystem == "com.apple.TimeMachine") && (eventMessage like[cd] "Failed * acquire device lock assertion*")' --last 24h

Example Output:

2025-07-29 00:06:02.716 E backupd[302:1e0295] [com.apple.TimeMachine:FileProtection] Failed to acquire device lock assertion for '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Mac mini/2025-07-29-000400/Data/Users/admin/Library/Daemon Containers/98A60FC5-070E-445D-AA12-296B81A11662/Data/com.apple.milod/milo.db-wal' (assertion state: <dropped>), error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"
2025-07-29 00:06:02.717 E backupd[302:1e0295] [com.apple.TimeMachine:FileProtection] Failed to acquire device lock assertion for '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/Mac mini/2025-07-29-000400/Data/Users/admin/Library/Daemon Containers/98A60FC5-070E-445D-AA12-296B81A11662/Data/com.apple.milod/milo.db-shm' (assertion state: <dropped>), error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted"

3. Using the paths in the error messages, add a Time Machine exclusion for the path to the com.apple.milod directory:

In my case, the command would be as follows (don't forget the \ before the space in Daemon Containers):

sudo tmutil addexclusion -p /Users/admin/Library/Daemon\ Containers/98A60FC5-070E-445D-AA12-296B81A11662/Data/com.apple.milod

You should see the exclusion by going to System Settings -> General -> Time Machine and clicking on the Options button.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.