Your comments

Hello Alexander,


first look into your log shows me some exclamation mark /screamer  in your directory path / filename - 

thats a problem for uboquity / java.

Remove it please from a directory and scan your content again - if the problem resists, there is some other bug, 

but my experience tells me that's the point of failture here ... 


Hope that helps 


Best regards from Munich (where currently the morning sun begins to shine)

TierparkToni

Hello Daniel,


first let me congratulate to your new TVS-871 - yay, its a very fine piece of HW ..

and now lets go on @ your problem : there may be some relevant checkboxes :

Did you test it enabled/ disabled? Maybe here's the problem found ... ? 

Sometimes the installation of Stefans qpkg goes deeply wrong, i check always after doing an uninstall via Bitvise SSH the complete uninstall (here the default path for the QNAP-Ubooquity-folder : /share/CACHEDEV1_DATA/.qpkg/UbooQuity 

Move temporaly all files below the Ubooquity-Folder into /tmp , reinstall Ubooquity via qpkq and check again... 


Best regard ! 


TierparkToni 

Hi again Daniel,


Im shure your folder structure isnt your problem - did you update via QPKG or just replace the Ubooquity.jar ? 

i've updated Ubooquity since the first releace of 2.x and had some issues with the remaining old 1.x program files ... 

If you just update the jar-file, the database format has changed and cannot be used by 2.x .

If you update via QPKG, uninstall it and install it "fresh" again - but after both methods, you have still to fresh setup your library directorys - with absolute paths (again) -> take a deeper look again at : 


https://ubooquity.userecho.com/communities/1/topics/552-version-210-configurationlogin-no-longer-possible#comment-3311


hope that helps ! 


best regards 


TierparkToni 


PS: how stable is your current firmware on your TS-453b-mini ? I have a TS-453mini (1st Edition) an lot's of trouble ( like many other)  with the firmwares newer than April 2018, so my current Firmware release is 4.3.4.0486 which runs almost stable... 

Hi mccorkled,


on your screenshot is the stop-symbol from Adblock - did you create a exlude rule for your ubooquity server ?


Hope that helps 


Best regards !


TierparkToni

Hi souvik,


When you read something, the Ubooquity server-engine preloads always only 2 Pages ahead and convert it into a graphic.

If the Page contains only text, the conversion is very fast - if the Page contains pictures too, the conversion take some time.. and the PDF-structure is as well a time-using factor : complicated structures need some time to convert... 


Maybe the initialization library scan could take some time, but after that, it will run as fast as possible - with your configuration it should be fast - depending on the content stuff (only-text or much text and graphics) ...


Beste regards !


TierparkToni

Hi luskin,


my opinion : the lit-format is rotten by Microsoft since 2012 (almost 6 years) and most time protected with a closed-source DRM. 


Currently the actual (and future) version of Ubooquity couldn't support lit-files. 


The one and only way to read and manage it with Ubooquity is to convert your lit-files with calibre to epub or PDF.

If this way doesn't work, here is in my view no other way to use it with Ubooquity.... 


Sorry for no good news ...


Best regards


TierparkToni

Hi Richard,


i had no problems, but i think knowing your problem, so here's my questions to help you :


- do you install the 32bit or the 64bit version of JAVA ? 

-> Running Ubooquity 2.x on a 32bit JAVA isn't recommended, you should uninstall the 32bit and install the 64bit version.


- the process user has "display-only" NFS Access rights and cannot real open/read the NFS-Share files 

-> check if the NFS security option AUTH_SYS is given and the UID and GID matches on both systems.

    Otherwise the NFS guest rights will your Ubooquity instance give only the lower "display content" rights.

    Eventually the NFS Squash gives your local root user on the Share only quest rights.

    If the NFS security option Kerberos (krb5, krb5i, krb5p) is set, this can give you (on an authentication failure 

    without a error message) on your NFS share only guest/display-only rights, too ... 


NFS Access rights synchronization is often tricky, i always recommend using SAMBA Shares to use with Ubooquity.


Hope that helps 


Best regards !


TierparkToni

Hi korrupto,

use http://192.168.0.157:2203/admin 


(url :2202 is for comic viewing, url :2203/admin is the admin interface) 


and be sure NOT to use the share directory direct (/share/comic) - use always the direct system path (/share/CACHEDEVX_DATA/comic or /share/MDX_DATA/comic, depending what you found on your NAS), 

that makes your user experience with ubooquity on a QNAP much easier and better :-) 


hope that helps 


best regards


TierparkToni 

(just awaken in a very windy, cloudy and rainy Munich city, brrr) 

@ QNAP : your welcome !

@Tom: Thanks again for posting the links !

Within the help inside the first link provided this case can be closed, nothing more to do - just keep comic reading again ... 

Best regards 

TierparkToni

Hello Tom,


thanks a lot for posting this links, the first seem to describe the solution : 


the qoolbox-qpkg version install the /etc/init.d/UbooQuity.sh only with the support for 

en_US.utf8
....
export LC_ALL=en_US.UTF-8
export LANG=en_US.UTF-8
export LC_CTYPE=en_US.UTF-8
....

I've changed it to fit my here needed German localisation 

de_DE.UTF-8....
....
export LC_ALL=de_DE.UTF-8
export LANG=de_DE.UTF-8
export LC_CTYPE=de_DE.UTF-8
....

, changed some already renamed files with "ue" letters to "ü" and start a new scanning, and - et voilà ! - it works !


@QNAP : select your country code from the following table


cs_CZ.UTF-8
da_DK.UTF-8
de_DE.UTF-8
en_US.UTF-8
es_ES.UTF-8
fr_FR.UTF-8
hu_HU.UTF-8
it_IT.UTF-8
ja_JP.UTF-8
ko_KR.UTF-8
nb_NO.UTF-8
nl_NL.UTF-8
pl_PL.UTF-8
pt_BR.UTF-8
pt_PT.UTF-8
ru_RU.UTF-8
sv_SE.UTF-8
tr_TR.UTF-8
zh_CN.UTF-8
zh_TW.UTF-8

 and replace any found

en_US.UTF-8

in your /etc/init.d/UbooQuity.sh with the previous selected.

Restart your Ubooquity-server, start a scan process and after it's finished, start a scan process again.

after the finish of the 2nd scan, check your log - the scan may now stopped reimporting previous imported comics/books..


Thanks again @ Tom


Hope that helps, QNAP


best regards ! 


TierparkToni