Overview

You may have received a memory utilization warning. For example:

PRD Swap WARNING Tue Apr 13 01:41:18 2021 13d 12:30:12 4/4 SWAP WARNING - 42% free (1674 MB out of 3999 MB) GNOC

It may be the case that Java is using a lot of memory.

Solution

The SMSM app may be using a lot of memory. The SMSM app is used only to access HLR. That is a stateless app that should not use a lot of memory. If the version used is v0.45, it may contain a memory leak. In case the current SMSM process has been running for a long time, it may be using a lot of memory.

1. Log in as root.
2. Restart the service (the expected downtime is less than 1 minute):
   

   #service mercury_smsm stop
   #service mercury_smsm start

3. Update SMSM to the latest version, testing it first in the lab environment.

Testing

1. Note the memory consumption after the SMSM service restart.
2. Check that the latest SRISM lookup was made after the service was restarted.
3. Check that the SMSM service is running #service mercury_smsm status.
4. Check that the last successful SRISM request was performed after the service was restarted:

   grep "SRISM lookup" /var/log/mercury/mdg/mdg.log | head