into /etc/hosts. Ping and all other services are able to do dns lookups correctly, so not sure why the Minecraft launcher can't.
How I found the workaround:
With the help of dtruss tool, I was able to find the launcher_log.txt (pity that noone pointed me to it - it's in /Users/[your_username]/Library/Application Support/minecraft/launcher_log.txt.
[Error: 2020-03-28 15:06:48.572628: NetQueue.cpp(444)] NetQueue: No ip address available. Error code 6, Url: launchermeta.mojang.com
[Info: 2020-03-28 15:06:48.572777: NetQueue.cpp(480)] NetQueue: Action failed with result "Could not resolve: launchermeta.mojang.com (Could not contact DNS servers)" (6) :
not sure why it does not work, as I was able to happily ping the address. I added the address to my /etc/hosts. After that the launcher tried to download bunch of files and crashed later. New log file nativeUpdaterLog.txt appeared in the same dir and according to it it failed to lookup the launcher.mojang.com. So I added that to /etc/hosts as well. After that the launcher started succesfully into login screen. I tried to remove the hosts entries then and it was still starting (but per log it was still failing to resolve the names). Only when I removed the /Users/[your_username]/Library/Application Support/minecraft it was failing again.
MCL-13419
I tried to remove all javas (I had multiple versions), then I installed oracle 11.6 jdk using binary intaller, but the problem is still the same.
$ ls -lah /Library/Java/JavaVirtualMachines total 0 drwxr-xr-x 2 root wheel 64B Mar 25 21:11 . drwxr-xr-x 4 root wheel 128B Sep 21 2018 .. $ java --version No Java runtime present, requesting install. # Installed it here $ java --version java 11.0.6 2020-01-14 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.6+8-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.6+8-LTS, mixed mode) $ ls -lah /Library/Java/JavaVirtualMachines total 0 drwxr-xr-x 3 root wheel 96B Mar 25 21:12 . drwxr-xr-x 4 root wheel 128B Mar 25 21:12 .. drwxr-xr-x 3 root wheel 96B Mar 25 21:12 jdk-11.0.6.jdk $ /Applications/Minecraft.app/Contents/MacOS/launcher 2020-03-25 21:16:35.383 launcher[1464:75212] Claimed it found a path: /Applications/Minecraft.app/Contents/MacOS/launcher (/Applications/Minecraft.app/Contents/MacOS/launcher) 4096 https://launchermeta.mojang.com/v1/products/launcher/022631aeac4a9addbce8e0503dce662152dc198d/mac-os.json SaveToBuffer failedAny more advice?
I was able to work around the problem by adding
into /etc/hosts. Ping and all other services are able to do dns lookups correctly, so not sure why the Minecraft launcher can't.
How I found the workaround:
With the help of dtruss tool, I was able to find the launcher_log.txt (pity that noone pointed me to it - it's in /Users/[your_username]/Library/Application Support/minecraft/launcher_log.txt.
In the launcher_log.txt
I noticed
not sure why it does not work, as I was able to happily ping the address. I added the address to my /etc/hosts. After that the launcher tried to download bunch of files and crashed later. New log file nativeUpdaterLog.txt appeared in the same dir and according to it it failed to lookup the launcher.mojang.com. So I added that to /etc/hosts as well. After that the launcher started succesfully into login screen. I tried to remove the hosts entries then and it was still starting (but per log it was still failing to resolve the names). Only when I removed the /Users/[your_username]/Library/Application Support/minecraft it was failing again.