I don’t have any issue with DietPi or the setup of Ubooquity.
I decided to move it from my NAS to the RPI4 who is running DietPi
If the setup was easy, I discovered that the scan speed is slow ( but really slow like 1 comics per minutes)
Yes the data are stored on the NAS but it’s on the same network.
I’m not sure if this is caused by the java heap space, but you can try and enlarge it.
How much RAM does you RPi 4 have?
To do this you have to edit the service itself. You can do this with dietpi-software, choose “ubooquity” there and then go to
Remove the # and change the 754m to something higher then now but fewer than your actual RAM size.
After this, add a line ExecStart= above the line you edited, it should look like:
(in this example I use 2GB (2048MB) max heap size.)
Save this file with ctrl+o, enter/return, ctrl+x
When you are back in the service control menu, choose the first entry State and hit Enter two times to restart (first enter is for stop)
If you want to undo this change you can do this form CLI:
Thanks for the detailed solution,
When I edited the file, I had:
#ExecStart=/usr/bin/java -Xmx384m -jar /mnt/dietpi_userdata/ubooquity/Ubooquity.jar --headless --remoteadmin --adminport 2038 --library
so I remove the # and set it to 754m … saved, stop,… and no restart it automatically failed …
if I put back the # … all is restarting correctly … not sure what is wrong…
Scan is a little bit faster but not as the same level of the NAS, reading is impossible … took almost a minute to read a page… I will give a try with a local USB storage to see if the CIFS share could be the issue or not…