Comments on: Automountd trying to connect to Backups.backupdb

By: James

James — Sat, 23 Oct 2010 08:05:18 +0000

I’ve just added the OpenDns settings to my network and I’m now getting this problem for the first time - must have something to do with them

By: christopher

christopher — Sat, 16 Oct 2010 17:42:44 +0000

also just got this message, so yep, still active. don’t have tm activated and don’t have any external drive connected, although adopted this macpro from a friend so it might be looking for something that used to be there.

it’s definitely frustrating that after two years there’s no more enlightening information about this.

By: Graham Perrin

Graham Perrin — Sun, 05 Sep 2010 20:12:18 +0000

> Either Time Machine is very badly broken, or…

I doubt that.

A DNS provider might gives a false result e.g. as shown at
http://pastebin.ca/1933873 — and less likely, there may be a world-writeable NFS share at the IP address that’s given by the provider — but Time Machine will not backup to that volume unless:

a) you explicitly ask Time Machine to use the volume

b) the person sharing knows the cookie that is normally associated with your backup volume. That’s extremely unlikely.

By: Nigel

Nigel — Sun, 05 Sep 2010 12:50:40 +0000

FWIW, I have a brand new Mac Pro running Snow Leopard 10.6.4. Little Snitch has been reporting this (and I’ve been denying until quit) for the past couiple of days. I don’t see how it can possibly have anything to do with Time Machine…well, unless the “OFF” switch in the Time Machine preferences pane is broken.

It has been over two years since the original blog entry on this “feature” of OS X. It still happens in Snow Leopard. Either Time Machine is very badly broken, or there is something else behind all this.

By: Guest

Guest — Sat, 12 Jun 2010 16:58:40 +0000

Reb: Pretty much any 3rd party Windows filrewall will do what LittleSnitch does and more. I recommend Comodo.

By: Reb

Reb — Sat, 06 Feb 2010 18:18:40 +0000

Thank you LS, for Mac first line defense! And THANK YOU, all poster and supporters of this link!
I have searched in vain for LS equiv. on Windows XP or 7. I love the new PC hardware, and price…
but getting a Windows system is like renting instead of buying, and finding out the landlord is still advertising your address as open house .

LS is doors, latches, and locks, and soundproofing.

Liinks like this are peepholes and keys. I now feel secure again.
Thank you ALL.
Hope you find the metaphor more useful than the space it takes…
Reb

By: Userland User

Userland User — Sat, 30 Jan 2010 12:14:45 +0000

I got this message, too…right after updating to latest Little Snitch; the prior version of Snitch had mysteriously started ‘quitting unexpectedly’ at odd times, but only when I was connected to the Internet. That was spooky. The update to Snitch 2.2.1 seems to have fixed that issue, and as a bonus, enabled Snitch to discover the Automountd attempt, for the very first time.

Also spooky is the additional info in the Snitch window…”User ID 0 root”. To an average non-Unix-wise user like me, it sounds as if my ‘root’ user appears to be trying to do things while I’m actually logged in under my normal admin account.

By: personguy

personguy — Sat, 30 Jan 2010 03:28:41 +0000

running 10.5.7
got the same message from the snitchster.
at around 3am saturday morning jan 30.

never did run time machine. it’s completely off.
but i do have developer tools installed.

By: glennac

glennac — Sat, 05 Dec 2009 21:09:47 +0000

@ Macs R We,

As some of the other comments above have revealed, Time Machine is not the only process that requires the services of automountd. So if you are not using TM then it is likely another process that is initiating automountd.

Actually, according to http://theprimepixel.com/list-of-mac-osx-common-processes …

“automount - Automatically Mounts/Unmounts Network Filesystems based on information provided by AutoFS.”

“autofsd - Runs in the background and waits for network filesystem requests or configuration changes, and when such an event occurs, launches automount to update the mount points.”

So the real culprit might actually be autofsd, not automountd. When this occurs again, it might be worth launching Console to see what autofsd was actually after when it launched automountd.

Cheers!

By: Dougit Design Blog » Blog Archive » Does your Apple notebook hard drive (HDD) ever sound like little mice are playing table tennis inside of it? Or, why your HDD might be pre-programmed for quick failure.

Thu, 03 Dec 2009 07:39:25 +0000

[...] now. I did do one system change, using Little Snitch, I denied allowing an outbound connection by automountd, which was trying to connect “UDP connections to port 111 (sunrpc) of [...]