seafile.service - Seafile
Loaded: loaded (/etc/systemd/system/seafile.service; enabled)
Active: active (exited) since Sun 2017-03-26 19:16:17 UTC; 2min 18s ago
Process: 24430 ExecStop=/home/seafile/haiwen/seafile-server-latest/seafile.sh stop (code=exited, status=0/SUCCESS)
Process: 26425 ExecStart=/home/seafile/haiwen/seafile-server-latest/seafile.sh start (code=exited, status=0/SUCCESS)
Main PID: 26425 (code=exited, status=0/SUCCESS)
After a few hours this is output of service status:
$ service seafile status
seafile.service - Seafile
Loaded: loaded (/etc/systemd/system/seafile.service; enabled)
Active: inactive (dead) since Sun 2017-03-26 17:20:41 UTC; 1h 54min ago
Process: 24430 ExecStop=/home/seafile/haiwen/seafile-server-latest/seafile.sh stop (code=exited, status=0/SUCCESS)
Process: 24278 ExecStart=/home/seafile/haiwen/seafile-server-latest/seafile.sh start (code=exited, status=0/SUCCESS)
Main PID: 24278 (code=exited, status=0/SUCCESS)
I’m using systemd services to start at boot and works fine. My services are configured as follows:
[Unit]
Description=Seafile
# add mysql.service or postgresql.service depending on your database to the line below
After=network.target mysql.service
RequiresMountsFor=/mnt/iomegahdd
[Service]
Type=oneshot
ExecStart=/home/seafile/haiwen/seafile-server-latest/seafile.sh start
ExecStop=/home/seafile/haiwen/seafile-server-latest/seafile.sh stop
RemainAfterExit=yes
User=seafile
Group=seafile
[Install]
WantedBy=multi-user.target
Seahub:
[Unit]
Description=Seafile hub
After=network.target seafile.service
[Service]
# change start to start-fastcgi if you want to run fastcgi
ExecStart=/home/seafile/haiwen/seafile-server-latest/seahub.sh start-fastcgi
ExecStop=/home/seafile/haiwen/seafile-server-latest/seahub.sh stop
User=seafile
Group=seafile
Type=oneshot
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Anyone know why it keeps stopping every few hours? The sync stops working but Seahub service keeps on running. I’m using seafile with mysql and nginx on a raspberry pi using raspbian.
I think you should use Seafile Server version 6.0.8 for Raspberry Pi, with raspbian I think there must be a problem with raspberry RAM (it takes at least 2 GB of RAM on a standard installation). The seafile server version for raspberry is optimized for this lack of RAM memory.
Check the kern.log file in /var/log to see if this is a memory problem.
I have not found the cause of your problem.
I put a link of your log files, if someone else wants to look at your configuration to find your problem. https://seafile.okki.me/d/d8f294b9d4/
Just a quick idea for your problem. The kern.log shows that your usb-disk is disconnecting and reconnecting 2 times with a “Buffer I/O error on dev sda1”. If you did not disconnect and reconnect the disk without unmounting it, this looks like a problem with your usb-disk/usb-ata bridge or the power supply of it.