2 Replies Latest reply on Dec 13, 2017 4:29 PM by George Sutherland

NPM alerting process

George Sutherland Dec 13, 2017 3:35 PM

Anyone experiencing a condition where the alerting process service stops for no obvious reason, or fails to start after a server reboot?

Over the last 3 weeks has happened 4 times.... will run perfectly for days and then stop. I can restart without issue.

(figured I would reach out before trying support)

Thanks in advance

George

Re: NPM alerting process

cahunt Dec 13, 2017 4:24 PM (in response to George Sutherland)
Have had this happen due to a few different reasons over the years. Your best bet is to reference your logs to determine what action is best. If you are not familiar with the logs, or do not have the time to search; I would suggest you open a case. So with that, confirm some details before you try anything

- Corrupt Folder/File/App - repair - InfoService, JobEngines
- Under Resourced Systems - check/trend hardware resource use, db IO
- only way to fix this is to add resources, or decrease your DB size
- this can also manifest in a few different ways, and if the case you will see constant issues, delays, slow load, etc. (If you do not see your cpu, ram or NIC constantly peaking at times then look for something more simple than this possible rabbit hole)

I have also seen Full Transaction Logs manifest this issue in a few client environments.
ref link : SolarWinds Information Service V3 fails to start - SolarWinds Worldwide, LLC. Help and Support

-CharlesH
Loop1 Systems: SolarWinds Training and Professional Services
LinkedIN: Loop1 Systems
Facebook: Loop1 Systems
Twitter: @Loop1Systems
Like (0)

Actions
- Re: NPM alerting process
  
  George Sutherland Dec 13, 2017 4:29 PM (in response to cahunt)
  
  Thank you cahunt... Will look at those.. (nothing obivious so far!)
  Appreciate it!
  
  Like (1)
  
  Actions