APM next polling Time is always in the past

Can anyone help with an issue we currently have.
Our application monitors are stuck on next polling time.
What i mean by this is that polling of APM appears to always be in the past.
Currently the next poll is yesterday.
If I create a new monitor then this just sits with a status "scheduler not available"
Ther next poll for this new monitor is either 5 years in the past or 5 years in the future.

I have restarted all services and servers but the polling still reports "next poll time" with yesterdays date

Please help..

Find more posts tagged with

apm_polling

Accepted answers

All comments

FormerMember

I asked the Dev team to look at this one, and their advice was for you to open a ticket so that we can collect diagnostics and help figure it out.

njoylif

I've had this happen recently on my NPM environment on about 600 nodes. quit polling availability and response time. tried changing next poll to future in DB. got a poll or two out of it, and reverted back to past....wierd.

anyways, case 218742

I've had this happen once before, but don't remember how I got around it...so anxiously awaiting supports response!

byrona

I just had this happen on a bunch of nodes after upgrading to APM 4.0.1. I just opened a support ticket so hopefully they will be able to help me.

Unfortunately this issue is almost impossible to detect and it caused us to miss a critical issue over the weekend.

njoylif

yea, argg!!!

Please post results of ticket when they are done. thanks

ukmdb

SQL Server was the problem for us that caused the polling times to be incorrect.

Our database was on sql 2005 with 4gig Memory 1 quad core CPU and local disks

We then invested in a corporate SQL Server to house many solutions. Windows 2008, SQl 2008, 2 x quad core cpu's and 32gig memory with san storage.

As soon as we migrated the database over I assigned a static amount of 8Gig of memory to the SQL Instance and it has not stopped flying. Never had a problem since.

Seriously, I know it sounds a cheap cop - out but first look at your memory and disks. I bet the disks are being thrashed, in rich case throw more memory at it first as this is the cheaper and simler option. then look at your disks.

Hopr it helps

Questionario

I would really like to know the outcome of this and what the root cause for this would be... we have had too many issues with orion already which made orion silently stop alerting which is the worst thing that could happen in my opinion... no way to explain the value of a monitoring system against the argument that the monitoring system does not reliably alert on system outages or creates false alerts.

byrona

The following process (performed on the primary NPM system, not additional pollers) is what SolarWinds support provided me and this seemed to resolve the issue. It seems that it's possible for the job queue to get corrupted. This process replaces the job queue and resets all polling. I had to re-install both of the components mentioned to resolve the issue.

There are 2 different components that can be responsible for updating the next poll time of components in apm. Here is information on how to fix both. Start with job engine v2 first.

I would like to replace the Job Engine version 2 components.
First, open the Orion service manager. Go to Start > All Programs > SolarWinds Orion > Advanced Features > Orion Service Manager.
Select Solarwinds Orion Module Engine service and hit stop. Once the service is stopped let's remove and re-add the jobengine. Go to add/remove programs. Look for the SW jobengine v2.x and remove it. To reinstall:

For 2008 go to C:\ProgramData\SolarWinds\Installers and execute the jobengineV2.msi.

For 2003 go to C:\Documents and Settings\All Users\Application Data\SolarWinds\Installers and execute the jobengineV2.msi.

When it asks, select typical.

Give this about 10 minutes to work. A job queue should be recreated that is responsible for polling your components. If the next poll time still does not update run through the same process with Solarwinds collector v2. The install file is in the same installers folder and it's called collector.msi.