The F5 Monitoring Service Data Source Singleton Error

Hi Julain,

 

 

To clarify, the management server are using Local System.

 

 

I have recreated the Health service Store folder only as I want to use the lightest touch approach and this seems to have helped the situation as the F5MonitoringService does not stop anymore.

 

 

I was also able to run the "Show Running Rules and Monitors for this Health Service" task and I will try running this again now that the f5Monitoringservice is stable and send you the results at the managementpack(at)f5(dot)com address.

 

 

This means that we are essentially back to where we were prior to attempting the discovery of the active device in that soon after the F5 monitoring service was restarted Event ID 401 and 806 were logged in the F5 Event Log as follows:

 

 

EVENT ID 401

 

The PerformanceDataSourceConnector connection to Operations Manager Health Service host localhost was lost: Failed to write to an IPC Port: The pipe is being closed.

 

 

EVENT ID 806

 

Unable to process device [F5 Device [xxx.xxx.xxx.xxx]] statistics due to data failure: The PerformanceDataSourceConnector connection to Operations Manager Health Service host HealthService could not be established: Failed to connect to an IPC Port: The system cannot find the file specified.

 

: HealthService

 

 

 

The 806 event repeats at 1 minute intervals with only the IP address of the referenced f5 device alternating between the two nodes and aftyer a while the 401 event will re-appear and so and so.

 

 

Looking at the Health Roll-up of the F5 management Server the f5 Monitoring Service monitor is now healthy since the service remains started which leaves just the Data Source Server -F5MonitoringService and Operations Manager Connector -f5monitoringService unit monitors as still critical.

 

 

Can you please clarify what the IPC Port that the event log errors refer to is? A colleague hazarded a guess at the Inter-Process Communication service but I don't want to assume.

 

 

It may be that by some quirk we are not running this service in our environment or that it is locked-down such that the F5MonitoringService is hampered but I can't be sure. All I know is that I do not see anything named Inter-Process Communication service in the services applet on the Management server so maybe we are missing something basic there?

 

 

I'll try and forward the results of the Show running tasks as soon as I can.

 

 

Regards,

 

 

Michael