Seafile will not start(docker) (logs provided)

Seafile Server
1

I’m running seafile via docker, using the example docker-compose.yml provided in the manual, with a few modifications. Here is my docker compose(sensitive info redacted):

  db:
    image: mariadb:10.1
    container_name: seafile-mysql
    environment:
      - PUID=1000
      - GUID=1000
      - MYSQL_ROOT_PASSWORD=<REDACTED>  # Requested, set the root's password of MySQL service.
      - MYSQL_LOG_CONSOLE=true
    volumes:
      - /opt/seafile-mysql/db:/var/lib/mysql  # Requested, specifies the path to MySQL data persistent store.
    networks:
      - seafile-net

  memcached:
    image: memcached:1.5.6
    container_name: seafile-memcached
    entrypoint: memcached -m 256
    networks:
      - seafile-net

  seafile:
    image: seafileltd/seafile-mc:latest
    container_name: seafile
    ports:
      - 9980:80
#     - "443:443"  # If https is enabled, cancel the comment.
    volumes:
      - /pool-1:/shared   # Requested, specifies the path to Seafile data persistent store.
    environment:
      - PUID=1000
      - GUID=1000
      - DB_HOST=db
      - DB_ROOT_PASSWD=<REDACTED>  # Requested, the value shuold be root's password of MySQL service.
      - TZ=America/New_York  # Optional, default is UTC. Should be uncomment and set to your local time zone.
      - SEAFILE_ADMIN_EMAIL=<REDACTED> # Specifies Seafile admin user, default is 'me@example.com'.
      - SEAFILE_ADMIN_PASSWORD=<REDACTED>     # Specifies Seafile admin password, default is 'asecret'.
      - SEAFILE_SERVER_LETSENCRYPT=false   # Whether to use https or not.
        #- SEAFILE_SERVER_HOSTNAME=docs.seafile.com # Specifies your host name if https is enabled.
    depends_on:
      - db
      - memcached
    networks:
      - seafile-net

networks:
  seafile-net:

When I run “docker-compose up -d” my db and memcached containers start but seafile does not. A look at the startup log is seen below. Thoughts?

docker-compose logs seafile
Attaching to seafile
seafile      | *** Running /etc/my_init.d/01_create_data_links.sh...
seafile      | *** Booting runit daemon...
seafile      | *** Runit started as PID 14
seafile      | *** Running /scripts/start.py...
seafile      | Checking python on this machine ...
seafile      | 
seafile      | 
seafile      | verifying password of user root ...  done
seafile      | 
seafile      | verifying password of user seafile ...  
seafile      | Failed to connect to mysql server using user "seafile" and password "***": Access denied for user 'seafile'@'172.19.0.4' (using password: YES)
seafile      | 
seafile      | [2020-09-30 21:31:53] Now running setup-seafile-mysql.py in auto mode.
seafile      | Traceback (most recent call last):
seafile      |   File "/scripts/start.py", line 86, in <module>
seafile      |     main()
seafile      |   File "/scripts/start.py", line 56, in main
seafile      |     init_seafile_server()
seafile      |   File "/scripts/bootstrap.py", line 145, in init_seafile_server
seafile      |     call('{} auto -n seafile'.format(setup_script), env=env)
seafile      |   File "/scripts/utils/__init__.py", line 70, in call
seafile      |     return subprocess.check_call(*a, **kw)
seafile      |   File "/usr/lib/python3.6/subprocess.py", line 311, in check_call
seafile      |     raise CalledProcessError(retcode, cmd)
seafile      | subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-7.1.5/setup-seafile-mysql.sh auto -n seafile' returned non-zero exit status 255.
seafile      | *** /scripts/start.py exited with status 1.
seafile      | *** Shutting down runit daemon (PID 14)...
seafile      | *** Running /etc/my_init.post_shutdown.d/10_syslog-ng.shutdown...
seafile      | *** Killing all processes...
2

Did you ever figure this out? I’m in the same boat using the sample yaml.

Edit I figured out my issue. Bad value in the timezone field. Needs to be America/New_York not NewYork. It’s up now. Hopefully this helps others.

1 Like
3

THANK YOU!! I had “America/Los Angeles” and it didn’t like that. Needed to switch to “America/Los_Angeles”. I never would have guessed that. With that were logged as an error somewhere

1 Like