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
<christopher.l...@thurweb.ch <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
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 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
