Jump to content
cmer

[Support] cmer - Seafile

108 posts in this topic Last Reply

Recommended Posts

On 7/12/2017 at 4:43 AM, thebored said:

Hello - 

 

I'm not sure if I'm nuts here, but it sure seems like I've done something wrong with the setup. Everyone else seems to be successful - so it must be me! 

 

Installing via CA, the setup appears to work fine. I browse to the instance and get the standard login page. Username & password specified at login do not work. I attempted to reset the password via reset-admin.sh but the script fails to execute (syntax error on line 9). Since the script only finds python and executes manage.py, I attempted to do that as well -- but it fails as well (no module named django.core.management). 

 

At this point, I'm stumped about how to log in. All logs (unRAID or application) appear clean or empty. 

 

My install process:

Running the current version of unRAID + CA. Added the docker, used the following settings (left default unless otherwise noted):

 

Instance URL: http://192.168.X.X (valid local IP of the server)

Email: X@gmail.com

Password: test (to verify no typos)

Web Interface Port: 8500 (8000 currently taken)

 

A user share called "seafile" exists.

 

Thanks for any assistance! 

@thebored can you please tell me if you were able to figure your login problem out. I've just installed the docker and get exactly the same problem.

Here is what i've tried:

- Basic installation by just changing the info where required (ip, admin email, passord etc...), launch webui, input exactly the same info as in the docker installation, cannot connect.

- Installed separate Maria-db database only for seafile, install docker container with maria-db parameter, launch webui, still login problem.

 

Thank you

Share this post


Link to post
11 hours ago, jonathansayeb said:

@thebored can you please tell me if you were able to figure your login problem out. I've just installed the docker and get exactly the same problem.

Here is what i've tried:

- Basic installation by just changing the info where required (ip, admin email, passord etc...), launch webui, input exactly the same info as in the docker installation, cannot connect.

- Installed separate Maria-db database only for seafile, install docker container with maria-db parameter, launch webui, still login problem.

 

Thank you

Sorry, nope. I held out for a response and tried for another week or so but never resolved the issue. 

Share this post


Link to post

I have no idea. You should contact the people making Seafile to find out. They might be able to help.

Share this post


Link to post

Hi,

after updating today server is crashing.

 

failed to run "ccnet-server -t"

[09/23/17 12:25:19] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf
[09/23/17 12:25:19] ../common/ccnet-db.c(142): Error exec query CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id): sqlite3_exec failed: table EmailUser has no column named reference_id.

I didnt change any settings.

 

Any idea?

 

edit: full log below

Installing Community Edition...
Downloading & Extracting https://download.seadrive.org/seafile-server_6.2.1_x86-64.tar.gz...
Using Community Edition...
Installation path: /opt/haiwen/seafile-server-6.2.1

Seahub is not running
Done.


seafile server not running yet
Done.

failed to run "ccnet-server -t"

[09/23/17 13:20:04] ../common/session.c(132): using config file /opt/haiwen/conf/ccnet.conf
[09/23/17 13:20:04] ../common/ccnet-db.c(142): Error exec query CREATE UNIQUE INDEX IF NOT EXISTS reference_id_index on EmailUser (reference_id): sqlite3_exec failed: table EmailUser has no column named reference_id.

 

edit2: I think Iv found the same problem here - https://forum.seafile.com/t/seafile-server-6-2-0-beta-is-ready-for-testing/3941/19

Dont know exatly how to solve within Unraid though...

 

Edited by tompa
more info

Share this post


Link to post

If you have problem with "Page unavailable" follow these steps:

 

1. copy content of `/opt/haiwen/seafile-server-6.2.2/upgrade/sql/6.2.0/mysql` from seafile docker container to, for example, mariadb directory which should be located in appdata directory

2. to access the container via Bash run this command: `docker exec -it mariadb /bin/bash`

3. then:

    cd config/

    mysql -u seafile -pPASSWORD seahub_db < seahub.sql
    mysql -u seafile -pPASSWORD ccnet_db < ccnet.sql

 

Edited by ki3lich

Share this post


Link to post
10 hours ago, ki3lich said:

If you have problem with "Page unavailable" follow these steps:

 

1. copy content of `/opt/haiwen/seafile-server-6.2.2/upgrade/sql/6.2.0/mysql` from seafile docker container to, for example, mariadb directory which should be located in appdata directory

2. to access the container via Bash run this command: `docker exec -it mariadb /bin/bash`

3. then:

    cd config/

    mysql -u seafile -pPASSWORD seahub_db < seahub.sql
    mysql -u seafile -pPASSWORD ccnet_db < ccnet.sql

 

 

Thanks for your answer ki3lich!

Im running sqlite, so maybe not the correct way?

 

Share this post


Link to post

For sqlite3 run this in directory where database is located: 

sqlite3 seahub.db < seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/seahub.sql

 

Dont forget about usermgr.sql.

 

Share this post


Link to post
22 hours ago, ki3lich said:

For sqlite3 run this in directory where database is located: 

sqlite3 seahub.db < seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/seahub.sql

 

Dont forget about usermgr.sql.

 

 

Thanks again ki3lich!

 

Basic question;

do I run this as two lines?

    sqlite3 seahub.db

    seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/seahub.sql

and

    sqlite3 usermgr.db

    seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/usermgr.sql

 

Share this post


Link to post

I'm not using sqlite3 so i don't know where database is located. Manual states that they should be located in /haiwen/.

 

Run commands in one line with '<' in the middle

cd to haiwen directory

sqlite3 seahub.db < seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/seahub.sql

sqlite3 ccnet/PeerMgr/usermgr.db < seafile-server-6.2.2/upgrade/sql/6.2.0/sqlite3/ccnet/usermgr.sql

 

 

Share this post


Link to post

FYI - didn't manage to update to 6.2.2, however I did manage to recover my backup in a separate v6.1.2 server and the reinstall 6.2.2.

Share this post


Link to post

Folks, I just wanted to let you know that I have updated the image with the ability to set a specific version. This is useful if you want to run an older version, for example.

 

All you need to do is set the VERSION environment variable.

 

Please let me know if you run into any issues.

Share this post


Link to post
On 10/7/2017 at 5:07 AM, cmer said:

Folks, I just wanted to let you know that I have updated the image with the ability to set a specific version. This is useful if you want to run an older version, for example.

 

All you need to do is set the VERSION environment variable.

 

Please let me know if you run into any issues.

 

Thanks cmer, this sounds awesome!

Could you show an example how to do this?

Share this post


Link to post

Im trying to run Seafile FSCK - https://manual.seafile.com/maintain/seafile_fsck.html

 

But there is obvious a problem with user conflict, best way to solve this?

 

    root@server:~# docker exec -it Seafile bash

    root@server:/opt/haiwen/seafile-server-6.2.2# ./seaf-fsck.sh

    Starting seaf-fsck, please wait ...

    [10/10/17 12:38:20] seaf-fsck.c(155): Current user (0) is not the user for running seafile server (1000). Unable to run fsck.
    seaf-fsck run done

    Done.
    root@server:/opt/haiwen/seafile-server-6.2.2#

 

 

Share this post


Link to post
4 hours ago, cmer said:

Just ‘su’ to the correct user first. 

 

Thanks again!

Worked fine with seafile as user.

Share this post


Link to post

Hi,

 

I am succesfully running Seafile 6.1.2 with a nginx configuration.

 

When I wanted to try to setup as a test instance the new Seafile 6.2.3, I can not get the uploading and downloading running. I always get a "FILE NOT FOUND".

I am using the same nginx configuration (only a different subdomain) as with Seafile 6.1.2.

I setup the Service_URL and FILE_SERVER_ROOT via database. The FILE_SERVER_ROOT is "https://url/seafhttp"

 

Here is my nginx configuration with Seafile 6.2.3:

server {
    listen       80;
    server_name  url;
    location / {
    
        proxy_pass http://internal-ip-address:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_buffering off;
    }
    
location /seafhttp {

        rewrite ^/seafhttp(.*)$ $1 break;
        proxy_pass http://internal-ip-address:8082;
        client_max_body_size 0;
        proxy_connect_timeout  36000s;
        proxy_read_timeout  36000s;
        proxy_send_timeout  36000s;
        send_timeout  36000s;
        proxy_request_buffering off;
    }

}

server {
    listen       443 ssl;
    server_name  url;

   

    .......SSL Configuration
    
    location / {

        proxy_pass http://internal-ip-address:8000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_buffering off;        
    }
    
    location /seafhttp {

        rewrite ^/seafhttp(.*)$ $1 break;
        proxy_pass http://internal-ip-address:8082;
        client_max_body_size 0;
        proxy_connect_timeout  36000s;
        proxy_read_timeout  36000s;
        proxy_send_timeout  36000s;
        send_timeout  36000s;
        proxy_request_buffering off;
    }

}

 

Any help is appreciated. Thank you.

 

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.