Operational Defect Database
BugZero updated this defect 67 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
VMware | 372961
Watch4Net: Alerting on Scheduled Report fails with "Unable to transfer report to remote locations and/or Alerting managers...java.lang.Exception: Could not find the alert manager '<manager-name>'!" message in log
Last update date:
3/22/2024
Affected products:
Smart Assurance - Watch4net/M&R
Affected releases:
No affected releases provided.
Fixed releases:
No fixed releases provided.
Description:
Symptoms
Watch4net Alerting on Scheduled Report fails with the following message: java.lang.Exception: Could not find the alert manager '<manager-name>'! The following error is seen in the Watch4net log after the scheduled report fails: Unable to transfer report to remote locations and/or Alerting managers. Please check that the remote locations and/or Alerting managers are valid and accessible. Details: 130416 14:57:18 : SEVERE: Error while sending file: Databases_2013-04-16_14h57130416 14:57:18 : java.lang.Exception: Could not find the alert manager 'Local Manager'!130416 14:57:18 : SEVERE: Scheduled Report `Databases` for user `admin` could not be sent: Tuesday, April 16, 2013 2:57:18 PM IST SEVERE: Scheduled Report `remote location` for user `admin` for type `Databases` failed!130416 14:57:18 : Caused by: java.lang.Exception: Could not find the alert manager 'Local Manager'!130416 14:57:18 : SEVERE: Report generation contained errors.130416 14:57:18 : com.watch4net.apg.report.scheduling.generator.ScheduledReportGenerationException: Report generation failed with code 13 For more information please contact your APG administrator.
Cause
The name of the Alerting Manager is not consistent in the alerting-frontend.xml and report-generation-config.xml Watch4net configuration files. The following sections show an example of this mismatch. Example #1: Alerting Manager name in alerting-frontend.xml fileThe following shows in alerting-frontend.xml file configured with Alerting Manager name "Local Manager". File location:/opt/APG/Web-Servers/Tomcat/Default/conf/Catalina/localhost/alerting-frontend.xml File content:<!-- Alerting Properties --> <Resource name="manager/Local Manager" auth="Container" type="com.watch4net.alerting.jmx.AlertManagerFactory" factory="org.apache.naming.factory.BeanFactory" user="admin" pass="changeme" url="service:jmx:rmi:///jndi/rmi://localhost:52569/jmxrmi" /> Example #2: Alerting Manager name in report-generation-config.xml fileThe following shows in report-generation-config.xml file configured with Alerting Manager name "Local Manager123". File name:/opt/APG/Tools/Frontend-Report-Generator/Default/conf/report-generation-config.xml File content:<!-- Alerting Properties --> <manager name="Local Manager123" user="admin" pass="changeme" url="service:jmx:rmi:///jndi/rmi://localhost:52569/jmxrmi" />
Resolution
If you encounter this issue, do the following: Rename the entry in report-generation-config.xml so that it has the same name as that in alerting-frontend.xml. The following shows the above examples with the Alert Manager renamed to "Local Manager" in both files: /opt/APG/Web-Servers/Tomcat/Default/conf/Catalina/localhost/alerting-frontend.xml <!-- Alerting Properties --> <Resource name="manager/Local Manager" auth="Container" type="com.watch4net.alerting.jmx.AlertManagerFactory" factory="org.apache.naming.factory.BeanFactory" user="admin" pass="changeme" url="service:jmx:rmi:///jndi/rmi://localhost:52569/jmxrmi" /> /opt/APG/Tools/Frontend-Report-Generator/Default/conf/report-generation-config.xml <!-- Alerting Properties --> <manager name="Local Manager" user="admin" pass="changeme" url="service:jmx:rmi:///jndi/rmi://localhost:52569/jmxrmi" /> If the Alerting-Backend is on a separate server to the frontend, the "Resource name" entry from alerting-frontend.xml also needs to be copied into the APG.xml.Restart the task scheduler service using the following command: /opt/APG/bin/manage-modules.sh service restart task-scheduler
Related Information
See the APG-Alerting-Guide.pdf (/opt/APG/Doc) section titled "Configure alerting communication" for more information.
