A bit of an odd one, I'm not sure if it's a bug or something else and I've not found anyone with the same issue.

Some of my nicely scrapped comics are only displaying the comic story title instead of Series Name and Number (Year).

Is there anyway to change/toggle this as i would prefer the "Series Name #Number (Year)" as the story title can be very long sometimes and sometimes just looks bad.

Hi,

Is there any way to remove the file numbers from in front of the cover icons?

Many Thanks.

Porph!

Hi,

Title says it all, I've changed permissions and moved both the jar and sh files to /opt/ubooquity and still no joy.

I've had a look in the sh file and can see no issues

Am stumped

Cheers all

Porph

Here is an extract from my log when adding and removing items in database

20160930 10:51:24 [Scanner thread]  INFO com.ubooquity.data.database.b - Inserting/updating comic entry in 
database : /volume1/comics/Général/Corto Maltese (N&B)/Corto Maltese - 10 - Mû.cbz
20160930 10:51:31 [Scanner thread]  INFO  com.ubooquity.data.database.b - Deleting comic with id 5066 from database

The inserting/updating gives a lot of details (although it would be nice to know whether it's an update or a new item

The deletion doesn't give any details: we don't know which comic was deleted. This is very annoying: can you add information about the location of the file or at least the title? like you do when inserting an element?

First, thanks for making a super application - it works very well.

I can't seem to solve an issue - using Challenger Viewer, I can sync OPDS-COMICS from Ubooquity however for some reason if a folder on the server contains more than 20 comics, Challenger Viewer will only group them into clusters of 20 per thumbnail - then will begin creating additional groups of 20 in a new generically titled "Comics" thumbnail rather than using metadata names.

Web viewing works just fine - not sure if this is an Ubooquity question or a Challenger question?

Aside from this little frustration, Ubooquity works very well as a home-based book server!

20160919 23:32:00 [pool-1-thread-16] WARN com.ubooquity.e.e - Interrupted while sending response (perhaps the client stopped the download) - java.net.SocketException - Software caused connection abort: socket write error

Gets about 30 of these and then it crashes. Every 48 hours.

I made an app to load the epubs but it is not an elegant solution. It has to download the entire file first and then post process. In the future, will the epubreader support directly loading a specified page number much like how comicreader works?

I'm running Ubooquity on a Mac Mini that scans a network drive. If there's a glitch in network and the drive goes offline, the database needs to be cataloged from scratch. With 14,000 comics in my collection, this can take some time. It looks like the database is being reset if the volume isn't present.

Hi, On scanning I get this error:

20160911 00:28:07 [Scanner thread] INFO com.ubooquity.fileformat.pdf.b - Reading metadata of pdf file: H:\temp\My Books\My Books\Fiction\Wings\03 (18009)\03 - Wings.pdf

Both ubooquity and java on latest version, Windows 10 PC.

Hello I just setup nginx and ubooquity reverse proxy successfully. I did two benchmarking test and the results look great.

First test was done with nginx as reverse proxy like this

ab -kc 1000 -n 10000 http://104.251.217.110/admin

and it gives the following result:

Server Software: nginx/1.4.6
Server Hostname: 104.251.217.110
Server Port: 80

Document Path: /admin
Document Length: 2071 bytes

Concurrency Level: 1000
Time taken for tests: 9.236 seconds
Complete requests: 10000
Failed requests: 0
Keep-Alive requests: 10000
Total transferred: 22290000 bytes
HTML transferred: 20710000 bytes
Requests per second: 1082.67 [#/sec] (mean)
Time per request: 923.645 [ms] (mean)
Time per request: 0.924 [ms] (mean, across all concurrent requests)
Transfer rate: 2356.70 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 78 287.5 0 1747
Processing: 194 806 503.3 700 5544
Waiting: 193 775 439.2 698 4108
Total: 194 884 582.7 720 5544

Percentage of the requests served within a certain time (ms)
50% 720
66% 836
75% 1037
80% 1202
90% 1580
95% 2146
98% 2615
99% 3118
100% 5544 (longest request)

And I did the same thing with just ubooquity itself using

ab -kc 1000 -n 10000 http://104.251.217.110:2202/admin

And the test failed with the following results

Concurrency Level: 1000
Time taken for tests: 18.322 seconds
Complete requests: 10000
Failed requests: 4999

But while all of this sounds interesting I am reluctant to put this into a production server since nginx is just passing request to nanohttpd server which is not designed for that type of usage.

My concern is that nanohttpd may just be unresponsive in a production environment even if nginx is right in front of him...

PleaseTom, let me know what do you think...

Bellow is a complete result of my tests:

pi@raspberrypi:~ $ ab -kc 1000 -n 10000 http://104.251.217.110/admin
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 104.251.217.110 (be patient)
Completed 1000 requests
Completed 2000 requests
Completed 3000 requests
Completed 4000 requests
Completed 5000 requests
Completed 6000 requests
Completed 7000 requests
Completed 8000 requests
Completed 9000 requests
Completed 10000 requests
Finished 10000 requests


Server Software: nginx/1.4.6
Server Hostname: 104.251.217.110
Server Port: 80

Document Path: /admin
Document Length: 2071 bytes

Concurrency Level: 1000
Time taken for tests: 9.236 seconds
Complete requests: 10000
Failed requests: 0
Keep-Alive requests: 10000
Total transferred: 22290000 bytes
HTML transferred: 20710000 bytes
Requests per second: 1082.67 [#/sec] (mean)
Time per request: 923.645 [ms] (mean)
Time per request: 0.924 [ms] (mean, across all concurrent requests)
Transfer rate: 2356.70 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 78 287.5 0 1747
Processing: 194 806 503.3 700 5544
Waiting: 193 775 439.2 698 4108
Total: 194 884 582.7 720 5544

Percentage of the requests served within a certain time (ms)
50% 720
66% 836
75% 1037
80% 1202
90% 1580
95% 2146
98% 2615
99% 3118
100% 5544 (longest request)






pi@raspberrypi:~ $ ab -kc 1000 -n 10000 http://104.251.217.110:2202/admin
This is ApacheBench, Version 2.3 <$Revision: 1604373 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 104.251.217.110 (be patient)
Completed 1000 requests
Completed 2000 requests
Completed 3000 requests
Completed 4000 requests
Completed 5000 requests
Completed 6000 requests
Completed 7000 requests
Completed 8000 requests
Completed 9000 requests
Completed 10000 requests
Finished 10000 requests


Server Software:
Server Hostname: 104.251.217.110
Server Port: 2202

Document Path: /admin
Document Length: 2071 bytes

Concurrency Level: 1000
Time taken for tests: 18.322 seconds
Complete requests: 10000
Failed requests: 4999
(Connect: 0, Receive: 0, Length: 4999, Exceptions: 0)
Keep-Alive requests: 5001
Total transferred: 10998792 bytes
HTML transferred: 10363284 bytes
Requests per second: 545.78 [#/sec] (mean)
Time per request: 1832.247 [ms] (mean)
Time per request: 1.832 [ms] (mean, across all concurrent requests)
Transfer rate: 586.22 [Kbytes/sec] received

Connection Times (ms)
min mean[+/-sd] median max
Connect: 0 733 2065.9 173 15309
Processing: 0 130 153.5 172 1908
Waiting: 0 119 135.7 175 932
Total: 0 863 2105.9 355 15506

Percentage of the requests served within a certain time (ms)
50% 355
66% 439
75% 490
80% 1280
90% 1511
95% 3453
98% 7453
99% 15417
100% 15506 (longest request)