[SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."

[Juha Kallioinen]

Hi Christopher,

the changing networks may play a part in this problem. Did I already 
sometime earlier ask you to modify your Mac's /etc/hosts file?

It has helped in some cases to add the name for the MerSDK virtual 
machine to /etc/hosts like this:

127.0.0.1 SailfishSDK

Or if you already have the 127.0.0.1 there, just add the SailfishSDK to 
the end of the existing line like this:

127.0.0.1        localhost.localdomain localhost SailfishSDK

Could you try this and let me know if there's any improvement? If you 
already have it there.. well then we'll have to think of something else. 
VirtualBox has some DNS related settings like these:

|--natdnsproxy<1-N> on|off|: This option makes the NAT engine proxy all 
guest DNS requests to the host's DNS servers|
|

|--natdnshostresolver<1-N> on|off|: This option makes the NAT engine use 
the host's resolver mechanisms to handle DNS requests

Of these we use the "--natdnshostresolver1 on" in MerSDK and the Emulator.

The options are documented here:

http://www.virtualbox.org/manual/ch08.html#vboxmanage-modifyvm

The rpmbuild command does a DNS query in the place where the failure is 
in your log. Usually it just prints out:

"warning: Could not canonicalize hostname: SailfishSDK"


Which is fine.. but in some networks that bit can cause a failure. In 
those cases modifying the /etc/hosts file has helped.

Best regards,
  Juha

On 03.06.2014 10:24, Christopher Lamb wrote:
> Hi Saija
>
> In my case restarting the VMs does not help. I think (from memory) 
> that rebooting the whole laptop does help.
>
> It is possible that the same reported error may have a number of 
> different causes - in my case it seems to be when my development host 
> loses its network connection (though as with all sporadic problems it 
> is difficult to be sure).
>
> Thanks
>
> Chris
> On 03.06.14 09:02, Saija Saarenpää wrote:
>> I get the same error often when developing with Windows 8 64-bit, 
>> never on Mac OSX 10. They are both always connected to the (same) 
>> network. It helps to close and open the virtual machine, the  it 
>> stays reachable for another while once it does the same again.
>>
>> - Saija
>>
>> Lähetetty iPadista
>>
>>> "Christopher Lamb" <christopher.lamb at thurweb.ch> kirjoitti 3.6.2014 
>>> kello 9.58:
>>>
>>> Hi Jarko
>>>
>>> Still on the train, now with the Jolla Wifi Hotspot active, and I 
>>> can build without problems.
>>>
>>> This indicates that I get the problem when no network is connected. 
>>> In this case I am deploying to the Emulator, so no network should be 
>>> required ....
>>>
>>> Grüsse
>>>
>>> Chris
>>>
>>>> On 02.06.14 10:23, Jarko Vihriala wrote:
>>>> journalctl -fa
>>> _______________________________________________
>>> SailfishOS.org Devel mailing list
>>> To unsubscribe, please send a mail to 
>>> devel-unsubscribe at lists.sailfishos.org
>> _______________________________________________
>> SailfishOS.org Devel mailing list
>> To unsubscribe, please send a mail to 
>> devel-unsubscribe at lists.sailfishos.org
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to 
> devel-unsubscribe at lists.sailfishos.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20140603/b8e26f70/attachment-0001.html>