Back to Geneos FAQ

NetProbe - RMC (Reuters Management Class) - Info and troubleshooting

The main tools for troubleshooting are the RMC recorders and the Refinitiv adsmon and adhmon.

Note

To alleviate the issue of faulty shared memory, the memory testing was made optional in GA3.0.12. Unfortunately, this created some instability. This was finally solved in GA3.0.21. Any versions in between these should be avoided if you are using the RMC-Interface plugin.

The RMC-Interface plugin reads information out of the shared memory on boxes running RTDS components like ADH, ADS, ATS, DACS, RRCP and RMON. The plugin runs an rmcTest followed by an rmcGet on success.

The ADH, ADS and ATS write to shared memory by default. DACS comes with a dacs\_trans process that will do the same for DACS. RRCP and RMON can write to shared memory using the TR RMS tools available from MyRefinitiv Customer Zone. All of these are 64 bit.

The default shared memory segments are the following:

Expand table

The way to check if the process is publishing to shared memory is to run ipcs -a from command line and check for the semaphore keys.

Read it with the RMC plugin Copied

Within the shared memory the individual variables take a certain syntax, such as stlimsrh1.1.ads.processID.

In the plugin, we would refer to this as $host.$instance.ads.processid, where the instance is taken from the sampler configuration. The host variable comes from the shell.

Check if the value is there using ITRS or TR tools Copied

The rmcRecorder is available from our downloads page; run it with the syntax ./rmcRecorder\_<os> -k <key>.

This will produce a mapping of the shared memory segment followed by updates received within the run period. A run period of approx. 5 minutes piped into a file should give you a good amount of recurring data showing that the component is running and reporting. Always use the bit version matching the writing process (such as ADS). The default is now 64 bit. If you are looking for a particular key, combine this with grep.

The adsmon or adhmon are placed by default in /opt/refinitiv/ads/bin/, /opt/refinitiv/adh/bin or /opt/rtds/ads/bin/, /opt/rtds/adh/bin. Navigating these structures, you can drill into the specific elements showing updating values all the way down to the actual variable behind it.

For other components that don’t have a mon process you can run, you can run up either adsmon or adhmon using the syntax ./adsmon -mob -key <key>. This allows you to browse the structure of the shared memory segment. You can also use the -print option to output the entire structure to a file.

Known issues Copied

• Probe crashes on startup with segmentation failure - wrong bit version; test with rmc recorder.
• Key not available - check if the semaphore key is available using ipcs -a; the shared memory might be limited in number of users allowed. This can be checked in the local rmds.cnf (default location /opt/refinitiv/SOFTWARE/globalconfig or /opt/rtds/SOFTWARE/globalconfig) then test with rmcRecorder.
• Values are truncated or individual values missing - the shared memory might be running out of physical memory. Check the size in the local rmds.cnf. It has been seen that the rmcTest will fail if the process has had a dirty restart, such as kill -9. If this is done, the shared memory will not clear out before restarting. This can be resolved by turning off the Shared Memory test in the sampler.
• Probe error message - Failed loadGatewayParameter(), which is due to the plugin not being able to resolve a setting. This is normally due to a variable being set in one of the plugin options which cannot be resolved. This can be checked with the Gateway Setup Editor and running the verify option which will report an error if a variable cannot be resolved.

Timing record Copied

One way of testing the memory without relying on the rmcTest is to use a timing record. Each component publishes a heartbeat every 5 seconds. The default variable is $host.$instance.<component>.admin.memorystats/time.