Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
This happens on Windows as well, after resume (Win7 in particular) On Tue, Jul 15, 2014 at 7:35 PM, Marcin M. wrote: > It happened to me after resuming my Linux box from suspend. Maybe this'll > give some clue. > -- > Marcin > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to > devel-unsubscr...@lists.sailfishos.org > ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
[SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
It happened to me after resuming my Linux box from suspend. Maybe this'll give some clue. -- Marcin ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
On 03.06.2014 19:57, Christopher Lamb wrote: Hi Juha I am now on the train. Deployment also works with WiFi active, but not properly connected. This means that - at least in my case - adding SailfishSDK to the /etc/hosts is a good fix for this error. Hi, I'm happy to hear that it works for you! I've added a section about this to the SDK known issues page [1] as you suggested. [1] https://sailfishos.org/wiki/SDK_Alpha_Qt5_Known_Issues Best regards, Juha ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi Juha I am now on the train. Deployment also works with WiFi active, but not properly connected. This means that - at least in my case - adding SailfishSDK to the /etc/hosts is a good fix for this error. I think this is one for the Known Issues page. I guess that (without the entry in /etc/hosts) active networking is required for "SailfishSDK" to be resolved. Of course I could SSH in, because I was using localhost as the machine name to connect (ssh -p -i ~/SailfishOS/vmshare/ssh/private_keys/engine/root root@localhost). Thanks for your help and forebearance, Chris On 03.06.14 17:15, Christopher Lamb wrote: Hi Juha I have edited my /etc/hosts to look like this: 127.0.0.1 localhost SailfishSDK 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost Now in the office, with WIFI turned off, and no ethernet plugged in, I can deploy as RPM successfully! So for the moment it looks like editing the /etc/hosts may be enough. Later this evening on train on the way home I will try with WiFi activated but no proper connection (which means it will probably default to the SBB/Swisscom WiFi which requires a logon to properly connect). Thanks Chris On 03.06.14 11:24, Juha Kallioinen wrote: 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.1localhost.localdomain localhost SailfishSDK Could you try this and let me know if there's any improvement? ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi Juha I have edited my /etc/hosts to look like this: 127.0.0.1 localhost SailfishSDK 255.255.255.255 broadcasthost ::1 localhost fe80::1%lo0 localhost Now in the office, with WIFI turned off, and no ethernet plugged in, I can deploy as RPM successfully! So for the moment it looks like editing the /etc/hosts may be enough. Later this evening on train on the way home I will try with WiFi activated but no proper connection (which means it will probably default to the SBB/Swisscom WiFi which requires a logon to properly connect). Thanks Chris On 03.06.14 11:24, Juha Kallioinen wrote: 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.1localhost.localdomain localhost SailfishSDK Could you try this and let me know if there's any improvement? ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
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.1localhost.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" 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-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Oh, that sounds like a lot worse case than mine. I can live with mine since it's easy to fix temporarily, but I truly hope the cause is found for your case and fixed permanently. - Saija Lähetetty iPadista > "Christopher Lamb" kirjoitti 3.6.2014 kello > 10.24: > > 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" 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-unsubscr...@lists.sailfishos.org >> ___ >> SailfishOS.org Devel mailing list >> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org > > ___ > SailfishOS.org Devel mailing list > To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
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" 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-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
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" 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-unsubscr...@lists.sailfishos.org ___ SailfishOS.org Devel mailing list To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
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-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi Jarko Have got on the train, started deploying, and get the problem. Below is output from the SDK and QtCreator. I am starting to wonder if the problem is related to networking in some way. This morning I successfully deployed at home - connected to the home wireless network. Now I am on the train - when I deployed / got the error) I was not connected to any network. (I have just opened the Jolla hotspot to send this mai). Chris SDK journalctl -fa output Apple-Pip:~ christopherlamb$ ssh -p -i ~/SailfishOS/vmshare/ssh/private_keys/engine/root root@localhost Last login: Wed Apr 30 07:00:35 2014 [root@SailfishSDK ~]# journalctl -fa Logs begin at Tue, 03 Jun 2014 06:00:29 +. Jun 03 06:48:07 SailfishSDK sshd[10191]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:48:07 SailfishSDK sshd[9470]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:48:07 SailfishSDK sshd[9447]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:48:07 SailfishSDK sshd[9447]: syslogin_perform_logout: logout() returned an error Jun 03 06:48:07 SailfishSDK systemd-logind[143]: Removed session c36. Jun 03 06:48:07 SailfishSDK systemd-logind[143]: Removed session c32. Jun 03 06:48:07 SailfishSDK systemd-logind[143]: Removed session c33. Jun 03 06:48:25 SailfishSDK sshd[10683]: Accepted publickey for root from 10.0.2.2 port 59953 ssh2 Jun 03 06:48:25 SailfishSDK systemd-logind[143]: New session c37 of user root. Jun 03 06:48:25 SailfishSDK sshd[10683]: pam_unix(sshd:session): session opened for user root by (uid=0) Jun 03 06:48:54 SailfishSDK sshd[10702]: Accepted publickey for mersdk from 10.0.2.2 port 59955 ssh2 Jun 03 06:48:54 SailfishSDK systemd-logind[143]: New session c38 of user mersdk. Jun 03 06:48:54 SailfishSDK sshd[10702]: pam_unix(sshd:session): session opened for user mersdk by (uid=0) Jun 03 06:49:00 SailfishSDK sshd[10707]: Accepted publickey for mersdk from 10.0.2.2 port 59958 ssh2 Jun 03 06:49:00 SailfishSDK systemd-logind[143]: New session c39 of user mersdk. Jun 03 06:49:00 SailfishSDK sshd[10707]: pam_unix(sshd:session): session opened for user mersdk by (uid=0) Jun 03 06:49:01 SailfishSDK sshd[10707]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:49:01 SailfishSDK systemd-logind[143]: Removed session c39. Jun 03 06:49:01 SailfishSDK sshd[11124]: Accepted publickey for mersdk from 10.0.2.2 port 59960 ssh2 Jun 03 06:49:01 SailfishSDK systemd-logind[143]: New session c40 of user mersdk. Jun 03 06:49:01 SailfishSDK sshd[11124]: pam_unix(sshd:session): session opened for user mersdk by (uid=0) Jun 03 06:49:04 SailfishSDK sshd[11124]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:49:04 SailfishSDK systemd-logind[143]: Removed session c40. Jun 03 06:49:04 SailfishSDK sshd[11423]: Accepted publickey for mersdk from 10.0.2.2 port 59962 ssh2 Jun 03 06:49:04 SailfishSDK systemd-logind[143]: New session c41 of user mersdk. Jun 03 06:49:04 SailfishSDK sshd[11423]: pam_unix(sshd:session): session opened for user mersdk by (uid=0) Jun 03 06:49:04 SailfishSDK sshd[10705]: dispatch_protocol_error: type 128 seq 5 Jun 03 06:50:07 SailfishSDK sshd[11426]: dispatch_protocol_error: type 128 seq 8 Jun 03 06:50:07 SailfishSDK sshd[10705]: dispatch_protocol_error: type 128 seq 6 Jun 03 06:50:07 SailfishSDK sshd[10705]: Received disconnect from 10.0.2.2: 11: Jun 03 06:50:07 SailfishSDK sshd[11423]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:50:07 SailfishSDK sshd[10702]: pam_unix(sshd:session): session closed for user mersdk Jun 03 06:50:07 SailfishSDK systemd-logind[143]: Removed session c41. Jun 03 06:50:07 SailfishSDK systemd-logind[143]: Removed session c38. //Qt Creator Output 08:49:00: Running steps for project beertent... 08:49:00: Starting: "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-i486/qmake" /Users/christopherlamb/SailfishProjects/beertent/beertent/beertent.pro -r -spec linux-g++ CONFIG+=debug CONFIG+=declarative_debug CONFIG+=qml_debug Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.Abqi8B 08:49:01: The process "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-i486/qmake" exited normally. 08:49:01: Starting: "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-i486/make" Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.vaeuWx mkdir -p translations && lupdate /home/mersdk/share/SailfishProjects/beertent/beertent/src /home/mersdk/share/SailfishProjects/beertent/beertent/qml -ts /home/mersdk/share/SailfishProjects/beertent/beertent/translations/beertent.ts Scanning directory '/home/mersdk/share/SailfishProjects/beertent/beertent/src'... Scanning directory '/home/mersdk/share/SailfishProjects/beertent/beertent/qml'... Updating '../beertent/translations/beertent.ts'... Found 7 source text(s) (0 new and 7 already existing) lrelease /home/mersdk/share/SailfishProjects
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi Jarko and Juha
Right now QtCreator is deploying as RPM without a problem - whereas last
week it was consistently giving the error. I am sure it will rear its
ugly head soon, so I will report back then following your advice.
In the meantime, some more background info.
I am on OSX 10.8.5 on a MBA. I am running the very latest SailfishOS
SDK, but have had this problem with previous versions to.
I have lots of applicaitons running on the MBA, including QtCreator
Lotus Notes, MS Office, Thunderbird, Chrome, Safari, Terminal, a VPN
etc. I almost never shutdown / restart unless forced to. . I move
between various networks - at home, office, hotspot on Jolla, VPN to
office etc. I do a lot of Sailfish Development mobile - on the train,
and thus often open and shut the laptop lid during development
The problem can occur out of the blue: i.e. 30 seconds previously it
successfully deployed - I make a small one line change to the code, try
to redeploy, and bingo: the problem occurs. The progress bar for the
build was at about 50 % complete or more. The timeout comes after
seconds rather than minutes (but I need to reproduce it again to give
more accurate timings).
During the problem I have been able to ssh into the SDK and Emulator
with no noticeable problem.
Chris
On 02.06.14 10:23, Jarko Vihriala wrote:
when that happens, have you tried to SSH into the MerSDK from command
line. We have seen issues where the SSH key exchange takes long time
for some reason , currently that's under investigation. If you want to
help in that,
- you could do a SSH session inside MerSDK and run journalctl -fa in
terminal
- run deploy commands from Qt Creator
- observe the output, is there a +10s timeout in the log somewhere
(looking at timestamps)?
thanks, Jarko
*From:* devel-boun...@lists.sailfishos.org
[devel-boun...@lists.sailfishos.org] on behalf of Tone Kastlunger
[users.giulie...@gmail.com]
*Sent:* Saturday, May 31, 2014 11:28 AM
*To:* Sailfish OS Developers
*Subject:* Re: [SailfishDevel] sporadic bouts of "Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi I for once happen to get the issue every once in a while even
during binary deployment.
Best,
tk
On Thursday, May 29, 2014, Christopher Lamb
mailto:christopher.l...@thurweb.ch>> wrote:
Hi All
I am still suffering from this issue, and getting more and more
frustrated!
Right now "it" is refusing to deploy as RPM to the Emulator.
Is anything I can do to better debug / understand this issue?
The timeout settings previously suggested are probably
red-herrings, as they apply to the device (phone / Emulator),
whereas the error is a timeout to the SDK.
All help greatly appreciated.
Grüsse
Chris
On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences /
devices and increased this from the default 2 secs to 10 secs.
This does seem to help, but as always with sporadic problems
only time will tell if this is a fix, or if the problem is
just dormant for a while.
What I don't understand is, given the error says "Could not
connect to
MerSDK Virtual Machine" why should a timeout for
connecting to a Jolla device play any role?
Is the error misleading? is the problem actually in connecting
FROM the MerSDK to the Jolla?
Chris
{1} when the preferences pane opens, at least on my OSX host
the timeout setting is "offscreen" in an embedded pane with
scroll bars in the middle of the preferences pane. Only if you
scroll down in the embedded pane are further settings
including the timeout revealed. Truly a wonderful bit of UI
design 8-)
Zitat von fasza2mob...@gmail.com:
I believe the timeout setting can be adjusted in
QtCreator where you set up your mer device(ssh password,
etc). By increasing this value you can probably prevent
the timeout issue altogether. I don't have the SDK in
front of me to give you the exact menu you need to open,
but it isn't too hard to find once you know what you're
looking for.
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST),
christopher.l...@thurweb.ch wrote:
Hi All
I am suffering from sporadic bouts of the error:
"Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from
server"
One moment I can be happily hacking and deploying code
to my Jolla
without error. Then I ma
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
On 28.04.2014 09:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix, or if the problem is just dormant for a while.
What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a
Jolla device play any role?
Is the error misleading? is the problem actually in connecting FROM
the MerSDK to the Jolla?
Hi, I can't seem to reproduce these timeout problems when I'm testing
this. I've tried on Linux and Windows and a bit less on a Mac. I wish I
could, so I could debug this because I can't fix it if I can't reproduce it.
The error you get might be a bit misleading. The deploy operation does
currently go through the MerSDK machine:
Qt Creator -> ssh mersdk -> rsync to device (from mersdk) -> ssh to
device to install package (from mersdk)
Qt Creator -> ssh to device to run the app
So Qt Creator does not really know what happens inside MerSDK as it
requests the deploy operation and if a timeout happens at some point, it
will just look like a timeout connecting to MerSDK.
Can you describe in detail what happens when you get the timeout? Does
it timeout after 2 seconds or 10 seconds or a minute or two?
Chris
{1} when the preferences pane opens, at least on my OSX host the
timeout setting is "offscreen" in an embedded pane with scroll bars in
the middle of the preferences pane. Only if you scroll down in the
embedded pane are further settings including the timeout revealed.
Truly a wonderful bit of UI design 8-)
Yes, I noted that comment earlier and tried for a few minutes to
rearrange the view. Failed. It's in the "todo when all the fires are
out" - list.
Best regards,
Juha
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
when that happens, have you tried to SSH into the MerSDK from command line. We
have seen issues where the SSH key exchange takes long time for some reason ,
currently that's under investigation. If you want to help in that,
- you could do a SSH session inside MerSDK and run journalctl -fa in terminal
- run deploy commands from Qt Creator
- observe the output, is there a +10s timeout in the log somewhere (looking at
timestamps)?
thanks, Jarko
From: devel-boun...@lists.sailfishos.org [devel-boun...@lists.sailfishos.org]
on behalf of Tone Kastlunger [users.giulie...@gmail.com]
Sent: Saturday, May 31, 2014 11:28 AM
To: Sailfish OS Developers
Subject: Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK
Virtual Machine. Timeout waiting for reply from server."
Hi I for once happen to get the issue every once in a while even during binary
deployment.
Best,
tk
On Thursday, May 29, 2014, Christopher Lamb
mailto:christopher.l...@thurweb.ch>> wrote:
Hi All
I am still suffering from this issue, and getting more and more frustrated!
Right now "it" is refusing to deploy as RPM to the Emulator.
Is anything I can do to better debug / understand this issue?
The timeout settings previously suggested are probably red-herrings, as they
apply to the device (phone / Emulator), whereas the error is a timeout to the
SDK.
All help greatly appreciated.
Grüsse
Chris
On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices and
increased this from the default 2 secs to 10 secs. This does seem to help, but
as always with sporadic problems only time will tell if this is a fix, or if
the problem is just dormant for a while.
What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a Jolla device
play any role?
Is the error misleading? is the problem actually in connecting FROM the MerSDK
to the Jolla?
Chris
{1} when the preferences pane opens, at least on my OSX host the timeout
setting is "offscreen" in an embedded pane with scroll bars in the middle of
the preferences pane. Only if you scroll down in the embedded pane are further
settings including the timeout revealed. Truly a wonderful bit of UI design 8-)
Zitat von fasza2mob...@gmail.com:
I believe the timeout setting can be adjusted in QtCreator where you set up
your mer device(ssh password, etc). By increasing this value you can probably
prevent the timeout issue altogether. I don't have the SDK in front of me to
give you the exact menu you need to open, but it isn't too hard to find once
you know what you're looking for.
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST), christopher.l...@thurweb.ch wrote:
Hi All
I am suffering from sporadic bouts of the error: "Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server"
One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing! the error rears its ugly head once again like a scandinavian
troll from under a bridge.
Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server.
14:02:28: The process
"/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy"
exited with code
1.
Error while building/deploying project landed26_QT5 (kit:
MerSDK-SailfishOS-armv7hl)
When executing step 'Rpm'
14:02:28: Elapsed time: 00:27.
When the error occurs, there seem to be at least 2 variants:
1) It will successfully deploy "As binaries" without error, but will
give the error on "deploy as RPM".
2) Any kind of deploy gives the error.
The strange thing is, that despite the error, it does seem to
(sometimes) deploy (or possibly partially deploy) code.
Right now I am getting the error in constellation 1), so according to
the error a "deploy as RPM" should fail. Yet the test below indicates
that it is at least partially deploying code.
[root@Jolla javascript]# pwd
/usr/share/landed26_QT5/qml/javascript
[root@Jolla javascript]#
[root@Jolla javascript]# ls -ahl
total 52K
drwxr-xr-x 1 root root 180 2014-04-26 13:56 .
drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js
//create new file testDeploy.js in QtCreator, then attempt deploy as
RPM. Error is generated. Repeat attempt to deploy as RP
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi I for once happen to get the issue every once in a while even during
binary deployment.
Best,
tk
On Thursday, May 29, 2014, Christopher Lamb
wrote:
> Hi All
>
> I am still suffering from this issue, and getting more and more frustrated!
>
> Right now "it" is refusing to deploy as RPM to the Emulator.
>
> Is anything I can do to better debug / understand this issue?
>
> The timeout settings previously suggested are probably red-herrings, as
> they apply to the device (phone / Emulator), whereas the error is a timeout
> to the SDK.
>
> All help greatly appreciated.
>
> Grüsse
>
> Chris
>
>
>
> On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
>
> Hi
>
> Thanks.
>
> I found a well hidden {1} timeout setting in the preferences / devices and
> increased this from the default 2 secs to 10 secs. This does seem to help,
> but as always with sporadic problems only time will tell if this is a fix,
> or if the problem is just dormant for a while.
>
> What I don't understand is, given the error says "Could not connect to
>
> MerSDK Virtual Machine" why should a timeout for connecting to a Jolla
> device play any role?
>
>
> Is the error misleading? is the problem actually in connecting FROM the
> MerSDK to the Jolla?
>
> Chris
>
> {1} when the preferences pane opens, at least on my OSX host the timeout
> setting is "offscreen" in an embedded pane with scroll bars in the middle
> of the preferences pane. Only if you scroll down in the embedded pane are
> further settings including the timeout revealed. Truly a wonderful bit of
> UI design 8-)
>
>
>
> Zitat von fasza2mob...@gmail.com:
>
> I believe the timeout setting can be adjusted in QtCreator where you set
> up your mer device(ssh password, etc). By increasing this value you can
> probably prevent the timeout issue altogether. I don't have the SDK in
> front of me to give you the exact menu you need to open, but it isn't too
> hard to find once you know what you're looking for.
>
> On Sat Apr 26 2014 13:41:20 GMT+0100 (BST), christopher.l...@thurweb.ch
> wrote:
>
> Hi All
>
> I am suffering from sporadic bouts of the error: "Could not connect to
> MerSDK Virtual Machine. Timeout waiting for reply from server"
>
> One moment I can be happily hacking and deploying code to my Jolla
> without error. Then I make a small change to the code, try to deploy,
> and bing! the error rears its ugly head once again like a scandinavian
> troll from under a bridge.
>
>
> Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
> waiting for reply from server.
> 14:02:28: The process
> "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-
> tools/MerSDK/SailfishOS-armv7hl/deploy" exited with code
> 1.
> Error while building/deploying project landed26_QT5 (kit:
> MerSDK-SailfishOS-armv7hl)
> When executing step 'Rpm'
> 14:02:28: Elapsed time: 00:27.
>
>
> When the error occurs, there seem to be at least 2 variants:
>
> 1) It will successfully deploy "As binaries" without error, but will
> give the error on "deploy as RPM".
>
> 2) Any kind of deploy gives the error.
>
>
> The strange thing is, that despite the error, it does seem to
> (sometimes) deploy (or possibly partially deploy) code.
>
> Right now I am getting the error in constellation 1), so according to
> the error a "deploy as RPM" should fail. Yet the test below indicates
> that it is at least partially deploying code.
>
>
> [root@Jolla javascript]# pwd
> /usr/share/landed26_QT5/qml/javascript
> [root@Jolla javascript]#
> [root@Jolla javascript]# ls -ahl
> total 52K
> drwxr-xr-x 1 root root 180 2014-04-26 13:56 .
> drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..
> -rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
> -rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
> -rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js
> -rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
> -rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
> -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
> -rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js
>
> //create new file testDeploy.js in QtCreator, then attempt deploy as
> RPM. Error is generated. Repeat attempt to deploy as RPM. Error is
> generated again.
> //but testDeploy.js is now on the Jolla!
>
> [root@Jolla javascript]# ls -ahl
> total 56K
> drwxr-xr-x 1 root root 206 2014-04-26 14:01 .
> drwxr-xr-x 1 root root 110 2014-04-26 14:01 ..
> -rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js
> -rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js
> -rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js
> -rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js
> -rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js
> -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
> -rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy
>
> To unsubscribe, please send a mail to
> devel-unsubscr...@lists.sailfishos.org
>
___
SailfishOS.org Devel mailing lis
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi All
I am still suffering from this issue, and getting more and more frustrated!
Right now "it" is refusing to deploy as RPM to the Emulator.
Is anything I can do to better debug / understand this issue?
The timeout settings previously suggested are probably red-herrings, as
they apply to the device (phone / Emulator), whereas the error is a
timeout to the SDK.
All help greatly appreciated.
Grüsse
Chris
On 28.04.14 08:01, christopher.l...@thurweb.ch wrote:
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix, or if the problem is just dormant for a while.
What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a
Jolla device play any role?
Is the error misleading? is the problem actually in connecting FROM
the MerSDK to the Jolla?
Chris
{1} when the preferences pane opens, at least on my OSX host the
timeout setting is "offscreen" in an embedded pane with scroll bars in
the middle of the preferences pane. Only if you scroll down in the
embedded pane are further settings including the timeout revealed.
Truly a wonderful bit of UI design 8-)
Zitat von fasza2mob...@gmail.com:
I believe the timeout setting can be adjusted in QtCreator where you
set up your mer device(ssh password, etc). By increasing this value
you can probably prevent the timeout issue altogether. I don't have
the SDK in front of me to give you the exact menu you need to open,
but it isn't too hard to find once you know what you're looking for.
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST),
christopher.l...@thurweb.ch wrote:
Hi All
I am suffering from sporadic bouts of the error: "Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server"
One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing! the error rears its ugly head once again like a scandinavian
troll from under a bridge.
Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server.
14:02:28: The process
"/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy"
exited with code
1.
Error while building/deploying project landed26_QT5 (kit:
MerSDK-SailfishOS-armv7hl)
When executing step 'Rpm'
14:02:28: Elapsed time: 00:27.
When the error occurs, there seem to be at least 2 variants:
1) It will successfully deploy "As binaries" without error, but will
give the error on "deploy as RPM".
2) Any kind of deploy gives the error.
The strange thing is, that despite the error, it does seem to
(sometimes) deploy (or possibly partially deploy) code.
Right now I am getting the error in constellation 1), so according to
the error a "deploy as RPM" should fail. Yet the test below indicates
that it is at least partially deploying code.
[root@Jolla javascript]# pwd
/usr/share/landed26_QT5/qml/javascript
[root@Jolla javascript]#
[root@Jolla javascript]# ls -ahl
total 52K
drwxr-xr-x 1 root root 180 2014-04-26 13:56 .
drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js
//create new file testDeploy.js in QtCreator, then attempt deploy as
RPM. Error is generated. Repeat attempt to deploy as RPM. Error is
generated again.
//but testDeploy.js is now on the Jolla!
[root@Jolla javascript]# ls -ahl
total 56K
drwxr-xr-x 1 root root 206 2014-04-26 14:01 .
drwxr-xr-x 1 root root 110 2014-04-26 14:01 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 14:00 writeDataModel.js
So it looks like that after a second failed deploy, the file is
actually deployed!
During bouts of the error, QtCreator seems to get out of sync the true
status of the SDK VM (indicated by the VirtualBox GUI). So QtCreator
may show the green "Start SDK" status, even though the SDK is already
running. Or QtCreator shows the same button grey.
So far I have not found any lasting solution to prevent the error in
the first place. Sometimes it goes awa
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi
Thanks.
I found a well hidden {1} timeout setting in the preferences / devices
and increased this from the default 2 secs to 10 secs. This does seem
to help, but as always with sporadic problems only time will tell if
this is a fix, or if the problem is just dormant for a while.
What I don't understand is, given the error says "Could not connect to
MerSDK Virtual Machine" why should a timeout for connecting to a
Jolla device play any role?
Is the error misleading? is the problem actually in connecting FROM
the MerSDK to the Jolla?
Chris
{1} when the preferences pane opens, at least on my OSX host the
timeout setting is "offscreen" in an embedded pane with scroll bars in
the middle of the preferences pane. Only if you scroll down in the
embedded pane are further settings including the timeout revealed.
Truly a wonderful bit of UI design 8-)
Zitat von fasza2mob...@gmail.com:
I believe the timeout setting can be adjusted in QtCreator where
you set up your mer device(ssh password, etc). By increasing this
value you can probably prevent the timeout issue altogether. I don't
have the SDK in front of me to give you the exact menu you need to
open, but it isn't too hard to find once you know what you're
looking for.
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST),
christopher.l...@thurweb.ch wrote:
Hi All
I am suffering from sporadic bouts of the error: "Could not connect to
MerSDK Virtual Machine. Timeout waiting for reply from server"
One moment I can be happily hacking and deploying code to my Jolla
without error. Then I make a small change to the code, try to deploy,
and bing! the error rears its ugly head once again like a scandinavian
troll from under a bridge.
Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server.
14:02:28: The process
"/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy" exited with
code
1.
Error while building/deploying project landed26_QT5 (kit:
MerSDK-SailfishOS-armv7hl)
When executing step 'Rpm'
14:02:28: Elapsed time: 00:27.
When the error occurs, there seem to be at least 2 variants:
1) It will successfully deploy "As binaries" without error, but will
give the error on "deploy as RPM".
2) Any kind of deploy gives the error.
The strange thing is, that despite the error, it does seem to
(sometimes) deploy (or possibly partially deploy) code.
Right now I am getting the error in constellation 1), so according to
the error a "deploy as RPM" should fail. Yet the test below indicates
that it is at least partially deploying code.
[root@Jolla javascript]# pwd
/usr/share/landed26_QT5/qml/javascript
[root@Jolla javascript]#
[root@Jolla javascript]# ls -ahl
total 52K
drwxr-xr-x 1 root root 180 2014-04-26 13:56 .
drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js
//create new file testDeploy.js in QtCreator, then attempt deploy as
RPM. Error is generated. Repeat attempt to deploy as RPM. Error is
generated again.
//but testDeploy.js is now on the Jolla!
[root@Jolla javascript]# ls -ahl
total 56K
drwxr-xr-x 1 root root 206 2014-04-26 14:01 .
drwxr-xr-x 1 root root 110 2014-04-26 14:01 ..
-rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js
-rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js
-rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js
-rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js
-rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js
-rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy.js
-rw-r--r-- 1 root root 5.2K 2014-04-26 14:00 writeDataModel.js
So it looks like that after a second failed deploy, the file is
actually deployed!
During bouts of the error, QtCreator seems to get out of sync the true
status of the SDK VM (indicated by the VirtualBox GUI). So QtCreator
may show the green "Start SDK" status, even though the SDK is already
running. Or QtCreator shows the same button grey.
So far I have not found any lasting solution to prevent the error in
the first place. Sometimes it goes away on its own accord, and
sometimes various combinations of restarting VirtualBox, the VM,
QtCreator or my development host help for a while (but rarely for long).
What exactly is the timeout? Is this a property that I can increase?
The "known issues" page of the Alpha (Qt4.8) SDK suggests:
https://sailfishos.org/wiki/SDK_Alpha_Known_Issues
VBoxManage modifyvm MerSDK --natdnshostresolver1 on
But that has not helped.
I am running the very latest versio
Re: [SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
I believe the timeout setting can be adjusted in QtCreator where you set up your mer device(ssh password, etc). By increasing this value you can probably prevent the timeout issue altogether. I don't have the SDK in front of me to give you the exact menu you need to open, but it isn't too hard to find once you know what you're looking for. On Sat Apr 26 2014 13:41:20 GMT+0100 (BST), christopher.l...@thurweb.ch wrote: > Hi All > > I am suffering from sporadic bouts of the error: "Could not connect to > MerSDK Virtual Machine. Timeout waiting for reply from server" > > One moment I can be happily hacking and deploying code to my Jolla > without error. Then I make a small change to the code, try to deploy, > and bing! the error rears its ugly head once again like a scandinavian > troll from under a bridge. > > > Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout > waiting for reply from server. > 14:02:28: The process > "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy" > exited with code > 1. > Error while building/deploying project landed26_QT5 (kit: > MerSDK-SailfishOS-armv7hl) > When executing step 'Rpm' > 14:02:28: Elapsed time: 00:27. > > > When the error occurs, there seem to be at least 2 variants: > > 1) It will successfully deploy "As binaries" without error, but will > give the error on "deploy as RPM". > > 2) Any kind of deploy gives the error. > > > The strange thing is, that despite the error, it does seem to > (sometimes) deploy (or possibly partially deploy) code. > > Right now I am getting the error in constellation 1), so according to > the error a "deploy as RPM" should fail. Yet the test below indicates > that it is at least partially deploying code. > > > [root@Jolla javascript]# pwd > /usr/share/landed26_QT5/qml/javascript > [root@Jolla javascript]# > [root@Jolla javascript]# ls -ahl > total 52K > drwxr-xr-x 1 root root 180 2014-04-26 13:56 . > drwxr-xr-x 1 root root 110 2014-04-26 13:56 .. > -rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js > -rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js > -rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js > -rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js > -rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js > -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js > -rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js > > //create new file testDeploy.js in QtCreator, then attempt deploy as > RPM. Error is generated. Repeat attempt to deploy as RPM. Error is > generated again. > //but testDeploy.js is now on the Jolla! > > [root@Jolla javascript]# ls -ahl > total 56K > drwxr-xr-x 1 root root 206 2014-04-26 14:01 . > drwxr-xr-x 1 root root 110 2014-04-26 14:01 .. > -rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js > -rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js > -rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js > -rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js > -rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js > -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js > -rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy.js > -rw-r--r-- 1 root root 5.2K 2014-04-26 14:00 writeDataModel.js > > So it looks like that after a second failed deploy, the file is > actually deployed! > > > During bouts of the error, QtCreator seems to get out of sync the true > status of the SDK VM (indicated by the VirtualBox GUI). So QtCreator > may show the green "Start SDK" status, even though the SDK is already > running. Or QtCreator shows the same button grey. > > So far I have not found any lasting solution to prevent the error in > the first place. Sometimes it goes away on its own accord, and > sometimes various combinations of restarting VirtualBox, the VM, > QtCreator or my development host help for a while (but rarely for long). > > What exactly is the timeout? Is this a property that I can increase? > > The "known issues" page of the Alpha (Qt4.8) SDK suggests: > > https://sailfishos.org/wiki/SDK_Alpha_Known_Issues > > VBoxManage modifyvm MerSDK --natdnshostresolver1 on > > But that has not helped. > > I am running the very latest version of the SailfishOS SDK, but had > the same error with previous versions. > > Any ideas? > > Chris > > > > ___ > SailfishOS.org Devel mailing list > ___ SailfishOS.org Devel mailing list
[SailfishDevel] sporadic bouts of "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server."
Hi All I am suffering from sporadic bouts of the error: "Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server" One moment I can be happily hacking and deploying code to my Jolla without error. Then I make a small change to the code, try to deploy, and bing! the error rears its ugly head once again like a scandinavian troll from under a bridge. Project ERROR: Could not connect to MerSDK Virtual Machine. Timeout waiting for reply from server. 14:02:28: The process "/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy" exited with code 1. Error while building/deploying project landed26_QT5 (kit: MerSDK-SailfishOS-armv7hl) When executing step 'Rpm' 14:02:28: Elapsed time: 00:27. When the error occurs, there seem to be at least 2 variants: 1) It will successfully deploy "As binaries" without error, but will give the error on "deploy as RPM". 2) Any kind of deploy gives the error. The strange thing is, that despite the error, it does seem to (sometimes) deploy (or possibly partially deploy) code. Right now I am getting the error in constellation 1), so according to the error a "deploy as RPM" should fail. Yet the test below indicates that it is at least partially deploying code. [root@Jolla javascript]# pwd /usr/share/landed26_QT5/qml/javascript [root@Jolla javascript]# [root@Jolla javascript]# ls -ahl total 52K drwxr-xr-x 1 root root 180 2014-04-26 13:56 . drwxr-xr-x 1 root root 110 2014-04-26 13:56 .. -rw-r--r-- 1 root root 4.2K 2014-04-26 13:55 jsonpath.js -rw-r--r-- 1 root root 1.3K 2014-04-26 13:55 jsonSupport.js -rw-r--r-- 1 root root 349 2014-04-26 13:55 landed.js -rw-r--r-- 1 root root 1.2K 2014-04-26 13:55 message.js -rw-r--r-- 1 root root 8.4K 2014-04-26 13:55 readDataModel.js -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js -rw-r--r-- 1 root root 5.2K 2014-04-26 13:55 writeDataModel.js //create new file testDeploy.js in QtCreator, then attempt deploy as RPM. Error is generated. Repeat attempt to deploy as RPM. Error is generated again. //but testDeploy.js is now on the Jolla! [root@Jolla javascript]# ls -ahl total 56K drwxr-xr-x 1 root root 206 2014-04-26 14:01 . drwxr-xr-x 1 root root 110 2014-04-26 14:01 .. -rw-r--r-- 1 root root 4.2K 2014-04-26 14:00 jsonpath.js -rw-r--r-- 1 root root 1.3K 2014-04-26 14:00 jsonSupport.js -rw-r--r-- 1 root root 349 2014-04-26 14:00 landed.js -rw-r--r-- 1 root root 1.2K 2014-04-26 14:00 message.js -rw-r--r-- 1 root root 8.4K 2014-04-26 14:00 readDataModel.js -rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32 settingsDB.js -rw-r--r-- 1 root root 38 2014-04-26 14:00 testDeploy.js -rw-r--r-- 1 root root 5.2K 2014-04-26 14:00 writeDataModel.js So it looks like that after a second failed deploy, the file is actually deployed! During bouts of the error, QtCreator seems to get out of sync the true status of the SDK VM (indicated by the VirtualBox GUI). So QtCreator may show the green "Start SDK" status, even though the SDK is already running. Or QtCreator shows the same button grey. So far I have not found any lasting solution to prevent the error in the first place. Sometimes it goes away on its own accord, and sometimes various combinations of restarting VirtualBox, the VM, QtCreator or my development host help for a while (but rarely for long). What exactly is the timeout? Is this a property that I can increase? The "known issues" page of the Alpha (Qt4.8) SDK suggests: https://sailfishos.org/wiki/SDK_Alpha_Known_Issues VBoxManage modifyvm MerSDK --natdnshostresolver1 on But that has not helped. I am running the very latest version of the SailfishOS SDK, but had the same error with previous versions. Any ideas? Chris ___ SailfishOS.org Devel mailing list
