search

cmer / docker-seafile

MIT License
3 stars 2 forks source link

6.3 install does not work - Error: '/opt/haiwen/conf/gunicorn.conf' doesn't exist #6

Open crscheid opened 6 years ago

crscheid commented 6 years ago

I believe with the 6.3 community edition update, the install process doesn't work any more. The following error was received.

seafile_1  | Generating download URL for:
seafile_1  |   VERSION: latest
seafile_1  |   ARCHITECTURE: x86-64
seafile_1  |   EDITION: Community
seafile_1  | 
seafile_1  | Installing Community Edition...
seafile_1  | 
seafile_1  | Downloading & Extracting https://download.seadrive.org/seafile-server_6.3.0_x86-64.tar.gz...
seafile_1  | 
seafile_1  | Done!
seafile_1  | Using Community Edition...
seafile_1  | Installation path: /opt/haiwen/seafile-server-6.3.0
seafile_1  | 
seafile_1  | Seahub is not running
seafile_1  | Done.
seafile_1  | 
seafile_1  | 
seafile_1  | seafile server not running yet
seafile_1  | Done.
seafile_1  | 
seafile_1  | [06/01/18 19:07:55] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf
seafile_1  | Starting seafile server, please wait ...
seafile_1  | Seafile server started
seafile_1  | 
seafile_1  | Done.
seafile_1  | 
seafile_1  | Starting seahub at port 8000 ...
seafile_1  | 
seafile_1  | Error: '/opt/haiwen/conf/gunicorn.conf' doesn't exist
seafile_1  | Error:Seahub failed to start.
seafile_1  | Please try to run "./seahub.sh start" again
seafile_seafile_1 exited with code 1

Using the following docker-compose.yml configuration:

version: '2.2'
services:

  # The application itself
  seafile:
    restart: unless-stopped
    image: cmer/seafile:latest
    volumes:
      - /Users/xxxxx/Desktop/seafile/data:/seafile
    environment:
      SEAFILE_NAME: TSeafile
      SEAFILE_ADDRESS: 10.0.1.3
      SEAFILE_ADMIN: xxxx.xxxx@gmail.com
      SEAFILE_ADMIN_PW: xxxxxxxxx
    # Already exposes ports 8000 8082
    ports:
      - "8000:8000"
      - "8082:8082"
gaby-one commented 6 years ago

Same issue here. I had to modify some things on my unraid server before noticing that my seafile container was down and won't start properly, I don't know if the issue is due to an update or my bad. PLease note that I have the same error : 

Starting seahub at port 8000 ...

Error happened during creating seafile admin.

Error: '/opt/haiwen/conf/gunicorn.conf' doesn't exist
Error:Seahub failed to start.
Please try to run "./seahub.sh start" again

Did anyone solved this issue? Is it possible to restore an old version? Also I don't know how to run command "./seahub.sh start" as requested because my container won't stay running.

dorkhouse commented 6 years ago

Same deal with me. I took the unRAID server down to replace a drive and then noticed my Seafile docker wouldn't stay running afterward.

Similar issue reported in the cmer - Seafile support page, but it doesn't seem to apply here. Mine already had a VERSION='latest' environment variable.

Generating download URL for: VERSION: latest ARCHITECTURE: x86-64 EDITION: Community

Installing Community Edition...

Downloading & Extracting https://download.seadrive.org/seafile-server_6.3.1_x86-64.tar.gz...

Done! Using Community Edition... Installation path: /opt/haiwen/seafile-server-6.3.1

Seahub is not running Done.

seafile server not running yet Done.

[07/04/18 18:17:13] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf Starting seafile server, please wait ... Seafile server started

Done.

Starting seahub at port 8000 ...

Error: '/opt/haiwen/conf/gunicorn.conf' doesn't exist Error:Seahub failed to start. Please try to run "./seahub.sh start" again

crscheid commented 6 years ago

For those still having this issue. I've solved my use case by moving on to another image: foxel/seafile. Seems to work well and allows me to lock versions. I'm using foxel/seafile:6.3.0 for about a month now and it seems to be working well.

gaby-one commented 6 years ago

I had found that you have to modify the already existing variable VERSION form "latest" to "6.2.5" in order to make it work again, as explained in the support thread of the forum.

dorkhouse commented 6 years ago

Thanks, this also worked for me although, from the support page, "and specify desired version" in the text vs the 6.2.5 shown in screenshot doesn't quite qualify as "explained" to me. ;)

I"ve also since moved on to trying out NextcloudPlus (formerly NextcloudPi) on an Rpi3B+. So far, so good there.

crscheid commented 6 years ago

Thanks for the workaround. I agree with DW. The image touts the ability to download and utilize the latest version. Clearly it was broken in this case.

Will leave this open.