2.0.3 built on linux 64-bit drops connection after a couple of minutes #101

rolfep · 2017-02-22T17:25:06Z

Howdy,
I am running Sachesi on ROSA Desktop Fresh R8 release. When I start Sachesi and connect my Q10 running 10.3.3.2205, a second possible device is detected and, soon, Sachesi loads all the info of my Q10.

I go to the backup tab, choose all three checkboxes, choose to back up blind, and select a save file location and name.

The spinner spins, progress stays at 0%, and, after a couple of minutes, the connection wizard is running, showing only one possibility, which I think is my HDHomeRun device on the lan.

The connection log contains:

The following message is repeated until the connection to Q10 is made:

08:58:52] Communication Error: 203 (Error transferring http://192.168.1.115/cgi-bin/discovery.cgi - server replied: Not Found) from 192.168.1.115
[08:58:52] Connected to MSM8960 V3.2.1.1 F NEWPORT Rev:17 at 169.254.0.1.
[08:59:22] Communication Error: 203 (Error transferring http://192.168.1.115/cgi-bin/discovery.cgi - server replied: Not Found) from 192.168.1.115
[08:59:22] Connected to MSM8960 V3.2.1.1 F NEWPORT Rev:17 at 169.254.0.1.
[09:04:39] Communication Error: 4 (Socket operation timed out) from 169.254.0.1
[09:04:40] Communication Error: 203 (Error transferring http://192.168.1.115/cgi-bin/discovery.cgi - server replied: Not Found) from 192.168.1.115

The previous message is repeated until I quit Sachesi.

192.168.1.115 is the static dhcp address I assign to the HDHomeRun in OpenWRT on my router.
192.168.1.218 is assigned to the Q10, btw, and I have that set by static dhcp in order to bookmark ftp connections and so forth.

My LAN is on 192.168.1.xxx and the usb-connected Q10 is reported by ifconfig at 169.254.0.2

I thought devices had to be on the same network to 'talk'? If I go into the Q10 usb settings to try to set an ip address on my LAN, the choices are limited to only start with 169.

Thanks.

The text was updated successfully, but these errors were encountered:

rolfep · 2017-02-22T18:21:33Z

On another machine on the lan, running Mageia release 5 (Official) for x86_64, I built 2.0.3 but get an error when trying to start it:

$ Sachesi 
Cannot mix incompatible Qt library (version 0x50201) with this library (version 0x50402)
Aborted

I can run Sachesi-1.4.0, here, ifconfig shows the ip as 169.254.0.2, and I just completed a backup to an NFS share on the LAN:

$ ll /mnt/stuff/q10/sachesi/20170222-full.bbb 
-rw-rw-r-- 1 rolf rolf 3667206547 02-22-2017 09:56 /mnt/stuff/q10/sachesi/20170222-full.bbb

Edit:
I had enabled developer mode for this 1.4.0 session, then disabled it, removed the device password, and connected to 1.4.0 again without password.

This session, ifconfig shows the Q10 ip as 169.254.237.190 and Sachesi-1.4.0 seems to perform as expected, remains connected and the only line in the Log is:

Connected to MSM8960_V3.2.1.1_F_NEWPORT_Rev:17 at 169.254.237.189.

xsacha · 2017-02-22T20:01:19Z

Unfortunately it is trying to connect to the HD Home Lan as it appears in the list and somehow met the criteria and had the right port open. I haven't run in to that issue before.
I guess the app needs to be changed to ignore that. In some versions it looks only for 169.*. You could temporarily disable wifi as a workaround.

rolfep · 2017-02-25T13:46:57Z

All the devices on the LAN are wired, except phones, and turning off wifi on the Q10 does not change the behavior, is probably not what you meant.

I pulled the ethernet cord from the HDHomeRun TV tuner and started Sachesi 2.0.3 with Q10 connected. It was recognized and, as before, I go to the backup tab, choose all three checkboxes, choose to back up blind, and select a save file location and name. After a few minutes of spinner and 0% progress reported, the connection is lost. The log is simpler, no HDHomeRun ip, only two lines:

[05:02:58] Connected to MSM8960 V3.2.1.1 F NEWPORT Rev:17 at 169.254.82.61.
[05:05:13] Communication Error: 4 (Socket operation timed out) from 169.254.82.61

I've been trying a lot of different strategies of downloading, building, and running Sachesi so, for a little precision, this Sachesi executable came from a download of Sachesi2.0.3-Linux.tar.bz2

Thanks.

camellan · 2017-11-12T15:30:24Z

I solved the connection problems, installing packages qml-module-qt-websockets and qml-module-qtwebsockets.

klango · 2017-11-18T17:52:51Z

Hi I ended up here when had the problem connecting my Passport (10.3.3.1435)

Sachesi 2.0.3
Dev mode on
Mass storage off
Errors
"Communication Error: 4 (Socket operation timed out) from 169.254.0.1" and
"Communication Error: 203 (Error downloading http://192.168.2.105/cgi-bin/discovery.cgi - server replied: Not Found) from 192.168.2.105"

Tried all suggested procedures with no luck. I changed the IP Adress on BB10 under Development mode to 169.254.0.5 (instead default 169.254.0.1)
Sachesi then was able to recognize. I hope this can help someone.

Cheers

Vistaus · 2018-01-23T12:58:45Z

I have the same problem. Tried @klango's suggestion of changing the IP address to 169.254.0.5 but that doesn't help :( Running Solus (Linux).

klango · 2018-01-23T20:40:36Z

Try dhcpclient and the adapter name Am Dienstag, 23. Januar 2018 schrieb Heimen Stoffels :

…

I have the same problem. Tried @klango <https://github.com/klango>'s suggestion of changing the IP address to 169.254.0.5 but that doesn't help :( Running Solus (Linux). — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#101 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALF0TsOsPEfNziu8hvmNN6S_mO0KXhpCks5tNdeHgaJpZM4MI8aG> .

Vistaus · 2018-01-23T21:21:09Z

@klango Thanks, but that doesn't help either :(

camellan · 2018-01-31T18:03:28Z

camellan@ladoga:~$ cat /etc/network/if-up.d/blackberry_dhcp

#!/bin/sh
if [ "$IFACE" = enp0s19f2u3 ]; then
dhcpcd enp0s19f2u3
fi
if [ "$IFACE" = usb0 ]; then
dhcpcd usb0
fi

xsacha · 2018-01-31T19:10:47Z

Thanks. This is a common issue on particular distros that do not automatically connect USB network devices.
Perhaps for security reasons.

Vistaus · 2018-01-31T19:13:31Z

@camellan @xsacha That's nice and all, but on Solus (which I'm using) there is no /etc/network folder.

xsacha · 2018-01-31T19:27:36Z

Do you have ability to run a dhcp daemon on an interface in Solus?

Vistaus · 2018-01-31T20:45:13Z

Yes, I already tried that several times to no avail. I mean: the command runs fine and stuff, but Sachesi still doesn't pick up my Passport.

camellan · 2018-02-01T01:44:58Z

In my case, dhclient did not work either, and dhcpcd did everything perfectly. And try installing packages qml-module-qt-websockets and qml-module-qtwebsockets.

Vistaus · 2018-02-01T12:55:28Z

@camellan Thanks. That did not really help much, although one particular error in the terminal is gone now. But Sachesi still doesn't connect.

Here's the output from dhcpcd:

[I] ╭─vistaus@solus /home/vistaus/Downloads  ‹system› 
╰─$  sudo dhcpcd enp0s20u2                                                                                                                                                                                                   ↵ 1
DUID 00:01:00:01:22:05:ca:41:a6:e4:b8:36:4b:a9
enp0s20u2: IAID b8:36:4b:a9
enp0s20u2: soliciting an IPv6 router
enp0s20u2: soliciting a DHCP lease
enp0s20u2: offered 169.254.0.2 from 169.254.0.1
enp0s20u2: leased 169.254.0.2 for 604800 seconds
enp0s20u2: adding route to 169.254.0.0/30
enp0s20u2: adding host route to 169.254.0.1
forked to background, child pid 1784
[I] ╭─vistaus@solus /home/vistaus/Downloads  ‹system› 
╰─$ sudo dhcpcd usb0
usb0: interface not found or invalid
dhcpcd exited
[I] ╭─vistaus@solus /home/vistaus/Downloads

So it seems to invoke the first command just right, but usb0 is not a valid interface?

camellan · 2018-02-01T15:16:04Z

This means that you do not have a usb0 interface. The name of the network interface Blackberry - enp0s20u2. You set the suggested me in the previous post packages?

Vistaus · 2018-02-01T15:38:26Z

Yes.

camellan · 2018-02-03T17:18:56Z

Display the output of the "ifconfig" command.

klango · 2018-02-03T22:11:16Z

In my case dhcpclient works and dhcpcd doesnt lol. Very akward. Running opensuse here. Am Samstag, 3. Februar 2018 schrieb Camellan :

Display the output of the "ifconfig" command. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.<

https://ci6.googleusercontent.com/proxy/AhxK5b-f4HzJ8829rygfBc44fzmUpBwNeF9uJbs8ciO8WkH00yPwVtoJsiaIY8sYsRvIOSkqlWVSRyNoV5l17szKfMZe38IGhASWHPYEk7nRtmxM27FZWFexJ1UrjtdiWnZ_SuK0-FWtqaUsdDLoR0L1Up22Zw=s0-d-e1-ft#https://github.com/notifications/beacon/ALF0TiBXZz-DFxG0dbB_Wb3nPyBh0Q_Xks5tRJUBgaJpZM4MI8aG.gif>

Vistaus · 2018-02-05T12:30:40Z

@camellan

╭─vistaus@solus /home/vistaus/Downloads  ‹system› 
╰─$ ifconfig
enp0s20u2 Link encap:Ethernet  HWaddr A6:E4:B8:36:4B:A9
          inet addr:169.254.205.130  Bcast:169.254.205.131  Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47 errors:0 dropped:0 overruns:0 frame:0
          TX packets:96 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11022  TX bytes:14710

enp0s20u2i2Link encap:Ethernet  HWaddr A6:E4:B8:36:4B:AB
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0  TX bytes:0

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:0.0.0.0  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:1431 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1431 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:112575  TX bytes:112575

wlp1s0    Link encap:Ethernet  HWaddr 58:91:CF:D3:0B:B2
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:672647 errors:0 dropped:0 overruns:0 frame:0
          TX packets:519133 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:665389603  TX bytes:167493765

[I] ╭─vistaus@solus /home/vistaus/Downloads  ‹system› 
╰─$

camellan · 2018-02-06T05:03:51Z

Well, the network is all right. Try installing the libssl0.9.8 package in addition. There are no more ideas ...

Vistaus · 2018-02-07T10:26:53Z

@camellan There's no libssl0.9.8 package in Solus. Where can I download the source code of libssl 0.9.8?

xsacha · 2018-02-07T10:28:05Z

If you compile from source you can use whatever libssl you want.
The binaries have a static libssl too. So not sure how this can be a problem.

Vistaus · 2018-02-09T10:22:55Z

I finally got it to compile from source again and now it connected just fine! Thanks for all of you guys help! :)

xsacha · 2018-02-09T10:28:21Z

Awesome news

klango · 2018-02-09T15:21:38Z

nice to know! great support from you guys 2018-02-09 11:28 GMT+01:00 Sacha <notifications@github.com>:

…

Awesome news — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#101 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALF0TqkT90WK-7-Fw1_Dzs4JGKUQwZL9ks5tTB3GgaJpZM4MI8aG> .

xsacha closed this as completed May 12, 2018

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

2.0.3 built on linux 64-bit drops connection after a couple of minutes #101

2.0.3 built on linux 64-bit drops connection after a couple of minutes #101

rolfep commented Feb 22, 2017

rolfep commented Feb 22, 2017 •

edited

Loading

xsacha commented Feb 22, 2017

rolfep commented Feb 25, 2017

camellan commented Nov 12, 2017

klango commented Nov 18, 2017

Vistaus commented Jan 23, 2018

klango commented Jan 23, 2018 via email

Vistaus commented Jan 23, 2018

camellan commented Jan 31, 2018 •

edited

Loading

xsacha commented Jan 31, 2018

Vistaus commented Jan 31, 2018

xsacha commented Jan 31, 2018

Vistaus commented Jan 31, 2018

camellan commented Feb 1, 2018

Vistaus commented Feb 1, 2018 •

edited

Loading

camellan commented Feb 1, 2018 •

edited

Loading

Vistaus commented Feb 1, 2018

camellan commented Feb 3, 2018

klango commented Feb 3, 2018 via email

Vistaus commented Feb 5, 2018

camellan commented Feb 6, 2018

Vistaus commented Feb 7, 2018

xsacha commented Feb 7, 2018

Vistaus commented Feb 9, 2018

xsacha commented Feb 9, 2018

klango commented Feb 9, 2018 via email

2.0.3 built on linux 64-bit drops connection after a couple of minutes #101

2.0.3 built on linux 64-bit drops connection after a couple of minutes #101

Comments

rolfep commented Feb 22, 2017

rolfep commented Feb 22, 2017 • edited Loading

xsacha commented Feb 22, 2017

rolfep commented Feb 25, 2017

camellan commented Nov 12, 2017

klango commented Nov 18, 2017

Vistaus commented Jan 23, 2018

klango commented Jan 23, 2018 via email

Vistaus commented Jan 23, 2018

camellan commented Jan 31, 2018 • edited Loading

xsacha commented Jan 31, 2018

Vistaus commented Jan 31, 2018

xsacha commented Jan 31, 2018

Vistaus commented Jan 31, 2018

camellan commented Feb 1, 2018

Vistaus commented Feb 1, 2018 • edited Loading

camellan commented Feb 1, 2018 • edited Loading

Vistaus commented Feb 1, 2018

camellan commented Feb 3, 2018

klango commented Feb 3, 2018 via email

Vistaus commented Feb 5, 2018

camellan commented Feb 6, 2018

Vistaus commented Feb 7, 2018

xsacha commented Feb 7, 2018

Vistaus commented Feb 9, 2018

xsacha commented Feb 9, 2018

klango commented Feb 9, 2018 via email

rolfep commented Feb 22, 2017 •

edited

Loading

camellan commented Jan 31, 2018 •

edited

Loading

Vistaus commented Feb 1, 2018 •

edited

Loading

camellan commented Feb 1, 2018 •

edited

Loading