Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8E23C11C05 for ; Thu, 1 May 2014 13:18:35 +0000 (UTC) Received: (qmail 64699 invoked by uid 500); 1 May 2014 13:18:33 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 64656 invoked by uid 500); 1 May 2014 13:18:33 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 64648 invoked by uid 99); 1 May 2014 13:18:33 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 13:18:33 +0000 Received: from localhost (HELO [192.168.1.105]) (127.0.0.1) (smtp-auth username kocolosk, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 May 2014 13:18:32 +0000 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Help understanding crash log From: Adam Kocoloski In-Reply-To: Date: Thu, 1 May 2014 09:18:30 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <2094852F-FC64-475F-A5F1-8CF9B1BF773F@apache.org> References: <0672596E-2C8C-4491-A7D3-4C751FEFDF93@gmail.com> <376A690F-0F8C-4B79-8B56-9D923551808A@apache.org> <2A153738-449F-4D14-9B9A-67D5CBB5B056@gmail.com> To: user@couchdb.apache.org X-Mailer: Apple Mail (2.1874) On May 1, 2014, at 8:47 AM, Interactive Blueprints = wrote: > 2014-05-01 13:14 GMT+02:00 Herman Chan : >> Thanks Adam, >>=20 >> It seems like it is happening again, with more info this time. It = looks like I am hitting some sort of system limit, can anyone point out = where to look next? >=20 > Just guessing here.. > What could be is that you hit the max open file limit of your system. > With "ulimit -a" you can see the limits on your system. > Usually the max open file limit is somewhere around 1024. > I noticed that couchdb loves to have a lot of files open = simultaneously. >=20 > Iin the same shell you start couchdb, right before you start couchdb, > you can do a "ulimit -a 4096" (or another large value), this should > give coudhb the ability to open more files. >=20 > Hope this helps. >=20 > Pieter van der Eems > Interactive Blueprints That's a good thought Pieter, though typically in that case you'll see = an 'emfile' error in the logs. This particular system_limit error (with = {erlang, spawn_link, ...} following it) occurs when the Erlang VM has = reached the maximum number of processes it's allowed to spawn. Judging = from the *long* list of processes linked to couch_httpd in this = stacktrace I'd say Herman's client is improperly leaving connections = open. Herman, did you intend to have 1000s of open TCP connections on = this server? Regards, Adam=