0

Difficulties with the Synology instructions

amcfarla 3 months ago • updated by markc1975 2 months ago 17

Trying to configure this on my Synology NAS and having issues.  Following the steps from this site https://vaemendis.github.io/ubooquity-doc/pages/tutorials/install-on-synology.html I am getting to the point of this step:


The Ubooquity service is now installed. It will start on boot and you can start or stop it at anytime using start ubooquity or stop ubooquity. You can also see the status of the ubooquity processs unsing <em>status ubooquity</em>


I am not able to start up the service but I am using the Java8 that comes from Synology, so on the following steps, I am not having any success with these:


NOTE if Java8 is used

If you used Synology Java8 package instead of Java Manager then the service script will have the wrong path to the java binary. Edit the /etc/init/ubooquity.conf and change path to java binary from:

<em>exec /var/packages/JavaManager/target/Java/bin/java -jar -Xmx1024m /var/packages/Ubooquity/Ubooquity.jar -port 2202 -webadmin -workdir "/volume1/Comics/Ubooquity"</em>

to

<em>exec /var/packages/Java8/target/j2sdk-image/bin/java -jar -Xmx1024m /var/packages/Ubooquity/Ubooquity.jar -port 2202 -webadmin -workdir "/volume1/Comics/Ubooquity"</em>


I am not sure how to edit this file, I will admit linux is not my forte at all so I am just kind of winging this at the moment, I used the command (per a friend's help) 


sudo vi ubooquity.conf


which looking at this document I don't have any of this information:


exec /var/packages/JavaManager/target/Java/bin/java -jar -Xmx1024m /var/packages/Ubooquity/Ubooquity.jar -port 2202 -webadmin -workdir "/volume1/Comics/Ubooquity"


to correct the document.


Everything below script on this conf file is the following:


setuid Ubooquity

script
 # installation settings
 JAVA_DIR=/var/packages/Java8/target/j2sdk-image/bin
 WORK_DIR=/volume1/homes/Ubooquity/.Ubooquity2
 PCKG_DIR=/var/packages/Ubooquity
 PCKG_BIN=Ubooquity.jar


 # app settings
 PORT=2202
 ADMINPORT=2203
 MEM=512m


 # This ensures that ubooquity reads special characters properly
 ENCO=UTF-8
 LANG=fr_FR.$ENCO
 export LANG


 # Main command for ubooquity
 exec "$JAVA_DIR/java" -Dfile.encoding=$ENCO -Xmx$MEM -jar $PCKG_DIR/$PCKG_BIN --libraryport $PORT --workdir "$WORK_DIR"  --adminport $ADMINPORT --remoteadmin --headless
end script


So at this point I am not sure what I need to change to get this to work.  Using WinSCP I have all the directories listed in the installation settings, except the WORK_DIR  I don't have that directory, but I did create a /volume1/Comics directory for my items.  if someone is able to assist me since I am lost on what I need to do to fix this issue.  Thank you.

Have you considered using docker? I am having a great time on my synology with the image from https://hub.docker.com/r/linuxserver/ubooquity/
It works like charm and is very easy to manage...


Cheers,

RiC

Looking at this site using docker, it doesn't have any instructions setting this up and doing a google search I am not finding any instructions doing this.  Is there any instructions to set this up?

Just install Docker via the package manager and go from there. The graphical interface is quite easy and the help topics comprehensive. Feel free to ask if you have specific questions.

I have it running, but from here I am not sure how to access the admin panel to configure anything: 



The Admin-Interface is at Port :2203/admin , in your case it would be <Diskstation-IP>:32768/admin since the Container Port 2203 is mapped to Port 32768 on your DS.


You can change the local Ports to something more usable. Also remember to add the Variables (PGID for GroupID and PUID for UserID) at the Environment Tab and Folders at the Volume Tab.


At https://hub.docker.com/r/linuxserver/ubooquity/ -p are the Ports (you got these), -e are the Variables, -v are the Folders.


For the PUID and PGID refer to "User / Group Identifiers" in the instructions. You can get them via SSH. For my DS its PUID 1031 and PGID 100

With the latest version of DSM, it's much easier to install and start Ubooquity. I did these a couple of days ago:


ssh myuser@mysynology


$ sudo su -

# cd /var/packages/

# mkdir Ubooquity
# wget -O ubooquity.zip http://vaemendis.net/ubooquity/service/download.php
# unzip -o ubooquity.zip && rm ubooquity.zip

# vim run.sh

----------[ content of run.sh ]------------

#!/bin/sh

JV="/var/packages/Java8/target/j2sdk-image/bin/java"

cd /var/packages/Ubooquity
$JV -jar Ubooquity.jar --remoteadmin --headless

----------[ end content of run.sh ]------------

# chmod +x run.sh


Then in the DSM UI, go to Control Panel > Task Scheduler and create a new Triggered Task / User Defined Script as you can see in the screenshots. Enable it, click Run and you should be fine. Admin will be on port 2203, and user interface on 2202, for example:


admin: http://your-nas-ip:2203/admin/

main interface: http://your-nas-ip:2202/




















Hello,


I'm hoping someone can help, as I have installed Docker and am trying to get Ubooquity running, but not having much luck.  I should point out my Linux knowledge is next to nothing, so command-line stuff is almost an alien language to me.


I have posted screens of my settings, however I still can't connect to the admin page from my browser.  I'm just getting a page cannot be reached message.


My Comics are in a folder called 'Comics' on the root of the folder structure.  I have no idea what a 'Mount path' is so I just copied it from an Ubooquity script I had been playing with.  The PUID and PGID I got from running 'id admin' from a command prompt via putty connected to the NAS.


I had Ubooquity running about a year ago, through trial and error, and have just started to try again.  


Hope someone can help!


Many thanks,


Mark

You got the Server and Container sides of the volume settings mixed up. Left side is the folder location on your NAS, and right side the path inside the container where the folder is mounted (the idea is, that the data locations can be outside the container, but the sytem running inside the container can access it like it were inside its own file structure). So just switch it (provided your comics are on your NAS within /volume1/Comics).


Similar with the Ports. Right side are the ports of the Containers system, left where they are mapped to on your NAS so you can access them. You can either look on the running containers details window where they are mapped to automatically if you leave your settings on Auto (but know that these assignments are dynamic an can change after restaring the container) or you can assign the ports yourself (recommended, usually you can just use the same ones like within the container).


On a sidenote, for safety reasons I would not recommend acessing the data-directories as admin, the Dockeruser ("docker" on my DS) is a much safer way. Naturally you have to make sure the Dockeruser has access rights to your Comic folder.

Hello RiC,


Thanks for the reply.


I have changed the Server and Container as you suggested.  When I browse for my Comics folder in the GUI, it actually comes up as /Comics.  The only one I can edit is the Mount Point, so I changed that to /Comics instead of volume1/Comics.


I left everything else as is.


I launched the container again, however I still can't connect to 'http://192.168.x.x:32774/admin' or 'http://192.168.x.x:2203/admin' via my browser.  Just get the page not found error in Edge.


Interestingly, when I try to connect to the admin page in Ubooquity, the page that I'm logged into my Synology on quits out back to the login screen, so I suspect there's a setting somewhere on the Synology preventing the connection.


I did switch the firewall off completely to try it, but that didn't work either.


Any ideas would be most welcome!


Mark

Mount point should be "/comics" (lowercase). You also need to provide a folder for the configuration filses (settings and database) and set it to mount point "/config". Make sure this directory is writable for Docker.


Then check if the container and Ubooquity is actually starting by looking at the output in the Terminal tab of the running containers details window. Any errors should also be in the Logging tab.

Hello RiC,


I feel like we're getting somewhere!  I now have a docker folder, with a bunch of files in it, on the root of my NAS.  The admin account has read/write access to it.


I'm doing everything as admin at the moment, then when I get it working, will create a Docker account and switch it over.


Here's the Details and log file, looks to be running the scanner, and there's a ubooquity-5.mv.db file in the docker folder, along with a preferences.json, and cache, fonts, logs and themes folders.


Still no access from the browser though, just getting the usual 'can't reach page' error.


Any ideas what could be stopping the access on the NAS?


Cheers,


Mark

Possibly worth updating DSM on my Synology?  Currently on DSM 6.1.


Also, is there any chance you can post screenshots of your setup?  Or alternatively email them to me in a zip file, so I can compare.


Cheers,


Mark

Hello again,


Thanks for all the help so far.  I have updated the DSM, and the Docker version, and now have settings similar to the ones posted above (though still no access yet!)


Everything seems to be running, as the log file is running after the container launched on reboot.


Can't reach it on port 32770 or 2203 though.  I have enabled all ports on the firewall on the NAS, and my router, but not having much joy.


Mark

Just to add, I created a new Comics folder called 'Comics1' and placed a 'Docker' folder in it.  I copied one folder of comics to the new location too, and gave write access to everything.


Now when I run the container for Ubooquity, the Docker folder called 'cache' updates with all the cover art from the comics.  This never happened before, so we're getting there slowly.


With the Firewall on, I can't access anything.


With the Firewall off, I get a different error message, though still no access to the /admin page.  I have also configured static ports, but no joy.


Any more ideas?


Mark

Hello,


I have one more question... in the Network settings for Docker, should the Bridge subnet be left at 172.17.0.0/16.  This is the connection the Ubooquity container is using.


My internal network is on the 192.168.x.x range.  Could this be one of the issues?


Cheers,

I never changed any network settings for docker in my setup, so I dont really think that has anything to do with your problems. Docker itself should take care of mapping the container ports from its bridge subnet to the ports specified for your host (=NAS).

Solved.


Microsoft Edge is a crap browser.


Tried Firefox, and I was straight into the admin page.


Need to copy all my comics over now!


Thanks for all the help!