[SailfishDevel] Timeout of MerSDK and the Emulator
Marcin Mielniczuk
marmistrzmar at gmail.com
Sun Jul 24 09:20:26 UTC 2016
Hi,
That was exactly the same problem. Checking those boxes fixed that for
me too.
Thanks!
On 23.07.2016 16:28, r0kk3rz wrote:
> Hi Guys,
>
> I just faced a similar issue and figured out that in the VBox network
> settings for the VM that the 'Cable Connected' checkbox for each
> adapter was unticked after a clean install.
>
> Checking those boxes fixed the issue
>
> Regards,
>
> Lewis Rockliffe
>
> On Thu, Jul 21, 2016 at 8:24 AM, Marcin Mielniczuk
> <marmistrzmar at gmail.com <mailto:marmistrzmar at gmail.com>> wrote:
>
> Hi,
>
> I tried zyppering the package, but
>
> Error code: connection failed
> Error message: Couldn't resolve host: 'releases.jolla.com
> <http://releases.jolla.com>'
>
> $ ping 8.8.8.8
> connect: Network is unreachable
>
> So I have no networking inside the VM.
>
> Last upgrade was a couple of days ago, next will be today. I did
> reboot ;)
>
> The port is open:
>
> State Recv-Q Send-Q
> Local Address:Port Peer Address:Port
> LISTEN 0 10 127.0.0.1:2222 <http://127.0.0.1:2222> *:*
> users:(("VirtualBox",pid=31842,fd=47))
>
> I'm the member of the following groups: adm, bumblebee, lp, sudo,
> vboxusers, wheel
>
> On 21.07.2016 07:50, Martin Kampas wrote:
>> Hi Marcin,
>>
>> failed.log, statefs.log: both failing statefs and tmpfiles are
>> known issues and shouldn't be related to this.
>>
>> sshd.log: according to the log you mistyped "sshd" as "ssh", but
>> anyway "sshd.service" is not used, instead you should check the
>> status of "sshd.socket". Also note that the config is
>> "/etc/ssh/sshd_config_engine".
>>
>> If the output of `journalctl _COMM=sshd -b` was empty after
>> trying to log in via SSH even with verbosity increased, then my
>> suspicion falls on host/virtualbox.
>>
>> You could also verify with tcpdump that it did not reach the
>> guest (install with `zypper in tcpdump`, run as `tcpdump -n port
>> ssh` inside the MerSDK VM). And on host you can check that the
>> ports are really occupied by virtualbox with `sudo ss -tpln |grep
>> ':222[23]\>'`.
>>
>> I am also using Arch Linux as you (last full system upgrade on
>> 2016-06-28) and it works well. Did you try reboot? :)
>>
>> BR,
>> Martin
>>
>
> --
> Marcin
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to
> devel-unsubscribe at lists.sailfishos.org
> <mailto:devel-unsubscribe at lists.sailfishos.org>
>
>
>
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscribe at lists.sailfishos.org
--
Marcin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.sailfishos.org/pipermail/devel/attachments/20160724/6a2c8c1e/attachment-0001.html>
More information about the Devel
mailing list