Quote:
Originally Posted by kdsksg
I have sent a CC debug log to the provided email and acquired a calibre debug log, but would like to request an email address to send that to also.
|
Please send the calibre debug log to the same email address used for the CC debug log: cc_debug_logs [at] haleys [dot] org
Looking at the CC debug log I see that on multiple times on 16 and 17 April CC tried using the default settings. CC asked the network if calibre was there. Calibre answered "Yes" and provided an IP address, the same one you mentioned. CC then attempted to connect to that IP address and failed. The usual reason for this kind of failure is security SW such as an antivirus or firewall on the calibre computer. The second-most reason is "guest mode" or other security settings on the home wifi router. The third-most reason (very rare) is wifi congestion: too many neighbors on the same wifi channel. The last reason is bugs on the device itself.
Bottom line: something on your network is preventing CC from connecting to calibre. A CC log extract is:
Code:
2017-04-17 18:39:01.539: WDConnection: Starting connect process
2017-04-17 18:39:01.546: WDConnection: Broadcasting ...
2017-04-17 18:39:02.771: WDConnection: MDNS ServiceAdded. name=calibre smart device client (on xxxxx, address=192.168.1.102, port=9090
2017-04-17 18:39:04.270: WDConnection: received broadcast response calibre wireless device client (on xxxxx);8080,9090, address 192.168.1.102
2017-04-17 18:39:04.330: Networking: identical mdns & broadcast host 192.168.1.102 9090
2017-04-17 18:39:04.332: WDConnection: using broadcast server address 192.168.1.102 port 9090
2017-04-17 18:39:04.364: WDConnection: my ip address is: 192.168.1.139
2017-04-17 18:39:04.366: WDConnection: trying server address 192.168.1.102 port 9090
2017-04-17 18:39:09.370: Attempt to connect resulted in exception
java.net.SocketTimeoutException: failed to connect to /192.168.1.102 (port 9090) after 5000ms
MDNS is an alternate name for Bonjour and some implementations of universal-Plug-and-Play.
Note that it took calibre almost 3 seconds to answer the broadcast. This is an unusually long time, and might indicate that the computer running calibre is running very slowly, perhaps because of lack of memory or other processes running at the same time. If the calibre computer is very slow then perhaps CC's timeout of 5 seconds (5,000 milliseconds) isn't long enough.
The calibre log might provide more detail about what is happening.