Forum Discussion

Jeff_Jezek_4399's avatar
Jeff_Jezek_4399
Icon for Nimbostratus rankNimbostratus
Jan 25, 2011

Service not running after 2.1.5.440 upgrade

Hi,

 

This morning I upgraded our MP 2.1.3.217 to 2.1.5.440 and have run into a few issues. We have one RMS and one MS. Upgrade was run on both with same results.

 

 

1) At the end of the upgrade got the following error: The DataSource and ConditionDetection modules required for the F5 Monitory 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 onec any issues have been resolved. (See attached "F5 Install Error.jpg")

 

 

2) F5 Monitoring Service on both servers will start but immediatly stops with error in Event Log. (See attached "F5 Event 201.txt")

 

 

 

Attached is the setup.log file (setup.log.txt).

 

 

This looks very much like the issue "F5 monitoring agent not stable after upgrading MP to 2.1.5.440 x64" posted on 1/10/2011 but I don't see a resolution to that posting.

 

 

Any help is appreciated.

 

 

Thanks,

 

Jeff
  • Julian_Balog_34's avatar
    Julian_Balog_34
    Historic F5 Account
    Hi Jeff,

     

     

    Please check if the F5 Management Pack is showing up among the installed management packs (on the RMS): SCOM Operations Console > Administration > Management Packs > F5 Networks (v2.1.5.440). (Make sure to refresh the list of management packs before checking). If you don't have the F5 Management Pack imported in SCOM, please import it manually: SCOM Operations Console > Administration > Management Packs > right click > Import Management Packs > browse to the F5 Management Pack's installation folder and choose F5_ManagementPack.mp. After you're done, restart the SCOM Health Services on both, RMS and MS where you had the F5 Management Pack installed. Make sure the F5 Monitoring Service is running on the Management Server (on the RMS is best to have it disabled).

     

     

    Let me know please if this would fix the problem. I believe I've seen a similar behavior with a different customer and we're investigating to see what condition may cause to miss the import of the F5 Management Pack during upgrade.

     

     

    Thank you for the feedback!

     

    Julian
  • Hi Julian,

     

     

    The F5 Management Pack shows as installed, version 2.1.5.440.

     

     

    This does remind me of an earlier problem (last year) we had with dependencies on other management packs. We use a separate management pack for overrides called "F5 Network - Overrides". Could that be playing a part of the problem?

     

     

    Thanks,

     

    Jeff

     

  • Julian_Balog_34's avatar
    Julian_Balog_34
    Historic F5 Account
    Thanks for the quick feedback Jeff.

     

     

    Now that you mentioned the override management pack depending on the F5 Management Pack, first thought that comes to my mind is the possibility of failed F5 MP workflows that could make the Health Service eventually discard the F5 data sources. The Operations Manager event log will possibly tell us more. Can you please zip it to managementpack(at)f5(dot)com? And while we're analyzing the log, could you also temporarily remove the override pack (and re-import later), if that's an option, to see if the problem persist?

     

     

    On a side note, the post that you referred to as possibly pointing to a similar behavior ("F5 monitoring agent not stable after upgrading MP to 2.1.5.440 x64") had the SCOM Health Service crashing intermittently, with error event IDs 4000, preceded by event ID 33333 (data access error). The crash is apparently being induced by workflows run by other management packs. The F5 Management Pack workflows were exposing the problem more noticeably and within a shorter time span.

     

     

    Send us please the Operations Manager event log and we'll take it from there.

     

     

    Thank you!

     

    Julian
  • Julian,

     

     

    I just emailed the logs.

     

     

    Also, I removed the override mgmt pack but it did not help the service to run.

     

     

    Thanks

     

    Jeff