> Hey Thomas > Thanks for the answer. The command output is this: > Max cpu time unlimited unlimited seconds > Max file size unlimited unlimited bytes > Max data size unlimited unlimited bytes > Max stack size 8388608 unlimited bytes > Max core file size 0 unlimited bytes > Max resident set unlimited unlimited bytes > Max processes 514866 514866 > processes > Max open files 4096 4096 files > Max locked memory 65536 65536 bytes > Max address space unlimited unlimited bytes > Max file locks unlimited unlimited locks > Max pending signals 514866 514866 signals > Max msgqueue size 819200 819200 bytes > Max nice priority 0 0 > Max realtime priority 0 0 > Max realtime timeout unlimited unlimited us > > Max Open Files seems a bit low, is that the reason?
Very likely, so try to increase the Max open files limit and restart the Firebird process. Increasing the limits might be a bit tricky, cause it may differ across Linux distros (to have new limits being persistent) and even more interestingly, how processes are started (e.g. via user based SSH session vs. started as systemd service etc.) Try to Google for your Linux distro. So, best check if new limits have been applied is always done via: sudo cat /proc/<pid>/limits Hope this helps. -- With regards, Thomas Steinmaurer http://www.upscene.com/ Professional Tools and Services for Firebird FB TraceManager, IB LogManager, Database Health Check, Tuning etc.
