[DATABASE]
type = mysql
host = xxx.xxx.xxx.xxx
port = 3312
username = xxxxxxx
password = xxxxxxxxxxxxxxxxxxx
name = seahub-db
[AUDIT]
enabled = true
[STATISTICS]
enabled = true
[INDEX FILES]
enabled = true
interval = 10m
// If true, indexes the contents of office/pdf files while updating search index
// Note: If you change this option from “false” to “true”, then you need to clear the search index and update the index again. See the FAQ for details.
index_office_pdf = true
[OFFICE CONVERTER]
enabled = true
workers = 1
// how many pages are allowed to be previewed online. Default is 50 pages
max-pages = 50
// the max size of documents allowed to be previewed online, in MB. Default is 10 MB
// Previewing a large file (for example >30M) online is likely going to freeze the browser.
max-size = 10
[EVENTS PUBLISH]
// must be “true” to enable publish events messages
enabled = true
// message format: repo-update\t{{repo_id}}}\t{{commit_id}}
// Currently only support redis message queue
mq_type = redis
[REDIS]
// redis use the 0 database and “repo_update” channel
server = xxx.xxx.xxx.xxx
port = 6379
password = xxxxxxxxxxxxxxxxxx
[SEAHUB EMAIL]
enabled = true
// interval of sending Seahub email. Can be s(seconds), m(minutes), h(hours), d(days)
interval = 30m
Stopping services and creating the file manually (empty - and with the correct owner) the controll log goes:
[05/01/19 08:49:33] seafile-controller.c(132): bad pidfile format: /opt/seafile/pids/seafevents.pid
[05/01/19 08:49:33] seafile-controller.c(595): failed to read pidfile /opt/seafile/pids/seafevents.pid: Success
[05/01/19 08:49:43] seafile-controller.c(132): bad pidfile format: /opt/seafile/pids/seafevents.pid
[05/01/19 08:49:43] seafile-controller.c(595): failed to read pidfile /opt/seafile/pids/seafevents.pid: Success
[05/01/19 08:49:53] seafile-controller.c(132): bad pidfile format: /opt/seafile/pids/seafevents.pid
[05/01/19 08:49:53] seafile-controller.c(595): failed to read pidfile /opt/seafile/pids/seafevents.pid: Success
I think the second scenario is understandable. The process should create the file, and if the file is there, then it can not read it. The first scenario is the one I have troubles with. Why is the file not created? The directory, the config and the log files all seems to have the correct ownership (as suggested by uosseafile).
I found an unresolved entry at github about exactly that. But it’s old and there was no conclusion:
i can get result pong if i run “redis-cli -h 127.0.0.1 -a password -p 6379 ping”
and for “redis-server --version” i get following output
Redis server v=3.0.6 sha=00000000:0 malloc=jemalloc-3.6.0 bits=64 build=7785291a3d2152db
Also my main issue is i’m not able to open any doc file after upgrading from 6.3 to 7.0.14. PDF and image files open as before but doc file is not opening