Forum Discussion
yuej_100825
Nimbostratus
Nimbostratusfailed during install 2.1.0.43: DataSource and ConditionDetection modules required ...
Error Message: (GUI and log)
FatalError: The DataSource and ConditionDetection modules required for the F5 Monitoring Service to run could not be loaded by Operations Manager monitoring host. Check the Operations Manager Event Log for errors and manually start the F5 Monitoring Service once any issues have been resolved.
My environment:
- Install version: 2.1.0.43 64-bit
- SCOM 2007 R2 64-bit on WS08 R2 64-bit
- Both Install Account and Service Account are member of a group with SCOM Administrators privilege as well as Local Administrator of the RMS server.
- RMS not clustered
Notes:
- Installation failed after a long 5 mins wait and prompted to examine the log file.
- F5 Monitoring Service wouldn't stay up and running.
- 'F5 Networks' folder appears in the SCOM Monitoring pan and there are some views and subfolders underneath
- F5 MP powershell installed
- Tried to install on C:\... (default path) and D:\.... (desired install path)
- verified service account credential by logging on to the RMS and launching SCOM console.
- I remember seeing some sort of cannot connect to IPC Port when using the Repair Installation option.
Any help is appreciated.
More Logs:
< TimeStamp > Info: Verifying the DataSource and ConditionDetection modules required for the F5 Monitoring Service to run are loaded by Operations Manager monitoring host.
< TimeStamp > FatalError: Trying to run msiexec failed with exception: System.InvalidOperationException: Cannot process request because the process (4352) has exited. at System.Diagnostics.ProcessManager.OpenProcess(Int32 processId, Int32 access, Boolean throwIfExited) at System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly) at System.Diagnostics.Process.get_Modules() at F5Networks.ManagementPack.Setup.SetupHarness._VerifyModulesLoaded(SetupLogger setupLog, Boolean debugLogging) at F5Networks.ManagementPack.Setup.SetupHarness._RunMsi(Settings settings, SetupLogger setupLog, SetupUI setupGui, String& msiInstallType) at F5Networks.ManagementPack.Setup.SetupHarness._RunMsiWithErrorHandler(Settings settings, SetupLogger setupLog, SetupUI setupGui, String& msiInstallType)
< TimeStamp > Info: LogFiles: C:\Program Files\F5 Networks\Management Pack\log\msisetup.log and C:\Program Files\F5 Networks\Management Pack\log\SetupHelper.log
< TimeStamp > FatalError: An error has occurred during the F5 Networks Management Pack Setup. Please contact the F5 Management Pack team at managementpack@f5.com with the following information: The F5 Networks Management Pack setup has failed for the following reason: Cannot process request because the process (4352) has exited.
- Could you please send us the following application logs on the RMS server where you installed the F5 Management Pack:
- F5 Monitoring Log
- Operations Manager
This would give us more information about why the F5MP Condition Detection and DataSource modules are not loaded by SCOM.
You can send the archived zip files directly to managementpack(at)f5(dot)com.
Thank you.
Julian - From what I gather in the logs, there's a repeating error pattern that's pointing to a crash of the OpsMgr monitoring host. This error apparently was there before installing the F5 Management Pack (unless you attempted previous installs for which we don't have the setup log). The error that I'm concerned about is (in the Operations Manager event log):
EventId: 4000; Source: HealthService
A monitoring host is unresponsive or has crashed. The status code for the host failure was 2164195371.
This is followed by an access denied error within the HealthService:
EventId: 6002; Source: HealthService
Performance data from the Health Service could not be collected since opening the shared data failed with error 5L (Access is denied.).
Regarding the 4000 error, there's a Microsoft KB article/hotfix addressing directly this problem:
http://support.microsoft.com/kb/951526
The error condition apparently could be produced by the import of management packs that "monitor certain network devices". This hotfix is not installed on your RMS server, according to our setup log. I would like to see this error gone before we attempt on troubleshooting deeper the F5 Management Pack.
Are you still seeing this error showing up in your Operations Manager log?
Julian 
yuej_100825I attempted to install and uninstall several times. Got same experience on both lab and production OpsMgr environment. The RMS still grayed out with the healthy sign.
Looking at the KB article, the hotfix is for SCOM 2007 SP1 only and is first corrected in SCOM2007 R2. I'm running R2, the file version on my RMS is newer (6.1.7221.0) than the one in the KB (6.0.6278.24)
For now I'll uninstall the F5 MP and wait for your advice.- In trying to better understand your monitoring environment in the hope that we could somehow reproduce the problem here in our lab:
- Can you confirm that once you removed / uninstalled the F5 MP from your RMS, the EventId 4000 errors are gone?
- Do you have any SNMP monitoring set up for the F5 devices (through other management packs)?
One reason for the monitoring host crashing with event id 4000 could be that too much null data gets imported (as rule/stats) into Operations Manager. So we'll have to identify the management pack defining the rule-sets requesting the null data and remove it. And I'd like to make sure it's our F5 Management Pack. So after you remove the F5 MP and flush the health service cache on the RMS (where I assume you're monitoring the F5 devices from), can you tell if the event id 4000 still occurs?
Thank you.
Julian - yuej_100825There are no more 4000 errors found in the event logs after removing F5 MP. SCOM07 R2 is a relatively new built environment and I don't have any other network / unix devices being monitored. F5 MP is the first non windows MP being introduced to SCOM here. Is it possible for you to webex to my box to see it in action?
- Sure, we can do that!
I'll look for you to set up the webex meeting at your best convenience, and I'll try to remote in. You can send the webex meeting request to managementpack(at)f5(dot)com.
Thanks!
Julian - yuej_100825The issue is fixed with the help of the brilliant support team, especially Dave and Julian.
It came down to the OpsMgr SDKConfig did not have right to do a lot of things during installation. Adding the SDKConfig account to the OpsMgr Administrators Role did the trick. - Jasper,
Thank you for your kindness and open attitude in helping us troubleshoot the problem in your test/production environment.
We have just released a new version of the F5 Management Pack that includes a number of fixes, and overall improves the quality of the F5 MP, we hope.
You can download this release from: http://devcentral.f5.com/Community/GroupDetails/tabid/1082223/asg/54/aft/1174022/aff/2301/afv/topic/showtab/groupforums/Default.aspx
Let us know if this works or if you still run into any issues.
And thank you for your patience through all of this!
Julian
