Seafile Server 7.1.4 for Raspberry Pi is ready! 23.05.2020

And now i got next problem, Error:Seahub failed to start…
Could it be that my python (on armbian stretch) is too old? (python3 -V says Python 3.5.3) ?

sure cancel it, and don’t worry. The compilation process will long about almost 4 hours with a raspberry pi 3b+ with the enabled-optimizations flag

Seems you have the same error like me (I use also an Debian Stretch but on a Cubietruck). We have to install like @jobenvil has suggested Python 3.6.10

@nihilistaX :cold_face: yes, i told you, please here:



1 Like

OK, sorry for that, its hard work to collect all needed things and forget nothing :grin:

You are true, I created the symbolic link in the wrong place. I just correct it and… the issue is still here.

ls -la /home/pi/SeaFile/seafile-server-7.1.4/seafile/lib give me :

lrwxrwxrwx 1 seafile nogroup 9 mai 24 02:44 python3.6 -> python3.7

Great! Thank you very much :wink:

After start seahub, I have this message :
File “/home/seafile/seafile-server-7.1.4/”, line 284, in init[29214]: import ccnet[29214]: ModuleNotFoundError: No module named ‘ccnet’
what’s going on ?

@jobenvil, the python modules for seafdav seem missing.
They are listed on github seafdav/requirements.txt.

Did you check all above?
I had this error, too, but i had to read much and upgrade my device to buster for newer python version (did you check yours?), set the python3.6 link and so on… i think you missed something.
And @jobenvil : Great work, all working good if step by step doing what you recommended above. :+1:
Bit tricky as a python-noob and i did buster upgrade instead of fiddling with python…but after several hours of work i get all working again, btw… :sweat_smile:

All we suffered with the Python3 stuff, not only you. :wink: but now, you are save until Python4 :laughing:

The following updates will be like the old good days. Don’t worry.

@axstet unless you want to install outdated packages I recommend you don’t do it. The mandatory dependences are already documented on the manual, like jinja2, sqlalchemy:

pip3 install --timeout=3600 Pillow pylibmc captcha jinja2 sqlalchemy \    django-pylibmc django-simple-captcha python3-ldap

Others like PyYAML are optional and in fact, we don’t use it at all, since we don’t work at all with a yaml config file.

BUT, I realized that for lxml package, even if it is optional requirement, you will get follow WARNING, while starting SeafDAV:

2020-04-22 20:18:12.276 - <-1225219248> wsgidav WARNING : Could not import lxml: using xml instead (up to 10% slower)

And we don’t want be in any case 10% slower using WebDAV, do we? Absolutly not :muscle:

The point is that lxml depends on other dev libraries (libxml2-dev libxslt-dev ) to be compiled and they cause many MBs more for the rpi-packages. Anyhow, I put them on the rpi packages.

Either you can download the new packages or do it yourself. I recommend to avoid pip if these packages are for your OS available. Try:

sudo apt-get install libxml2-dev libxslt-dev

and then sudo apt install python3-lxml python3-jsmin python3-defusedxml python3-pam

These will install your native libraries from your OS and the adventage, they will get updated every time with your OS and not manually by using pip

Thanks for reporting.

Did you get any errors when you try to run You must go to the $INSTALLDIR/seafile/lib/ and then execute ln -s python3.7 python3.6 so that you get a symlink in the library directory
blablub@hostname:/mnt/daten/seafile/seafile-server-7.1.4/seafile/lib# ls -ald python*
lrwxrwxrwx 1 root root 9 Mai 24 16:44 python3.6 -> python3.7
drwxr-xr-x 3 seafile seafile 4096 Mai 21 17:58 python3.7

Same for you herve:

You must go to the "$INSTALLDIR/seafile/lib/" and then execute "ln -s python3.7 python3.6" so that you get a symlink in the library directory

Hey, thank you very much for all the great work here!!
But regarding the specific points you made here, I have to disagree: on my installation, SeafDAV did only start after installing jsmin, defusedxml and pyyaml via pip. Otherwise, it failed when trying to import these modules.

I decide to do an in place distribution upgrade from Debian Stretch to Debian Buster. All the necessary commands I was using are listed here:

Do a update from the momentary installed Debian Stretch:
apt update -y
apt upgrade -y

Edit the packages sources:
apt edit-sources OR edit /etc/apt/sources.list

deb buster main contrib non-free
#deb-src buster main contrib non-free

deb buster-updates main contrib non-free
#deb-src buster-updates main contrib non-free

deb buster-backports main contrib non-free
#deb-src buster-backports main contrib non-free

deb buster/updates main contrib non-free
#deb-src buster/updates main contrib non-free

apt edit sources armbian.list OR edit /etc/apt/sources.list.d/armbian.list

deb buster main

Do the in place distribution upgrade:

apt update -y
apt clean
apt dist-upgrade -y

Maybe some questions about how to proceed with configuration files will be shown where the user has to decide what to do, to override with new version or to leave the original one

Restart the server after the upgrade is finished:


After reboot obsolete unncessary packages can be deleted with:
apt autoremove -y

I set the symbolic link:
cd $INSTALLDIR/seafile/lib/
ln -s python3.7 python3.6

Then I did a restart from the services with:

systemctl restart seafile.service seahub.service

1 Like

Installing via pip should be avoided if your OS already has the python3 package unless you have a good argument. i.e. you use the --user flag therefore only seafile user can use it adn so forth. Which OS do you have?

No specific reason, thanks for the advice—replaced the pip packages now with apt-get versions, but nevertheless, they were missing completely on my system before. I am on a Raspbian/Debian Buster installation.

Regarding my specific issue, that occures when I execute the installation script ./, I’m not sure that the solution is the symbolic link python3.6 -> python 3.7 because :

  1. I did it and the issue is still here ;
  2. In the folder /home/pi/SeaFile/seafile-server-7.1.4/seafile/bin/ the file seaf-server-init is actually missing. When I copy/paste a file seaf-server-init from an old installation on Raspbian Stretch the installation script ./ displays the mistake below (and once again is actually missing in $INSTALLDIR/seafile/lib/ but it’s probably linked with use of old seaf-server-init)

/home/pi/SeaFile/seafile-server-7.1.4/seafile/bin/seaf-server-init: error while loading shared libraries: cannot open shared object file: No such file or directory
Failed to generate seafile configuration

Sorry to boring everybody with my will to perform a fresh install of SeaFile and not just an update (probably more easier)… Many thanks for your help !!!

Have a nice day.

@IssueFindings don’t worry, the point from @klangborste is that if you use the rpi.stretch version, you must install Python 3.6.10 as well. It is not enough creating the symlink.