Re: [SailfishDevel] Error starting build Engine

2019-08-06 Thread Thomas Tanghus
On Tuesday, 6 August 2019 08.39.07 CEST Martin Kampas wrote:
> Hi Thomas,
> 
> All the errors in the log you shared are expected errors, they do not
> cause any issue.
> 
> The error "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
> exists" is also unrelated to your issues.
> 
> The errors from qt.network.ssl are something I would be worry about, but
> again it is not related to your issues.
> 
> What I bet is (was) the source of your issues is the content of your
> VirtualBox.xml.
> >>   
> > src="/home/tol/SailfishOS/mersdk/Sailfish OS Build
> > Engine/Sailfish
> > OS Build Engine.vbox"/>>
> >   
> >>   
> > src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish
> > OS
> > Emulator.vbox"/>>
> >   
> >>   
> > src="/home/thomas/SailfishOS/mersdk/MerSDK/MerSDK.vbox"/>
> >   
> >>   
> > src="/home/thomas/SailfishOS/mersdk/Sailfish OS Build
> > Engine/Sailfish OS Build Engine.vbox"/>>
> >   
> >>   
> > src="/home/thomas/SailfishOS/emulator/Sailfish OS Emulator
> > 3.1.0.12/Sailfish OS Emulator 3.1.0.12/Sailfish OS Emulator
> > 3.1.0.12.vbox"/>>
> > 
> > 
> 
> Did you change your user name in past or so?

Yes. I have just reinstalled - long time overdue - but kept my $HOME. And 
for historical reasons that used  to be 'tol' ;)
The weird thing is, that this error occurred *after* I had had wiped 
~/.config/SailfishOS-SDK and ~/.config/VirtualBox, so I don't know how it 
would have retained info about that installation..?

> Qt Creator uses VM names instead of UUIDs

Well, isn't that just plain stupid? ;)

> so which VM would it be trying to start with `vboxmanage startvm
> 'Sailfish OS Build Engine'`? The existing one under /home/thomas or the
> unavailable one under /home/tol?

Probably the latter. Anyhow, now it seems to be working perfectly.

> BR,
> Martin

Thank you so much to you and deloptes.


-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-06 Thread Martin Kampas
Hi Iosif,

> Under Win10 during installation I get the following error: SSH timeout.
> 
> If I press retry I continuously get the same error. If I press ignore I get
> the same error for all targets. At some time the installation succeeds, but
> cannot start the build engine

The installation is likely to be broken, but still it may be in a state that 
can be used to debug the 
connection issue more conveniently that during the installation, so let's 
continue with that.

Could you please try if you can SSH to the build engine from command line using 
something like 
this from the Git Bash? (Start the VM first, using VBox interface.)

ssh -p  -i /c/SailfishOS/vmshare/ssh/private_keys/engine/mersdk 
mersdk@localhost

If this fails, try with one or more '-v' to increase SSH's verbosity.

Next, could you please collect the debug output from Qt Creator? You should be 
able to enable 
the necessary logging categories by creating the file 
C:\SailfishOS\bin\QtProject\qtlogging.ini 
with the following content:

[Rules]
mer.vms*.debug=true
qtc.ssh.debug=true

(Check https://doc.qt.io/qt-5/qloggingcategory.html#configuring-categories for 
more info)

AFAIK on Windows you will also need to run Qt Creator under debugger in order 
to see the 
console output. I use WinDbg for that, in File -> Open Executable choose C:
\SailfishOS\bin\qtcreator.exe and also file Start directory in the same dialog 
as C:\SailfishOS\bin 
(important!).

BR,
Martin

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-06 Thread Martin Kampas
Hi Thomas,

All the errors in the log you shared are expected errors, they do not cause any 
issue.

The error "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already 
exists" is also unrelated to your issues.

The errors from qt.network.ssl are something I would be worry about, but again 
it is not related 
to your issues.

What I bet is (was) the source of your issues is the content of your 
VirtualBox.xml.

>  
> src="/home/tol/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish
> OS Build Engine.vbox"/>>   
>  
> src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish OS
> Emulator.vbox"/>>   
>  
> src="/home/thomas/SailfishOS/mersdk/MerSDK/MerSDK.vbox"/>
>   
>  
> src="/home/thomas/SailfishOS/mersdk/Sailfish OS Build
> Engine/Sailfish OS Build Engine.vbox"/>>   
>  
> src="/home/thomas/SailfishOS/emulator/Sailfish OS Emulator
> 3.1.0.12/Sailfish OS Emulator 3.1.0.12/Sailfish OS Emulator
> 3.1.0.12.vbox"/>> 
> 

Did you change your user name in past or so?

There are two entries with "/home/tol/" as the home directory, while the others 
have "/home/
thomas/". One of them is for a "Sailfish OS Build Engine" from some older SDK 
installation that I 
believe is not available anymore on that path under /home/tol, which would be a 
possible reason 
to end with VBOX_E_INVALID_OBJECT_STATE. Qt Creator uses VM names instead of 
UUIDs, so 
which VM would it be trying to start with `vboxmanage startvm 'Sailfish OS 
Build Engine'`? The 
existing one under /home/thomas or the unavailable one under /home/tol?

BR,
Martin

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-05 Thread Thomas Tanghus
After having reinstalled one more time, I was just about to throw in the 
towel - when, lo and behold, it was working!!! Except for having to 
authorize the device, it was out-of-the-box.

Anyways, this was what I had written, and warnings in the installation log 
were quite frightening. Link included.

On mandag den 5. august 2019 16.33.12 CEST deloptes wrote:
> I do not see these machines in the list
> 
> Try the maintenance tool to remove or clean up manually.

I ended with cleaning it up manually and reinstall from scratch.

This time I followed the details, and they left me to believe there's 
something wrong with the installation file.

The log was something like 25,000 lines; I managed to cut it down, but still 
too long for a mailing list, so here's a link: https://cloud.tanghus.net/s/
crxomHnHXQnZs6r

-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-05 Thread deloptes
Thomas Tanghus wrote:

> Yes, I do.
> I have these:
> 
>  src="/home/tol/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish OS
> Build Engine.vbox"/>  uuid="{1b641bc9-9c41-47fe-998a-8b8e91810c5b}"
> src="/home/tol/SailfishOS/emulator/Sailfish OS Emulator/Sailfish OS
> Emulator.vbox"/>  uuid="{aa96b162-4811-475c-bb57-8147302d6178}"
> src="/home/thomas/SailfishOS/mersdk/MerSDK/MerSDK.vbox"/>  uuid="{1944d1bb-99ff-4ac8-8507-1475fdbcfa6d}"
> src="/home/thomas/SailfishOS/mersdk/Sailfish OS Build Engine/Sailfish OS
> Build Engine.vbox"/>  uuid="{f8bc1e14-f8e1-48ed-a1a0-e51cd94296da}"
> src="/home/thomas/SailfishOS/emulator/Sailfish OS Emulator
> 3.1.0.12/Sailfish OS Emulator 3.1.0.12/Sailfish OS Emulator
> 3.1.0.12.vbox"/> 
> 
> I have no idea about what to keep and what to remove.
> Trying with the maintenance tool doesn't really get me any further. In the
> Add/Remove I don't really see what to do, and when trying "Update
> components" it prints "Cannot retrieve remote tree. No package source set
> for this applications"


Based on the error machine can not be found with id
- {b69ce3fb-2375-4f3a-8b48-8706f37a3a40} in kit 
SailfishOS-3.1.0.12-i486 (in Sailfish OS Build Engine)
- {8cb7bb7b-818d-4143-83bc-381d48275160} in kit 
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine)

I do not see these machines in the list

Try the maintenance tool to remove or clean up manually.

regards

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-05 Thread Thomas Tanghus
On mandag den 5. august 2019 13.22.09 CEST deloptes wrote:
> Thomas Tanghus wrote:
> > Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
> > exists":
> > 
> > I had to install/remove several times to get it in a semi-working state.
> > One of those times I manually removed the ~/SailfishOS and
> > ~/.config/SailfishOS- SDK and ~/.config/VirtualBox directories, but
> > apparently that wasn't enough..?
> > 
> > Any idea on how to get this thing movin' will be much appreciated.
> 
> In .config/VirtualBox/VirtualBox.xml - do you have under MachineRegistry
> entry with "Sailfish OS Emulator 3.1.0.12"?
> 
> Does the directory exist?
> 
> Perhaps it is better to use the SDKMaintenanceTool and try to repare or
> manually fix entry/directory in the MachineRegistry.
> 

Yes, I do. 
I have these:

  
  
  
  
  


I have no idea about what to keep and what to remove. 
Trying with the maintenance tool doesn't really get me any further. In the 
Add/Remove 
I don't really see what to do, and when trying "Update components" it prints 
"Cannot 
retrieve remote tree. No package source set for this applications"


-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-05 Thread deloptes
Iosif Hamlatzis wrote:

> Under Win10 during installation I get the following error: SSH timeout.

Sorry I do not use windows. On Linux I deleted everything and removed the
entry from the xml file. Windows might be registry thing - no idea - sorry.

regards

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

Re: [SailfishDevel] Error starting build Engine

2019-08-05 Thread Iosif Hamlatzis
How did you manage to install the SDK?

Under Win10 during installation I get the following error: SSH timeout.

If I press retry I continuously get the same error. If I press ignore I get
the same error for all targets. At some time the installation succeeds, but
cannot start the build engine

On Mon, 5 Aug 2019, 14:22 deloptes,  wrote:

> Thomas Tanghus wrote:
>
> > Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12"
> already
> > exists":
> >
> > I had to install/remove several times to get it in a semi-working state.
> > One of those times I manually removed the ~/SailfishOS and
> > ~/.config/SailfishOS- SDK and ~/.config/VirtualBox directories, but
> > apparently that wasn't enough..?
> >
> > Any idea on how to get this thing movin' will be much appreciated.
>
> In .config/VirtualBox/VirtualBox.xml - do you have under MachineRegistry
> entry with "Sailfish OS Emulator 3.1.0.12"?
>
> Does the directory exist?
>
> Perhaps it is better to use the SDKMaintenanceTool and try to repare or
> manually fix entry/directory in the MachineRegistry.
>
> I had similar but not same issue lately.
>
> regards
>
> ___
> 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] Error starting build Engine

2019-08-05 Thread deloptes
Thomas Tanghus wrote:

> Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already
> exists":
> 
> I had to install/remove several times to get it in a semi-working state.
> One of those times I manually removed the ~/SailfishOS and
> ~/.config/SailfishOS- SDK and ~/.config/VirtualBox directories, but
> apparently that wasn't enough..?
> 
> Any idea on how to get this thing movin' will be much appreciated.

In .config/VirtualBox/VirtualBox.xml - do you have under MachineRegistry
entry with "Sailfish OS Emulator 3.1.0.12"?

Does the directory exist? 

Perhaps it is better to use the SDKMaintenanceTool and try to repare or
manually fix entry/directory in the MachineRegistry.

I had similar but not same issue lately.

regards

___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org

[SailfishDevel] Error starting build Engine

2019-08-05 Thread Thomas Tanghus
Hi,

I finally got the newest SDK installed, but the build stops with: 

'Error while building/deploying project harbour-kitchentimer (kit: 
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine))
When executing step "Start Build Engine"'

In the console it prints:

---[snip]
MerConnection: Another instance for VM "Sailfish OS Emulator 3.1.0.12" already 
exists
Unknown debugger id {b69ce3fb-2375-4f3a-8b48-8706f37a3a40} in kit 
SailfishOS-3.1.0.12-i486 (in Sailfish OS Build Engine)
Unknown debugger id {8cb7bb7b-818d-4143-83bc-381d48275160} in kit 
SailfishOS-3.1.0.12-armv7hl (in Sailfish OS Build Engine)
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_num_locks
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_id_callback
qt.network.ssl: QSslSocket: cannot resolve CRYPTO_set_locking_callback
qt.network.ssl: QSslSocket: cannot resolve ERR_free_strings
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_cleanup
qt.network.ssl: QSslSocket: cannot resolve EVP_CIPHER_CTX_init
qt.network.ssl: QSslSocket: cannot resolve sk_new_null
qt.network.ssl: QSslSocket: cannot resolve sk_push
qt.network.ssl: QSslSocket: cannot resolve sk_free
qt.network.ssl: QSslSocket: cannot resolve sk_num
qt.network.ssl: QSslSocket: cannot resolve sk_pop_free
qt.network.ssl: QSslSocket: cannot resolve sk_value
qt.network.ssl: QSslSocket: cannot resolve SSL_library_init
qt.network.ssl: QSslSocket: cannot resolve SSL_load_error_strings
qt.network.ssl: QSslSocket: cannot resolve SSL_get_ex_new_index
qt.network.ssl: QSslSocket: cannot resolve SSLv3_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_client_method
qt.network.ssl: QSslSocket: cannot resolve SSLv3_server_method
qt.network.ssl: QSslSocket: cannot resolve SSLv23_server_method
qt.network.ssl: QSslSocket: cannot resolve X509_STORE_CTX_get_chain
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_noconf
qt.network.ssl: QSslSocket: cannot resolve OPENSSL_add_all_algorithms_conf
qt.network.ssl: QSslSocket: cannot resolve SSLeay
qt.network.ssl: QSslSocket: cannot resolve SSLeay_version
qt.network.ssl: QSslSocket: cannot call unresolved function SSLeay
qt.network.ssl: Incompatible version of OpenSSL
VBoxManage: error: Locking of attached media failed. A possible reason is that 
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), 
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
VBoxManage: error: Locking of attached media failed. A possible reason is that 
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), 
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
VBoxManage: error: Locking of attached media failed. A possible reason is that 
one of the media is attached to a running VM
VBoxManage: error: Details: code VBOX_E_INVALID_OBJECT_STATE (0x80bb0007), 
component SessionMachine, interface IMachine
MerConnection: "Failed to start virtual machine \"Sailfish OS Build Engine\""
---[snip]

Regarding "Another instance for VM "Sailfish OS Emulator 3.1.0.12" already 
exists":

I had to install/remove several times to get it in a semi-working state. One 
of those times I manually removed the ~/SailfishOS and ~/.config/SailfishOS-
SDK and ~/.config/VirtualBox directories, but apparently that wasn't enough..?

Any idea on how to get this thing movin' will be much appreciated.

-- 
Med venlig hilsen / Best regards

Thomas Tanghus

A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?


signature.asc
Description: This is a digitally signed message part.
___
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org