Created
June 5, 2015 15:18
-
-
Save BigZaphod/e92f3827a8a6d7811959 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We need more information to investigate this issue. | |
If this happens again: please check if turning off/on wifi resolves the issue? | |
Another thing that can be done is getting mDNSResponder logs: | |
1. Turn on verbose logging with | |
a) sudo syslog -c mDNSResponder -i | |
b) sudo killall -USR1 mDNSResponder | |
c) sudo killall -USR2 mDNSResponder | |
d) syslog -w > ~/Desktop/mDNS.log | |
2. Let the following `tcpdump` command run in a terminal window to collect a packet capture: | |
sudo tcpdump -w ~/Desktop/dns.pcap | |
3. Reproduce the problem and take note of the time problem reproduced | |
4. Stop tcpdump with Ctrl+C | |
5. From Terminal, execute '/System/Library/Frameworks/SystemConfiguration.framework/Resources/get-mobility-info' | |
6. From Terminal, execute '/usr/bin/sysdiagnose’ | |
7. When you’re done, turn off verbose logging by rebooting OR | |
sudo killall -TSTP mDNSResponder | |
8. Files to collect: | |
~/Desktop/mobility-info*.tar.gz | |
/var/tmp/sysdiagnose*.tar.gz | |
~/Desktop/dns.pcap | |
~/Desktop/mDNS.log | |
Please provide your response or results by updating your bug report. | |
Please compress any bundled files (e.g. nested folders) prior to uploading. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment