08-21-2017, 09:02 AM | #16 |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
|
08-21-2017, 09:12 AM | #17 |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
I didn't realize there was a misunderstanding on your part.
I should have been more specific. My apologies. |
08-22-2017, 11:42 PM | #18 |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
Hello.
I've got the files. There's something about a 'port 54982'. |
08-23-2017, 05:01 AM | #19 | |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
The debug log tells us that CC is able to ask calibre if it is there. The sequence that CC uses is:
Code:
SMART_DEV ( 39.22: 37.046) run received broadcast ('localhost', ('192.168.0.101', 54982)) calibre wireless device client (on XXXXX);8080,9090 One way to test the above hypothesis - that something is blocking incoming connections - is to connect to calibre using a web browser. It would be 2-step test. The first step is to connect from the localhost -- the laptop itself -- to avoid the router and the incoming firewall. Open a web browser on the laptop and connect to 127.0.0.1:9090. When I do that on my laptop I get the following lines in the calibre debug log, which up to the last line are what should appear when CC connect. Code:
SMART_DEV ( 15.14: 13.011) run attempt to open device socket SMART_DEV ( 15.18: 0.034) open SMART_DEV ( 15.19: 0.001) _call_client GET_INITIALIZATION_INFO wfr True SMART_DEV ( 15.21: 0.006) _receive_from_client protocol error -- empty json string SMART_DEV ( 15.23: 0.000) _call_client other exception Assuming that the first step works, the second step is to try the same thing from the web browser on your device. Open that browser and connect to 192.168.0.100:9090. You should see exactly the same messages in the debug log. If connecting from your device using the web browser generates those lines then the only possibility left is that something in calibre is preventing the wireless device driver from "seeing" the connection request in the 5 seconds that CC is willing to wait. If this is the case I could give you a version of CC that waits for much longer, say 30 seconds, to see if the problem is simply one of time. We will cross this bridge when we come to it. If the first step does not work then one possibility is to change CC's port to something way up in the not-normally-used range, for example 42876, then try the same steps. You change CC's port by stopping the wireless device driver (calibre / Connect/Share) then starting it again. You will see a dialog where you can set the port. BTW: the Similar Stories plugin you have installed is broken. I is still using the old version of the graphic toolkit QT. I wonder what all those XmbTextListToTextProperty result code -2 lines are, and what side effects, if any, the error might have. |
|
08-23-2017, 08:59 AM | #20 |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
First step didn't work. I changed the port too.
No port forwarding rules. My router's more 3g WiFi Dongle. Can be used as both a modem and router. Pretty basic settings on its webpage. I don't think it's the firewall as it's turned off, but perhaps I should read up on it. BTW, anything more than 32000 (port number) is invalid according to Calibre. Also, removed the Similar Stories plugin. Last edited by Wryhder; 08-23-2017 at 09:12 AM. Reason: added the last two lines |
08-23-2017, 12:13 PM | #21 | |||
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
Quote:
Quote:
It is time to check some really basic things. The examples, when I can provide them, are from my debian VPS. Open a terminal and run netstat. Verify that calibre is actually listening on the port and that the listening ip address is 0.0.0.0. Code:
www:~# netstat -t -l -p -v Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name [...] tcp 0 0 *:9192 *:* LISTEN 14151/calibre-serve tcp 0 0 localhost:mysql *:* LISTEN 14735/mysqld [...] Code:
iptables -L -vn > aaaaa Code:
Chain net2fw (1 references) pkts bytes target prot opt in out source destination 508K 29M ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:80 /* HTTP */ As far as I can tell, Ubuntu uses the firewall ufw. I don't use ufw so I can't provide any examples. ufw can do process-based filtering. Try the commend Code:
ufw status Try running the command Code:
ufw app list |
|||
08-23-2017, 02:32 PM | #22 |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Also, just to make sure that the web browser works the way we expect, start calibre then in the web browser try to open 127.0.0.1:8080. That should open the content server. CC can see that so it should be visible from the laptop.
|
08-30-2017, 08:54 PM | #23 | |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
Quote:
The web browser works as it should. |
|
08-31-2017, 04:07 AM | #24 | |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
A few posts back you said that "the first step didn't work". I want to be sure that that means the same thing for both of us. If on your laptop in a web browser you connect to 127.0.0.1:9090 you should see something like the following (I am using Chrome). Note the "invalid response". If you connect to 127.0.0.1:9091 (an invalid port) you should see something like this. Note that "site cannot be reached". If you get "site cannot be reached" with port 9090 then something on your laptop is blocking that port. That "something" is local to the machine because 127.0.0.1 addresses do not go through the external network. If you get "invalid response" with port 9090 then try the same thing from your Android device, but using 192.168.... (the laptop's IP address) instead of 127.0.0.1. If you don't get "invalid response" then something on your network is blocking access to that port. That "something" can be your router, the dongle, or the firewall. If you get "invalid response" then try CC. It should work. |
|
08-31-2017, 06:02 AM | #25 | |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
Quote:
I'll stick with the new port. I think this means the problem isn't with the port (I've tried various ports over the past few weeks) or firewall. Perhaps I should re-install Calibre. |
|
08-31-2017, 06:54 AM | #26 | |
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
An experiment you can try: turn off the content server, assign port 8080 to the wireless device, then see what happens. Do any experiments work? My guess is yes. If so, you can assign 8081 (or something) to the content server and see if that still works. |
|
08-31-2017, 08:44 AM | #27 | |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
Quote:
Image 1 Spoiler:
Image 1 Spoiler:
I still couldn't access it from CC or my mobile web browser ("site cannot be reached"). I found these lines in /etc/services/, so that's probably normal? Code:
http-alt 8080/tcp webcache # WWW caching service http-alt 8080/udp Last edited by chaley; 08-31-2017 at 10:12 AM. |
|
08-31-2017, 10:33 AM | #28 | ||
Grand Sorcerer
Posts: 11,741
Karma: 6997045
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
The second image says that the request timed out, so it failed to connect instead of connecting and getting "wrong" data. Quote:
|
||
09-01-2017, 12:58 AM | #29 | |
Member
Posts: 19
Karma: 10
Join Date: Oct 2016
Device: Samsung Galaxy Note 10.1 (GT-N8013)
|
Quote:
I'll keep working on it. If I somehow stumble on a fix, I'll make sure to post it here. Last edited by Wryhder; 09-01-2017 at 01:00 AM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
[Android] Calibre companion debug log | waldoB | Calibre Companion | 4 | 12-27-2016 08:35 AM |
[Android] CC Change Log | chaley | Calibre Companion | 2 | 01-25-2013 05:27 AM |
Log in from Android Tablet | Quelch | Android Devices | 5 | 01-14-2013 10:29 PM |
Is there a log reader | TonyP123 | Calibre | 4 | 03-09-2012 07:44 PM |