Thanks very much. We have installed the 2008-04-21 --nightly=current, and are now running, MonetDB server v5.5.0, based on kernel v1.23.0 Serving database 'BUSINESS' Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked We have also updated to the JDBC 1.7 (Canephora_p2 20080418 based on MCL v1.3) driver, which seems to fix unrelated connection issues. All is well for now, thanks again. On Friday 18 April 2008 04:27:26 Fabian Groffen wrote:
On 18-04-2008 09:37:19 +0200, Fabian Groffen wrote:
Hi Matthew, (you found a bug)
I just did an attempt to fix this in CVS stable. I'm not sure but I thought you use "current" at the moment, which means you need to wait for propagation to occur before you can try out my fix.
My wannabe fix plugs a hole in code that's called upon each client connection. I'll stresstest merovingian here using a simple bash script and mclient connecting in a loop, but I'd be pleased if you could test it in your development environment which is less artificial.
This indicates Merovingian or Sabaoth leaks filedescriptors. After your 10 days it has reached the limit of maximum open files allowed by your OS. Kudos for me that Merovingian doesn't crash but properly reports this. Bad karma for me that I leak the filedescriptors somewhere, hence the too many opened files.