You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When one tries to establish too many concurrent client connections to monetdbd (e.g. 1000 mclients), acceptConnections() will fail with "Too many open files". Subsequently monetdbd will decide to simply stop working (i.e. exit(0)).
So, it's not a crash, but monetdbd shouldn't exit after such a non-critical error.
Date: 2018-08-02 11:12:41 +0200
From: @yzchang
To: Merovingian devs <>
Version: 11.29.7 (Mar2018-SP1)
Last updated: 2018-08-31 13:23:12 +0200
Comment 26583
Date: 2018-08-02 11:12:41 +0200
From: @yzchang
When one tries to establish too many concurrent client connections to monetdbd (e.g. 1000 mclients), acceptConnections() will fail with "Too many open files". Subsequently monetdbd will decide to simply stop working (i.e. exit(0)).
So, it's not a crash, but monetdbd shouldn't exit after such a non-critical error.
Comment 26588
Date: 2018-08-03 13:19:01 +0200
From: MonetDB Mercurial Repository <>
Changeset a0fec1753e6f made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a0fec1753e6f
Changeset description:
Comment 26589
Date: 2018-08-08 10:13:21 +0200
From: @sjoerdmullender
With no indication to the contrary, I'm assuming this has been adequately fixed.
The text was updated successfully, but these errors were encountered: