Raspberry pi (Bulseye): Failed to start seafile server

Seafile Server
1

Hi,
I installed Seafile 9.0.2 on my Raspberry pi wit the new bullseye.
Everything going well on the installation also the seafile user and the mysql.
But if I try to start the server the first time with this:

seafile@raspberrypi:~/seafile-server-latest $ ./seafile.sh start

Starting seafile server, please wait ...
./seafile.sh: Zeile 143: /home/seafile/seafile-server-9.0.2/seafile/bin/seafile-controller: Datei oder Verzeichnis nicht gefunden
Failed to start seafile server

I see the error Failed to start seafile server.
I have no Idea what the problem can be. In the seafile journal journalctl -u seahub is nothing declared.
Hopefull someone can help me?

EDIT: with ./seahub.sh start-fastcgi I got a error:

LC_ALL is not set in ENV, set to en_US.UTF-8
./seahub.sh: Zeile 220: Warnung: setlocale: LC_ALL: Kann die Regionseinstellungen nicht ändern (en_US.UTF-8): Datei oder Verzeichnis nicht gefunden

Warning: seafile-controller not running. Have you run "./seafile.sh start" ?

I found something here at the forum for adding unit with systemd. But there I got this error

Job for seahub.service failed because the control process exited with error code.
See "systemctl status seahub.service" and "journalctl -xe" for details.

with systemctl status seafile.serviceI got this output:

● seafile.service - Seafile
     Loaded: loaded (/etc/systemd/system/seafile.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2022-03-20 23:48:35 GMT; 40s ago
   Main PID: 2644 (code=exited, status=1/FAILURE)
        CPU: 277ms

Second EDIT:
With the help from here I solved the error /path/to/seafile/seahub.sh: line 210: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory. But the server still does not start.

Cheers

2

Is /home/seafile/seafile-server-9.0.2/seafile/bin/seafile-controller really missing?

3

Hi,
no the file is there.
I followed the instruction here for installing on bullseye.

EDIT: Okay I was not in the application folder. it was the folder where are the installation files where and not the end application.

4

Not sure to understand, is this a yes or a no? :upside_down_face:

Then, there’s no difference between “installation files” and “end application files” in the instructions you’ve linked (which is expected). Looks like you moved some files you shouldn’t have to.

Easier way is probably to clean things and repeat these steps (and following):

Archiv herunterladen, entpacken und in Ordner „installed“ verschieben (sieht einfach schöner aus):

wget https://github.com/haiwen/seafile-rpi/releases/download/v9.0.2/seafile-server-9.0.2-bullseye-arm32v7l.tar.gz
tar xfvz seafile-server-9.0.2-bullseye-arm32v7l.tar.gz
mkdir installed
mv seafile-server-9.0.2-bullseye-arm32v7l.tar.gz installed/

In den entpackten Ordner wechsel und Installation starten:

cd seafile-server-9.0.2
./setup-seafile-mysql.sh
5

Hi,
yes your right.
There was files where they not should be.
I startet everting new and the server is running.
But now I have a problem with my nginx. I can’t open the webpage.
I got a Not found or 500 Error.
I installed the seafile on Port 8085 no0t on 8082 so I changed it in the seafile.conf

server {
    listen 80;
    listen [::]:80;
    
    server_name _;

    proxy_set_header X-Forwarded-For $remote_addr;

    location / {
         proxy_pass         http://127.0.0.1:8000;
         proxy_set_header   Host $host;
         proxy_set_header   X-Real-IP $remote_addr;
         proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
         proxy_set_header   X-Forwarded-Host $server_name;
         proxy_read_timeout  1200s;

         client_max_body_size 0;

         access_log      /var/log/nginx/seahub.access.log;
         error_log       /var/log/nginx/seahub.error.log;
    }
	
    location /seafhttp {
	rewrite ^/seafhttp(.*)$ $1 break;
	proxy_pass http://127.0.0.1:8085;
	client_max_body_size 0;
	proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;

	proxy_connect_timeout  36000s;
	proxy_read_timeout  36000s;
	proxy_send_timeout  36000s;

	send_timeout  36000s;

	access_log      /var/log/nginx/seafhttp.access.log;
	error_log       /var/log/nginx/seafhttp.error.log;
    }
    location /media {
        root /home/seafile/seafile-server-latest/seahub;
    }
}

here is also my seahub_settings.py

# -*- coding: utf-8 -*-
SECRET_KEY = ****************

SERVICE_URL = 'http://192.168.178.28'

FILE_SERVER_ROOT = 'http://192.168.178.28/seafhttp'

DATABASES = {
    'default': {
        'ENGINE': 'django.db.backends.mysql',
        'NAME': 'seahub-db',
        'USER': 'seafile',
        'PASSWORD': ************,
        'HOST': '127.0.0.1',
        'PORT': '3306',
        'OPTIONS': {'charset': 'utf8mb4'},
    }
}

I’m a little bit lost to identify my nginx problem.

6

I don’t see anything obvious, something in the logs (home/seafile/logs)?

For which path do you get which error?

7

Hi,
in my seafile.log file I have this:

2022-03-26 18:20:52 socket file exists, delete it anyway
2022-03-26 18:20:52 ../common/seaf-utils.c(333): Use database Mysql
2022-03-26 18:20:52 http-server.c(192): fileserver: worker_threads = 10
2022-03-26 18:20:52 http-server.c(206): fileserver: fixed_block_size = 8388608
2022-03-26 18:20:52 http-server.c(221): fileserver: web_token_expire_time = 3600
2022-03-26 18:20:52 http-server.c(236): fileserver: max_indexing_threads = 1
2022-03-26 18:20:52 http-server.c(251): fileserver: max_index_processing_threads= 3
2022-03-26 18:20:52 http-server.c(273): fileserver: cluster_shared_temp_file_mode = 600
2022-03-26 18:21:16 start to serve on pipe client

It looks like okay. All other files are empty.
On the configuration I mentioned on my post before I got a Not found. I thing it stands for a 400er error.

If I try to load http://192.168.178.28/seafhttp directly in the browser I got the 500.

EDIT: I take a look if the port 8085 is open with sudo netstat -pant | grep 8085 and i got this as a output tcp 0 0 0.0.0.0:8085 0.0.0.0:* LISTEN 844/seaf-server should there not stand 127.0.0.1 where actually is print 0 0.0.0.0?
What have I do here wrong?

Best

8

This is expected, you’re not supposed to access this path directly from your browser. This shows that at least the fileserver works.

Then, looks like you have another service running on port 8000, you should check that.

9

@Barolo Thank you very much for your help.
I deleted the whole raspberry and start install all again from scratch.
I got in last also a crashed Maria DB and It was enough for me.

Cheers