I set up an S3 backend for my server, and when I start Seafile it fails with the following messages in the log:
[03/14/18 16:09:01] ../common/obj-cache.c(30): Failed to create memcached pool.
[03/14/18 16:09:01] ../common/obj-store.c(170): [Object store] Failed to load backend for commits.
[03/14/18 16:09:01] seaf-server.c(1405): Failed to create seafile session.
I have Seafile Professional Server 6.2.9 installed on Ubuntu 16.04. I was using the community version, but I migrated to Pro when I realized I needed it for my S3 config to work. My seafile.conf looks like this:
[fileserver]
port=8082
[commit_object_backend]
name = s3
# bucket name can only use lowercase characters, numbers, periods and dashes. Period cannot be used in Frankfurt region.
bucket = my-commit-objects9
key_id = XXX
key = XXX
memcached_options = --SERVR=localhost --POOL-MIN=10 --POOL-MAX=100
[fs_object_backend]
name = s3
# bucket name can only use lowercase characters, numbers, periods and dashes. Period cannot be used in Frankfurt region.
bucket = my-fs-objects9
key_id = XXX
key = XXX
memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100
[block_backend]
name = s3
# bucket name can only use lowercase characters, numbers, periods and dashes. Period cannot be used in Frankfurt region.
bucket = my-block-objects9
key_id = XXX
key = XXX
memcached_options = --SERVER=localhost --POOL-MIN=10 --POOL-MAX=100
I have my set up on Amazon. I’m using us-west-1.
I tried using the guide at https://manual.seafile.com/deploy_pro/migrate.html to set migrate to S3 since I originally stored the files locally. The script ran fine, but seemed to change nothing.