Forum Discussion
chadRS_14639
Nimbostratus
Nimbostratusremoved virtual servers from F5 but they are still in SCOM
We removed a QA pool from the F5, but it is still showing up in SCOM and it is hitting our log on F5 every minute with errors. I updated to the latest management pack to see if that would resolve the issue, but it did not. Here are the errors we have in the F5 logs.
Mon Mar 15 15:57:13 CDT 2010 err local/CorpLBA mcpd[3214] 01020036 The requested virtual_server (Q_MS_MYANSWERS_80) was not found.
Mon Mar 15 15:57:01 CDT 2010 err local/CorpLBA mcpd[3214] 01020036 The requested pool member (Q_MS_MYANSWERS_80 172.23.23.82 http) was not found.
The only error we have in the SCOM F5 log was this one after installing the updated management pack. We received 2 301s 4 minutes later and havent not received anything in the log since. Any help would be greatly appreciated.
Thanks,
Chad
Event Type:Error
Event Source:F5 Events
Event Category:None
Event ID:201
Date:3/15/2010
Time:1:43:33 PM
User:N/A
Computer:NTMOMRPA
Description:
Unhandled exception in DefaultDomain
Detailed Exception Information:
F5Networks.F5Exception: Unhandled exception in DefaultDomain ---> System.Threading.ThreadAbortException: Thread was being aborted.
at System.Threading.WaitHandle.WaitOneNative(SafeWaitHandle waitHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(Int64 timeout, Boolean exitContext)
at System.Threading.WaitHandle.WaitOne(TimeSpan timeout, Boolean exitContext)
at System.ServiceModel.TimeoutHelper.WaitOne(WaitHandle waitHandle, TimeSpan timeout, Boolean exitSync)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.SyncDuplexRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.EnterpriseManagement.Common.ITypeSpaceDataAccess.GetRulesByCriteria(String criteria, String languageCodes, IList`1 targetTypeIds, Boolean includeBaseTypes)
at Microsoft.EnterpriseManagement.DataAbstractionLayer.TypeSpaceOperations.GetRulesByCriteria(MonitoringRuleCriteria criteria, String languageCodes, IList`1 typeIds, BaseClassTraversalDepth baseClassTraversalDepth)
at Microsoft.EnterpriseManagement.ManagementGroup.GetMonitoringRulesInternal(MonitoringRuleCriteria criteria, IList`1 targetTypeIds, BaseClassTraversalDepth baseClassTraversalDepth)
at Microsoft.EnterpriseManagement.ManagementGroup.GetMonitoringRules()
at F5Networks.ManagementPack.DataAccess.OperationsManager.CoreConnector.<_Connect>b__9()
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClass6.b__5()
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClassb`1.b__8()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification[TReturnResult](GenericVoidHandler`1 activeCode, String action)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification(VoidVoidDelegate activeCode, String action)
at F5Networks.ManagementPack.DataAccess.OperationsManager.CoreConnector._Connect(Boolean checkForManagementPack, Boolean useDataWarehouse)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClass6.b__5()
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.<>c__DisplayClassb`1.b__8()
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode, VoidVoidDelegate postCodeSuccess, VoidGenericHandler`1 postCodeFailure)
at F5Networks.ProgressTracking.Tracer.DoActionWithTryFinally[TReturnResult](GenericVoidHandler`1 activeCode, VoidVoidDelegate preCode, VoidGenericHandler`1 postCode)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification[TReturnResult](GenericVoidHandler`1 activeCode, String action)
at F5Networks.ProgressTracking.ProgressEventSourceBase`1.DoActionWithProgressNotification(VoidVoidDelegate activeCode, String action)
at F5Networks.ManagementPack.DataAccess.OperationsManager.CoreConnector.Connect(Boolean checkForManagementPack, Boolean useDataWarehouse)
at F5Networks.ManagementPack.DataAccess.OperationsManager.ManagedOpsMgrConnection`1.CoreConnect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1._DoConnectWithRecovery()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.Connect()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._CreatePoolMember()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2._InitializeCache()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.Initialize(UInt32 initialOperationSize)
at F5Networks.ManagementPack.Services.DeviceMonitor._CreateOpsMgrConnections(Credentials opsMgrCredentials)
at F5Networks.ManagementPack.Services.DeviceMonitor._InitializeDataStore()
at F5Networks.ManagementPack.Services.DeviceMonitor._CreateDiscoveryManager()
at F5Networks.ManagementPack.Services.DeviceMonitor.OnAsyncServiceStart()
at F5Networks.Services.WorkerServiceBase._OnAsyncServiceStartHelper()
--- End of inner exception stack trace ---
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
- Hey Chad,
First I would try to Rediscover the F5 Device. There are a couple of ways to do this, but first try running the Rediscover task that is associated with the top level F5 Device. You will want to run this task using custom credentials for the user who originally discovered the device or it might fail. If that goes through, you should see the objects go away and the errors as well.
If the Rediscover task does not work, you can just run the Discover F5 Device wizard again which can be found by clicking on the F5 Monitoring Service group or the F5 Action Tasks. Let us know if this fixes it for you.
Thanks,
-Dave 
chadRS_14639It worked, until we did another change and now we have the same issue. I am wondering if there is something misconfigured in our f5 mp setup causing this issue. Any ideas?
Chad- Chad, it would help greatly to have some detailed logs from your installation -- details on how to get those logs here:
http://devcentral.f5.com/wiki/default.aspx/MgmtPack/GeneralTroubleshooting.html
It would be best if you could turn on logging, then create/reproduce the problem again, then send the logs.
Thanks -- Joel Hendrickson - chadRS_14639We disabled this for not because we were getting 10,000 log events a day. We will work on testing this again next week.
Thanks,
Chad - Thanks Chad -- it so happens that we are releasing a new version in the near future. If there's any chance you can send logs later this week (or even a better description of the 10K events) then we would have a better chance of getting fixes into the new version if fixes need to be made. Either way, we'll get it figured out.
Joel - Chad - I thought I would ping you one more time - we are very close to freezing our code for the upcoming release. I was hoping to get your problem investigated in case anything needs to be fixed in the product.
