GFI Software

Welcome to the GFI Software community forum! For support please open a ticket from https://support.gfi.com.

Home » GFI User Forums » Kerio Connect » KThreadPool.cpp error
KThreadPool.cpp error [message #135395] Thu, 11 May 2017 11:13 Go to next message
arodella is currently offline  arodella
Messages: 15
Registered: July 2016
Location: Italy
I am getting all the day this kind of error and the server is becoming very unstable.

KThreadPool.cpp: Cannot create new worker thread: (12) Cannot allocate memory

How can I solve it?


thanks in advance
Re: KThreadPool.cpp error [message #135398 is a reply to message #135395] Thu, 11 May 2017 12:27 Go to previous messageGo to next message
vtripp is currently offline  vtripp
Messages: 616
Registered: September 2009
Location: Cambridge
Hi Antony,

Have you looked at opened folders to see if any folder have a high count? As you can get these messages sometimes if a folder is stuck. Also how much memory does the machine have and which version of Kerio Connect are you running?

Cheers,
Vicky
Re: KThreadPool.cpp error [message #135401 is a reply to message #135398] Thu, 11 May 2017 12:40 Go to previous messageGo to next message
arodella is currently offline  arodella
Messages: 15
Registered: July 2016
Location: Italy
Version 9.0.1 (394), Mac OS X (10.11.3), x86_64 and 16GB RAM

only open folders are the inbox
Re: KThreadPool.cpp error [message #135402 is a reply to message #135401] Thu, 11 May 2017 12:43 Go to previous message
vtripp is currently offline  vtripp
Messages: 616
Registered: September 2009
Location: Cambridge
What is the count for some of those folders? Any equal to or above 10?

Also I would suggest upgrading as you are using a version of connect that is over a year and a half old.

Cheers,
Vicky
Previous Topic: Disable kerio connect splash screen in desktop app?
Next Topic: Shared Contacts in Kerio Connect Webmail not appearing in macOS Contacts
Goto Forum:
  


Current Time: Thu Jun 08 13:55:46 CEST 2023

Total time taken to generate the page: 0.02044 seconds