For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Topher_60415's avatar
Topher_60415
Icon for Nimbostratus rankNimbostratus
Jul 23, 2009

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 in...
management
microsoft
scom
joel_hendrickso's avatar
joel_hendrickso
Historic F5 Account
Jul 29, 2009
We have found the cause of this problem and put in a fix that will be in the next release, scheduled for the week of august 10th (2 weeks from now).

 

 

If a pool member with port 4444 is discovered, any state changes (such as enable/disable/up/down) to that pool member will cause the service to crash. This has to do with the way that Big-IP translates some ports when it notifies us of state updates (in this case, 4444="KRB524").

 

 

There is no workaround at this point besides restarting the service.