Re: Itunes not responding

2013-10-17 Thread Neil Houghton 
Hi Ronni,

Thanks for your continued interest.

> I would say the connection between iOS devices and iTunes on the Host gets
> dropped.

Well, the messages that you highlighted, just before usbmuxd crashes, are
all generated AFTER I quit iTunes ­ so I suppose they are generated during
the process of iTunes shutting down - when I would expect the host to drop
the connection anyway.

I tend to think that the messages during iTunes start up are due to some
problem (maybe usbmuxd crashing out earlier?). Then everything seems to work
OK - then, on iTunes shutdown, the problem prevents a graceful shutdown and
usbmuxd crashes.

Well, that¹s just me thinking out loud, really ;o)


Happy to hear your thoughts at anytime ­ certainly no sense of urgency here.


Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com




on 17/10/13 20:56, Ronda Brown at ro...@mac.com wrote:

> Hi Neil,
> 
> I have been busy with clients work all day, have just found time to go through
> your logs again.
> 
> I would say the connection between iOS devices and iTunes on the Host gets
> dropped.
> Your Console gives the following messages just before the usbmuxd crashed
> 
>>> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Parent: Error
>>> or timeout on select
>>> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Child with pid
>>> 3135 exited normally
>>> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]
>>> ATHostConnectionDestroy 0x2dd18e0
>>> 16/10/13 19:36:28[0x0-0x229229].com.apple.iTunes[3130]AppleGVA::
>>> Error creating the accelerator 1
>>> 16/10/13 19:36:47com.apple.usbmuxd[1137]_heartbeat_failed heartbeat
>>> detected detach for device 0x1-192.168.2.101:0!
>>> 16/10/13 19:36:48com.apple.launchd[1](com.apple.usbmuxd[1137]) Job
>>> appears to have crashed: Segmentation fault
> 
> Have you experienced Wi-Fi Network dropouts or slowdowns at other times?
> 
> I will be rather busy with clients work for the next couple of days, but will
> get back to you when possible.
> 
> Cheers,
> Ronni
> 
> Sent from Ronni's iPad4
> 
> On 16 Oct 2013, at 7:51 pm, Neil Houghton  wrote:
> 
>> Re: Itunes not responding Hi Ronni,
>> 
>> Replies against your questions in message body.
>> 
>> 
>> on 16/10/13 16:54, Ronni Brown at ro...@mac.com wrote:
>> 
>>> Hi Neil,
>>> 
>>>> So something else is the culprit :o((
>>> 
>>> Well, certainly something is not right on your System.
>>> iTunes uses usbmuxd for Wi-Fi syncing with iOS devices.
>>> NONE of the Console messages I have marked below in Bold Red should be
>>> displaying.
>>> 
>>> Today I connected my iPhone 4S via USB to iTunes and set up "Sync with this
>>> iPhone over Wi-Fi"
>>> Then disconnected my iPhone cable from the USB port (don't eject it) - and
>>> as it should, iPhone remains in the Devices section of the iTunes sidebar,
>>> even though I have disconnected it from my computer.
>>> 
>>> I then carried out the testing below to see if I could replica any of the
>>> messages you are receiving in Console.
>>> The messages below are the messages you should see in Console.
>>> 
>>> 1. Console messages after Opening iTunes:
>>> 
>>> 16/10/13 1:54:29.504 PM com.apple.usbmuxd[29]:
>>> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,9bc6086f
>>> 16/10/13 1:54:31.991 PM com.apple.usbmuxd[29]: _SendAttachNotification
>>> Device 
>>> d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has
>>> already appeared on interface 5. Suppressing duplicate attach notification.
>>> 
>>> 2. Console Messages after connecting iPhone to Power & iPhone automatically
>>> Wi-Fi syncs with iTunes:
>>> 
>>> 16/10/13 1:59:29.657 PM com.apple.usbmuxd[29]: _SendAttachNotification
>>> Device 
>>> d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has
>>> already appeared on interface 5. Suppressing duplicate attach notification.
>>> 16/10/13 1:59:37.382 PM AppleMobileBackup[20566]: WARNING: Backing up
>>> dccc21a42cf2895823a057ab1f251e0946cd4dd3
>>> 
>>> 3. Console Messages after instigating a Wi-Fi sync (Settings > General >
>>> iTunes Wi-Fi Sync - ŒSync Now¹ ) on iPhone 4S connected to the same Network:
>>> 
>>> 16/10/13 4:01:28.701 PM com.apple.usbmuxd[29]: _SendAttachNotification
>>> Device 
>>> d0:23:db:4f:78:

Re: Itunes not responding

2013-10-17 Thread Ronda Brown 
otification 
> Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev2._tcp.local. 
> has already appeared on interface 6. Suppressing duplicate attach 
> notification.
> 16/10/13 19:35:02AppleMobileBackup[3159]WARNING: Backing up 
> 7dad31d8e20f065f00208be5e663327caed867da
> 16/10/13 19:35:02[0x0-0x229229].com.apple.iTunes[3130]2013-10-16 
> 19:35:02.583 AppleMobileBackup[3159:903] WARNING: Backing up 
> 7dad31d8e20f065f00208be5e663327caed867da
> 16/10/13 19:35:07/Applications/iTunes.app/Contents/MacOS/iTunes[3130]
> Entered:_AMMuxedDeviceDisconnected, mux-device:4
> 16/10/13 19:35:07AppleMobileBackup[3159]INFO: Device detached 
> 0x103001860/ff25d9ca613360738970fe008e8e63a02c535aab
> 16/10/13 19:35:07/Applications/iTunes.app/Contents/MacOS/iTunes[3130]
> Entered:__thr_AMMuxedDeviceDisconnected, mux-device:4
> 16/10/13 19:35:07[0x0-0x229229].com.apple.iTunes[3130]2013-10-16 
> 19:35:07.919 AppleMobileBackup[3159:903] INFO: Device detached 
> 0x103001860/ff25d9ca613360738970fe008e8e63a02c535aab
> 16/10/13 19:35:07/Applications/iTunes.app/Contents/MacOS/iTunes[3130]
> tid:14f23 - Mux ID not found in mapping dictionary
> 16/10/13 19:35:07/Applications/iTunes.app/Contents/MacOS/iTunes[3130]
> tid:14f23 - Can't handle disconnect with invalid ecid
> 16/10/13 19:35:53iTunes[3130]AMDeviceSecureTransferPath (thread 
> 0xb0631000): disableDelta: FALSE
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Parent: Error 
> or timeout on select
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Child with pid 
> 3134 exited normally
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]
> ATHostConnectionDestroy 0x2d83cc0
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Parent: Error 
> or timeout on select
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Child with pid 
> 3135 exited normally
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]
> ATHostConnectionDestroy 0x2dd18e0
> 16/10/13 19:36:28[0x0-0x229229].com.apple.iTunes[3130]AppleGVA:: 
> Error creating the accelerator 1
> 16/10/13 19:36:47com.apple.usbmuxd[1137]_heartbeat_failed heartbeat 
> detected detach for device 0x1-192.168.2.101:0!
> 16/10/13 19:36:48com.apple.launchd[1](com.apple.usbmuxd[1137]) Job 
> appears to have crashed: Segmentation fault
> 16/10/13 19:36:48com.apple.usbmuxd[3163]usbmuxd-323 on Jul 29 2013 at 
> 23:21:29, running 64 bit
> 16/10/13 19:36:48com.apple.ReportCrash.Root[3162]2013-10-16 
> 19:36:48.072 ReportCrash[3162:2903] Saved crash report for usbmuxd[1137] 
> version ??? (???) to 
> /Library/Logs/DiagnosticReports/usbmuxd_2013-10-16-193648_localhost.crash
> ---
> 
> 
> It’s very strange, the messages point to a problem – but everything SEEMS to 
> be working OK
> 
> 
> Cheers
> 
> 
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
> 
> 
> 
> 
> Cheers,
> Ronni
> 
> On 15/10/2013, at 7:54 PM, Neil Houghton  wrote:
> 
> Re: Itunes not responding 
> Aaargh!
> 
> 
> I spoke to soon. I just noticed that I had the console messages filtered for 
> mDNS. When I removed the filter, I see that the usbmuxd crash is still 
> occurring:
> 
> ---
> 15/10/13 19:36:02activitymonitord[1110]sending signal: 1 to pid: 18
> 15/10/13 19:36:02mDNSResponder[18]SIGHUP: Purge cache
> 15/10/13 19:37:20[0x0-0xb60b6].com.apple.iTunes[1125]Returning 0x0. 
> Advertising wake service for libraryIdentifier "D5B5885051837D5B".
> 15/10/13 19:37:20com.apple.usbmuxd[1065]
> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
> 15/10/13 19:37:20com.apple.usbmuxd[1065]_SendAttachNotification 
> Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local. 
> has already appeared on interface 6. Suppressing duplicate attach 
> notification.
> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:55202 
> proto=6
> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:3689 
> proto=6
> 15/10/13 19:37:21Firewall[74]iTunes is listening from :::3689 proto=6
> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152, 
> expectingLength = 3152
> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x9aa8024 
> atifb:(3.1.0)
> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
> 15/10/13 19:37:29kernelM

Re: Itunes not responding

2013-10-16 Thread Neil Houghton 
10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Parent: Error or
> timeout on select
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Child with pid
> 3134 exited normally
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]
> ATHostConnectionDestroy 0x2d83cc0
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Parent: Error or
> timeout on select
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]Child with pid
> 3135 exited normally
> 16/10/13 19:36:27[0x0-0x229229].com.apple.iTunes[3130]
> ATHostConnectionDestroy 0x2dd18e0
> 16/10/13 19:36:28[0x0-0x229229].com.apple.iTunes[3130]AppleGVA:: Error
> creating the accelerator 1
> 16/10/13 19:36:47com.apple.usbmuxd[1137]_heartbeat_failed heartbeat
> detected detach for device 0x1-192.168.2.101:0!
> 16/10/13 19:36:48com.apple.launchd[1](com.apple.usbmuxd[1137]) Job
> appears to have crashed: Segmentation fault
> 16/10/13 19:36:48com.apple.usbmuxd[3163]usbmuxd-323 on Jul 29 2013 at
> 23:21:29, running 64 bit
> 16/10/13 19:36:48com.apple.ReportCrash.Root[3162]2013-10-16
> 19:36:48.072 ReportCrash[3162:2903] Saved crash report for usbmuxd[1137]
> version ??? (???) to
> /Library/Logs/DiagnosticReports/usbmuxd_2013-10-16-193648_localhost.crash
> ---


It¹s very strange, the messages point to a problem ­ but everything SEEMS to
be working OK


Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com

> 
> 
> 
> Cheers,
> Ronni
> 
> On 15/10/2013, at 7:54 PM, Neil Houghton  wrote:
> 
>> Re: Itunes not responding
>> Aaargh!
>> 
>> 
>> I spoke to soon. I just noticed that I had the console messages filtered for
>> mDNS. When I removed the filter, I see that the usbmuxd crash is still
>> occurring:
>> 
>>> ---
>>> 15/10/13 19:36:02activitymonitord[1110]sending signal: 1 to pid: 18
>>> 15/10/13 19:36:02mDNSResponder[18]SIGHUP: Purge cache
>>> 15/10/13 19:37:20[0x0-0xb60b6].com.apple.iTunes[1125]Returning 0x0.
>>> Advertising wake service for libraryIdentifier "D5B5885051837D5B".
>>> 15/10/13 19:37:20com.apple.usbmuxd[1065]
>>> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
>>> 15/10/13 19:37:20com.apple.usbmuxd[1065]_SendAttachNotification
>>> Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
>>> has already appeared on interface 6. Suppressing duplicate attach
>>> notification.
>>> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:55202
>>> proto=6
>>> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:3689
>>> proto=6
>>> 15/10/13 19:37:21Firewall[74]iTunes is listening from :::3689
>>> proto=6
>>> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
>>> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152,
>>> expectingLength = 3152
>>> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x9aa8024
>>> atifb:(3.1.0)
>>> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
>>> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152,
>>> expectingLength = 3152
>>> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x983d024
>>> atifb:(3.1.0)
>>> 15/10/13 19:38:11com.apple.usbmuxd[1065]_SendAttachNotification
>>> Device 
>>> 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev2._tcp.local. has
>>> already appeared on interface 6. Suppressing duplicate attach notification.
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Parent: Error
>>> or timeout on select
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
>>> 1129 exited normally
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]
>>> ATHostConnectionDestroy 0x2c19a00
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Parent: Error
>>> or timeout on select
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
>>> 1135 exited normally
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
>>> 1135 exited normally
>>> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]
>>> ATHostConnectionDestroy 0x1f37cf80
>>> 15/10/13 19:38:20[0x0-0xb60b6].com.apple.iTunes[1125]AppleGVA::
>>> Error creating the accelerator 1
>>> 15/10/13 19:38:22com.apple.launchd[1](com.apple.usbmuxd[1065]) Job
>>> appears to have crashed: Segmentation fault
>>> 15/10/13 19:38:22com.apple.usbmuxd[1137]usbmuxd-323 on Jul 29 2013
>>> at 23:21:29, running 64 bit
>>> 15/10/13 19:38:22com.apple.ReportCrash.Root[1136]2013-10-15
>>> 19:38:22.406 ReportCrash[1136:2803] Saved crash report for usbmuxd[1065]
>>> version ??? (???) to
>>> /Library/Logs/DiagnosticReports/usbmuxd_2013-10-15-193822_localhost.crash
>>> ---
>> 
>> So something else is the culprit :o((
>> 
> 
> 

-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Settings & Unsubscribe - <http://lists.wamug.org.au/listinfo/wamug.org.au-wamug>

Re: Itunes not responding

2013-10-16 Thread Ronni Brown 
Hi Neil,

> So something else is the culprit :o((

Well, certainly something is not right on your System. 
iTunes uses usbmuxd for Wi-Fi syncing with iOS devices.
NONE of the Console messages I have marked below in Bold Red should be 
displaying.

Today I connected my iPhone 4S via USB to iTunes and set up "Sync with this 
iPhone over Wi-Fi"
Then disconnected my iPhone cable from the USB port (don't eject it) - and as 
it should, iPhone remains in the Devices section of the iTunes sidebar, even 
though I have disconnected it from my computer.

I then carried out the testing below to see if I could replica any of the 
messages you are receiving in Console.
The messages below are the messages you should see in Console.

1. Console messages after Opening iTunes:

16/10/13 1:54:29.504 PM com.apple.usbmuxd[29]: LOCKDOWN_V2_BONJOUR_SERVICE_NAME 
is _apple-mobdev2._tcp,9bc6086f
16/10/13 1:54:31.991 PM com.apple.usbmuxd[29]: _SendAttachNotification Device 
d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has 
already appeared on interface 5. Suppressing duplicate attach notification.

2. Console Messages after connecting iPhone to Power & iPhone automatically 
Wi-Fi syncs with iTunes:

16/10/13 1:59:29.657 PM com.apple.usbmuxd[29]: _SendAttachNotification Device 
d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has 
already appeared on interface 5. Suppressing duplicate attach notification.
16/10/13 1:59:37.382 PM AppleMobileBackup[20566]: WARNING: Backing up 
dccc21a42cf2895823a057ab1f251e0946cd4dd3

3. Console Messages after instigating a Wi-Fi sync (Settings > General > iTunes 
Wi-Fi Sync - ‘Sync Now’ ) on iPhone 4S connected to the same Network:

16/10/13 4:01:28.701 PM com.apple.usbmuxd[29]: _SendAttachNotification Device 
d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has 
already appeared on interface 5. Suppressing duplicate attach notification.
16/10/13 4:02:00.111 PM AppleMobileBackup[358]: WARNING: Backing up 
dccc21a42cf2895823a057ab1f251e0946cd4dd3

4. Console Messages after Restart of Mac & opening iTunes:

16/10/13 3:58:43.262 PM com.apple.usbmuxd[29]: LOCKDOWN_V2_BONJOUR_SERVICE_NAME 
is _apple-mobdev2._tcp,9bc6086f
16/10/13 3:58:44.353 PM com.apple.usbmuxd[29]: _SendAttachNotification Device 
d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has 
already appeared on interface 5. Suppressing duplicate attach notification.

5. Console Messages after Quitting iTunes and then Opening iTunes:

16/10/13 4:04:41.309 PM com.apple.usbmuxd[29]: _SendAttachNotification Device 
d0:23:db:4f:78:c4@fe80::d223:dbff:fe4f:78c4._apple-mobdev2._tcp.local. has 
already appeared on interface 5. Suppressing duplicate attach notification.

So Neil... what is causing you to see all the Firewall / kernel / 0x0-0xb60b6 
errors/ usbmuxd crash?

Do you have "Allow incoming connections" selected for iTunes.app in your 
Firewall settings?
Are you using any another Firewall or have LittleSnitch or something similar 
installed?
Did you "Repair Permissions" after installing iTunes 11.1.1?

Cheers,
Ronni

On 15/10/2013, at 7:54 PM, Neil Houghton  wrote:

> Aaargh!
> 
> 
> I spoke to soon. I just noticed that I had the console messages filtered for 
> mDNS. When I removed the filter, I see that the usbmuxd crash is still 
> occurring:
> 
>> ---
>> 15/10/13 19:36:02activitymonitord[1110]sending signal: 1 to pid: 18
>> 15/10/13 19:36:02mDNSResponder[18]SIGHUP: Purge cache
>> 15/10/13 19:37:20[0x0-0xb60b6].com.apple.iTunes[1125]Returning 0x0. 
>> Advertising wake service for libraryIdentifier "D5B5885051837D5B".
>> 15/10/13 19:37:20com.apple.usbmuxd[1065]
>> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
>> 15/10/13 19:37:20com.apple.usbmuxd[1065]_SendAttachNotification 
>> Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local. 
>> has already appeared on interface 6. Suppressing duplicate attach 
>> notification.
>> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:55202 
>> proto=6
>> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:3689 
>> proto=6
>> 15/10/13 19:37:21Firewall[74]iTunes is listening from :::3689 proto=6
>> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
>> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152, 
>> expectingLength = 3152
>> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x9aa8024 
>> atifb:(3.1.0)
>> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
>> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152, 
>> expectingLength = 3152
>> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x983d024 
>> atifb:(3.1.0)
>> 15/10/13 19:38:11com.apple.usbmuxd[1065]_SendAttachNotification 
>> Device 
>> 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1

Re: Itunes not responding

2013-10-15 Thread Neil Houghton 
Aaargh!


I spoke to soon. I just noticed that I had the console messages filtered for
mDNS. When I removed the filter, I see that the usbmuxd crash is still
occurring:

> ---
> 15/10/13 19:36:02activitymonitord[1110]sending signal: 1 to pid: 18
> 15/10/13 19:36:02mDNSResponder[18]SIGHUP: Purge cache
> 15/10/13 19:37:20[0x0-0xb60b6].com.apple.iTunes[1125]Returning 0x0.
> Advertising wake service for libraryIdentifier "D5B5885051837D5B".
> 15/10/13 19:37:20com.apple.usbmuxd[1065]
> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
> 15/10/13 19:37:20com.apple.usbmuxd[1065]_SendAttachNotification Device
> 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local. has
> already appeared on interface 6. Suppressing duplicate attach notification.
> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:55202
> proto=6
> 15/10/13 19:37:21Firewall[74]iTunes is listening from 0.0.0.0:3689
> proto=6
> 15/10/13 19:37:21Firewall[74]iTunes is listening from :::3689 proto=6
> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x9aa8024
> atifb:(3.1.0)
> 15/10/13 19:37:29kernelMessage Version Check or Length Not Match.
> 15/10/13 19:37:29kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 15/10/13 19:37:29kernelMessage Version Check - msg(0.0.0)@0x983d024
> atifb:(3.1.0)
> 15/10/13 19:38:11com.apple.usbmuxd[1065]_SendAttachNotification Device
> 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev2._tcp.local. has
> already appeared on interface 6. Suppressing duplicate attach notification.
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Parent: Error or
> timeout on select
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
> 1129 exited normally
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]
> ATHostConnectionDestroy 0x2c19a00
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Parent: Error or
> timeout on select
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
> 1135 exited normally
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]Child with pid
> 1135 exited normally
> 15/10/13 19:38:19[0x0-0xb60b6].com.apple.iTunes[1125]
> ATHostConnectionDestroy 0x1f37cf80
> 15/10/13 19:38:20[0x0-0xb60b6].com.apple.iTunes[1125]AppleGVA:: Error
> creating the accelerator 1
> 15/10/13 19:38:22com.apple.launchd[1](com.apple.usbmuxd[1065]) Job
> appears to have crashed: Segmentation fault
> 15/10/13 19:38:22com.apple.usbmuxd[1137]usbmuxd-323 on Jul 29 2013 at
> 23:21:29, running 64 bit
> 15/10/13 19:38:22com.apple.ReportCrash.Root[1136]2013-10-15
> 19:38:22.406 ReportCrash[1136:2803] Saved crash report for usbmuxd[1065]
> version ??? (???) to
> /Library/Logs/DiagnosticReports/usbmuxd_2013-10-15-193822_localhost.crash
> ---

So something else is the culprit :o((


Cheers



Neil
-- 
Neil R. Houghton
Albany, Western Australia
Tel: +61 8 9841 6063
Email: n...@possumology.com



on 15/10/13 19:47, Neil Houghton at n...@possumology.com wrote:

> Hi Ronni,
> 
> That¹s interesting. I will follow your procedure for clearing the DNS cache
> sometime in the next few days (I¹ve a few more things I need to attend to
> first) and report back.
> 
> A couple of points worth noting:
> 
> The message:
>> 14/10/13 12:16:43mDNSResponder[18]Client application
>> bug:DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for
>> over
>> two minutes. This places considerable burden on the network.
> Was only seen before I did the Safe Mode fix ­ it has not been generated
> since.
> 
> Whereas:
>> 15/10/13 11:57:51mDNSResponder[18]ERROR: handle_resolve_request bad
>> interfaceIndex 1   - down to 24
> Was not appearing during the iTunes problem and only appeared this morning
> after restarting everything and rechecking.
> 
> Ie these two messages were never being generated at the same time/status.
> 
> The mDNSResponder messages appear to have been a one-off, whereas the usbmuxd
> crashing seems to be ongoing. Here is the full log generated by opening
> iTunes, refreshing the podcast catalogue(which did not add any messages) and
> quitting iTunes (the messages from 19:14:12 on) - there are no mDNSResponder
> messages:
> 
> 
> ---
> 15/10/13 19:12:37[0x0-0xa90a9].com.apple.iTunes[1045]Returning 0x0.
> Advertising wake service for libraryIdentifier "D5B5885051837D5B".
> 15/10/13 19:12:37com.apple.usbmuxd[293]
> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
> 15/10/13 19:12:37com.apple.usbmuxd[293]_SendAttachNotification Device
> 7c:c5:3

Re: Itunes not responding

2013-10-15 Thread Neil Houghton 
Hi Ronni,

That¹s interesting. I will follow your procedure for clearing the DNS cache
sometime in the next few days (I¹ve a few more things I need to attend to
first) and report back.

A couple of points worth noting:

The message:
> 14/10/13 12:16:43mDNSResponder[18]Client application
> bug:DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for
> over
> two minutes. This places considerable burden on the network.
Was only seen before I did the Safe Mode fix ­ it has not been generated
since.

Whereas:
> 15/10/13 11:57:51mDNSResponder[18]ERROR: handle_resolve_request bad
> interfaceIndex 1   - down to 24
Was not appearing during the iTunes problem and only appeared this morning
after restarting everything and rechecking.

Ie these two messages were never being generated at the same time/status.

The mDNSResponder messages appear to have been a one-off, whereas the
usbmuxd crashing seems to be ongoing. Here is the full log generated by
opening iTunes, refreshing the podcast catalogue(which did not add any
messages) and quitting iTunes (the messages from 19:14:12 on) - there are no
mDNSResponder messages:


---
15/10/13 19:12:37[0x0-0xa90a9].com.apple.iTunes[1045]Returning 0x0.
Advertising wake service for libraryIdentifier "D5B5885051837D5B".
15/10/13 19:12:37com.apple.usbmuxd[293]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
15/10/13 19:12:37com.apple.usbmuxd[293]_SendAttachNotification
Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
15/10/13 19:12:37com.apple.usbmuxd[293]_SendAttachNotification
Device 
98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev2._tcp.local. has
already appeared on interface 6. Suppressing duplicate attach notification.
15/10/13 19:12:39Firewall[74]iTunes is listening from 0.0.0.0:54755
proto=6
15/10/13 19:12:39Firewall[74]iTunes is listening from 0.0.0.0:3689
proto=6
15/10/13 19:12:39Firewall[74]iTunes is listening from :::3689
proto=6
15/10/13 19:12:46kernelMessage Version Check or Length Not Match.
15/10/13 19:12:46kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
15/10/13 19:12:46kernelMessage Version Check - msg(0.0.0)@0x884c024
atifb:(3.1.0)
15/10/13 19:12:46kernelMessage Version Check or Length Not Match.
15/10/13 19:12:46kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
15/10/13 19:12:46kernelMessage Version Check - msg(0.0.0)@0xa24e024
atifb:(3.1.0)
15/10/13 19:13:14/Applications/iTunes.app/Contents/MacOS/iTunes[1045]
Entered:_AMMuxedDeviceDisconnected, mux-device:2
15/10/13 19:13:14/Applications/iTunes.app/Contents/MacOS/iTunes[1045]
Entered:__thr_AMMuxedDeviceDisconnected, mux-device:2
15/10/13 19:13:14/Applications/iTunes.app/Contents/MacOS/iTunes[1045]
tid:16513 - Mux ID not found in mapping dictionary
15/10/13 19:13:14/Applications/iTunes.app/Contents/MacOS/iTunes[1045]
tid:16513 - Can't handle disconnect with invalid ecid
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]Parent: Error
or timeout on select
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]Child with pid
1050 exited normally
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]
ATHostConnectionDestroy 0x2d50b50
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]Parent: Error
or timeout on select
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]Child with pid
1051 exited normally
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]
ATHostConnectionDestroy 0x2b61d00
15/10/13 19:14:12[0x0-0xa90a9].com.apple.iTunes[1045]AppleGVA::
Error creating the accelerator 1
15/10/13 19:14:29com.apple.usbmuxd[293]_heartbeat_failed heartbeat
detected detach for device 0x1-192.168.2.101:0!
15/10/13 19:14:30com.apple.launchd[1](com.apple.usbmuxd[293]) Job
appears to have crashed: Segmentation fault
15/10/13 19:14:30com.apple.usbmuxd[1065]usbmuxd-323 on Jul 29 2013
at 23:21:29, running 64 bit
15/10/13 19:14:30com.apple.ReportCrash.Root[1064]2013-10-15
19:14:30.903 ReportCrash[1064:2903] Saved crash report for usbmuxd[293]
version ??? (???) to
/Library/Logs/DiagnosticReports/usbmuxd_2013-10-15-191430_localhost.crash
---


Not sure if that gives you any extra clues ;o)


UPDATE:
I just realised your DNS cache clearing method using Activity monitor was so
simple & quick I should just do it!

So I did ­ and it seems to have solved the usbmuxd crashing  problem. I
purged the cache, started iTunes, refreshed the iTunes U directory and then
quit iTunes and the only message was the initial purge cache message:
> 15/10/13 19:36:02mDNSResponder[18]SIGHUP: Purge cache


BRILLIANT!

I will keep an eye on this, from time to time, to see if the problem recurs
but

Re: Itunes not responding

2013-10-15 Thread Ronni Brown 
On 15/10/2013, at 2:03 PM, Ronda Brown  wrote:

> 
>> On 15 Oct 2013, at 12:28 pm, Neil Houghton  wrote:
>> 
>> Well, Ronni, you DID say you were curious ;o)
>> 
>> For myself, I'm happy that it all seems to be working OK and don't really
>> want to spend any more time on it - though that may, of course change if
>> further problems arise.
>> 
>> Thanks again for your help and interest Ronni - and I'm with you - always
>> stay curious - there's so much to learn ;o))
> 
> Thanks Neil for 'doing the exercise' and supplying the information and log 
> files.
> When I find some time I will study the logs and info more thoroughly. 
> Something is going on with your system, but as you mention if you are not 
> experiencing any problems I guess it is not all that important ... At this 
> moment!! 
> 
> I am curious as to why you are getting all these messages in console, so I 
> will give it more thought (when time permits) and if I come up with 'the 
> WHY'... I will let you know ;-)
> 
> Cheers,
> Ronni
> Sent from Ronni's iPad4

Hi Neil,

When I read your first posting to the mailing list; the Console Log messages 
that jumped out at me were these messages: 
1)  14/10/13 12:14:32com.apple.usbmuxd[11654]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5

2) 14/10/13 12:16:43mDNSResponder[18]Client application bug:
DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for over
two minutes. This places considerable burden on the network.

I thought at the time... "ah perhaps a Bonjour issue"? iTunes uses Bonjour (as 
well as other Bonjour-compatible devices and services).

Now after reading your last message to the mailing list and thoroughly going 
through your "full unfiltered console log" and noticing the "mDNSResponder[18]  
 ERROR messages  

15/10/13 11:57:51mDNSResponder[18]ERROR: handle_resolve_request bad
interfaceIndex 1   - down to 24

I'm pretty certain that my original assumption was correct and Bonjour is 
involved.
My reasoning for coming to this conclusion is:
The process that makes Bonjour work is mDNSResponder, located in /usr/sbin. 
/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist invokes 
mDNSResponder on boot. 

NOTE: I don't want you deleting the .plist above I only mentioned where it is 
located ;-)

What I would suggest you do is Reset / Clear the DNS cache.
OS X keeps a local cache of resolved DNS queries for a time defined by the DNS 
server, but sometimes it may be necessary to reset the cache.

In Lion & Mountain Lion, Apple has changed the caching routines done by the 
mDNSResponder process (the core process responsible for DNS resolution) so they 
are kept in memory by the process as long as it maintains a connection to the 
DNS network. 
Therefore, to clear the cache, you just need to send the mDNSResponder process 
a hang-up command to have it reinitialise its configuration without being fully 
shut down and restarted. 

To do this, you can run the following command in the Terminal:

 sudo killall -HUP mDNSResponder

Note the dscacheutil still exists in 10.7 and 10.8, but the official method to 
clear out DNS caches is through killing mDNSResponder.

OR - you can use Activity Monitor - In addition to the killall command in the 
Terminal, you can also do this in Activity Monitor by the following process:

1.  Open Activity Monitor (in the /Applications/Utilities/ folder).
2.  In the main Activity Monitor window is not present, press Command-1 to show 
it.
3.  Locate and select the mDNSResponder process (you can search for it to make 
this easier).
4.  Choose Send Signal To Process from the View menu.
5.  Select Hangup (SIGHUP) from the menu that appears (it should be the first 
option that is already selected).
6.  Click the Send button.
When you do this, you may see another mDNSResponder process appear for a few 
seconds in Activity Monitor as the system reinitialises the process, and once 
this disappears, the DNS cache should be cleared.

That's it! 
... for today anyway ;-)

Cheers,
Ronni

17" MacBook Pro 2.3GHz Quad-Core i7 “Thunderbolt"
2.3GHz / 8GB / 750GB @ 7200rpm HD

OS X 10.8.5 Mountain Lion
Windows 7 Ultimate (under sufferance)




















-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Settings & Unsubscribe -

Re: Itunes not responding

2013-10-14 Thread Ronda Brown 

> On 15 Oct 2013, at 12:28 pm, Neil Houghton  wrote:
> 
> Well, Ronni, you DID say you were curious ;o)
> 
> For myself, I'm happy that it all seems to be working OK and don't really
> want to spend any more time on it - though that may, of course change if
> further problems arise.
> 
> Thanks again for your help and interest Ronni - and I'm with you - always
> stay curious - there's so much to learn ;o))

Thanks Neil for 'doing the exercise' and supplying the information and log 
files.
When I find some time I will study the logs and info more thoroughly. 
Something is going on with your system, but as you mention if you are not 
experiencing any problems I guess it is not all that important ... At this 
moment!! 

I am curious as to why you are getting all these messages in console, so I will 
give it more thought (when time permits) and if I come up with 'the WHY'... I 
will let you know ;-)

Cheers,
Ronni
Sent from Ronni's iPad4
-- The WA Macintosh User Group Mailing List --
Archives - 
Guidelines - 
Settings & Unsubscribe -

Re: Itunes not responding

2013-10-14 Thread Neil Houghton 
Hi Ronni,

Due to all the console verbiage, I have trimmed the earlier responses from
this reply and just addressed your last email. This response was generated
over time, as I progressed through various steps and reported as I went:

Cleared Console display and restarted iTunes. Console messages generated
were:

---
14/10/13 17:27:07[0x0-0x50050].com.apple.iTunes[534]Returning 0x0.
Advertising wake service for libraryIdentifier "D5B5885051837D5B".
14/10/13 17:27:07com.apple.usbmuxd[492]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
14/10/13 17:27:07com.apple.usbmuxd[492]_SendAttachNotification
Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 17:27:07Firewall[75]iTunes is listening from 0.0.0.0:50938
proto=6
14/10/13 17:27:07Firewall[75]iTunes is listening from 0.0.0.0:3689
proto=6
14/10/13 17:27:07Firewall[75]iTunes is listening from :::3689
proto=6
14/10/13 17:27:07com.apple.usbmuxd[492]_SendAttachNotification
Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 17:27:15kernelMessage Version Check or Length Not Match.
14/10/13 17:27:15kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 17:27:15kernelMessage Version Check - msg(0.0.0)@0x940f024
atifb:(3.1.0)
14/10/13 17:27:15kernelMessage Version Check or Length Not Match.
14/10/13 17:27:15kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 17:27:15kernelMessage Version Check - msg(0.0.0)@0x9413024
atifb:(3.1.0)
14/10/13 17:27:41/Applications/iTunes.app/Contents/MacOS/iTunes[534]
Entered:_AMMuxedDeviceDisconnected, mux-device:1
14/10/13 17:27:41/Applications/iTunes.app/Contents/MacOS/iTunes[534]
Entered:__thr_AMMuxedDeviceDisconnected, mux-device:1
14/10/13 17:27:41/Applications/iTunes.app/Contents/MacOS/iTunes[534]
tid:1392b - Mux ID not found in mapping dictionary
14/10/13 17:27:41/Applications/iTunes.app/Contents/MacOS/iTunes[534]
tid:1392b - Can't handle disconnect with invalid ecid
---

So, yes, those messages are still being generated and, as you say, don't
exactly look "right"

I did a google on the message and found this:


Where someone says:
> I trashed com.apple.usbmuxd.plist and restarted.  All is good now.

Which is the pref file that you mentioned - so, after quitting iTunes, I
went to /System/Library/LaunchDaemons/com.apple.usbmuxd.plist and deleted it
- then restarted iTunes.

The messages were still there and iTunes did not recreate the prefs file. I
re-started iTunes in Safe Mode but the prefs file was still not recreated -
I downloaded an app update and all still seems to be working - so I quit
iTunes.

At this point the console is showing:

---
14/10/13 17:41:26kernelCODE SIGNING: cs_invalid_page(0x1000):
p=583[GoogleSoftwareUp] clearing CS_VALID
14/10/13 17:41:31[0x0-0x5a05a].com.apple.iTunes[588]Returning 0x0.
Advertising wake service for libraryIdentifier "D5B5885051837D5B".
14/10/13 17:41:31com.apple.usbmuxd[564]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
14/10/13 17:41:32com.apple.usbmuxd[564]_SendAttachNotification
Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 17:41:32Firewall[75]iTunes is listening from 0.0.0.0:51377
proto=6
14/10/13 17:41:32Firewall[75]iTunes is listening from 0.0.0.0:3689
proto=6
14/10/13 17:41:32Firewall[75]iTunes is listening from :::3689
proto=6
14/10/13 17:41:33com.apple.usbmuxd[564]_SendAttachNotification
Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 17:41:40kernelMessage Version Check or Length Not Match.
14/10/13 17:41:40kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 17:41:40kernelMessage Version Check - msg(0.0.0)@0xe690024
atifb:(3.1.0)
14/10/13 17:41:40kernelMessage Version Check or Length Not Match.
14/10/13 17:41:40kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 17:41:40kernelMessage Version Check - msg(0.0.0)@0x8cd9024
atifb:(3.1.0)
14/10/13 17:42:06/Applications/iTunes.app/Contents/MacOS/iTunes[588]
Entered:_AMMuxedDeviceDisconnected, mux-device:2
14/10/13 17:42:06/Applications/iTunes.app/Contents/MacOS/iTunes[588]
Entered:__thr_AMMuxedDeviceDisconnected, mux-device:2
14/10/13 17:42:06/Applications/iTunes.app/Contents/MacOS/iTunes[588]
tid:15b13

Re: Itunes not responding

2013-10-14 Thread Ronda Brown 
Hi Neil,
> 
> So far all is good and it appears the problem is hopefully solved :o))
> 
> Thanks very much for your help and suggestions Ronni. I'll now go and read
> some more about starting apps in Safe Mode ;o)

Starting iTunes in Safe Mode allows you to be able to check things and follow 
prompts that iTunes shows you. It allows iTunes to download and update iTunes 
components.
Safe Mode disables any non generic plugins / add-ons etc, allowing iTunes to go 
back to bare operating basics.

Neil, while iTunes is behaving would you do a restart of iTunes and check in 
Console if these messages still appear when iTunes runs please. I'm just 
curious :-)

14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
tid:1540f - Mux ID not found in mapping dictionary
14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
tid:1540f - Can't handle disconnect with invalid ecid

I don't think that should be happening it indicates to me that you might have 
been having a problem with "com.apple.usbmuxd.plist" file, which corrected 
after you were able to update etc.

Cheers,
Ronni
Sent from Ronni's iPad4

> On 14 Oct 2013, at 3:30 pm, Neil Houghton  wrote:
> 
> Hi ronni,
> 
> First off, I unplugged the AppleTV and let it sit for a while so that
> everything had a chance to recognise that. So the AppleTV itself is now out
> of the picture.
> 
> Then I used Console to monitor messages whilst I restarted iTunes, it again
> locked up and I force quit - messages below:
> 
> -
> 14/10/13 13:37:24[0x0-0x7a57a5].com.apple.iTunes[11820]Returning
> 0x0. Advertising wake service for libraryIdentifier "D5B5885051837D5B".
> 14/10/13 13:37:24com.apple.usbmuxd[11721]
> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
> 14/10/13 13:37:24com.apple.usbmuxd[11721]_SendAttachNotification
> Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
> has already appeared on interface 6. Suppressing duplicate attach
> notification.
> 14/10/13 13:37:24com.apple.usbmuxd[11721]_SendAttachNotification
> Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev._tcp.local.
> has already appeared on interface 6. Suppressing duplicate attach
> notification.
> 14/10/13 13:37:25Firewall[76]iTunes is listening from 0.0.0.0:58406
> proto=6
> 14/10/13 13:37:25Firewall[76]iTunes is listening from 0.0.0.0:3689
> proto=6
> 14/10/13 13:37:25Firewall[76]iTunes is listening from :::3689
> proto=6
> 14/10/13 13:37:33kernelMessage Version Check or Length Not Match.
> 14/10/13 13:37:33kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 14/10/13 13:37:33kernelMessage Version Check - msg(0.0.0)@0x9cab024
> atifb:(3.1.0)
> 14/10/13 13:37:33kernelMessage Version Check or Length Not Match.
> 14/10/13 13:37:33kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 14/10/13 13:37:33kernelMessage Version Check - msg(0.0.0)@0x9c8c024
> atifb:(3.1.0)
> 14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
> Entered:_AMMuxedDeviceDisconnected, mux-device:2
> 14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
> Entered:__thr_AMMuxedDeviceDisconnected, mux-device:2
> 14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
> tid:11f1b - Mux ID not found in mapping dictionary
> 14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
> tid:11f1b - Can't handle disconnect with invalid ecid
> 14/10/13 13:39:35mDNSResponder[18]Client application bug:
> DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for over
> two minutes. This places considerable burden on the network.
> 14/10/13 13:41:04com.apple.launchd.peruser.502[143]
> ([0x0-0x7a57a5].com.apple.iTunes[11820]) Exited: Terminated
> 14/10/13 13:41:16com.apple.usbmuxd[11721]_heartbeat_failed heartbeat
> detected detach for device 0x1-192.168.2.101:0!
> 14/10/13 13:41:16com.apple.launchd[1](com.apple.usbmuxd[11721]) Job
> appears to have crashed: Segmentation fault
> 14/10/13 13:41:16com.apple.usbmuxd[11854]usbmuxd-323 on Jul 29 2013
> at 23:21:29, running 64 bit
> 14/10/13 13:41:16com.apple.ReportCrash.Root[11853]2013-10-14
> 13:41:16.979 ReportCrash[11853:2803] Saved crash report for usbmuxd[11721]
> version ??? (???) to
> /Library/Logs/DiagnosticReports/usbmuxd_2013-10-14-134116_localhost.crash
> -
> 
> 
> The Mac and ADSL router have been rebooted several times since the problem
> started - BUT, to be sure, I restarted the mac and rebooted the ADSL router
> - essentially the problem remains - I won't include the console messages as
> they are functionally identical.
> 
> I then considered that the actual wireless network is created and run by the
> Airport Extreme - so I opened Airport Utility and saw t

Re: Itunes not responding

2013-10-14 Thread Neil Houghton 
Hi ronni,

First off, I unplugged the AppleTV and let it sit for a while so that
everything had a chance to recognise that. So the AppleTV itself is now out
of the picture.

Then I used Console to monitor messages whilst I restarted iTunes, it again
locked up and I force quit - messages below:

-
14/10/13 13:37:24[0x0-0x7a57a5].com.apple.iTunes[11820]Returning
0x0. Advertising wake service for libraryIdentifier "D5B5885051837D5B".
14/10/13 13:37:24com.apple.usbmuxd[11721]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
14/10/13 13:37:24com.apple.usbmuxd[11721]_SendAttachNotification
Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 13:37:24com.apple.usbmuxd[11721]_SendAttachNotification
Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev._tcp.local.
has already appeared on interface 6. Suppressing duplicate attach
notification.
14/10/13 13:37:25Firewall[76]iTunes is listening from 0.0.0.0:58406
proto=6
14/10/13 13:37:25Firewall[76]iTunes is listening from 0.0.0.0:3689
proto=6
14/10/13 13:37:25Firewall[76]iTunes is listening from :::3689
proto=6
14/10/13 13:37:33kernelMessage Version Check or Length Not Match.
14/10/13 13:37:33kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 13:37:33kernelMessage Version Check - msg(0.0.0)@0x9cab024
atifb:(3.1.0)
14/10/13 13:37:33kernelMessage Version Check or Length Not Match.
14/10/13 13:37:33kernelMessage Length Check - msglength = 3152,
expectingLength = 3152
14/10/13 13:37:33kernelMessage Version Check - msg(0.0.0)@0x9c8c024
atifb:(3.1.0)
14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
Entered:_AMMuxedDeviceDisconnected, mux-device:2
14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
Entered:__thr_AMMuxedDeviceDisconnected, mux-device:2
14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
tid:11f1b - Mux ID not found in mapping dictionary
14/10/13 13:37:59/Applications/iTunes.app/Contents/MacOS/iTunes[11820]
tid:11f1b - Can't handle disconnect with invalid ecid
14/10/13 13:39:35mDNSResponder[18]Client application bug:
DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for over
two minutes. This places considerable burden on the network.
14/10/13 13:41:04com.apple.launchd.peruser.502[143]
([0x0-0x7a57a5].com.apple.iTunes[11820]) Exited: Terminated
14/10/13 13:41:16com.apple.usbmuxd[11721]_heartbeat_failed heartbeat
detected detach for device 0x1-192.168.2.101:0!
14/10/13 13:41:16com.apple.launchd[1](com.apple.usbmuxd[11721]) Job
appears to have crashed: Segmentation fault
14/10/13 13:41:16com.apple.usbmuxd[11854]usbmuxd-323 on Jul 29 2013
at 23:21:29, running 64 bit
14/10/13 13:41:16com.apple.ReportCrash.Root[11853]2013-10-14
13:41:16.979 ReportCrash[11853:2803] Saved crash report for usbmuxd[11721]
version ??? (???) to
/Library/Logs/DiagnosticReports/usbmuxd_2013-10-14-134116_localhost.crash
-


The Mac and ADSL router have been rebooted several times since the problem
started - BUT, to be sure, I restarted the mac and rebooted the ADSL router
- essentially the problem remains - I won't include the console messages as
they are functionally identical.

I then considered that the actual wireless network is created and run by the
Airport Extreme - so I opened Airport Utility and saw that it was flagging a
firmware update - which I initiated. The firmware was successfully updated
and the Extreme restarted. As I still had Console opened, I noticed this
message which may be relevant? (Although I do have iTunes set-up so that I
do have to sign-in to purchase and don't have the remember this box ticked -
so this maybe normal?)

-
14/10/13 14:12:37AOSNotification[187][AOSNotification] Cannot obtain
password from generic keychain for service = iTools, account = neil_houghton

Again I started iTunes and noticed that some of the console messages had now
changed - however when I switched back to iTunes (after watching in console
for a while) it still locked up. The console messages are:

14/10/13 14:17:25kernelAirPort: RSN handshake complete on en1
14/10/13 14:17:30[0x0-0x2e02e].com.apple.iTunes[299]Returning 0x0.
Advertising wake service for libraryIdentifier "D5B5885051837D5B".
14/10/13 14:17:30Firewall[75]iTunes is listening from 0.0.0.0:49321
proto=6
14/10/13 14:17:30Firewall[75]iTunes is listening from 0.0.0.0:3689
proto=6
14/10/13 14:17:30Firewall[75]iTunes is listening from :::3689
proto=6
14/10/13 14:17:30com.apple.usbmuxd[253]
LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
14/10/13 14:17:31com.apple.u

Re: Itunes not responding

2013-10-13 Thread Ronda Brown 
Hi Neil,

Have you tried rebooting your Mac and rebooting your Router?
If that doesn't help:
Try starting iTunes in Safe Mode.
1. Hold down Command+Option when you open iTunes (this will open in Safe Mode)
Does the freeze still occur?

2. Long into another user account and test. See whether the freeze occurs in 
another User Account.

Cheers,
Ronni
Sent from Ronni's iPad4

> On 14 Oct 2013, at 12:31 pm, Neil Houghton  wrote:
> 
> I've got a problem with iTunes since my last (iTunes) update.
> 
> 27" iMac, 2.8GHz Core I7, OSX 10.6.8 running iTunes 11.1.1
> 
> I seem to remember that on first running iTunes after the 11.1.1 update some
> dialogue box came up - but I had also started iTunes downloading some app
> upgrades including a large one I didn't want to proceed so I tried to stop
> that before dealing with the dialogue box - which I then lost :o(
> 
> I don't really remember exactly how all this went down - but I mention it as
> it may well be the source of my current problem:
> 
> 
> 
> Which is that iTunes is not working - I can start it up and it seems to
> start OK but if I leave it running (without actually doing anything in
> iTunes) it seems to quickly lock up and activity monitor shows it as "Not
> Responding" - Quit process does not work but Force quit does.
> 
> I opened iTunes again and then immediately switched to Activity monitor to
> watch it - and all seemed fine - after about 4 minutes I switched back to
> iTunes (just clicked the iTunes window) and iTunes immediately went to the
> spinning beachball and Not responding.
> 
> I force quit again and restarted iTunes but then very quickly quit it - to
> see if a "normal" quit would smooth things out - but still iTunes starts OK
> but locks up within a minute or so.
> 
> I opened console, cleared the display, and then restarted iTunes and watched
> the messages - when there were no more I went back to iTunes (which
> immediately locked) and force quit. The console messages for this episode
> are below:
> 
> 14/10/13 12:14:32Firewall[76]iTunes is listening from 0.0.0.0:58180
> proto=6
> 14/10/13 12:14:32[0x0-0x78f78f].com.apple.iTunes[11668]Returning
> 0x0. Advertising wake service for libraryIdentifier "D5B5885051837D5B".
> 14/10/13 12:14:32Firewall[76]iTunes is listening from 0.0.0.0:3689
> proto=6
> 14/10/13 12:14:32Firewall[76]iTunes is listening from :::3689
> proto=6
> 14/10/13 12:14:32com.apple.usbmuxd[11654]
> LOCKDOWN_V2_BONJOUR_SERVICE_NAME is _apple-mobdev2._tcp,930d07f5
> 14/10/13 12:14:32com.apple.usbmuxd[11654]_SendAttachNotification
> Device 7c:c5:37:d0:13:8b@fe80::7ec5:37ff:fed0:138b._apple-mobdev._tcp.local.
> has already appeared on interface 6. Suppressing duplicate attach
> notification.
> 14/10/13 12:14:33com.apple.usbmuxd[11654]_SendAttachNotification
> Device 98:b8:e3:d1:50:64@fe80::9ab8:e3ff:fed1:5064._apple-mobdev._tcp.local.
> has already appeared on interface 6. Suppressing duplicate attach
> notification.
> 14/10/13 12:14:41kernelMessage Version Check or Length Not Match.
> 14/10/13 12:14:41kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 14/10/13 12:14:41kernelMessage Version Check - msg(0.0.0)@0x8ba7024
> atifb:(3.1.0)
> 14/10/13 12:14:41kernelMessage Version Check or Length Not Match.
> 14/10/13 12:14:41kernelMessage Length Check - msglength = 3152,
> expectingLength = 3152
> 14/10/13 12:14:41kernelMessage Version Check - msg(0.0.0)@0x8ac4024
> atifb:(3.1.0)
> 14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
> Entered:_AMMuxedDeviceDisconnected, mux-device:2
> 14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
> Entered:__thr_AMMuxedDeviceDisconnected, mux-device:2
> 14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
> tid:1540f - Mux ID not found in mapping dictionary
> 14/10/13 12:15:07/Applications/iTunes.app/Contents/MacOS/iTunes[11668]
> tid:1540f - Can't handle disconnect with invalid ecid
> 14/10/13 12:16:27kernelCODE SIGNING: cs_invalid_page(0x1000):
> p=11686[GoogleSoftwareUp] clearing CS_VALID
> 14/10/13 12:16:43mDNSResponder[18]Client application bug:
> DNSServiceResolve(53F5FEFC2612ED6D._appletv-v2._tcp.local.) active for over
> two minutes. This places considerable burden on the network.
> 14/10/13 12:23:06com.apple.launchd.peruser.502[143]
> ([0x0-0x78f78f].com.apple.iTunes[11668]) Exited: Terminated
> 
> There seems to be reference to Apple TV here - which is surprising since it
> is months since I actually used my AppleTV (though is is left switched on)
> 
> Ant thoughts at this stage? Prefs to delete?
> 
> My next step will be to switch off the Apple TV and see what effect that
> has.
> 
> 
> Cheers
> 
> 
> 
> Neil
> -- 
> Neil R. Houghton
> Albany, Western Australia
> Tel: +61 8 9841 6063
> Email: n...@possumology.com
-- The WA Macintosh User Group Mailing List --
Archives -