Updated: August 15, 2016
This article describes the issue when Kiwi Syslog Server constantly crashes and halts and you receive the following error: out of stack space
This issue may also be giving you less messages than the 2,000,000 maximum messages.
Sending too many messages to the Kiwi Syslog Server all at once combined with:
1. Generate a Tech-SupportFile.zip.
2. Fo to File > Create Tech-SupportFile.zip.
3. Open the file.
(note the above is for illustration purposes only)
According to the diagnostics (Example)
It is likely that you are pushing Kiwi Syslog too far and the best way to fix that is...
Disable DNS lookup. (see below)
Stop receiving Notice, Information and Debug messages. Warning and above are usually enough unless you have a legal requirement to store those.
The Kiwi Syslog application or service may stop if it is receiving more than 20 thousand messages per hour and IP resolution is enabled for messages. To fix that, you may try the following steps below:
1. Open the Kiwi Syslog Server interface.
2. Click File > Setup.
3. Click DNS Resolution.
4. Uncheck the following box:
5. Click Ok.
See if Kiwi Syslog Server continues to stop. If it does, please perform the following:
6. Open the Kiwi Syslog Server application.
7. Move down to the Message Buffer Information section and ensure that Message Queue Overflow is at 0. If it is not, you should increase the MessageBuffer size to a value that exceeds the sum of "Message Queue Max Size" and "Message Queue overflow".
a. On the Kiwi Syslog Server, open the registry editor (regedit.exe).
b. Open the following branch:
c. Add the following string value:
*** where ### is the sum calculated on step 9 plus some room for growth.
9. Restart the Kiwi Syslog Service/Manager.