Bug #4274
open
500 error when push big objects
0%
Description
Counting objects: 123894, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (49118/49118), done.
Writing objects: 100% (123894/123894), 168.71 MiB | 3.52 MiB/s, done.
Total 123894 (delta 66189), reused 123776 (delta 66106)
error: RPC failed; result=22, HTTP code = 500
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
Updated by feng mu about 8 years ago
sometime 502 error
Counting objects: 123894, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (49118/49118), done.
Writing objects: 100% (123894/123894), 168.71 MiB | 3.76 MiB/s, done.
Total 123894 (delta 66189), reused 123776 (delta 66106)
error: RPC failed; result=22, HTTP code = 502
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date
Updated by Marcin Kuzminski [CTO] about 8 years ago
- Target version set to v4.5
Are you using Apache/Nginx in front of RhodeCode ? It might be that it kills the connection. There should be no limit on handling big files. We test RhodeCode with repos of over 20GB in size with files that exceede several hundred MBs.
Please share a bit more about your setup. We can help then.
Updated by feng mu about 8 years ago
Yep , I am using it behind nginx. I think it is not that nginx killed the connection , I check rhodcode log , it says
[2016-10-13 16:21:09 +0000] [10758] [ERROR] Retrying in 1 second.
[2016-10-13 16:21:10 +0000] [10758] [ERROR] Connection in use: ('127.0.0.1', 10003)
[2016-10-13 16:21:10 +0000] [10758] [ERROR] Retrying in 1 second.
[2016-10-13 16:21:11 +0000] [10758] [ERROR] Connection in use: ('127.0.0.1', 10003)
[2016-10-13 16:21:11 +0000] [10758] [ERROR] Retrying in 1 second.
I run netstat , I can see the 1003 port is existed.
Updated by Marcin Kuzminski [CTO] about 8 years ago
Hi,
can you try out this: https://community.rhodecode.com/t/new-high-performance-http-backend/71/1
Updated by Marcin Kuzminski [CTO] about 8 years ago
- Target version changed from v4.5 to v4.6
Updated by Marcin Kuzminski [CTO] almost 8 years ago
- Target version changed from v4.6 to v4.7
Updated by Marcin Kuzminski [CTO] almost 8 years ago
- Status changed from New to In Progress
Updated by Marcin Kuzminski [CTO] almost 8 years ago
- Status changed from In Progress to Resolved
We belive this problem was resolved in 4.6.1 when streaming wasn't working as expected in GIT repos.