Quote:
Originally Posted by kdsksg
Oops! I forgot to attach the files. I've sent them again.
|
This log is clearly not complete. Putting aside the WD debug messages, calibre prints something like the following once it is fully initialized.
Code:
Started up in 4.05 seconds with 77 books
I don't see that line in your log. Are you saving the entire log, or are you copying the part that you can see in the window?
Grasping at straws, it could be that there was a logging problem in older versions of calibre.
Quote:
As to the other connection methods, I started a content server on calibre, but could not connect to it from the web browser on my device ("took too long to respond"). I also tried reaching it from another computer, which could not connect with the same error.
Just for completeness, I tried to connect to the content server from CC, which came up with the error that the content server was not running. And, of course, wireless device connection simply failed, as it has been.
So this would seem to indicate that the issue is on my home Wi-Fi network, instead?
Should I still try upgrading my calibre version, or is that no longer necessary?
|
Unfortunately the experiment doesn't provide definitive answers, but the implication is that the problem is in the hub or in the computer running calibre. If you were running Windows then I would be very confident that the problem is the firewall or the AV. Unfortunately I am ignorant about Macs, but as they must have some network security the problem could easily be there.
If the problem is with the hub then things become more complicated because it sometimes works. That implies transient problems instead of configuration problems. One transient problem is load from nearby hubs, which a wifi channel scan might help diagnose. See
http://osxdaily.com/2013/12/11/find-...less-tool-mac/. Another might be that the router has "degraded" to the point where its program memory is no longer correct. This can often be fixed by "re-flashing" the router's firmware. It could also be that the router is broken, but this is far enough down the list that we can ignore it.
Finally, it could be that the entire network is no longer stable, where IP addresses aren't unique. This can happen if the router is rebooted or otherwise disappears for a time. The fix is to shutdown every device, reboot the router, then restart the devices one by one. This happens to me every 18 months or so.
I really wish I could tell you to "do this and it will work". Unfortunately, networking problems are hard. We have had cases where we never found the problem.