Your comments

Words from Tom from a other case : 

" I don't know exactly what happened, but your database file definitely seems unusable. :(

If you want to make a test before getting rid of it, you can rename it (after stopping Ubooquity) in case you want to restore it later: the file is named "ubooquity-5.mv.db". "


(found @ : https://ubooquity.userecho.com/communities/1/topics/734-everything-was-working-great-then- )

Hi tml, 

sorry, but i have no solution for you, but i'm very interested in your script - can you post it here ? 

Best regards from Munich

TierParkToni

i've installed 2 KINGSTON DDR3 PC3-12800-SODIMM 8GB modules, and it works nearly 2,5 years without any trouble - the trouble with USB3 started with the 4.3.x versions of QTS and has nothing to do with Ubooquity or Java. I've running parallel 3 different VMs with virtualisation station and didn' have any problems, even running a database server on it. 

According to your errors/bugs it seems to be a RAM size problem : 3.5 GB is the default max memory setting running Ubooquity in the qpkg-version of Ubooquity, and your system has even this - and now needs to use swap. Swapping is much less performant than ram, so please check in the Ubooquity admin panel your system info for the value of max memory. If it says 3496 MB, you need to set your max memory th 2048 with  

"$JAVA -Xmx2048m -Dfile.encoding=UTF8 -jar Ubooquity.jar --headless --remoteadmin &" 

in your ubooquity-script found under your .qpkg-folder (/share/CACHEDEV1_DATA/.qpkg/UbooQuity/UbooQuity.sh).

Or you just try spend some more physical RAM - it seems worth it. 

Hope that helps ! 

Best regards

TierParkToni

hmm, same JRE here - strange ... 

Wich version of QTS runs on your NAS - because my x53 here have some big trouble runing the actual version and USB3, so i have to go back using 4.3.4.0695. 

And how much RAM do you have ? 

What QNAP-NAS model do you use : with intel or ARM CPU ? 


QNAP-NAS with ARM is generally not recommended as platform for Ubooquity because it's very low RAM-memory and have to share it with the OS... trust me, i've testet it with an HS-210 and an TS-239 - just no fun an a lot of side effects... 

In the case of a model with a intel CPU : 


Do you use the original JAVA provided by QNAP or the JAVA from QNAPclub https://qnapclub.eu ?

Using the original QNAP Java may sometimes only use the 32bit runtime, the QNAPclub Java runs perfect with 64bit.

It runs here on a TS453mini with 16GB RAM and nearly 50 Users (the NAS stores PDF-ebooks for car restorations).

And for your problem with the MOBI/FB2 books :calibre can do a "mass"-convert, but it really takes some time ;-) ... 

@santi (& tom h): ... just convert it via calibre before put it into Ubooquity - what's the problem ?

A auto-conversion with 3rd-party libs can nothing better, but anything mutch worther ... 

Hello Scott,

shure that you not using any comic reader chrome extension (or pc software with browser support) ? 

i've tested the download function it on 3 computers and can't replay your "cbr/cbz-effect" . 

But, if any cbr/cbz-extension for chrome ist installed, it will open it in a new tab....

Hope that helps !


best regards


TierParkToni

Now it's my turn to add me to the thanksgiver-list : it's always a pleasure reading my ebooks in a browser window or with Kuboo and your great peace of software on my NAS - knowing you at parenthood makes your work much, much worthy and valuable !

So : a very, very big thank you :-) !

1st solution-attempt for this problem :  


are these pdf or cbr/cbz ? 


- If PDF, just open it and check their PDF-properties - if there protected, try to unprotect them - or open it and just try to print it to an pdf-printer.. 

- If CBR/CBZ, just unpack these into an separate folder, zip / rar the extracted files again, then rename the new .zip-/.rar-files to .cbz / .cbr .

after all, try to scan these files again ... 

hope that helps !

best regards

TierParkToni

Hi Graham,


it's just your second post, and it look like that you doesnt read the basic v2.x manual : 


- first of all, the database from v1.x isnt 1:1 compatible with v2.x, so you have to rescan your library.

- before that, you must install a x64 version of Java - you just described a problem that occurs only with x86 Java.


And now, here is my recommendation to help you : 


- if you want to use your old settings, you can do this job ONLY by manually edit the config.file ( just a bad idea!) -> 

  but it's very easy to start over with fresh re-set your config in the admin page
   (http://yourip:2203, you remember from the manual describe the new startup call -> please say honestly just "no" ?)

 

- and here ist the next problem : how did you start the 2.x version? the old startup call doesnt work ...


give v2.x a chance by starting without any old file "crap" in your installation directory (and please -> RT(F)M)  ... 

that doesnt mean to clean your content, only remove/move out the old 1.x program files or install v2.x in an different folder than v1.x ... 


Tom has doing a very good job on 1.x and does an even better job on 2.x - it runs here for me and my guys/ladies with now nearly 100.000 PDF-files and in the meantime with 38 simultaneously active (but each different to other) user account without any bugs or problems -> on a QNAP TS453mini with only 4GB Ram allocated.


Before that, I used v1.x here and i tried it like you to "just migrate/update to v2.x", but honestly : that's no so easy going,..

After trying it (and stay nearly howling with anger) for some days, i decide to start absolutely fresh with an different blank installation directory and only the new uboquity.jar - and voila, just after 30 mins (except the waiting time for uboquity scanning the content, that takes 1 day) it runs nearly perfect til today ...   

hope that helps you out ! 


best regards from munich - only 4 days and the rest of today left to Oktoberfest/ Wiesn 2018  <|8-'} 


TierparkToni