[chaley]

Originally Posted by cybmole

i have sent a log + a message linking my email to this forum account so you can identify what it is about. I was to dumb for figure how to remove the CC.
I did not peek at the log so I don't know for sure if it covers the issue. anyway we can continue this via email once you get it. no need ot tell the world until it's solved!

The logs indicate that you have put an IP address and port into CC's connection server settings, and that most of the time connections to those values work. More below...

PS you mention time to wake up calibre, but if that is running ( idling) on PC then is it already awake enough to see any incoming content server requests, even if its not been asked to do anything for several hours ?

Ahhh, the wonders of virtual memory on computers.

If a running program hasn't done anything for quite some time then its "working set" (memory required to hold the program code) is usually shoved out onto the hard disk to make room for other programs, or simply to make room for the operating system to do other stuff. If and when the swapped-out program needs to run again, it must reload all that stuff back from the hard disk. This can take a long time, sometimes many seconds.

If the calibre content server is not resident in the computer's memory when CC tries to connect then calibre is reloaded. If the time to re-fetch calibre exceeds CC's timeout (2.5 seconds), then CC will give up and try something else. In this case, something else is to ask the network if calibre is around somewhere (the "broadcast") and wait for a few seconds. For some reason on your network, calibre never responds to a broadcast. The connection fails. However, because calibre has been loaded into memory, the next connection attempt succeeds within that 2.5-second window.

The only thing I can see to do is to increase the timeout, but I am not sure that doing so is a good idea. If I increase the timeout then there will be a higher likelihood that calibre will make it back into memory and be able to respond, but it isn't certain (how long is long enough?). On the other hand, people who are using primary and alternate connection settings will pay the extra time on every connection when the secondary connection is the one to use. Perhaps less important, but people who for whatever reason have put something invalid into CC's settings and are depending on broadcast will also pay the extra time.

PPS
You can't delete books when connected to the content server because it never occurred to us that someone would want to do that

well there's always one awkward so & so & here he is

why - because all I want to do is bring in book(s) them import into Kobo android app. That app will then offer to delete the book from Sd card, but if I say yes, then CC's own records of what is stored locally get messed up. CC will not know that Kobo app has just deleted a book.
SO its a better work flow ( fro me) to fetch with CC, then import book with Kobo app ( with copies it into kobo'a own database) then say no to kobo app offer to delete original, then do the delete from inside of CC ( for which I have to do a disconnect....)

Another workflow would be to allow the kobo app to delete the book, then from time to time run CC's "Find missing books" to remove the left-over CC database entries. Of course, running Find missing does require you to disconnect, but it obviates the need for you to remember which books have been deleted. Find missing is also much faster than deleting books one by one, as it can delete all the missing books in one swoop.

Regardless, I will think about deleting books from the content server's book details screen. The only real objection is the one I raised earlier, and perhaps that could be handled by a somewhat longer "Delete" menu line, something like "Delete CC's copy".

EDIT: if you are running Windows then be sure that your hard disk is not fragmented. I have seen virtual memory performance increase by a factor of ten simply by running defrag.