Shutdown processor service-proxy-proc(-5795) for bad update: 403 Bad Object

fraber commented 10 years ago

Hi!

I've more or less successfully installed Seafile 3.3.1 on a CentOS 6 server and since then I've played around with syncing folders both from the Intranet and from the Internet via OpenVPN. Now I get the error above and I'm not sure what to do. Here is how I got there:

I successfully uploaded a number of files in several libraries via the Windows client.
I connected via OpenVPN and did some modifications to libraries. Everything well.
I de-synchronized these libraries and connected again from the Intranet.
I successfully re-synced several small libraries using my seafile-3.1.3-en.msi Windows client.
However re-syncing a large folder "Customer" I get trouble now.

The client says:

Failed to get file information from remote library

The server says (tail -f /home/seafile/logs/*):

==> ccnet.log <== [08/10/14 11:49:10] ../common/processor.c(219): [Proc] Shutdown processor service-proxy-proc(-5795) for bad update: 403 Bad Object [08/10/14 11:49:10] ../common/processor.c(219): [Proc] Shutdown processor service-stub-proc(1027) for bad update: 403 Bad Object

==> seafile.log <== [08/10/14 11:49:10] Bad update: 403 Bad Object.

==> ccnet.log <== [08/10/14 11:49:10] ../common/peer.c(696): Delayed response from local-2(5f6ff23a05), id is 1027, 506 Bad update code

The server did not crash or shutdown uncleanly. I have to admit that this incident some affects my trust in Seafile. We are looking at Seafile as a future backbone for our small company and as an add-on for our SaaS customers (I'm the founder of ]project-open[, http://www.project-open.com/).

Cheers! Frank

killing commented 10 years ago

Can you send me the log file from client? They're in C:\users\username\ccnet\logs. My email is xjqkilling at gmail dot com. Thank you.

fraber commented 10 years ago

Hi,

I've sent you the logs to your mail. I've also attached the contents of my log files below. I made a minor error in the error description above, it's the folders "Internal" and "Archive" that cause the issues.

As mentioned in my mail, I can provide you with access to our server via OpenVPN, TeamViewer, Skype, GoToMeeting or SSH.

Thanks for the fast reply! Frank

controller.log:

[08/11/14 10:53:51] seafile-controller.c(155): starting ccnet-server ...
[08/11/14 10:53:51] seafile-controller.c(74): spawn_process: ccnet-server -c /home/seafile/ccnet -f /home/seafile/logs/ccnet.log -d -P /home/seafile/pids/ccnet.pid
[08/11/14 10:53:51] seafile-controller.c(89): spawned ccnet-server, pid 12062
[08/11/14 10:53:52] seafile-controller.c(594): ccnet daemon connected.
[08/11/14 10:53:52] seafile-controller.c(186): starting seaf-server ...
[08/11/14 10:53:52] seafile-controller.c(74): spawn_process: seaf-server -c /home/seafile/ccnet -d /home/seafile/seafile-data -l /home/seafile/logs/seafile.log -P /home/seafile/pids/seaf-server.pid
[08/11/14 10:53:52] seafile-controller.c(89): spawned seaf-server, pid 12071
[08/11/14 10:53:52] seafile-controller.c(74): spawn_process: fileserver -c /home/seafile/ccnet -d /home/seafile/seafile-data -l /home/seafile/logs/fileserver.log -P /home/seafile/pids/fileserver.pid
[08/11/14 10:53:52] seafile-controller.c(89): spawned fileserver, pid 12072
[08/11/14 10:53:52] seafile-controller.c(567): seafdav not enabled.

ccnet.log:

[08/11/14 10:53:51] ../common/session.c(385): Listen on 127.0.0.1 13418
[08/11/14 10:53:51] ../common/session.c(257): Update pubinfo file
[08/11/14 10:53:51] ../common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections
[08/11/14 10:53:52] ../common/session.c(365): Accepted a local client
[08/11/14 10:53:52] ../common/session.c(365): Accepted a local client
[08/11/14 10:53:52] ../common/session.c(365): Accepted a local client
[08/11/14 10:53:52] ../common/session.c(365): Accepted a local client
[08/11/14 10:53:59] ../common/connect-mgr.c(266): Unknown peer e7ef494df22deaccecd1b74977586e7de2e77f3c connecting
[08/11/14 10:56:43] ../common/session.c(365): Accepted a local client
[08/11/14 10:56:44] ../common/session.c(365): Accepted a local client
[08/11/14 10:57:18] ../common/session.c(365): Accepted a local client
[08/11/14 10:57:59] ../common/processor.c(219): [Proc] Shutdown processor service-proxy-proc(-13851) for bad update: 403 Bad Object
[08/11/14 10:57:59] ../common/processor.c(219): [Proc] Shutdown processor service-stub-proc(1028) for bad update: 403 Bad Object
[08/11/14 10:57:59] ../common/peer.c(696): Delayed response from local-2(5f6ff23a05), id is 1028, 506 Bad update code

seafile.log:

[08/11/14 10:53:52] ../common/mq-mgr.c(60): [mq client] mq cilent is started
[08/11/14 10:53:52] ../common/mq-mgr.c(106): [mq mgr] publish to hearbeat mq: seaf_server.heartbeat
[08/11/14 10:53:52] listen-mgr.c(115): listen on port 12001 for block tranfer
[08/11/14 10:57:59] Bad update: 403 Bad Object.

fileserver.log:

[08/11/2014 10:53:52 AM] fileserver.c(337): host = 0.0.0.0, port = 8082

2014-08-11 11_14_36-seafile

fraber commented 10 years ago

Hi!

I've got additional information: Looking at the applet.log file in C:\Users\ccnet\logs I see a:

[08/11/14 18:14:26] request failed for https://seafile.project-open.net/api2/events/: status code 404

Looking manually at the requested URL I get:

Events
GET /api2/events/
HTTP 403 FORBIDDEN Vary: Accept Content-Type: text/html Allow: GET, HEAD, OPTIONS
{
    "detail": "You do not have permission to perform this action."
}

Any idea how this could happen? I'm logged in as "Administrator" (the server admin).

Bests, Frank

killing commented 10 years ago

Hi Frank,

I've read your log. I found a potential bug that may lead to this error. But in my environment I can't reproduce that bug. Perhaps I can give a test version for you to see if it solves the problem.

Does your library contain duplicate files or folders? That may cause the error.

fraber commented 10 years ago

Hi Killing,

It's possible, that the same filename will occur more more than once.

Yesterday I installed the old 3.0.4 Windows client, and there are no issues anymore with this one. So you've got a regression issue!

One of the next days I'll test the 3.1.3 again on a different computer, I'll let you know about the result

We are now going to continue with Seafile for internal use, but definitely not for our customers. Guys, you still have a long way to go... You really need to sort out software quality, otherwise your big success (that you otherwise deserve!) won't appear...

Thanks! Frank

haiwen / seafile

Shutdown processor service-proxy-proc(-5795) for bad update: 403 Bad Object #790