search

haiwen / seafile

High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features.
http://seafile.com/
Other
12.25k stars 1.54k forks source link

http://host:8000 after seafile-admin start #743

Closed big-grizzly closed 8 years ago

big-grizzly commented 10 years ago

I am porting the 3.0.4 to FreeBSD 9.2 Release. I understand that you have no support. Although some ports dependencies are not fully written, the build, installation, and init runs for major components seem fine. I have a question, without setting apache or Ngix, what I should expect to http://host:8000 just after

seafile-admin start

I hit 500 Internal Server Error, does it mean httpserver has problem? Which log file I can triage what happens.

Thank you.

ghost commented 10 years ago

Hi freebsd guy,

It is quite interesting for me to find out that someone installed seafile sucessfully under freebsd. I believe you forgot execute ./manage.py syncdb in seahub directory before you start seafile. Or you can reference our manual

ghost commented 10 years ago

Hi @big-grizzly ,

You might want to turn on django's debug mode to get more information by adding a line to seahub_setting.py : 

DEBUG=True

PS: I spent some hours compiling seafile under FreeBSD, and only found out I got stuck with libevent2. I referenced some old issues with BSDs support (e.g. haiwen/ccnet#4 ) . I thought it is non-trivial work and I will look into the BSDs support of seafile once I get some free time. And it would be very awesome if you can contribute back to seafile.

Cheers, Chilledheart

stephenhoos commented 10 years ago

I would contribute to a bounty on this... big-grizzly will your work help us get the server running on FreeNAS?

big-grizzly commented 10 years ago

Somehow the above issue is resolved because I know there is something missing for FreeBSD code. Now the important problem in front of me is all the servers are running. But the downloading file size is always 0 byte, although the file size show in main web interface is 200+K bytes. When uploading, connection is always failed.

Yes, if possible, I would like to help FreeBSD, and FreeNAS community to port this project.

stephenhoos commented 10 years ago

big-grizzly, you might want to comment here --> http://forums.pcbsd.org/showthread.php?t=22607
you might get some support, if others know you are working on the project already. I put in a ticket with ixsystems asking them what it would take to get this into FreeNAS.

ghost commented 10 years ago

Hi @big-grizzly @stephenhoos It sounds coooooooool to get seafile into FreeNAS. If there is anything I can help with, please don't hesitate to cc me, or email me rwindz0 AT gmail DOT c0m.

Thanks!

stephenhoos commented 10 years ago

I am not a programmer just a sysadmin, so I can help with testing, but not programming. I run a few FreeNAS boxes, and I can spin up VMs too, so let me know if you need help with testing or anything like that.

big-grizzly commented 10 years ago

big_grizzly, you do not have permission to access this page. This could be due to one of several reasons:

  1. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  2. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.   It seems that I hit some issue to post reply.

Best, Jingfeng

On Monday, August 11, 2014 10:55 AM, stephenhoos notifications@github.com wrote:

I am not a programmer just a sysadmin, so I can help with testing, but not programming. I run a few FreeNAS boxes, and I can spin up VMs too, so let me know if you need help with testing or anything like that. — Reply to this email directly or view it on GitHub.

stephenhoos commented 10 years ago

big_grizzly, where are you having the problem? It looks like your reply showed up on github

On Wed, Aug 13, 2014 at 3:06 PM, big-grizzly notifications@github.com wrote:

big_grizzly, you do not have permission to access this page. This could be due to one of several reasons:

  1. Your user account may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
  2. If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

It seems that I hit some issue to post reply.

Best, Jingfeng

On Monday, August 11, 2014 10:55 AM, stephenhoos notifications@github.com wrote:

I am not a programmer just a sysadmin, so I can help with testing, but not programming. I run a few FreeNAS boxes, and I can spin up VMs too, so let me know if you need help with testing or anything like that. — Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/haiwen/seafile/issues/743#issuecomment-52118460.

ghost commented 10 years ago

some patches for FreeBSD(or FreeNAS, untested though)

sadly, seafile (seaf-daemon) requires additional support for fs change watch via kqueue, so building seafile-client (gui) would be quite tough.

big-grizzly commented 10 years ago

Hi,

Now the major parts work, and libsearpc, and ccnet can pass poudriere in freebsd ports.  I am working on finalize sea file ports.  There could be small script issue because one script still hangs somewhere. 

My working version is on 9.3-release amd64 (the uploading and downloading issues are gone)   Best, Jingfeng

On Friday, August 22, 2014 11:13 AM, Chilledheart notifications@github.com wrote:

some patches for FreeBSD(or FreeNAS, untested though) * ccnet https://github.com/Chilledheart/ccnet/tree/bsd_support * seafile https://github.com/Chilledheart/seafile/tree/bsd_support sadly, seafile (seaf-daemon) requires additional support for fs change watch via kqueue, so building seafile-client (gui) would be quite tough. — Reply to this email directly or view it on GitHub.

big-grizzly commented 10 years ago

root@freebsd93:/usr/local/www/haiwen/seafile-server # ./seahub.sh restart

Seahub is not running Starting seahub at port 8000 ...

It's the first time you start the seafile server. Now let's create the admin account

What is the email for the admin account? [ admin email ] yan_jingfeng@yahoo.com

What is the password for the admin account? [ admin password ]

Enter the password again: [ admin password again ]

Successfully created seafile admin

Loading ccnet config from /usr/local/www/haiwen/ccnet Loading seafile config from /usr/local/www/haiwen/seafile-data

Seahub is started

Done.

Created libevhtp (initial in freebsd already, need some correction), libsearpc, ccnet, sea file, and sea hub ports. Will submit to ports within one-two days.

Best, Jingfeng

On Friday, August 22, 2014 11:13 AM, Chilledheart notifications@github.com wrote:

some patches for FreeBSD(or FreeNAS, untested though) * ccnet https://github.com/Chilledheart/ccnet/tree/bsd_support * seafile https://github.com/Chilledheart/seafile/tree/bsd_support sadly, seafile (seaf-daemon) requires additional support for fs change watch via kqueue, so building seafile-client (gui) would be quite tough. — Reply to this email directly or view it on GitHub.

big-grizzly commented 10 years ago

bug list 193132,193133,193134,and 193135 to freebsd port tree (libevhtp has been committed, should be 1.2.9_1 soon)

cd /usr/ports/www/seahub

it is supposed to trig to build all dependencies (including ccnet, libsearpc, and seafile)

make install make clean

The default install directory is under /usr/local/www/haiwen/

User have to manually copy linux server version seahub/thirdpart contents because I don't know whether the

freebsd port system allows me to hold another tar there

I also don't want to deal with every python modules

cd /usr/local/www/haiwen/seafile-server/seahub/thirdpart

make sure that you have the following in the above directory

[files] drwxr-xr-x 6 root wheel 25 Aug 28 05:54 wsgidav drwxr-xr-x 5 root wheel 5 Aug 28 05:54 Djblets-0.6.14.dev-py2.6.egg drwxr-xr-x 4 root wheel 10 Aug 28 05:54 seafobj.orig drwxr-xr-x 4 root wheel 4 Aug 28 05:54 gunicorn-0.16.1-py2.6.egg drwxr-xr-x 4 root wheel 4 Aug 28 05:55 python_daemon-1.5.5-py2.6.egg drwxr-xr-x 4 root wheel 4 Aug 28 05:55 lockfile-0.9.1-py2.6.egg drwxr-xr-x 4 root wheel 4 Aug 28 05:55 chardet-2.1.1-py2.6.egg drwxr-xr-x 4 root wheel 4 Aug 28 05:55 flup-1.0-py2.6.egg drwxr-xr-x 4 root wheel 4 Aug 28 05:55 Django-1.5.1-py2.6.egg -rwxr-xr-x 1 root wheel 326 Aug 28 05:55 gunicorn_django -rw-r--r-- 1 root wheel 397 Aug 28 05:55 easy-install.pth -rwxr-xr-x 1 root wheel 191 Aug 28 05:55 django-admin.py -rwxr-xr-x 1 root wheel 190 Aug 28 05:55 chardetect.py -rw-r--r-- 1 root wheel 2362 Aug 28 05:55 site.py -rwxr-xr-x 1 root wheel 343 Aug 28 05:55 seafdav.orig -rwxr-xr-x 1 root wheel 326 Aug 28 05:55 gunicorn_paster -rwxr-xr-x 1 root wheel 312 Aug 28 05:55 gunicorn -rw-r--r-- 1 root wheel 1767 Aug 28 05:55 site.pyc drwxr-xr-x 3 root wheel 5 Aug 28 05:55 six-1.4.1-py2.6.egg drwxr-xr-x 4 root wheel 21 Aug 28 06:12 rest_framework drwxr-xr-x 4 root wheel 9 Aug 28 06:12 registration drwxr-xr-x 4 root wheel 10 Aug 28 06:12 captcha [files]

mount -t procfs proc /proc cd /usr/local/www/haiwen/seafile-server/seahub for file in makemessages.sh.template run-seahub.sh.template send_user_notifications.sh.template setenv.sh.template; do cp ${file} ${file%%.template} done

cd /usr/local/www/haiwen/seafile-server

You should following the manual book to change path, and config

source seahub/setenv.sh ./setup-seafile.sh ./seafile.sh start ./seafile.sh stop

Best, Jingfeng

On Friday, August 22, 2014 11:13 AM, Chilledheart notifications@github.com wrote:

some patches for FreeBSD(or FreeNAS, untested though) * ccnet https://github.com/Chilledheart/ccnet/tree/bsd_support * seafile https://github.com/Chilledheart/seafile/tree/bsd_support sadly, seafile (seaf-daemon) requires additional support for fs change watch via kqueue, so building seafile-client (gui) would be quite tough. — Reply to this email directly or view it on GitHub.

ghost commented 10 years ago

@big-grizzly I am not sure, but you might want to reference the python's requirements.txt for thirdpart stuff, notably django and djblets. Perhaps port www/py-django15 and www/py-djblets would fit this gap.

Thanks!

ghost commented 10 years ago

Yeah, I just found them in the freebsd bugzilla. List the links here for convenience :

big-grizzly commented 10 years ago

Hi,

First of all, I definitely will make try on python module requirement. I think that my original struggling experience with python modules on my 9,2 box is quite bad, especially for django15. The above two modules are still some starts. Gunicorn also make some trouble at that time. Honestly, that 9.2 box has some trouble of python version selection, and some other unclear issue in port mgmt.

Now, I fully work on a new 9.3-rel box, and I will try to fill in the gap as much as possible for sure. The bugs filed in freebsd port tree provide me a baseline that the server side can work on BSD system.

Secondary, I have finished building ccnet 3.1.4, seafile 3.1.4, latest libsearpc now. During the weekend, I will try to make python module into pkg as many as possible.

Finally, I guess turning ports to PBIs should be relatively "easy". Then, stephenhoos can have something tests on PC-BSD.

BTW, libevhtp has fix with bugid 191931 (seafile port needs it), which create shared object by default. It should be in the port tree soon.

Best, Jingfeng(big_grizzly)

On Friday, August 29, 2014 9:56 PM, Chilledheart notifications@github.com wrote:

Yeah, I just found them in the freebsd bugzilla. List the links here for convenience : * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193132 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193133 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193134 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193135 — Reply to this email directly or view it on GitHub.

big-grizzly commented 10 years ago

Hi All,

The port efforts for 3.1.5 has been done, which reach similar situ with porting 3.0.4. I will try to update the bug ids listed in previous post.

Now the steps are simplified to be:

(1) build seahub (2) mount -t procfs proc /proc (3) cd /usr/local/www/haiwen/seafile-server/seahub for file in makemessages.sh.template run-seahub.sh.template send_user_notifications.sh.template setenv.sh.template; do cp ${file} ${file%%.template} done (4) cd /usr/local/www/haiwen/seafile-server

You should following the manual book to change path, and config

source seahub/setenv.sh ./setup-seafile.sh ./seafile.sh start ./seahub.sh start

(other detail settings should follow the manual)

There are 2 issues for porting.

(1) requirements.txt is not part of release 3.1.5, and some of the requirements are not show in 3.1.5 third party packages. For example, pt-selenium. I added it into 3.1.5 port for future reference.

(2) Now the trouble maker is python djblets. The seafile chooses the combination of django and djblets in an interesting way. djblets 0.6.14 requires newer than django 1.1.1, and using django 1.5.1, which fit for the requirement of djblets. System like debian removes djblets package. while FreeBSD has djblets 0.7.28 port. However, the port follows egg requirement strictly, which uses django 1.4.x.

If I want to following normal way to install djblets 0.6.14 by ports, or packages, it will blocks to use existing djblets 0.7.28. I anyway will submit py-djblets06 ports. I don't prefer to this way.

Let me know if there is any suggestion. Thank you.

Finally, start to work on PBI for PC-BSD.

Best, Jingfeng On Saturday, August 30, 2014 2:48 AM, Jingfeng Yan yan_jingfeng@yahoo.com wrote:

Hi,

First of all, I definitely will make try on python module requirement. I think that my original struggling experience with python modules on my 9,2 box is quite bad, especially for django15. The above two modules are still some starts. Gunicorn also make some trouble at that time. Honestly, that 9.2 box has some trouble of python version selection, and some other unclear issue in port mgmt.

Now, I fully work on a new 9.3-rel box, and I will try to fill in the gap as much as possible for sure. The bugs filed in freebsd port tree provide me a baseline that the server side can work on BSD system.

Secondary, I have finished building ccnet 3.1.4, seafile 3.1.4, latest libsearpc now. During the weekend, I will try to make python module into pkg as many as possible.

Finally, I guess turning ports to PBIs should be relatively "easy". Then, stephenhoos can have something tests on PC-BSD.

BTW, libevhtp has fix with bugid 191931 (seafile port needs it), which create shared object by default. It should be in the port tree soon.

Best, Jingfeng(big_grizzly)

On Friday, August 29, 2014 9:56 PM, Chilledheart notifications@github.com wrote:

Yeah, I just found them in the freebsd bugzilla. List the links here for convenience : * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193132 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193133 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193134 * https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193135 — Reply to this email directly or view it on GitHub.

ghost commented 10 years ago

Hi @big-grizzly

Thanks for your work of bringing seafile to freebsd ports.

Here are some suggestions:

Cheers, Chilledheart

big-grizzly commented 10 years ago

Hi,

It seems that there is still an important issue. Originally I am facing with the problem web client (web browser) can not downloading and uploading. This seems to be fine. However, seafile client still have problem to connect the server. The connecting operation seems to be for ever. :(

It can log in and get information about which lib should be sync-ed. Any suggestion? Thank you.

Best, Jingfeng

On Monday, September 1, 2014 11:20 PM, Chilledheart notifications@github.com wrote:

Hi @big-grizzly Thanks for your work of bringing seafile to freebsd ports. Here are some suggestions: * py-selenium and unittest are required only for tests, and remain part of optional dependencies for seahub. Ignore them please, if you want. * The python djblets problem. Sorry, but I don't have a better solution currently. * I have installed freebsd 9.3-rel vm box in my pc, and if possible, I can volunteer to test these ports. Cheers, Chilledheart — Reply to this email directly or view it on GitHub.

ghost commented 10 years ago

Hi @big-grizzly

It is grad to see website part works without problems. And you are using seafile client from FreeBSD, aren't you? Try a different platform that seafile officially supports, and run client on it to see whether server part on FreeBSD is okay or not. I must tell that client part for FreeBSD is left incomplete (notably wt-monitor part, 200 loc or so left).

Cheers, Chilledheart

big-grizzly commented 10 years ago

Hi @Chilledheart

Hehe, I try client from Mac, Linux, Windows except BSD client. It seems that it is ccnet 10001 port have some issue.

[09/02/14 11:24:51] ../common/session.c(385): Listen on 127.0.0.1 13418 [09/02/14 11:24:51] ../common/session.c(257): Update pubinfo file [09/02/14 11:24:51] ../common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections [09/02/14 11:24:52] ../common/session.c(365): Accepted a local client [09/02/14 11:24:52] ../common/session.c(365): Accepted a local client [09/02/14 11:24:52] ../common/session.c(365): Accepted a local client [09/02/14 11:24:52] ../common/session.c(365): Accepted a local client [09/02/14 11:24:59] ../common/session.c(365): Accepted a local client [09/02/14 11:24:59] ../common/peer.c(942): Local peer down [09/02/14 11:25:28] ../common/session.c(365): Accepted a local client [09/02/14 11:25:28] ../common/session.c(365): Accepted a local client [09/02/14 11:25:29] ../common/session.c(365): Accepted a local client

(never been connected)

By the way, what do you mean "200 loc or so left"?

Best, Jingfeng

On Tuesday, September 2, 2014 11:53 AM, Chilledheart notifications@github.com wrote:

Hi @big-grizzly It is grad to see website part works without problems. And you are using seafile client from FreeBSD, aren't you? Try a different platform that seafile officially supports, and run client on it to see whether server part on FreeBSD is okay or not. I must tell that client part for FreeBSD is left incomplete (notably wt-monitor part, 200 loc or so left). Cheers, Chilledheart — Reply to this email directly or view it on GitHub.

ghost commented 10 years ago

Hi @big-grizzly I meant there is a 200 lines of code (or so-called loc) of wt-monitor part to fill the gap from linux to FreeBSD. And I will check that issue(ccnet clide-side connection) later.

Cheers, Chilledheart

big-grizzly commented 10 years ago

Server connection issue is resolved by some "hacking" code. Will work will chilled heart to get it firmed.

Best, Jingfeng

On Tuesday, September 2, 2014 12:10 PM, Chilledheart notifications@github.com wrote:

Hi @big-grizzly I meant there is a 200 lines of code (or so-called loc) of wt-monitor part to fill the gap from linux to FreeBSD. And I will check that issue(ccnet clide-side connection) later. Cheers, Chilledheart — Reply to this email directly or view it on GitHub.

big-grizzly commented 10 years ago

seafile-client GUI works fine (sync from server, upload/push to server when changes happens) in FreeBSD (for some simple test), working on formal ports.

Best, Jingfeng

On Tuesday, September 2, 2014 11:00 PM, Jingfeng Yan yan_jingfeng@yahoo.com wrote:

Server connection issue is resolved by some "hacking" code. Will work will chilled heart to get it firmed.

Best, Jingfeng

On Tuesday, September 2, 2014 12:10 PM, Chilledheart notifications@github.com wrote:

Hi @big-grizzly I meant there is a 200 lines of code (or so-called loc) of wt-monitor part to fill the gap from linux to FreeBSD. And I will check that issue(ccnet clide-side connection) later. Cheers, Chilledheart — Reply to this email directly or view it on GitHub.