Error in Sitescope’s bac_integration\discovery.log file

Business Availability Center (BAC) 8.04, SiteScope 10.11

SiteScope\bac_integration\discovery.log shows:

2010-10-01 17:14:42,610 [SiteScope Main] … UCMDB\.PROBE\.(\d+\.\d+.\d+)\.Build_(\d+) does not matches data in file c:\collectors\versions.properties

2010-10-01 17:14:42,610 [SiteScope Main] (CollectorsParameters.java:506) ERROR – Using default UCMDB.PROBE.8.0.Build_0

SiteScope and BPM installed on the same server is causing a port conflict.

If you have BPM and SiteScope installed on same machine, this creates a port conflict. BPM cannot be installed on the same machine as SiteScope.

Advertisements

SAP CCMS Monitors – Failed to Get Counters

Unable to manually add SAP CCMS Monitors for one particular SAP server instances, SiteScope shows an error: "Failed to get Counters"

This is not a SiteScope issue, is normally associated to Windows Buffer issues, this can be confirmed using SiteScope SAP DEBUG, a new log file will be created only for SAP monitors, the file name is sap_monitors.log, in this file a message like the following could be found it:

ERRNO TEXT WSAENOBUFS: No buffer space available

How to activate the SAP DEBUG

Open this file in your SiteScope server: SiteScope\conf\core\Tools\log4j\PlainJava\log4j.properties

At the end of the file, add these lines:

##################################################################################

# SAP monitors

##################################################################################

log4j.category.com.mercury.sitescope.monitors.sap=DEBUG, monitors.sap.appender

log4j.additivity.com.mercury.sitescope.monitors.sap=false

log4j.appender.monitors.sap.appender=org.apache.log4j.RollingFileAppender

log4j.appender.monitors.sap.appender.File=../${log.file.path}/sap_monitors.log

log4j.appender.monitors.sap.appender.MaxFileSize=${def.file.max.size}

log4j.appender.monitors.sap.appender.MaxBackupIndex=${def.files.backup.count}

log4j.appender.monitors.sap.appender.layout=org.apache.log4j.PatternLayout

log4j.appender.monitors.sap.appender.layout.ConversionPattern=%d [%t] (%F:%L) %-5p – %m%n

##################################################################################

Close the file and try to create the SAP monitor again.

As this is a Windows issue, we recommend review the following links:

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/wsaenobufs-no-buffer-space-available-in-saprouter-1193692

http://technet.microsoft.com/en-us/library/bb124810%28EXCHG.65%29.aspx

http://support.microsoft.com/kb/196271/en-us

SiteScope 10.12 – Technology Database Integration monitor does not work correctly

SiteScope 10.12 – Technology Database Integration monitor does not work correctly

Customer has various Technology Database Integration monitors set up (63 in total, this number will increase)

– there is only one monitor working as expected

– various other do NOT work

– all monitors query the same database with a similar query like

SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.did=’1938′ and t.tname=’brian’)

– the monitors should always return a value ( 1 row collected)

This is due to the nature of the table (view) the monitor queries. The entries are feed in from a different system and updated all two minutes, and reflect one particular status.

The monitor thus is supposed to pick up the current status, and pass it on to BAC.

trace of a working monitor:

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:67) DEBUG – going to execute query: SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.did=’1938′ and t.tname=’brian’) AND e.created > 2010-07-14 09:18:37.497 ORDER BY e.created

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:97) DEBUG – add event to the buffer

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:126) DEBUG – New enumerating field’s value is: 2010-07-14 09:18:37.497258

2010-07-14 09:31:01,362 [ALFA_brian(group.71/1) ] (DefaultDataCollector.java:129) DEBUG – 1 events created of 1 data rows

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (ObserverSource.java:81) DEBUG – update method started

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (ObserverSource.java:87) DEBUG – pushing the event {COLOR=green, TNAME=brian, DNS_NAME=ALFA, created=2010-07-14 09:18:37.497258}

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:138) DEBUG – ==>pushEvent

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:152) DEBUG – <==pushEvent execution time 0 seconds

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (JdbcMonitor.java:92) DEBUG – the monitor updated successfully collected 1 events , sent 1 events to Topaz, ignored 0 events

2010-07-14 09:31:01,799 [ALFA_brian(group.71/1) ] (Probe.java:39) DEBUG – ctor

trace of a non-working monitor:

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:67) DEBUG – going to execute query: SELECT d.dns_name, t.tname, e.color,e.created FROM devices d, present_events e, tests t WHERE (d.did=e.hostname_id and t.tid=e.testname_id and d.dns_name=’mnp.server.na.avtenti’ and t.tname=’http’) AND e.created > 2010-01-22 13:11:57.0 ORDER BY e.created

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:97) DEBUG – add event to the buffer

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:144) DEBUG – 1 events removed from the collection

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:126) DEBUG – New enumerating field’s value is: null

2010-07-14 09:31:02,143 [axalfa_conn(group.72/1) ] (DefaultDataCollector.java:129) DEBUG – 0 events created of 1 data rows

2010-07-14 09:31:02,596 [axalfa_conn(group.72/1) ] (JdbcMonitor.java:92) DEBUG – the monitor updated successfully collected 0 events , sent 0 events to Topaz, ignored 0 events

The cause is unknown at the moment:

– DB query is perfectly fine. From the DB design the data queried is just a status, feedback from another system, and updated all 2 minutes

– stopped SiteScope, deleted mg.bak and .dyn file for axalfa_conn, started SiteScope, now the new timestamp is reflected, but still nothing is returned

To fix this issue,

– all monitors run all 5 minutes, after changing this to 1 minute, the monitor starts to work as expected!

– one minute nothing is returned, as the data in the database has not been updated,

DEBUG – add event to the buffer

DEBUG – 1 events removed from the collection

DEBUG – New enumerating field’s value is: null

DEBUG – 0 events created of 1 data rows

DEBUG – the monitor updated successfully collected 0 events , sent 0 events to Topaz, ignored 0 events

in the next run (one minute later), data is retrieved and we see a trace like

DEBUG – add event to the buffer

DEBUG – New enumerating field’s value is: 2010-07-15 13:18:37.497258

DEBUG – 1 events created of 1 data rows

DEBUG – pushing the event {COLOR=green, .. , created=2010-07-15 13:16:37.497258}

DEBUG – the monitor updated successfully collected 1 events , sent 1 events to Topaz, ignored 0 events

– tried with 5 minutes again, then the monitor doesn’t work anymore, same for 2,3,4 minutes, or 110 seconds

only 1 minute works

Change all monitors to execute every 1 minute.

SiteScope 11.x New Available Monitors

SiteScope 11.x introduces several new monitor types. Where can information be found on these new monitors?

New monitors in SiteScope 11.x are: Amazon Elastic Compute Cloud (EC2), HP Integrated Lights-Out (iLO), and Microsoft Hyper-V.

Documentation for each monitor can be found in the <SS>\sisdocs\pdfs\SiteScopeMonitorReference.pdf file:

Amazon Web Services Monitor: Chapter 2, Page 29

HP ILO (Integrated Lights-Out) Monitor: Chapter 25, Page 193

Microsoft Hyper-V Monitor: Chapter 42, Page 313