Introduction

During my last post about the DS215j from Sinology i introduced the DiskStation and provided a way to bootstrap the NAS. Lately i found myself in the situation that it was not enough to be able to install packages using bootstrap and ipkg. I’d like to have a working pyLoad installation to be able to handle all of my downloading belongings. The provided DownloadStation was not capable of handling so called OneClickHoster especially the captcha request.

Because of this reason i needed an alternative. It was very easy to find some, pyLoad. It was not that easy to get it running on my DS215j. There are precompiled .ipk packages of pyLoad on their homepage but they are not working because of an issue with python.

I will provide the instructions to install pyLoad from ipkg even if it is not runnable. Because if someone has the same problems, he will find this article and sees the better solution.

Install pyLoad

From ipkg sources

This part of the article won’t provide you a running pyLoad instance by now. Maybe there will be a python2.7 fix for the following issues.

Needed packages

First we need a list of packages to be able to run pyLoad. The following command will install them. You have to log-in into your DiskStation using root or a user able to use sudo.

sudo ipkg install screen nano wget unzip unrar psmisc wget tesseract-ocr tesseract-ocr-lang-eng ossp-js unrar

1	sudo ipkg install screen nano wget unzip unrar psmisc wget tesseract-ocr tesseract-ocr-lang-eng ossp-js unrar

Download the pyLoad package

The precompiled package will be downloaded directly from the homepage of pyLoad and installed afterwards.

wget http://get.pyload.org/static/pyload-v0.4.9-noarch.ipk
sudo ipkg install pyload-v0.4.9-noarch.ipk

1 2	wget http://get.pyload.org/static/pyload-v0.4.9-noarch.ipk sudo ipkg install pyload-v0.4.9-noarch.ipk

Running pyLoadCore

During the first start, pyLoad should place its default configuration under ~/.pyLoad, which it does, but nothing more. The -s parameter starts the initial setup process.

sudo pyLoadCore -s

1	sudo pyLoadCore -s

The command finished exactly after it was started. This couldn’t be the way it should work. I dug a little bit deeper and ran the following command to be able to see a few debug messages.

cd /volume1/@optware/share/pyload/
sudo python -vv pyLoadCore.py

1 2	cd /volume1/@optware/share/pyload/ sudo python -vv pyLoadCore.py

This provided me with this truncated output.

...
# trying /volume1/@optware/share/pyload/module/module.pyc
# trying /volume1/@optware/share/pyload/module/utils.so
# trying /volume1/@optware/share/pyload/module/utilsmodule.so
# trying /volume1/@optware/share/pyload/module/utils.py
# /volume1/@optware/share/pyload/module/utils.pyc has bad magic

...

# trying /volume1/@optware/share/pyload/module/module.pyc

# trying /volume1/@optware/share/pyload/module/utils.so

# trying /volume1/@optware/share/pyload/module/utilsmodule.so

# trying /volume1/@optware/share/pyload/module/utils.py

# /volume1/@optware/share/pyload/module/utils.pyc has bad magic

That message indicates a problem with some module. Some googling showed me, there is a problem with pyLoad an python2.5, which is default, running the python command. Knowing about this i tried python2.6, getting the same result. Only python2.7 gave me another result. But not the one i was expecting.

> $ sudo python2.7 pyLoadCore.py -s
Traceback (most recent call last):
  File "pyLoadCore.py", line 48, in <module>
    from module.network.RequestFactory import RequestFactory
  File "/volume1/@optware/share/pyload/module/network/RequestFactory.py", line 22, in <module>
    from Browser import Browser
  File "/volume1/@optware/share/pyload/module/network/Browser.py", line 6, in <module>
    from HTTPRequest import HTTPRequest
  File "/volume1/@optware/share/pyload/module/network/HTTPRequest.py", line 20, in <module>
    import pycurl
ImportError: No module named pycurl

> $ sudo python2.7 pyLoadCore.py -s

Traceback (most recent call last):

File "pyLoadCore.py", line 48, in <module>

from module.network.RequestFactory import RequestFactory

File "/volume1/@optware/share/pyload/module/network/RequestFactory.py", line 22, in <module>

from Browser import Browser

File "/volume1/@optware/share/pyload/module/network/Browser.py", line 6, in <module>

from HTTPRequest import HTTPRequest

File "/volume1/@optware/share/pyload/module/network/HTTPRequest.py", line 20, in <module>

import pycurl

ImportError: No module named pycurl

The needed pycurl is currently not available for python2.7 on arm architecture.

Now it was time to give up this way and switch to a more powerful but advanced solution.

Using a Debian chroot environment

What is chroot

Chroot is short for change root and means to change the root directory of a process running on a linux system. The process is encapsulated inside this environment and can’t access files and folders outside of it. With a few device mount-points we are able to run a whole linux system inside of this sandbox and can use all of the benefits of it without changing the host operating system. Chroot is a simple sandboxing and virtualization approach.

Remove pyLoad ipkg installation

Before we are getting started with our chroot installation, we will clean the mess we did earlier.

sudo ipkg remove pyload
sudo ipkg remove tesseract-ocr tesseract-ocr-lang-eng ossp-js  -force-removal-of-dependent-packages

1 2	sudo ipkg remove pyload sudo ipkg remove tesseract-ocr tesseract-ocr-lang-eng ossp-js -force-removal-of-dependent-packages

Chroot package from SynoCommunity

The guys over at SynoCommunity are providing a fully functional debian wheezy chroot environment. If you have added their repository into your DSM Package Center, simply install the debian-chroot package that can be found under the community tab.

: Community packages overview

: Debian chroot package

This will take a few minutes install because of its size. After the installation is finished, click the action dropdown and select run. The next steps will be performed via ssh on your DiskStation.

Set up your chroot environment

The first things we have to do, is to mount your Volume and to add all of your users. The last step is needed to prevent file-mode issues between the host system and your chroot.

Mount your volume

To enter your new environment, the package provides a simple script that could be called with some params. We will run the following commands to enter the chroot as root user and create a folder to mount your volume.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot
mkdir /volume1
exit

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

mkdir /volume1

exit

Now we have to edit the script we called seconds ago and add a few lines to handle the mounting of our volume. I will post the whole modified script with adding descriptions in just before the lines i added.

#!/bin/sh

# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"

# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`


start_daemon ()
{
    # Mount if install is finished
    if [ -f ${INSTALL_DIR}/var/installed ]; then
        # Make sure we don't mount twice
        grep -q "${CHROOTTARGET}/proc " /proc/mounts || mount -t proc proc ${CHROOTTARGET}/proc
        grep -q "${CHROOTTARGET}/sys " /proc/mounts || mount -t sysfs sys ${CHROOTTARGET}/sys
        grep -q "${CHROOTTARGET}/dev " /proc/mounts || mount -o bind /dev ${CHROOTTARGET}/dev
        grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts || mount -o bind /dev/pts ${CHROOTTARGET}/dev/pts

        ### ADDED mount volume 1 during start
        grep -q "${CHROOTTARGET}/volume1 " /proc/mounts || mount -o bind /volume1 ${CHROOTTARGET}/volume1

        # Start all services
        ${INSTALL_DIR}/app/start.py
    fi
}

stop_daemon ()
{
    # Stop running services
    ${INSTALL_DIR}/app/stop.py

    # Unmount
    umount ${CHROOTTARGET}/dev/pts
    umount ${CHROOTTARGET}/dev
    umount ${CHROOTTARGET}/sys
    umount ${CHROOTTARGET}/proc

    ### ADDED unmount volume 1 during shutdown
    umount ${CHROOTTARGET}/volume1

}

daemon_status ()
{
    `grep -q "${CHROOTTARGET}/proc " /proc/mounts` && `grep -q "${CHROOTTARGET}/sys " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts`
}


case $1 in
    start)
        if daemon_status; then
            echo ${DNAME} is already running
            exit 0
        else
            echo Starting ${DNAME} ...
            start_daemon
            exit $?
        fi
        ;;
    stop)
        if daemon_status; then
            echo Stopping ${DNAME} ...
            stop_daemon
            exit 0
        else
            echo ${DNAME} is not running
            exit 0
        fi
        ;;
    status)
        if daemon_status; then
            echo ${DNAME} is running
            exit 0
        else
            echo ${DNAME} is not running
            exit 1
        fi
        ;;
    chroot)
        chroot ${CHROOTTARGET}/ /bin/bash
        ;;
    *)
        exit 1
        ;;
esac

#!/bin/sh

# Package

PACKAGE="debian-chroot"

DNAME="Debian Chroot"

# Others

INSTALL_DIR="/usr/local/${PACKAGE}"

PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"

CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

start_daemon ()

{

# Mount if install is finished

if [ -f ${INSTALL_DIR}/var/installed ]; then

# Make sure we don't mount twice

grep -q "${CHROOTTARGET}/proc " /proc/mounts || mount -t proc proc ${CHROOTTARGET}/proc

grep -q "${CHROOTTARGET}/sys " /proc/mounts || mount -t sysfs sys ${CHROOTTARGET}/sys

grep -q "${CHROOTTARGET}/dev " /proc/mounts || mount -o bind /dev ${CHROOTTARGET}/dev

grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts || mount -o bind /dev/pts ${CHROOTTARGET}/dev/pts

### ADDED mount volume 1 during start

grep -q "${CHROOTTARGET}/volume1 " /proc/mounts || mount -o bind /volume1 ${CHROOTTARGET}/volume1

# Start all services

${INSTALL_DIR}/app/start.py

}

stop_daemon ()

{

# Stop running services

${INSTALL_DIR}/app/stop.py

# Unmount

umount ${CHROOTTARGET}/dev/pts

umount ${CHROOTTARGET}/dev

umount ${CHROOTTARGET}/sys

umount ${CHROOTTARGET}/proc

### ADDED unmount volume 1 during shutdown

umount ${CHROOTTARGET}/volume1

}

daemon_status ()

{

`grep -q "${CHROOTTARGET}/proc " /proc/mounts` && `grep -q "${CHROOTTARGET}/sys " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev " /proc/mounts` && `grep -q "${CHROOTTARGET}/dev/pts " /proc/mounts`

}

case $1 in

start)

if daemon_status; then

echo ${DNAME} is already running

exit 0

else

echo Starting ${DNAME} ...

start_daemon

exit $?

;;

stop)

if daemon_status; then

echo Stopping ${DNAME} ...

stop_daemon

exit 0

else

echo ${DNAME} is not running

exit 0

;;

status)

if daemon_status; then

echo ${DNAME} is running

exit 0

else

echo ${DNAME} is not running

exit 1

;;

chroot)

chroot ${CHROOTTARGET}/ /bin/bash

;;

exit 1

;;

esac

Now we can stop and restart the environment to be able to use our mounted volume.

sudo /var/packages/debian-chroot/scripts/start-stop-status stop
sudo /var/packages/debian-chroot/scripts/start-stop-status start

1 2	sudo /var/packages/debian-chroot/scripts/start-stop-status stop sudo /var/packages/debian-chroot/scripts/start-stop-status start

Generate locales and set timezone

By default Debian has no configured locale packages. We have to install them and set them up according to our needs.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

1	sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

aptitude update
aptitude upgrade
aptitude install locales
dpkg-reconfigure locales
dpkg-reconfigure tzdata
exit

aptitude update

aptitude upgrade

aptitude install locales

dpkg-reconfigure locales

dpkg-reconfigure tzdata

exit

Add the users and groups

To be able to write and read onto your data you have to set up a group inside your DSM that has full access to your volume and contains all of the users that should have access from inside your chroot.

Adding a new group is quiet simple. Open your DSM, start the Control Panel, click on groups and create a new one. Mine is called chroot and has access to all of my shared folders.

chroot group on dsm

For the next step we have to leave the DSM because there is no way to get the needed data from there. On your DiskStation shell, type the following commands and note the user id of your user added to the chroot-group and the id of the group itself.

> $ id andre
uid=1026(andre) gid=100(users) groups=100(users),101(administrators),65536(chroot),1023(http)

1 2	> $ id andre uid=1026(andre) gid=100(users) groups=100(users),101(administrators),65536(chroot),1023(http)

My user id is 1026 and the group id of chroot is 65536. With this information we can log into our debian environment.

sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

1	sudo /var/packages/debian-chroot/scripts/start-stop-status chroot

Now we are adding the user, in my case it is andre, and the group to the chroot environment. The home folder of the user is my DSM home folder. This is very convenient because now i’m able to share files and configurations that are stored inside of it between the host and the sandboxed system. Another benefit of it is, if you plan to remove the debian-chroot, all files will be kept inside of this folder even after removing the package.

adduser andre --uid 1026 --home /volume1/homes/andre/
addgroup --gid 65536 chroot
usermod -a -G chroot andre

adduser andre --uid 1026 --home /volume1/homes/andre/

addgroup --gid 65536 chroot

usermod -a -G chroot andre

If everything went fine you can check the following command and compare the output.

> # groups andre
andre : andre chroot

1 2	> # groups andre andre : andre chroot

Install pyLoad in chroot

The installation is simple, paste the following commands and you are ready to go.

apt-get install python-crypto python-pycurl python-imaging python-beaker tesseract-ocr tesseract-ocr-eng gocr unrar python-django
wget http://get.pyload.org/get/ubuntu-cli/ -O pyload-cli-v0.4.9-all.deb
dpkg -i pyload-cli-v0.4.9-all.deb

apt-get install python-crypto python-pycurl python-imaging python-beaker tesseract-ocr tesseract-ocr-eng gocr unrar python-django

wget http://get.pyload.org/get/ubuntu-cli/ -O pyload-cli-v0.4.9-all.deb

dpkg -i pyload-cli-v0.4.9-all.deb

You can now run the pyLoad setup process. But for me it was not suitable to run it as root, so i decided to change it to my local user andre. The following steps will show how to do it.

su andre
cd ~
pyLoadCore -s

su andre

cd ~

pyLoadCore -s

This starts the configuration wizard that will guide you through all necessary parts with ease.

After the config part you can run it directly with removing the -s part from the command. We will start it inside of a screen, to be able to detach the session and keep it up and running.

screen -d -m pyLoadCore

1	screen -d -m pyLoadCore

Autostart pyLoad on DiskStation boot

Because of your chroot-environment not being able to start and stop services by its own during boot-up or shutdown, we have to provide a little script that works from the inside of your DiskStation and is able to do this task.

vi /usr/syno/etc/rc.d/Z01debian-services.sh

1	vi /usr/syno/etc/rc.d/Z01debian-services.sh

Paste these code into the file.

#!/bin/sh

# Package
PACKAGE="debian-chroot"
DNAME="Debian Chroot"

# Others
INSTALL_DIR="/usr/local/${PACKAGE}"
PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"
CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

if [ "$*" = 'start' ] ; then
        # start chroot with mounts, this should be the first
        /var/packages/debian-chroot/scripts/start-stop-status start

        # starting pyload
        chroot ${CHROOTTARGET}/ su -c 'screen -d -m pyLoadCore' andre
else
        # shutdown pyload
        chroot ${CHROOTTARGET}/ su -c 'pyLoadCore -q' andre

        # shutdown chroot env
        /var/packages/debian-chroot/scripts/start-stop-status stop
fi

#!/bin/sh

# Package

PACKAGE="debian-chroot"

DNAME="Debian Chroot"

# Others

INSTALL_DIR="/usr/local/${PACKAGE}"

PATH="${INSTALL_DIR}/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/syno/sbin:/usr/syno/bin"

CHROOTTARGET=`realpath ${INSTALL_DIR}/var/chroottarget`

if [ "$*" = 'start' ] ; then

# start chroot with mounts, this should be the first

/var/packages/debian-chroot/scripts/start-stop-status start

# starting pyload

chroot ${CHROOTTARGET}/ su -c 'screen -d -m pyLoadCore' andre

else

# shutdown pyload

chroot ${CHROOTTARGET}/ su -c 'pyLoadCore -q' andre

# shutdown chroot env

/var/packages/debian-chroot/scripts/start-stop-status stop

The script will be launched every time the NAS will boot or shutdown and runs some commands inside your chroot to start or stop your services.

Thats it, you are now able to use pyLoad and it will start and stop automatically.

Use pyLoad

There are many ways to interact with the pyLoad-daemon. The most common way is to use the web-interface. Simply open http://{ip-of-your-ds}:8080 in your preferred browser and you will see some of the following screens. All of the configuration you did earlier during the set-up process can be changed under the config tab.

: pyLoad main screen

: pyLoad configuration screen

Sources

17 thoughts on “pyLoad in a Debian chroot on the DS215j”

William says:

Thank you for your solution!!
You explained very well.
And now I can download with pyload.

Youhoooooooooooooooooo


March 20, 2015 at 12:48 am
- TMJ says:
  
  Hi,
  
  I try this tutorial “pyLoad in a Debian chroot on the DS215j” but after editing “start-stop-status” file with nano editor when i try to start it i’ve this error msg : /var/packages/debian-chroot/scripts/start-stop-status: line 96: /volume1: Permission denied
  
  Where is my error ? I’ve copy and paste your whole modified script …
  
  Regards
  
  
  April 7, 2015 at 1:14 am
  - André says:
    
    Hi,
    
    could you please check to things.
    Your error message looks a bit suspicious, because my initial script only has 89 lines and the your error occured on line 96?
    Could you please paste the whole script?
    
    Did you run the script as root?
    
    Best regards,
    André
    
    
    April 7, 2015 at 9:01 am
Squall_Titus says:

Sorry but i get stuck on the step

Generate locales and set timezone
By default Debian has no configured locale packages. We have to install them and set them up according to our needs.

I get the message
chroot: can’t execute ‘/bin/zsh’: No such file or directory

zsh is not installed so this message is correct. What can i do?


April 7, 2015 at 9:01 pm
- André says:
  
  Hi Klaus,
  
  you have been completely right.
  by mistake i copied my zsh startup-command. i fixed it now.
  You just have to replace zsh with bash.
  
  Thanks for this comment.
  
  Best regards,
  André
  
  
  April 10, 2015 at 2:51 pm
Chrosey says:

Hey,

I try to follow your How-To but when i try to Mount my Volume shell tells me
“ash: sudo: not found”

Can you help me?


June 13, 2015 at 2:33 pm
- André says:
  
  Hey,
  
  this tutorial depends on my other how-to bootstrap ds215j.
  You just have to install sudo via ipkg as root.
  ipkg install sudo.
  
  Or the simplest way is to use the root user, then there is no need for sudo.
  
  Best regards,
  André
  
  
  June 13, 2015 at 8:30 pm
Alex says:

You won’t need this anymore. SynoCommunity just released a pyload beta package, which is availably in their repo. Just install and you are fine. 🙂


June 14, 2015 at 2:52 pm
Rico says:

@André
Thanks for the guide, it worked but I couldn’t get pyload to start automatically in chroot

@Alex
THANKS A THOUSAND TIMES for posting this. I would have never seen they released it!


June 16, 2015 at 9:42 pm
- André says:
  
  Hi Rico,
  
  did you follow the autostart steps from “Autostart pyLoad on DiskStation boot”?
  I think you have to change the user used in this script from “andre” to your debian username. Hopefully this will solve your issues.
  
  best regards
  André
  
  
  June 17, 2015 at 9:17 am
david says:

@Alex
I tried to install the pyload beta package of SynoCommunity but it did not work.

@André
Is your method still the only one that works?


November 27, 2015 at 9:02 pm
- André says:
  
  Hey David,
  
  as far as I know, it is.
  But I moved from pyload to JDownloader2 in headless mode using the debian chroot.
  
  Best regards,
  André
  
  
  November 27, 2015 at 9:12 pm
  - david says:
    
    Hi André,
    
    Why did you move from Pyload to JDownloader2? Can you explain a little what are the pros and cons?
    
    I’ve found a tutorial to install JDownloader2 without using debian chroot. Is it better to use debian chroot?
    
    I am a new owner of a SYNOLOGY DS215J so I don’t know so much about all these stuffs…
    
    Best regards,
    David
    
    
    November 28, 2015 at 7:27 am
    - André says:
      
      The main reason why i switched from pyLoad to JDownloader is the performance and the overall integration.
      Lately pyLoad became very slow, it took almost 10s to render the downloads overview or to add a new link.
      I searched for an alternative and remembered that JDownloader was capable of all the things i need but i thought i needs at least an x-server (window-server) to be able to run.
      The latest JDownloader2 integrates their own web-cloud-frontend (http://my.jdownloader.org). This enables you to add links from wherever you want. There is also an app for Android.
      And it redirects the captcha request directly to you.
      
      Regarding the bootstrap, I had problem with installing java on my DS215j outside of the bootstrapped debian, but if you have a good tutorial, please forward it to me 😉
      
      If you have any question feel free to ask.
      
      FYI: JDownloader eats a lot of CPU (because of Java), you should be aware of this, when you install it on your diskstation.
      
      
      November 29, 2015 at 5:09 pm
- David says:
  
  Hi André,
  
  Finally I decided to install Pyload with your tutorial but i’m stuck with the installation of the locale packages:
  
  Nas1> /var/packages/debian-chroot/scripts/start-stop-status chroot
  bash: warning: setlocale: LC_ALL: cannot change locale (en_US.utf8)
  root@Nas1:/# aptitude update
  bash: aptitude: command not found
  
  How do I install ‘aptitude’?
  
  
  December 5, 2015 at 6:27 pm
  - André says:
    
    Hey David,
    
    the “locale” output is just a warning, you can ignore it by now.
    To install aptitude just type apt-get install aptitude.
    Or replace every aptitude command with apt-get, it does the same, but aptitude has some more advantages that are not needed to install pyload.
    
    Best regards,
    André
    
    
    December 5, 2015 at 6:33 pm
    - David says:
      
      Hi André,
      
      Thank you very much for your help! I had to fix some other issues but now I have Pyload correctly installed in my ds215j.
      
      Best regards,
      David
      
      
      December 6, 2015 at 8:13 pm

refresh your live

refresh your live

about cooking, coding and the perfect work-out

pyLoad in a Debian chroot on the DS215j

Introduction

Install pyLoad

From ipkg sources

Needed packages

Download the pyLoad package

Running pyLoadCore

Using a Debian chroot environment

What is chroot

Remove pyLoad ipkg installation

Chroot package from SynoCommunity

Set up your chroot environment

Mount your volume

Generate locales and set timezone

Add the users and groups

Install pyLoad in chroot

Autostart pyLoad on DiskStation boot

Use pyLoad

Sources

Related

17 thoughts on “pyLoad in a Debian chroot on the DS215j”

Leave a Reply Cancel reply

refresh your live

Introduction

Install pyLoad

From ipkg sources

Needed packages

Download the pyLoad package

Running pyLoadCore

Using a Debian chroot environment

What is chroot

Remove pyLoad ipkg installation

Chroot package from SynoCommunity

Set up your chroot environment

Mount your volume

Generate locales and set timezone

Add the users and groups

Install pyLoad in chroot

Autostart pyLoad on DiskStation boot

Use pyLoad

Sources

Share this:

Related

17 thoughts on “pyLoad in a Debian chroot on the DS215j”

Leave a Reply Cancel reply