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

seaf-server segfault every 30s, then Error 500 on web client #923

Closed JackTh38 closed 8 years ago

JackTh38 commented 9 years ago

Hi there,

I have a strange behaviour of my seafile server 3.1.7 on debian Wheezy. It appeared suddenly yesterday, with no change on serverside Symptoms are I get random HTTP 500 error on nginx on any page (/home/my) for example Every 30 seconds, there is a segfault in Syslog : [ 9975.773400] seaf-server[14023]: segfault at 0 ip (null) sp 00007fff12c14568 error 14 in seaf-server[400000+75000] at the same time, here is what I find in the seafile logs :

ccnet.log [11/13/14 14:24:00] ../common/processor.c(218): [Proc] Shutdown processor service-proxy-proc(-554038) for bad update: 403 Bad Object [11/13/14 14:24:00] ../common/processor.c(218): [Proc] Shutdown processor service-stub-proc(1230) for bad update: 403 Bad Object [11/13/14 14:24:00] ../common/peer.c(943): Local peer down [11/13/14 14:24:00] ../common/peer.c(943): Local peer down [11/13/14 14:24:00] ../common/peer.c(943): Local peer down [11/13/14 14:24:00] ../common/processor.c(292): [Proc] peer 248e39225c, Shutdown processor service-stub-proc(1034) for bad response: 515 peer down [11/13/14 14:24:00] ../common/processor.c(292): [Proc] peer 248e39225c, Shutdown processor service-proxy-proc(-1002) for bad response: 515 peer down [11/13/14 14:24:00] ../common/processor.c(218): [Proc] Shutdown processor mqserver-proc(-1020) for bad update: 515 peer down [11/13/14 14:24:00] ../common/processor.c(218): [Proc] Shutdown processor rpcserver-proc(-1001) for bad update: 515 peer down [11/13/14 14:24:00] ../common/processor.c(218): [Proc] Shutdown processor threaded-rpcserver-proc(-1001) for bad update: 515 peer down

seahub_django_request.log: 2014-11-13 14:25:59,946 [ERROR] django.request:212 handle_uncaught_exception Internal Server Error: /api2/repos/ Traceback (most recent call last): File "/home/seafile/seafile-server-3.1.7/seahub/thirdpart/Django-1.5.1-py2.6.egg/django/core/handlers/base.py", line 115, in get_response response = callback(request, _callback_args, _callback_kwargs) File "/home/seafile/seafile-server-3.1.7/seahub/thirdpart/Django-1.5.1-py2.6.egg/django/views/generic/base.py", line 68, in view return self.dispatch(request, _args, _kwargs) File "/home/seafile/seafile-server-3.1.7/seahub/thirdpart/Django-1.5.1-py2.6.egg/django/views/decorators/csrf.py", line 77, in wrapped_view return view_func(_args, _kwargs) File "/home/seafile/seafile-server-3.1.7/seahub/thirdpart/rest_framework/views.py", line 363, in dispatch response = self.handle_exception(exc) File "/home/seafile/seafile-server-3.1.7/seahub/thirdpart/rest_framework/views.py", line 360, in dispatch response = handler(request, _args, _kwargs) File "/home/seafile/seafile-server-3.1.7/seahub/seahub/api2/views.py", line 455, in get shared_repos = get_share_in_repo_list(request, -1, -1) File "/home/seafile/seafile-server-3.1.7/seahub/seahub/views/ajax.py", line 1435, in get_share_in_repo_list repo_list = seafile_api.get_share_in_repo_list(username, -1, -1) File "/home/seafile/seafile-server-3.1.7/seafile/lib64/python2.6/site-packages/seaserv/api.py", line 212, in get_share_in_repo_list start, limit) File "/home/seafile/seafile-server-3.1.7/seafile/lib64/python2.6/site-packages/pysearpc/client.py", line 110, in newfunc ret_str = self.call_remote_func_sync(fcall_str) File "/home/seafile/seafile-server-3.1.7/seafile/lib64/python2.6/site-packages/ccnet/rpc.py", line 75, in call_remote_func_sync req_id = self._start_service(client) File "/home/seafile/seafile-server-3.1.7/seafile/lib64/python2.6/site-packages/ccnet/rpc.py", line 36, in _start_service raise SearpcError("Error received: %s %s (In _start_service)" % (rsp.code, rsp.code_msg)) SearpcError: Error received: 511 Unknown service (In _start_service)

I feel there is something wrong in one of my user's library, but I an't fond out whitch one

Any help welcomes Regards, Jack

freeplant commented 9 years ago

What's in seafile.log?

JackTh38 commented 9 years ago

Here are the last lines of seafile.log (same messages every 30sec too) :

[11/13/14 14:53:03] ../common/mq-mgr.c(60): [mq client] mq cilent is started [11/13/14 14:53:03] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seaf_server.heartbeat [11/13/14 14:53:03] listen-mgr.c(115): listen on port 12001 for block tranfer [11/13/14 14:53:15] [recvcommit] Bad update: 401 Object not found [11/13/14 14:53:33] ../common/mq-mgr.c(60): [mq client] mq cilent is started [11/13/14 14:53:33] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seaf_server.heartbeat [11/13/14 14:53:33] listen-mgr.c(115): listen on port 12001 for block tranfer [11/13/14 14:53:45] [recvcommit] Bad update: 401 Object not found [11/13/14 14:54:03] ../common/mq-mgr.c(60): [mq client] mq cilent is started [11/13/14 14:54:03] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seaf_server.heartbeat [11/13/14 14:54:03] listen-mgr.c(115): listen on port 12001 for block tranfer

killing commented 9 years ago

I cannot see any clue from the log. @freeplant Can you provide a package with debug symbols?