Things go wrong when the network is bad and the repo is big.

[melochale]

I always receive this message when the repo is big and the network could be bad, so sad :(

Compressing objects: 100% (4537/4537), done.
Writing objects: 100% (6381/6381), 43.95 MiB | 12.00 KiB/s, done.
Total 6381 (delta 1334), reused 6381 (delta 1334)
error: RPC failed; result=22, HTTP code = 500
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly

version: 0.6.5.0815 Beta

[unknwon]

Thanks your report!

Can you post the exact error of 500 logged in Gogs?

[melochale]

015/08/27 10:35:38 [...s/middleware/repo.go:288 func·009()] [E] GetTags: fork/exec /bin/git: cannot allocate memory
2015/08/27 10:36:07 [I] Log Mode: File(Info)
2015/08/27 10:36:07 [I] Redis Supported
2015/08/27 10:36:07 [I] Memcache Supported
2015/08/27 10:36:07 [I] Cache Service Enabled
2015/08/27 10:36:07 [I] Session Service Enabled
2015/08/27 10:36:08 [I] SQLite3 Supported
2015/08/27 10:36:08 [I] Run Mode: Production
2015/08/27 10:36:08 [I] Listen: https://0.0.0.0:443
2015/08/27 11:21:02 [...s/middleware/repo.go:288 func·009()] [E] GetTags: fork/exec /bin/git: cannot allocate memory
2015/08/27 11:21:39 [...s/middleware/repo.go:288 func·009()] [E] GetTags: fork/exec /bin/git: cannot allocate memor

[unknwon]

Well... the error is pretty obvious.

Which version of Gogs are you running?

[melochale]

version: 0.6.5.0815 Beta，the latest released version.

[unknwon]

@melote thanks for following up!

But still, it is caused your memory is all being used.

What does Gogs /admin panel say about how much memory has been used by Gogs?

[melochale]

@unknwon , Let me check that, Hmm, now 500 code error happened, the monitor info is:

Server Uptime
2 hours, 23 minutes, 20 seconds
Current Goroutines
20
Current Memory Usage
72MB
Total Memory Allocated
176MB
Memory Obtained
154MB
Pointer Lookup Times
1883
Memory Allocate Times
670280
Memory Free Times
584384
Current Heap Usage
72MB
Heap Memory Obtained
143MB
Heap Memory Idle
69MB
Heap Memory In Use
74MB
Heap Memory Released
36MB
Heap Objects
85896
Bootstrap Stack Usage
416KB
Stack Memory Obtained
416KB
MSpan Structures Usage
100KB
MSpan Structures Obtained
143MB
MCache Structures Usage
1.2KB
MCache Structures Obtained
16KB
Profiling Bucket Hash Table Obtained
1.4MB
GC Metadada Obtained
9.0MB
Other System Allocation Obtained
480KB
Next GC Recycle
143MB
Since Last GC Time
34.2s
Total GC Pause
0.7s
Last GC Pause
0.011s
GC Times
79

and my VPS memory info is:

[root@iZ28j4wwubeZ ~]# free
             total       used       free     shared    buffers     cached
Mem:        500576     486072      14504      12644       8368      54096
-/+ buffers/cache:     423608      76968
Swap:            0          0          0

the gogs memory usage:

[root@iZ28j4wwubeZ ~]# top
  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND
 1278 root      20   0  767084   6788   3752 S  0.3  1.4   9:02.72 AliYunDun
 1296 root      20   0  790524   5276   2996 S  0.3  1.1   8:13.30 AliHids
10317 root      20   0  366976  68176   9240 S  0.3 13.6   0:08.64 gogs

[root@iZ28j4wwubeZ ~]# ps -aux | grep gogs
root     10317  0.0 13.5 366976 67912 ?        Ssl  11:26   0:08 ./gogs web

[unknwon]

OK... So does restart Gogs solves your problem? Because code in master has attempted to fix a memory leak on HTTP push/pull . This could be a reason.

[unknwon]

If not, then means your push is so large that really needs more RAM...

[melochale]

@unknwon , yes, everything has been all right since restart gogs.

[unknwon]

@melote OK, let's see how things are going after next release(with memory leak fix)!