As I wrote earlier, the database file is entirely managed by the database library used by Ubooquity (H2, which is a very widely used, very robust library).

Now, between Ubooquity 1.10.1 and 2.0.0, I updated the H2 version from 1.4.187 to 1.4.193.

This should not have caused any issue, but funny side effects that happen only on specific setups are always possible.

So I built two special versions of Ubooquity 2.1.0:

• One with H2 1.4.187 (the one used in Ubooquity 1.10.1)
• One with H2 1.4.196 (the latest one available, in case a recent change has fixed your issue)

So if you're still interested in using Ubooquity 2.x, you can try these versions in case they work better for you.

Of course, I would be interested in knowing the result of your tests. I don't know if it could be enough to pinpoint the cause of your issue, but you never know...

The logs displayed in the admin interface are limited to 1000 lines.

This log page is intended to provide an idea of the last events that happened on the server, not parse and display the full log file, that can be quite big depending o the logger configuration.

For a complete review of the logs, looking at the original log file like you did is the right thing to do.

Already planned (no ETA though).

See this post for a workaround.

Nice ! I didn't know this one. :)

Ubooquity needs writing authorization on the files located in its working directory.

Did you happen to launch Ubooquity manually the first time (allowing to create all its files with user A) then as a service (with user B, hence the rights problem) ?

Same answer as above: send me a link where I can download an example of mobi file for which Ubooquity does not correctly guess the cover, and I'll take a look to see if the extraction algorithm can be improved.

You can't recover it, but you can reset it: instructions in the FAQ.

This message, "Sorry, you are not authorized to access any file on this server", is what Ubooquity displays when it has nothing to show, meaning when no folder has been shared yet, or when the user you are logged in with doesn't have rights on any of the shared folder.

In other word, when you donwload and run Ubooquity with further configuration, you get this message.

I guess I should reword it to be more explicit.

So the fix for your problem is simply to configure Ubooquity again (The documentation has been updated, should you need any help).

"Address already in use" means that another application uses one of the ports Ubooquity uses (2202 for the library, 2203 for the admin page).

You have to use other ports (see here for command line options).

By the way, according to your logs, you are using Java 8 (which is a good thing, since Ubooquity does not work with Java 7).

Thanks for the nice words. :)