Smarts 10.1.X
There are three default accounts in the RabbitMQ installation:
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. 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
<Base-SAM-Dir>/smarts/bin/dmctl -s <SAM DOMAIN> exec dmdebug --queues --output=queues.txt
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.
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.
<Base-SAM-Dir>/SAM/bin/sm_edit conf/clientConnect.conf
*:AMQP/*:publisher:<E-1.0>948D22513AC23588FE1F3E1F85BF6B037208CF4BE61FA0A8EE0BA7307A4B9F63
*:AMQP/*:publisher:<Enter the Password Here>
<Base-SAM-Dir>/smarts/bin/dmctl -s <SAM DOMAIN> invoke SM_AMQPNotificationPublisher::SMAMQPNotificationPublisher stop