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

Strange Orion Problem

Hey All,

After troubleshooting a problem with Orion for the past month and a half and running into a dead end with support, I've recently rebuilt our Orion server, but the problems persist. I'm wondering if anyone here has faced these issues before? They basically consist of two problems:

1) Custom Poller service randomly fails. While the service remains "started", it stops polling (identified by the "last polled" time not incrementing. It does not start until I stop/start the service.

2) Log shows a bunch of errors starting at midnight each day (can't identify any scheduled maintenance happening on either the Orion server or our DB server). There is an error for the Alerting Engine which seems to reoccur about every 3-4 minutes until I restart the Alerting service ... and until I restart the Alerting service, the web console is dead. Additionally, the Alerting Engine does not page out during this time (even though, like above, the service shows as 'started'). The error we get (in the solarwinds event log) is copied below:

2007-10-23 08:02:40,778 [AlertCheckingThread] WARN Error - Exception in CheckAlert.CheckAlert.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)

at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)

at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)

at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)

at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()

at AlertingEngine.CheckAlert.WriteSQLErrorToDB()

at AlertingEngine.CheckAlert.GetAlertFromDateBase()

at AlertingEngine.CheckAlert.CheckAlert()

Find more posts tagged with

Accepted answers

All comments

dperdue

EverestM,

I am not sure if your first issue is fixed in 8.5.1, but the second one should be fixed. We have just released 8.5.1 this morning.

Please let us know if 8.5.1 does not fix either of these issues and we will look into them further.

EverestM

The second problem seems to mostly be solved with 8.5.1... There are still erros at midnight, but there are less of them and the alerting service & web console continue to work.

Unfortunately we're still having problem No. 1. Has anyone run into this before?

dperdue

For the issues that remain, please enter a support ticket so we can work with you to figure out the cause and a fix for this.

EverestM

I've been working under ticket #16866 for a few months now .. but it doesn't seem to be going anywhere which is why I figured I'd see if anyone here had run into this issue as well.

Azazzello

I have the same #1 problem. Week or two ago I opened case #21323 and was advised:

"There’s no need to run the AlertingEngine service on more than one server. This service doesn’t filter nodes by engine – it always processes all alerts on all nodes. For huge deployments there can be performance issues, but it looks like this customer is nowhere near those limits. I recommend the customer disable the AlertingEngine service on the additional poller."

But it didn't solved issue.

bbusbey

I'm getting every 5 seconds in the swAlert.log:

2007-11-01 16:15:22,916 [MainTaskThread] ERROR All - Error in SetupMainDBConnection Object reference not set to an instance of an object.

Bruce

mark_wiggans

Bruce-

cannot tell you why that is happening but see this post for instructions on clearing them out so your logs do not become full-

Debbi

Bruce I had that problem and restarting the alerting service fixed it. Apparently this can also be due to one alert being misconfigured and you can uncheck each of your alerts in turn (and save) to see if the EV messages stop. -Debbi