Weird System Log Error

Question

Level 1

0 points

Weird System Log Error

Hi,

I keep getting the following message in my system log every minute or so:

Oct 16 15:28:33 Athena com.apple.usbmuxd[34]: _SendDetachNotification (thread 0x7fff79a85960): sending detach for device cc:08:e0:f6:98:cd@fe80::ce08:e0ff:fef6:98cd._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.

Oct 16 15:28:56 Athena com.apple.usbmuxd[34]: _SendAttachNotification (thread 0x7fff79a85960): sending attach for device cc:08:e0:f6:98:cd@fe80::ce08:e0ff:fef6:98cd._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.

Anyone have any ideas on what's causing this? Thanks!

Posted on Oct 16, 2011 3:38 PM

Reply

Answer 1

Best reply

qap

Level 1

23 points

Oct 16, 2011 5:32 PM in response to alphaace

Oh I'm just asking myself the same... after the 10.7.2 and iOS 5 update I see the same infinite logs but:

alphaace wrote:

...

Anyone have any ideas on what's causing this? Thanks!

...yes, I've get these logs too when my iPhone is in the same network with wifi on! They go away if I don't set the "Sync iPhone via WiFi" in iTunes! Infact the cc:08ecc.. is the iPhone MAC address, it's very annoying, I also think that this thing (I don't know what is, maybe a call by the mac to the phone to know if the iPhone is still wifi connected) could drain the iPhone battery!

Reply

Answer 2

qap

Level 1

23 points

Oct 16, 2011 5:42 PM in response to qap

Oh and if I turn off the WIFI in the iPhone immediatly after I see these logs and after no others weird logs:

17/10/11 02:36:10,691 com.apple.usbmuxd: _SendAttachNotification (thread 0x7fff73842960): sending attach for device 14:8f:c6:0f:9e:ec@fe80::168f:c6ff:fe0f:9eec._apple-mobdev._tcp.local.: _GetAddrInfoReplyReceivedCallback matched.

17/10/11 02:36:10,900 usbmuxd: _AMDeviceConnectByAddressAndPort (thread 0x100797000): IPv4

17/10/11 02:36:41,104 com.apple.usbmuxd: _handle_timer Fish out of water!!!

17/10/11 02:36:48,060 com.apple.usbmuxd: _SendDetachNotification (thread 0x7fff73842960): sending detach for device 14:8f:c6:0f:9e:ec@fe80::168f:c6ff:fe0f:9eec._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.

17/10/11 02:36:48,060 com.apple.usbmuxd: networkDeviceCallback Surprisingly, there is no mie matching name

Fish out of water!!! -> What??? 😁 Maybe "iPhone out of network"? 😁

Reply

Answer 3

alphaace Author

Level 1

0 points

Oct 16, 2011 6:04 PM in response to qap

Ah, much better. At least I know something funky is going on with my hardware. Many thanks!

Reply

Answer 4

Aamchi

Level 1

0 points

Nov 4, 2011 6:49 AM in response to alphaace

Some log entries here too. Did any of you find a solution yet?

Reply

Answer 5

alphaace Author

Level 1

0 points

Nov 4, 2011 2:39 PM in response to Aamchi

See the answer I marked as correct. If you disable wireless syncing, that log entry should go away. Basically it's checking if the phone is nearby.

Reply

Answer 6

mburstin

Level 1

4 points

Nov 8, 2011 6:06 AM in response to alphaace

I don't know that that really is a "solution". Its is saying to disable a useful feature to prevent syslog from getting blasted by errors. I think its an Apple bug.

Reply

Answer 7

abross86

Level 1

20 points

Dec 6, 2011 6:28 AM in response to alphaace

I'm having this problem too on a 4S. Even worse, it persists even after I've completely disabled wifi sync in itunes. I'm seeing these same error logs running 10.6.8 on another computer. Could this be the source of some of the ios5 battery woes?

FYI, even after turning off wifi on the iphone I'm getting this console error several times/minute:

12/6/11 9:27:05 AM com.apple.usbmuxd[33] _SendDetachNotification (thread 0x7fff70bcecc0): sending detach for device 5c:59:48:1b:7d:9e@fe80::5e59:48ff:fe1b:7d9e._apple-mobdev._tcp.local.: _BrowseReplyReceivedCallback got bonjour removal.

Reply

Answer 8

yu123

Level 1

0 points

Dec 19, 2011 1:27 AM in response to alphaace

I have the same issue. I didn't think it is due to the wireless sync, so thanks for the folks on this thread. And as @mburstin said, I want another better solution for that not to kill the useful feature.

Also what really bother me is that it tries to make display to the screen-saver mode whenever, even when I'm working on it. I suspect it has something to do with this issue. Does anyone have any idea for that?

Reply