Topher_60415
Jul 23, 2009Nimbostratus
F5MonitoringService Keeps Crashing
All servers running Windows Server 2003 R2 x64 with full patches.
Installed version of SCOM is 2007 R2 RTM.
Installed version of F5 Management Pack is 1.2.0.579-x64.
Service is installed and disabled on RMS and is also deployed to a secondary MS in a running capacity.
I am monitoring 2 F5 LTM devices
Behavior - Service gets started with no issues and runs for approximately 2 hours, then crashes and dumps an event to the Event Log. The recovery behavior in the definitions of the service is to automatically restart, but it does not. Creating an automatic recovery response for the monitor in SCOM to start the service also has no effect. Error thrown to the Event Log is as follows:
Event Type:Error
Event Source:F5 Events
Event Category:None
Event ID:201
Date:7/23/2009
Time:2:05:18 PM
User:N/A
Computer:NRUSCA-S3040
Description:
Unhandled exception in DefaultDomain
Detailed Exception Information:
F5Networks.F5Exception: Unhandled exception in DefaultDomain ---> System.InvalidOperationException: Cannot modify key property 'TargetServicePort', that would change the object's identity.
at F5Networks.ManagementPack.DataAccess.OperationsManager.SdkConnector.UpdateObject(MonitoringObject monitoringObj, EntityData entityChanges, ConfigData configData)
at F5Networks.ManagementPack.DataAccess.OperationsManager.SdkConnector.UpdateObject(Guid monitoringId, EntityData entityChanges, ConfigData configData)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrMonitoringAdapter._UpdateDeviceConfig_Modify(SdkConnector connector, IPAddress deviceIP, ConfigChange configChange, DeviceConfigStats configStats, List`1 entitiesNeedingStateUpdates)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrMonitoringAdapter.<>c__DisplayClass22.b__1e()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.<>c__DisplayClass6.b__5()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.CoreDoOperation[ReturnResult](GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrConnectionPool`1.CoreDoOperationWithExceptionMapping[ReturnResult](ManagedOpsMgrConnection`1 connection, GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.<>c__DisplayClass9`1.b__8()
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ManagedConnectionBase`1.DoOperationWithRecovery[ReturnResult](GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.UseConnectionForOperation[ReturnResult](ManagedConnectionType& connection, Object connectionTag, GenericVoidHandler`1 operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.ConnectionPoolBase`2.UseConnectionForOperation(ManagedConnectionType& connection, Object connectionTag, VoidVoidDelegate operation)
at F5Networks.ManagementPack.DataAccess.ManagedConnections.LockedConnectionPoolReference`2.UseConnection(VoidVoidDelegate operation)
at F5Networks.ManagementPack.DataAccess.OperationsManager.OpsMgrMonitoringAdapter.UpdateDeviceConfig(ConfigChange configChange, IPAddress deviceIP, Guid deviceId, ObjectsModified objectsModified, List`1 entitiesNeedingStateUpdates, List`1 entitiesAdded)
at F5Networks.ManagementPack.DataAccess.Configuration.ConfigManager`8.UpdateDeviceConfig(Device device, Queue`1 configurationPackets, Boolean saveRuleUpdates, ObjectsModified objectsModified, List`1 entitiesNeedingStateUpdates, List`1 entitiesAdded)
at F5Networks.ManagementPack.Services.DeviceMonitor._UpdateDeviceDataConfiguration(Device device, DataReceivedEventArgs dataArgs)
at F5Networks.ManagementPack.Services.DeviceMonitor._ConnectionDataReceived(ListeningDeviceConnectionCache connectionCache, DataReceivedEventArgs dataReceivedArgs)
at F5Networks.ManagementPack.ConnectionCache.ListeningDeviceConnectionCache.DoDataOperation(DeviceConnection deviceConnection, DataReceivedEventArgs args)
at F5Networks.ManagementPack.Services.DeviceMonitor._ConnectionDataReceived(ListeningDeviceConnectionCache connectionCache, DataReceivedEventArgs dataReceivedArgs)
at F5Networks.ManagementPack.Services.DeviceMonitor.ParsedResponseProcessor.ProcessData(Queue`1 responses)
at F5Networks.ManagementPack.Services.DeviceMonitor.BatchedParsedResponseProcessor._FlushQueue(Object synchronousCall)
--- End of inner exception stack trace ---
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Really needing some help here as the service seems unstable regardless of what I do. As an FYI, this environment was upgraded from SCOM 2007 SP1 and the crashes occurred in SP1 as well so I do not believe this is an R2 related issue (though I could certainly be wrong).