Your comments
you need to uncomment the $MEM parameter, and that should work.
See last post: I've put my script there
Hi all. there has been a sub-thread about special characters. Here I put my full script, that is working on my synology ds212. Adapt to you environment and save as "ubooquity.conf" in /etc/init/ folder on your NAS
#============================================
# Ubooquity
# upstart job configuration file for automatically
# starting ubooquity when syno starts
# title :ubooquity.conf
# date :20 11 2015
# original source: ubooquity forum about special characters
# http://ubooquity.userecho.com/topic/907059-comics-not-imported-umlaut-mark-bug/
#=============================================description "start/stop Ubooquity"
author "Elouan Le Bretton"
# automatically starts ubooquity after apache has been started
start on started httpd-user
# stop ubooquity on
stop on runlevel [06]
# [TODO] automatically respawn ubooquity if stops
# respawn
# respawn limit 5 10
# run the scripts as the 'http' user. Running as root (the default) is a bad idea.
setuid http
script # System variables.
JAVA_DIR=/volume1/@appstore/java8/ejdk1.8.0_65/linux_arm_sflt/jre/bin
WORK_DIR='/volume1/comics/.Ubooquity'
PKG_DIR=/var/packages/Ubooquity
PORT=2202
MEM=Xmx128m
# prepare environment
LANG=en_US.UTF-8
export LANG
exec $JAVA_DIR/java -Dfile.encoding=UTF-8 -$MEM -jar $PKG_DIR/Ubooquity.jar --port $PORT --webadmin --headless --workdir $WORK_DIR
end script
This happened to me quite a few times because of memory issue: java was issuing memory exceptions. I had to kill ubooquity, delete the pdf file, and relaunch ubooquity
The workaround that I've find to import those files anyway is to convert pdf into cbz: I've never had any memory issues with cbz
Thanks for the credit, but actually, I found the solution there. with a full script that launch syno automatically at boot
I've made another change to get ubooquity to read files/folders with special characters (lilke é, ü) : added encoding option when lauching java. It now reads like:
exec $JAVA_DIR/java -Dfile.encoding=UTF-8 -Xmx128m -jar /var/packages/Ubooquity/Ubooquity.jar --port $PORT --webadmin --workdir $WORK_DIR
Ok, I've found the solution in another topic: http://ubooquity.userecho.com/topic/907059-comics-not-imported-umlaut-mark-bug/
had to add encoding utf-8 option in the java options...
I use ubooquity on my synology DS212, and it's working fine. I'm pretty sure it should work fine on your Syno too.
I have 2 suggestions:
1: check the name of the folder you are trying to scan: "/Volume_1/Comics". On my station, the name is "volume1", not "Volume_1".
2: check the permissions on the folders you are trying to access with ubooquity. I granted read/write privileges for all user on my installation...there probalbly some way to make that more secure but haven't done that yet!
I second the request: would be a very nice to have feature. And since you can read metada, you could add browsing with series along wiht browsing with author
I've manage to install Ubooquity on my Synology DS212 model, using Matthew's tutorial Thanks for the god work!
I've had to make a few modifications in the script to adapt to the DS212, I'm sharing it hopping it can help other people to save time
Matthiew's script looks like this
exec /var/packages/JavaManager/target/Java/bin/java -Duser.dir='/volume1/Comics/Ubooquity' -jar -Xmx1024m /var/packages/Ubooquity/Ubooquity.jar -port 2202 -webadmin
my script looks like this:
exec /volume1/@appstore/java8/ejdk1.8.0_51/linux_arm_sflt/jre/bin/java -jar -Xmx128m /var/packages/Ubooquity/Ubooquity.jar --port 2202 --webadmin --workdir '/volume1/comics/Ubooquity'
Here are explanations:
- the DS212 doesn't have built-in java manager, so you have to install java using the separate [the link is in Mathew's]. I've installed a java8 compatible with my machine. But then you must change the path to java in the script. After installing java, you can find that path using 'which java command
- I've modified memory settings to 128Mb [the DS212 have 256M of memory].This proves enough even though I have a large collection of comics [>1000]. Some files create a java memory error. You can detect those files by looking at the log, and you must remove them from the directory and relaunch a scan to let ubooquity scan all the library. I haven't find another workaround yet
- I've also replaced the -Duser.dir <path> option with --workdir<path> as recommended by ubooquity author. This change is only valid for release 1.8.2
@Mathew: I think you should include that last change in your script, it reads like it's more reliable than changing -Duser.dir parameter?
Customer support service by UserEcho
Nah, I don't like that workaroud at all: I've spent quite a lot of time getting all the metadata into my collection, I don't want to remove it now
This requires new development. When opening OPDS feeds, we see different choices "Folder", "Latest", "All comics". We should add new choices there: "Series", "Authors" ["publishers" ...]
From what I see, ubooquity is building a database when scanning the files. Ubooquity could use queries to build the new reports from existing feature:
- "Folder" option should not read the meatada and display the collection by folder and by filename, like you would see in windows explorer
- new choice: "By series". This would read the metada and display by series and inside by number
- new choice: "By author". This would read the metada and display by author/series/number
At the end of scanning, ubooquity could build tables that would pre-process that information so ubooquity could generate the opds feed easily from those table [could achieve the same result with queries, but it might require too much load on a small NAS... ]