yes, the upgrade scripts have to be run as seafile user, if you don't run seafile as root in general.
Posts by sieben
-
-
one needs an entry in extra options
Why do you need an entry in extra options?
You can leave it as it is, to store the mysql data in the default directory. -
FYI: Version 5.1.4 is released:
Seafile Server 5.1.4 for Raspberry Pi
https://github.com/haiwen/seaf….1.4_stable_pi.tar.gz.tar
-> Be aware that it's packaged twice. 1) extract with "tar -xf ...." 2) extract with "tar -xzf ...."
Update procedure:
- Stop Seafile
- Be sure to use the seafile-dedicated user from now on:
- Extract downloaded file
- Check that all permissions are correct, according to your user used for seafile
- Select appropriate update script in the extracted directory (e.g. seafile-server-5.1.4/upgrade/minor_upgrade.sh)
- Execute the script.
- Start Seafile- Delete old seafile version, or keep it as a fallback version
-
@omavoss
The version of the mysql plugin doesn't matter for seafile. Don't worry about the data directory. -
1) Use the autoshutdown plug-in for scheduled shutdown, I'm not sure how it works with a scheduled wakeup (but WOL would fit for that)
2) WOL: enabled in the BIOS as well?
-
i get this error message on the terminal....
Just to make sure:
You installed the needed packages?Codeapt-get update apt-get install python2.7 libpython2.7 python-setuptools python-imaging \ python-ldap python-mysqldb python-memcache python-urllib3
@baldman btw: I think "python-urllib3" is not yet included in the tutorial
-
A lot of times I see people where their graphs data is corrupted. These are best instructions I give to reset graphs with corrupted database.
rm -r /var/lib/rrdcached/db/localhost
rm /var/lib/rrdcached/journal/*
service collectd restart
service rrdcached restartThis fixed my missing graphs, too. Obviously everything got corrupted because of some issues I had with ntp on a banana pi. Thanks!
-
no matter what i did, trying to download the 5.1.3 by using the link as generously instructed by sieben..
Sorry that I have to correct you, but the link in my post is still correct, as it includes the "download" directory. Maybe you took the wrong one (citation) at the top of my post.
Nevertheless: the most important thing is you have seafile 5 running
The installation on your c2 with erasmus should work as well. There is nothing crucial changing in the way of installing.
-
I fixed the permission error,
but it seems like jdownloader gets stuck during the update procedure.Does someone have any tweaks for a succesful installation via the plugins?
-
For other people struggling with the installation on a banana PI
You need armbian running first and afterwards you can use this thread to install OMV 3 -
Hey, I don't get jdownloader to run and already tried purging/reinstalling on OMV 2 - Plugin version 1.0.10
When I manually execute the command from the init script it returns this strange permission denied error:
start-stop-daemon: unable to start /usr/bin/java (Permission denied)
Does someone have any advice?
-
Please use the following link, you probably got a wrong link from somewhere.
Releases are published here: https://github.com/haiwen/seafile-rpi/releaseshttps://github.com/haiwen/seaf…er_stable_5.1.3_pi.tar.gz
Try to install seafile 5 with this zip from scratch, using @baldman instructions. They are well defined and tested.
-
Versions are the same as the regular Linux versions. Release is only a few days or weeks behind. Check
https://www.seafile.com/en/download/ -
I could try that, too. Mainly I want to have XBMC/Kodi & Plex (or emby) running on it.
-
Thanks. Then I will reinstall debian + OMV from scratch or maybe use another distribution which is better suitable for a HTPC environment.
I really liked the idea of having OMV on the HTPC, too. Not only on my bananaPI. -
Hey there,
I have a desktop debian 7 (I want to use the server as HTPC with connected TV, too) and installed OMV ontop.
Some point in time after I deinstalled some pre-installed debian packages I encounter this error when I tried to install omvextrasorg.
Did anyone encounter this error before? I'd love to hear some advice about this, otherwise I'd just reinstall the whole system.Code
Display Moreroot@server:/tmp# dpkg -i openmediavault-omvextrasorg_latest_all.deb Selecting previously unselected package openmediavault-omvextrasorg. (Reading database ... 126594 files and directories currently installed.) Unpacking openmediavault-omvextrasorg (from openmediavault-omvextrasorg_latest_all.deb) ... Setting up openmediavault-omvextrasorg (2.13.2) ... Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Initialize configuration Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 Warning: program compiled against libxml 209 using older 208 dpkg: error processing openmediavault-omvextrasorg (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for openmediavault ... Restarting engine daemon ... Errors were encountered while processing: openmediavault-omvextrasorg root@server:/tmp# warning: program compiled against "libxml 209 using older 208"
Thanks
-
I once did, but disabled it again...
-
Warning: program compiled against libxml 209 using older 208
I have the same issue, which pops up every time I'm updating or installing something. Is there any solution or known reason for this?
-
Then the seafile user doesn't have sufficient permission in the current directory.
You are in the root "/" directory --> no permissions for seafile user.You should install seafile either to the home directory of seafile /home/seafile/
or like the tutorial says:
in /opt/seafile (create this directory with root and give seafile-user the permissions) -
tcp6 0 0 :::7443 :::* LISTEN 0 1769697 3135/nginx
This shows you're using IPv6 protocol, that should be the reason.
I can't tell how to change that with the nginx plugin, I'm not using it, sorry.