SM_AMQPNotificationPublisher::SM-AMQPNotificationPublisher queue is constantly growing
Smarts SAM presentation domain shows memory growth when using EDAA after changing RabbitMQ password.
Environment
VMware Smart Assurance - SMARTS
Cause
How do I change the RabbitMQ passwords There are three default accounts in the RabbitMQ installation: an admin account, an account used by the SAM publisher to deliver messages into RabbitMQ, and an account used by the ingestion process to pull messages from RabbitMQ. You can change the password for each one of these accounts.How do I change the RabbitMQ passwords There are three default accounts in the RabbitMQ installation: an admin account, an account used by the SAM publisher to deliver messages into RabbitMQ, and an account used by the ingestion process to pull messages from RabbitMQ. You can change the password for each one of these accounts.How do I change the RabbitMQ passwords There are three default accounts in the RabbitMQ installation: an admin account, an account used by the SAM publisher to deliver messages into RabbitMQ, and an account used by the ingestion process to pull messages from RabbitMQ. You can change the password for each one of these accounts.How do I change the RabbitMQ passwords There are three default accounts in the RabbitMQ installation: an admin account, an account used by the SAM publisher to deliver messages into RabbitMQ, and an account used by the ingestion process to pull messages from RabbitMQ. You can change the password for each one of these accounts.Smarts Service Assurance Manager (Smarts SAM) presentation domain maintains a queue of objects to push to the RabbitMQ process and if the publisher password is mismatched between the entry in SAM/smarts/local/conf/clientConnect.conf and the publisher password in RabbitMQ this queue will not be processed and therefore grow over time.
To check if this queue is the cause of your SAM domains memory growth run the following command and check the output for the SM-AMQPNotificationPublisher queue
An example from SAM/smarts/local/logs/queues.txt is shown below:
SM_AMQPNotificationPublisher::SM-AMQPNotificationPublisher [1 worker(s)] Current size 27966, max 27966; processed entries 1
As the Current size equals the max and processed entries is 1 this is a good indication of this scenario.
Resolution
Please ensure publisher password is consistent in both clientConnect.conf and the RabbitMQ application.
The publisher is a component in the presentation SAM domain that sends notifications into RabbitMQ. The RabbitMQ login for this process is publisher with the default password of changeme. To change this password, you must update both RabbitMQ and the SAM configuration with a new matching password.
Procedure 1. Log in to the RabbitMQ web-based management interface as admin. 2. Click the Admin tab and select publisher from the list of RabbitMQ login users. 3. Click Update this user. 4. Enter the new password in both password fields. 5. Click Update User.
6. To change the password in the SAM configuration: a. Log in to the host where the presentation SAM is installed. b. Type sm_edit conf/clientConnect.conf. c. In the clientConnect.conf file, look for a line beginning with AMQP/* It is similar to this: *:AMQP/ *:publisher:<E-1.0>94FF41842043EDA1DE6E67FB08015B3D456752865F8B5 D7DC63F259270B36092 d. In the AMQP/*" line, replace the password field with the same password that you entered for the RabbitMQ publisher account. In this example, the password was set to california: *:AMQP/*:publisher:california e. Save clientConnect.conf and exit sm_edit.
7. Restart the publisher by connecting to your presentation SAM using dmctl.
For example: a. $ dmctl -s INCHARGE-SA-PRES b. dmctl> invoke SM_AMQPNotificationPublisher::SMAMQPNotificationPublisher stop