Data Aggregator fails to start when webconsole is disabled

book

Article ID: 209855

calendar_today

Updated On:

Products

CA Performance Management - Usage and Administration

Issue/Introduction

Data Aggregator fails to start when webconsole is disabled in Fault Tolerant Data Aggregator Environment

Log shows it as below

 WARN  GROOVY:? - checkAMQ: Exception occured when connecting to http://localhost:8161, Connection refused (Connection refused)

 

Cause

Disabled the Active MQ Admin Console

 

https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/performance-management/20-2/upgrading/complete-the-upgrade.html#concept.dita_6398393a634b6913244e3db48ddcce1b5151fbb8_OptionalDisabletheActiveMQAdminConsolefortheDataAggregatororDataCollector

Environment

3.7.x

20.2.x

Resolution

Edit below file

DA_Install_Directory/broker/apache-activemq-version/conf/activemq.xml

Uncomment below line

<import resource="jetty.xml"/>

Before UnCommenting contents of the file

 

After UnCommenting contents of the file

service activemq stop

service activemq start

 

Additional Information

For security purposes if the access need to be restricted then we can use the below workarounds

http://DA:8161/admin

 

Workarounds:

1.Write a firewall rule to enable communication on 8161 only between Proxy, DA1 and DA2 and rest of the world should not have access.

 

2.Change the default administrative username and password of Apache ActiveMQ by editing the file apache-activemq-x.x.x/conf/jetty-realm.properties.

Update below section

# Defines users that can access the web (console, demo, etc.)

# username: password [,rolename ...]

admin: admin, admin  (Change the default admin password to restrict the access)

user: user, user

 

 

Attachments