Syslog server stops responding

I have just upgraded to v10.4.0.57 and the issue is still occurring.  At this time I have no Syslog server, which is not the ideal situation

Let me see if I can reproduce on a local Vista x64 machine.

Thanks Floyd.  I should mention that we run Vista Enterprise x64.

Is your syslog server consuming significant CPU or memory when it hangs? 

It is ranging from 48-56% CPU usage, and 35,552K of memory.  I just had it stop responding again.

How many syslog messages are being sent to it?  Is it possible that your syslog server is just getting overwhelmed?

(Still working on testing on my local Vista x64 machine)

I also show 57% physical memory use, and the machine has 6.5GB of ram installed.

We have our devices set to send out at Warning level, and it averages about 80 messages every hour from 4 Cisco devices.

I do not see a Syslog service - shouldn't there be one?  Other tools like Kiwi require a service to be installed.  As a test, I have installed Kiwi Syslog on my Vista machine and it has not stopped responding since installing 15 minutes ago.  Whereas, the SolarWinds Syslog server stops responding within 2-3 minutes of launching.

Are you certain that this behavior started following the updates that you mentioned?

Yes.  In the past we have set the devices to send messages at debug level, and these come at a fast and furious rate.  The SolarWinds Syslog server was always able to handle that load without issue.

As mentioned, I installed Kiwi Syslog on the same machine and that is not experiencing the same issue as the SolarWinds Syslog.  As well, other syslog servers install a service onto the machine, where I cannot locate one for SolarWinds - only the SFTP/SCP and TFTP server services are listed.