<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Jarko and Juha<br>
<br>
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.<br>
<br>
In the meantime, some more background info.<br>
<br>
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.<br>
<br>
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<br>
<br>
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).<br>
<br>
During the problem I have been able to ssh into the SDK and Emulator
with no noticeable problem.<br>
<br>
Chris<br>
<br>
<br>
<div class="moz-cite-prefix">On 02.06.14 10:23, Jarko Vihriala
wrote:<br>
</div>
<blockquote
cite="mid:2747209DA5DF2045BD9A69BC25240F2437C23078@ORD2MBX02G.mex05.mlsrvr.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">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, <br>
- you could do a SSH session inside MerSDK and run journalctl
-fa in terminal <br>
- run deploy commands from Qt Creator<br>
- observe the output, is there a +10s timeout in the log
somewhere (looking at timestamps)?<br>
<br>
thanks, Jarko<br>
<br>
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF566181"><font
color="#000000" face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:devel-bounces@lists.sailfishos.org">devel-bounces@lists.sailfishos.org</a>
[<a class="moz-txt-link-abbreviated" href="mailto:devel-bounces@lists.sailfishos.org">devel-bounces@lists.sailfishos.org</a>] on behalf of Tone
Kastlunger [<a class="moz-txt-link-abbreviated" href="mailto:users.giulietta@gmail.com">users.giulietta@gmail.com</a>]<br>
<b>Sent:</b> Saturday, May 31, 2014 11:28 AM<br>
<b>To:</b> Sailfish OS Developers<br>
<b>Subject:</b> Re: [SailfishDevel] sporadic bouts of
"Could not connect to MerSDK Virtual Machine. Timeout
waiting for reply from server."<br>
</font><br>
</div>
<div>Hi I for once happen to get the issue every once in a
while even during binary deployment.
<div>Best,</div>
<div>tk<br>
<br>
On Thursday, May 29, 2014, Christopher Lamb <<a
moz-do-not-send="true"
href="mailto:christopher.lamb@thurweb.ch"
target="_blank">christopher.lamb@thurweb.ch</a>>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;
border-left:1px #ccc solid; padding-left:1ex">
Hi All<br>
<br>
I am still suffering from this issue, and getting more
and more frustrated!<br>
<br>
Right now "it" is refusing to deploy as RPM to the
Emulator.<br>
<br>
Is anything I can do to better debug / understand this
issue?<br>
<br>
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.<br>
<br>
All help greatly appreciated.<br>
<br>
Grüsse<br>
<br>
Chris<br>
<br>
<br>
<br>
On 28.04.14 08:01, <a moz-do-not-send="true">christopher.lamb@thurweb.ch</a>
wrote:<br>
<blockquote style="margin:0 0 0 .8ex; border-left:1px
#ccc solid; padding-left:1ex">
Hi<br>
<br>
Thanks.<br>
<br>
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.<br>
<br>
What I don't understand is, given the error says
"Could not connect to<br>
<blockquote style="margin:0 0 0 .8ex; border-left:1px
#ccc solid; padding-left:1ex">
<blockquote style="margin:0 0 0 .8ex;
border-left:1px #ccc solid; padding-left:1ex">
MerSDK Virtual Machine" why should a timeout for
connecting to a Jolla device play any role?<br>
</blockquote>
</blockquote>
<br>
Is the error misleading? is the problem actually in
connecting FROM the MerSDK to the Jolla?<br>
<br>
Chris<br>
<br>
{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-)<br>
<br>
<br>
<br>
Zitat von <a moz-do-not-send="true">fasza2mobile@gmail.com</a>:<br>
<br>
<blockquote style="margin:0 0 0 .8ex; border-left:1px
#ccc solid; padding-left:1ex">
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.<br>
<br>
On Sat Apr 26 2014 13:41:20 GMT+0100 (BST), <a
moz-do-not-send="true">christopher.lamb@thurweb.ch</a>
wrote:<br>
<blockquote style="margin:0 0 0 .8ex;
border-left:1px #ccc solid; padding-left:1ex">
Hi All<br>
<br>
I am suffering from sporadic bouts of the error:
"Could not connect to<br>
MerSDK Virtual Machine. Timeout waiting for reply
from server"<br>
<br>
One moment I can be happily hacking and deploying
code to my Jolla<br>
without error. Then I make a small change to the
code, try to deploy,<br>
and bing! the error rears its ugly head once again
like a scandinavian<br>
troll from under a bridge.<br>
<br>
<br>
Project ERROR: Could not connect to MerSDK Virtual
Machine. Timeout<br>
waiting for reply from server.<br>
14:02:28: The process<br>
"/Users/christopherlamb/.config/SailfishAlpha4/mer-sdk-tools/MerSDK/SailfishOS-armv7hl/deploy"
exited with code<br>
1.<br>
Error while building/deploying project
landed26_QT5 (kit:<br>
MerSDK-SailfishOS-armv7hl)<br>
When executing step 'Rpm'<br>
14:02:28: Elapsed time: 00:27.<br>
<br>
<br>
When the error occurs, there seem to be at least 2
variants:<br>
<br>
1) It will successfully deploy "As binaries"
without error, but will<br>
give the error on "deploy as RPM".<br>
<br>
2) Any kind of deploy gives the error.<br>
<br>
<br>
The strange thing is, that despite the error, it
does seem to<br>
(sometimes) deploy (or possibly partially deploy)
code.<br>
<br>
Right now I am getting the error in constellation
1), so according to<br>
the error a "deploy as RPM" should fail. Yet the
test below indicates<br>
that it is at least partially deploying code.<br>
<br>
<br>
[root@Jolla javascript]# pwd<br>
/usr/share/landed26_QT5/qml/javascript<br>
[root@Jolla javascript]#<br>
[root@Jolla javascript]# ls -ahl<br>
total 52K<br>
drwxr-xr-x 1 root root 180 2014-04-26 13:56 .<br>
drwxr-xr-x 1 root root 110 2014-04-26 13:56 ..<br>
-rw-r--r-- 1 root root 4.2K 2014-04-26 13:55
jsonpath.js<br>
-rw-r--r-- 1 root root 1.3K 2014-04-26 13:55
jsonSupport.js<br>
-rw-r--r-- 1 root root 349 2014-04-26 13:55
landed.js<br>
-rw-r--r-- 1 root root 1.2K 2014-04-26 13:55
message.js<br>
-rw-r--r-- 1 root root 8.4K 2014-04-26 13:55
readDataModel.js<br>
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32
settingsDB.js<br>
-rw-r--r-- 1 root root 5.2K 2014-04-26 13:55
writeDataModel.js<br>
<br>
//create new file testDeploy.js in QtCreator, then
attempt deploy as<br>
RPM. Error is generated. Repeat attempt to deploy
as RPM. Error is<br>
generated again.<br>
//but testDeploy.js is now on the Jolla!<br>
<br>
[root@Jolla javascript]# ls -ahl<br>
total 56K<br>
drwxr-xr-x 1 root root 206 2014-04-26 14:01 .<br>
drwxr-xr-x 1 root root 110 2014-04-26 14:01 ..<br>
-rw-r--r-- 1 root root 4.2K 2014-04-26 14:00
jsonpath.js<br>
-rw-r--r-- 1 root root 1.3K 2014-04-26 14:00
jsonSupport.js<br>
-rw-r--r-- 1 root root 349 2014-04-26 14:00
landed.js<br>
-rw-r--r-- 1 root root 1.2K 2014-04-26 14:00
message.js<br>
-rw-r--r-- 1 root root 8.4K 2014-04-26 14:00
readDataModel.js<br>
-rwxr-xr-x 1 root root 8.8K 2014-02-03 08:32
settingsDB.js<br>
-rw-r--r-- 1 root root 38 2014-04-26 14:00
testDeploy</blockquote>
</blockquote>
</blockquote>
To unsubscribe, please send a mail to <a
moz-do-not-send="true">devel-unsubscribe@lists.sailfishos.org</a><br>
</blockquote>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to <a class="moz-txt-link-abbreviated" href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a></pre>
</blockquote>
<br>
</body>
</html>