Systemd ubuntu scripts in manual are faulty


#1

The scripts lack runlevel info and dont work on ubuntu 18.
also after completing them with runlevel info seahub exits with failure. but it can be started manually. which log to look in for that error?
https://manual.seafile.com/deploy/start_seafile_at_system_bootup.html

my syslog:

Oct  7 08:24:46 -pc systemd[1]: Starting seafile.service...
Oct  7 08:24:46 -pc systemd[1]: Starting seahub.service...
Oct  7 08:24:46 -pc systemd[3020]: seafile.service: Failed to execute command: Exec format error
Oct  7 08:24:46 -pc systemd[3020]: seafile.service: Failed at step EXEC spawning /etc/init.d/seafile: Exec format error
Oct  7 08:24:46 -pc systemd[3022]: seahub.service: Failed to execute command: Exec format error
Oct  7 08:24:46 -pc systemd[3022]: seahub.service: Failed at step EXEC spawning /etc/init.d/seahub: Exec 
format error
Oct  7 08:24:46 -pc systemd[1]: seafile.service: Control process exited, code=exited status=203
Oct  7 08:24:46 -pc systemd[1]: seafile.service: Failed with result 'exit-code'.
Oct  7 08:24:46 -pc systemd[1]: Failed to start seafile.service.
Oct  7 08:24:46 -pc systemd[1]: seahub.service: Control process exited, code=exited status=203
Oct  7 08:24:46 -pc systemd[1]: seahub.service: Failed with result 'exit-code'.
Oct  7 08:24:46 -pc systemd[1]: Failed to start seahub.service.

seafile.service file:

#!/bin/bash
### BEGIN INIT INFO
# Provides:          seafile_server
# Required-Start:    $all
# Required-Stop:
# Default-Start:     5
# Default-Stop:         4
# Short-Description: Halts USB power...
### END INIT INFO
[Unit]
Description=Seafile
# add mysql.service or postgresql.service depending on your database to the line below
After=network.target

[Service]
Type=forking
ExecStart=/seafile-server/seafile-server-latest/seafile.sh start
ExecStop=/seafile-server/seafile-server-latest/seafile.sh stop
User=user
Group=user

[Install]
WantedBy=multi-user.target

seahub.service file:

#!/bin/bash
### BEGIN INIT INFO
# Provides:          seafile_server
# Required-Start:    $all
# Required-Stop:
# Default-Start:     5
# Default-Stop:         4
# Short-Description: Halts USB power...
### END INIT INFO

[Unit]
Description=Seafile hub
After=seafile.service

[Service]
Type=forking
# change start to start-fastcgi if you want to run fastcgi
ExecStart=/seafile-server/seafile-server-latest/seahub.sh start
ExecStop=/seafile-server/seafile-server-latest/seahub.sh stop
User=user
Group=user

[Install]
WantedBy=multi-user.target

Runnint the script in a shell as user /seafile-server/seafile-server-latest/seahub.sh start works. so it seems seahub.sh start needs a bash shell to execute?


#2

Why do you start it with a bash shebang? It’s systemd, not SyS V init or some rc init.


#3

ok removed that, same result, seahub does not want to start, but starts manually

root@--pc:/seafile-server/seafile-pro-server-6.2.9# systemctl status seahub.service
● seahub.service - Seafile hub
   Loaded: loaded (/etc/systemd/system/seahub.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-10-07 09:50:04 CEST; 7s ago
  Process: 10923 ExecStart=/seafile-server/seafile-server-latest/seahub.sh start (code=exited, status=1/FAILURE)

Okt 07 09:49:59 --pc systemd[1]: Starting Seafile hub...
Okt 07 09:49:59 --pc seahub.sh[10923]: LC_ALL is not set in ENV, set to en_US.UTF-8
Okt 07 09:49:59 --pc seahub.sh[10923]: Starting seahub at port 8000 ...
Okt 07 09:50:04 --pc seahub.sh[10923]: Error:Seahub failed to start.
Okt 07 09:50:04 --pc seahub.sh[10923]: Please try to run "./seahub.sh start" again
Okt 07 09:50:04 --pc systemd[1]: seahub.service: Control process exited, code=exited status=1
Okt 07 09:50:04 --pc systemd[1]: seahub.service: Failed with result 'exit-code'.
Okt 07 09:50:04 --pc systemd[1]: Failed to start Seafile hub.
root@--pc:/seafile-server/seafile-pro-server-6.2.9# /seafile-server/seafile-server-latest/seahub.sh start

LC_ALL is not set in ENV, set to en_US.UTF-8
Starting seahub at port 8000 ...

Seahub is started

Done.

#4

I’ll look when I’m back.
[Unit]
Description=Seafile
# add mysql.service or postgresql.service depending on your database to the line below
After=network.target mysql.service

[Service]
Type=forking
ExecStart=/home/seafile/seafile-server-latest/seafile.sh start
ExecStop=/home/seafile/seafile-server-latest/seafile.sh stop
User=seafile
Group=seafile

[Install]
WantedBy=multi-user.target


#5

Can you please post your seahub.log and seafile.log?


#6

al there is in seahub.log (i started on October 7th with the systemd thing):

2018-09-25 06:33:42,590 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-09-27 06:07:41,888 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-09-28 06:53:03,964 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-10-02 06:48:33,707 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-10-02 13:05:56,113 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-10-06 06:44:07,606 [WARNING] django.request:170 get_response Not Found: /seafhttp/protocol-version
2018-10-07 08:29:02,054 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 08:29:02,094 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 08:29:11,789 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 08:29:11,830 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 08:29:32,796 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 08:29:32,835 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 08:52:16,315 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 08:52:16,372 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 09:18:07,135 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 09:18:07,233 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 09:18:15,108 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-07 09:21:40,685 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-07 09:21:40,742 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-07 09:21:42,613 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-07 09:21:49,690 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-07 09:24:34,764 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-07 09:27:36,758 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain

seafile.log:

[10/04/2018 11:44:33 PM] size-sched.c(103): Repo size compute queue size is 0
[10/04/2018 11:49:33 PM] size-sched.c(103): Repo size compute queue size is 0
[10/06/18 08:44:02] http-server.c(195): fileserver: worker_threads = 10
[10/06/18 08:44:02] http-server.c(208): fileserver: backlog = 32
[10/06/18 08:44:02] http-server.c(223): fileserver: fixed_block_size = 8388608
[10/06/18 08:44:02] http-server.c(238): fileserver: web_token_expire_time = 3600
[10/06/18 08:44:02] http-server.c(253): fileserver: max_indexing_threads = 1
[10/06/2018 08:44:02 AM] ../common/mq-mgr.c(61): [mq client] mq cilent is started
[10/06/2018 08:44:02 AM] filelock-mgr.c(924): Cleaning expired file locks.
[10/06/2018 08:44:03 AM] size-sched.c(103): Repo size compute queue size is 0
[10/06/2018 08:49:03 AM] size-sched.c(103): Repo size compute queue size is 0
[10/06/2018 08:54:03 AM] size-sched.c(103): Repo size compute queue size is 0
[10/06/2018 08:59:03 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/18 08:51:36] http-server.c(195): fileserver: worker_threads = 10
[10/07/18 08:51:36] http-server.c(208): fileserver: backlog = 32
[10/07/18 08:51:36] http-server.c(223): fileserver: fixed_block_size = 8388608
[10/07/18 08:51:36] http-server.c(238): fileserver: web_token_expire_time = 3600
[10/07/18 08:51:36] http-server.c(253): fileserver: max_indexing_threads = 1
[10/07/2018 08:51:36 AM] ../common/mq-mgr.c(61): [mq client] mq cilent is started
[10/07/2018 08:51:36 AM] filelock-mgr.c(924): Cleaning expired file locks.
[10/07/2018 08:51:37 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 08:51:40 AM] Disconnected from daemon
[10/07/18 08:53:01] http-server.c(195): fileserver: worker_threads = 10
[10/07/18 08:53:01] http-server.c(208): fileserver: backlog = 32
[10/07/18 08:53:01] http-server.c(223): fileserver: fixed_block_size = 8388608
[10/07/18 08:53:01] http-server.c(238): fileserver: web_token_expire_time = 3600
[10/07/18 08:53:01] http-server.c(253): fileserver: max_indexing_threads = 1
[10/07/2018 08:53:01 AM] ../common/mq-mgr.c(61): [mq client] mq cilent is started
[10/07/2018 08:53:01 AM] filelock-mgr.c(924): Cleaning expired file locks.
[10/07/2018 08:53:02 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 08:53:52 AM] Disconnected from daemon
[10/07/18 09:01:16] http-server.c(195): fileserver: worker_threads = 10
[10/07/18 09:01:16] http-server.c(208): fileserver: backlog = 32
[10/07/18 09:01:16] http-server.c(223): fileserver: fixed_block_size = 8388608
[10/07/18 09:01:16] http-server.c(238): fileserver: web_token_expire_time = 3600
[10/07/18 09:01:16] http-server.c(253): fileserver: max_indexing_threads = 1
[10/07/2018 09:01:16 AM] ../common/mq-mgr.c(61): [mq client] mq cilent is started
[10/07/2018 09:01:16 AM] filelock-mgr.c(924): Cleaning expired file locks.
[10/07/2018 09:01:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:06:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:11:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:16:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:21:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:26:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:31:17 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/18 09:33:24] http-server.c(195): fileserver: worker_threads = 10
[10/07/18 09:33:24] http-server.c(208): fileserver: backlog = 32
[10/07/18 09:33:24] http-server.c(223): fileserver: fixed_block_size = 8388608
[10/07/18 09:33:24] http-server.c(238): fileserver: web_token_expire_time = 3600
[10/07/18 09:33:24] http-server.c(253): fileserver: max_indexing_threads = 1
[10/07/2018 09:33:24 AM] ../common/mq-mgr.c(61): [mq client] mq cilent is started
[10/07/2018 09:33:24 AM] filelock-mgr.c(924): Cleaning expired file locks.
[10/07/2018 09:33:25 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:38:25 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:43:25 AM] size-sched.c(103): Repo size compute queue size is 0
[10/07/2018 09:47:48 AM] Disconnected from daemon
[10/07/18 09:48:39] http-server.c(195): fileserver: worker_threads = 10
[10/07/18 09:48:39] http-server.c(208): fileserver: backlog = 32

#7

Seems the logs of 9:50 were never written. Is user just symbolic or real? Maybe try it with sh -c "/home/seafile/seafile-server-latest/seafile.sh start", that could help.


#8

user is a replacement for my username, the paths i have also truncated


#9

Ok, some Summary
SeaFile starts manually with the same user as under systemd.
With systemd SeaFile breaks.
right?


#10

right, but seafile starts with systemd, not seahub. seahub starts manually. at the last boot neither seafile nor seahub started. i now saw that networking.service fails too, i will first look into that.


#11

That would clarify the problems.


#12

ok, got it, systemd runs without errors now (it was the network interface that got renamed by the ubuntu upgrade process, repaired that).
except seahub is not starting via seahub

systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● seahub.service loaded failed failed Seafile hub

systemctl status seahub
● seahub.service - Seafile hub
Loaded: loaded (/etc/systemd/system/seahub.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-11-17 09:28:03 CET; 4min 33s ago
Process: 3244 ExecStart=//seafile-server/seafile-pro-server-6.2.9/seahub.sh start (code=exited, >status=1/FAILURE)

Nov 17 09:27:58 x-pc systemd[1]: Starting Seafile hub…
Nov 17 09:27:58 x-pc seahub.sh[3244]: LC_ALL is not set in ENV, set to en_US.UTF-8
Nov 17 09:27:58 x-pc seahub.sh[3244]: Starting seahub at port 8000 …
Nov 17 09:28:03 x-pc seahub.sh[3244]: Error:Seahub failed to start.
Nov 17 09:28:03 x-pc seahub.sh[3244]: Please try to run “./seahub.sh start” again
Nov 17 09:28:03 x-pc systemd[1]: seahub.service: Control process exited, code=exited status=1
Nov 17 09:28:03 x-pc systemd[1]: seahub.service: Failed with result ‘exit-code’.

after login in bash:

./seahub.sh start
Starting seahub at port 8000 …
Seahub is started

Done.

my configs are like here
https://manual.seafile.com/deploy/start_seafile_at_system_bootup.html

Has anybody any idea what it could be? I runt the service as the user that is intended to run seafile and seahub via the “user=” and “group=” command in the *.service files as suggested by the manual…

Same result wether i include Environment=“LC_ALL=C” in seahub.service.


#13

It’s just a simple workaround, maybe set ExecStart=bash -c "/seafile-server/seafile-server-latest/seahub.sh start"


#14

hy!
had to put it /bin/bash as it complained about no absolute path to the executable, but still doesnt work:

Process: 13420 ExecStart=/bin/bash -c /path/seahub.sh start >>(code=exited, status=1/FAILURE)

Nov 17 14:13:23 x-pc systemd[1]: Starting Seafile hub…
Nov 17 14:13:24 x-pc bash[13420]: Starting seahub at port 8000 …
Nov 17 14:13:29 x-pc bash[13420]: Error:Seahub failed to start.
Nov 17 14:13:29 x-pc bash[13420]: Please try to run “./seahub.sh start” again
Nov 17 14:13:29 x-pc systemd[1]: seahub.service: Control process exited, code=exited status=1
Nov 17 14:13:29 x-pc systemd[1]: seahub.service: Failed with result ‘exit-code’.
Nov 17 14:13:29 x-pc systemd[1]: Failed to start Seafile hub.


#15

Can you please post your seahub.log?


#16

i dont see anything remarkable in seahub.log, the last trials where on Nov, 17.:

2018-10-27 07:37:57,626 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
2018-10-29 08:26:40,131 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-29 08:26:40,277 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-29 08:27:10,353 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-29 08:27:10,393 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-29 08:27:32,813 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-29 08:27:33,353 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-29 08:36:34,039 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-29 09:25:31,704 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-29 09:25:31,762 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-29 09:25:36,178 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
2018-10-30 07:44:55,015 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-30 07:44:55,082 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-30 07:44:56,774 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-30 07:45:02,475 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-30 07:50:15,049 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-30 07:57:59,857 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-30 08:17:15,003 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 07:47:14,923 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-10-31 07:47:15,010 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-10-31 07:47:16,959 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 07:49:06,704 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 07:52:06,157 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 07:55:06,226 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 08:01:06,421 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-10-31 19:16:38,912 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
2018-11-01 07:30:18,542 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 07:30:18,606 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-01 07:51:03,654 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 07:51:03,973 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-01 08:43:12,107 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 08:43:12,386 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-01 19:04:16,191 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 19:04:16,327 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-01 19:30:00,982 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 19:30:01,283 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-01 21:38:10,108 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-01 21:38:10,209 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-03 07:02:28,788 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-03 07:02:28,874 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-03 07:17:50,044 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-03 07:17:50,110 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-03 07:41:08,440 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-03 07:41:08,509 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-03 09:01:08,114 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-03 09:01:08,313 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-07 19:11:22,178 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-07 19:11:23,243 [WARNING] django.request:152 get_response Not Found: /seafhttp/protocol-version
2018-11-07 19:17:58,402 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-07 19:17:59,663 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-07 19:18:00,287 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-07 19:18:01,655 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 07:45:09,696 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-17 07:45:09,899 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-17 07:45:11,726 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 07:45:20,558 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 07:45:20,571 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 07:45:20,582 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:30:09,237 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-17 08:30:09,273 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-17 08:30:18,797 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:31:16,283 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:33:15,813 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:41:59,097 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-17 08:41:59,153 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-17 08:42:09,924 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:42:11,628 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:42:13,158 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:42:13,158 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-17 08:42:13,158 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain
2018-11-19 07:55:08,475 [INFO] seafevents.db:74 create_engine_from_conf [seafevents] database: mysql, name: seahub-db
2018-11-19 07:55:08,565 [INFO] seafevents:109 is_audit_enabled audit is enabled
2018-11-19 07:56:07,070 [INFO] seafes:162 load_seafevents_conf [seafes] use highlighter plain

controller.log keeps repeating this:

[11/17/18 08:44:55] seafile-controller.c(87): spawn_process: /path/seafile-server/seafile-pro-server-6.3.6/pro/elasticsearch/bin/elasticsearch -Des.path.logs=/path/seafile-server/logs -Des.path.data=/mnt/$
[11/17/18 08:44:55] seafile-controller.c(102): spawned /patg/seafile-server/seafile-pro-server-6.3.6/pro/elasticsearch/bin/elasticsearch, pid 24815
[11/17/18 08:45:05] seafile-controller.c(590): pid file /path/seafile-server/pids/elasticsearch.pid does not exist
[11/17/18 08:45:05] seafile-controller.c(628): elasticsearch need restart…


#17

Are you on Pro?


#18

yes i am on pro.


#19

Is it possible that you haven’t all packages?


#20

couldnt tell, its up and running, currently seafile-pro-server_6.3.7. I had it running over a year now, but never with startup at boot.