Jump to content
cmer

[Support] cmer - Seafile

108 posts in this topic Last Reply

Recommended Posts

On 5/7/2018 at 9:09 PM, JoergHH said:

I understand that you don't have time to create a complete new image, but it would be helpful if you could change the existing image so that we can stop the SeaFile Server service only without closing the entire Docking container.

 

Here is work-around from the official Seafile Forum.

 

https://forum.seafile.com/t/docker-automatically-terminates-after-a-minute-within-the-container-opt-seafile-seafile-server-latest-seafile-sh-stop/6575/2

Quote

There is a workaround though:

Edit the script /scripts/start.py

and find the part with


    time.sleep(5)

and replace it with (1 week duration):


    time.sleep(604800)

restart the seafile server and than you are able to stop…

But its a workaround and there should be a true solution

 

 

I hope this helps

Share this post


Link to post
On 5/27/2018 at 3:50 PM, ncontorno said:

I just started having an issue. It looks like I upgraded from 6.2.5 to 6.3.0 and now seahub won't start and the container shuts down. Here is the log:

 


[05/27/18 15:42:55] ../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
[33mError:Seahub failed to start.[m
Please try to run "./seahub.sh start" again

I haven't changed any configs or anything, it just stopped working. Any way I can get this going again?

 

I am having the same issue and adding the VERSION env variable with the latest version 6.3.2 is not working fo rme either...

 

Error:

 

Seafile server started

Done.

Starting seahub at port 8000 ...

Starting seahub at port 8000 ...

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

 

any other iseas??

Share this post


Link to post
On 8/6/2018 at 10:23 PM, airbillion said:

 

I am having the same issue and adding the VERSION env variable with the latest version 6.3.2 is not working fo rme either...

 

Error:

 

Seafile server started

Done.

Starting seahub at port 8000 ...

Starting seahub at port 8000 ...

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

 

any other iseas??

I have the same problem. But if you switch the version no. back to 6.2.13 the (prof) server will be running again.

Edited by JoergHH
wrong vers. no.

Share this post


Link to post

I went back to Seafile a few months ago to sync files between my Linux and Windows machines. Everything was working fine but now it says:

Error: the user running the script ("seafile") is not the owner of "/seafile/seafile-data" folder, you should use the user "UNKNOWN" to run the script.

What could cause this?

Share this post


Link to post
On 11/5/2018 at 6:04 AM, dahlenu said:

If you have a SQL password containing "&" the sql setup script will fail.

Apparently, it has nothing to do with the SQL Password. I still havent figured out what causes it.

Share this post


Link to post

When autoupdating to latest Seafile (v7) from latest of v6, seafile doesnt see librairies anymore, any idea why?

I had to downgrade to see them again.

Share this post


Link to post

You might want to switch to the official Docker image. I no longer use or update this one.

 

This is the one I use now: 

docker.seadrive.org/seafileltd/seafile-pro:latest

You can read more about it here.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.