Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Syslog & Trap Services won't start

Had to manually start the services in services.msc.

However, when I go into the Orion Service Manager they're both listed as stopped. I click start, the hourglass comes up for a minute, then goes away. Problem is, nothing has happened. Services are still stopped.

I really need to get this thing working so I can find out what the heck is causing 2400 unknown protocol drops an hour on my MPLS router. How do I get this thing up and running?

Find more posts tagged with

Accepted answers

bshopp

Are there any messages in the Windows Event logs indicating what the issue is? Do you have any other Syslog or trap servers running on the same box?

All comments

bshopp

Are there any messages in the Windows Event logs indicating what the issue is? Do you have any other Syslog or trap servers running on the same box?

Poppinfresh

This was a good call. Our trial version of Kiwi was eating it all.

I guess my next question is this: Does the Syslog addon that's now in Orion replace Kiwi? All we want is a centrallized location to compile syslog events and send us alerts based on certain criteria. If we don't need the additional Kiwi software, that would be ideal (and make it easier for us to succeed when we ask the guys with the checkbooks to give us money to buy all this stuff)

bshopp

I think it really depends on your use case and how you want to use the Syslog server. Distributed or not? Volume? Archiving?