Opened at 2015-08-18T17:15:22Z

Closed at 2020-01-17T16:20:12Z

#2483 closed defect (was already fixed)

connection failed between gateway and (S4) server

Reported by: zooko Owned by:
Priority: normal Milestone: undecided
Component: code-network Version: 1.10.1
Keywords: Cc:
Launchpad Bug:

Description

I was just trying to upload a file and got a failure. Here is some diagnostic info about it...

Attachments (1)

incident-2015-08-18--17-04-19Z-rfjayvy.flog.bz2​ (9.4 KB) - added by zooko at 2015-08-18T17:16:43Z.
I hit the "report an incident" button after this failure.

Download all attachments as: .zip

Change History (3)

Changed at 2015-08-18T17:16:43Z by zooko

I hit the "report an incident" button after this failure.

comment:1 Changed at 2015-08-18T20:18:08Z by daira

Zooko and I successfully reproduced this failure, and a similar failure for SDMF. For MDMF, the storage server is consistently OOM-killed when it approaches the 595 MB available memory of a t1.micro EC2 instance (at around 543MB resident): 

Aug 18 19:36:20 ip-10-196-59-108 kernel: [33065383.602943]
 Out of memory: Kill process 1662 (tahoe) score 892 or sacrifice child
Aug 18 19:36:20 ip-10-196-59-108 kernel: [33065383.602960]
 Killed process 1662 (tahoe) total-vm:577324kB, anon-rss:542684kB, file-rss:0kB

For SDMF, the publish fails due to a Python MemoryError at around 442MB resident. The process survives but stays at the same memory usage for a while, then drops to 281MB resident.

More details to follow.

Last edited at 2015-08-18T20:26:42Z by daira (previous) (diff)

comment:2 Changed at 2020-01-17T16:20:12Z by exarkun

  • Resolution set to was already fixed
  • Status changed from new to closed

This is probably the wrong place for S4 bug reports. Also the S4 deployment infrastructure has changed such that the limits discussed above no longer exist.

Note: See TracTickets for help on using tickets.