Simple Diagnostics Agent Troubleshooting

SDA Checks General

All these checks can be done once the SDA has been deployed.

Check SDA Connectivity

At the Agent Action select Ping Agent and press Go.
You should get a pop-up containing some JSON formatted information.
if there is no pop-up
- have a look at the Info Area at the top of the screen for some error messages
- if you suspect connectivity issues
  - check the connectivity in transaction SM59

Check SDA Installation

in the details pane have a look at the Installation Log Messages. If you like to update the SDA, select the host and choose update from the selection menu.
!!! Unfortunately the window won't be refreshed, you have to search again to get the current information displayed !!!

Quick checks (Unix, adapt accordingly for Windows)

clear ; \

echo '=== SHA installed? ===' ; ls -l /usr/sap/hostctrl/ ; cd /usr/sap/hostctrl/ ; \

echo '=== SLD Destination configured? ===' ; ls -l exe/slddest.cfg* exe/config.d/slddest* ; \

echo '=== SLDREG run? ===' ; ls -l work/outsidediscovery.log ; \

echo '=== SDA installed? Version? ===' ; grep version SMDAgent/default/agent/configuration/agent/default.properties ; \

echo '=== Java Symlink present? ===' ; ls -l SMDAgent/default/sapjvm ; \

echo '=== Java startable? Version? ===' ; SMDAgent/default/sapjvm/bin/java -version ; \

echo '=== SDA running? ===' ; ps -fu sapadm ; \

echo '=== SDA pid correct? ===' ; cat SMDAgent/default/agent/pid ; \

echo '=== SDA password file permissions correct? ===' ; ls -l /usr/sap/hostctrl/SMDAgent/default/configuration/agent/#/master_password ; \

echo '=== port file present? ===' ; cat SMDAgent/default/agent/port

Expected Output

=== SHA installed? ===

total 12

drwxr-x--- 3 sapadm sapsys 4096 Mar 3 13:41 SMDAgent

drwxr-x--x 6 root sapsys 4096 May 4 18:32 exe

drwxr-x--- 11 sapadm sapsys 4096 May 4 18:32 work

=== SLD Destination configured? ===

-rw-r----- 1 root root 114 Jan 24 15:57 exe/slddest.cfg

=== SLDREG run? ===

-rw------- 1 root root 1049136 May 4 18:08 work/outsidediscovery.log

=== SDA installed? Version? ===

version=1.10.0.201705041226

=== Java Symlink present? ===

lrwxrwxrwx 1 sapadm sapsys 47 May 4 16:39 SMDAgent/default/sapjvm -> /usr/sap/hostctrl/SMDAgent/default/sapjvm_8_jre

=== Java startable? Version? ===

java version "1.8.0_112"

Java(TM) SE Runtime Environment (build 8.1.028)

SAP Java Server VM (build 8.1.028 25.51-b02, Dec 14 2016 16:11:21 - 81_REL - optU - linux amd64 - 6 - bas2:282279 (mixed mode))

=== SDA running? ===

UID PID PPID C STIME TTY TIME CMD

sapadm 12082 29457 0 17:44 ? 00:00:00 /bin/sh ./go.sh

sapadm 12140 12082 2 17:44 ? 00:01:31 ../sapjvm/bin/java -server -XtraceFile=../log/vm-trace.log -XX:OnOutOfMemoryError=./oom.sh -Xmx512m -XX:+DisableExplicitGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=../heap-dump -XX:HeapDumpOnDemandPath=../heap-dump-OnDemand -XX:ThreadDumpPath=thread-dump -Declipse.ignoreApp=true -Djava.awt.headless=true -Dj

sapadm 22143 1 0 18:32 ? 00:00:01 /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D

=== SDA pid correct? ===

12140

=== SDA password file permissions correct? ===

-r-------- 1 sapadm sapsys 256 Nov 12 2017 master_password

=== port file present? ===

loopback:3005

Check SDA Configuration

in the details pane have a look at the Configuration Information
find the last configuration you are looking and check the content by clicking the link in the Status, Version column to see the content of a particular configuration message
click the link in the Error Message column to see the full text of it.
The Configuration status is:
- White if the Diagnostics Agent is not configured. This should not be happen because there is always a default configuration at installation time. If you see a white configuration status anyway, do the following check
  - Open the 'LMDB' application
  - Search the host and open it by click on 'Display' after selecting the host in the result table
  - Get the timestamp of 'Last Change by Data Supplier'
  - Open SM37
  - Find Enter in the simple job selection
    - 'Job name': SAP_LMDB_NOTIFY_LDB*
    - 'User name': FRN_BTC_LDB
    - 'Job Start Condition': enter a time around the timestamp (-/+ 1h) you found in the LMDB
  - Execute the search
  - Check of all jobs were 'Finished'
  - Otherwise find the root cause in the job log and create a ticket for SV-FRN-INF-LDB
  - It is possible to execute the installation manually by using the 'Agent Administration'
- Green means that the metrics are sent successfully from the Solution Manager to the Diagnostics Agent. The status can have two different characteristic Confirmed or up-to-date, if the status is Confirmed than the agent has the configuration versions that it has expected. If the status is up-to-date, the confirmation by metrics is still missing.
- Yellow pending: the SRSM can't send any metrics to the Diagnostics Agent but it is assumed that it will be successfully send later. For that reason the SRSM tries to send the configuration in an interval and the status is “pending”. This happens e.g. if network problems occur, the authorization fails or the agent is not available for the moment.
- Yellow Confirmation outdated means that the SRSM has sent metrics to the Diagnostics Agent but the metric version is older than expected. The SRSM tries it later again (“self-healing”). You can identify this in the configuration information, looking for the Send Count > 1.
- Red if an error occurred on Diagnostics Agent side and it cannot manage the configuration.

SDA Error Messages

Bad credentials in SM59 destination xxx

Reason: The destination that is used to create a connection between SAP Focused Run and a SDA has wrong credentials for the sapadm user of SAP Host Agent.
Solution: Adjust the credentials in the corresponding destination on the SAP Focused Run system. In case you need to reset the credentials, consult the SAP Host Agent administrator.

Connect to <hostname>: 1128 failed: NIECONN_REFUSED(-10)

Reason: On the host, there is no SAP Host Agent installed.
Solution: The solution depends on the result that is expected. If the host is
- still valid
  - start with the (re-)installation of a SAP Host Agent
- invalid
  - start the cleanup of the host. The cleanup is a complex procedure and documented in Decommissioning

Connect to <hostname>: 1128 failed: NIEHOST_UNKNOWN(-2)

Reason: The SAP Focused Run system is not able to create a connection from the SAP Focused Run system to the SDA. The network is not able to find the host.
Solution: The solution depends on the result that is expected. If the host is
- still valid
  - start with the (re-)installation of a SAP Host Agent
- invalid
  - start the cleanup of the host. The cleanup is a complex procedure and documented in Decommissioning

Connection to partner timed out after 180s

Reason: The SAP Host Agent is not able to connect to the SDA via HTTP, but the SDA process is still up and running. Usually the root cause is an issue with the SDA update process.
Solution: Stop the SDA process on the host.
- Windows
  - Start the Task Manager, find the java process and stop it.

Linux
- execute 'ps -fu sapadm' to find the running process (<pid>). Stop the process by 'kill <pid>'.

In the Agent Administration, select the host and execute the Agent Action 'PING'. This operation should restart the agent. It cannot be precluded that this results aftereffects.

Error: HTTP 404 Not Found

Reason: The SAP Host Agent is not able to create a connection to the Simple DIagnostics Agent. In the directory of the SDA a port file is missing. Usually the file will be created, when the SAP Host Agent starts the SDA for the first time. But the start of the SDA might fail if on the host, several processes of the SDA were started.

Solution: Stop all java processes of 'sapadm' user, Stop all /bin/sh ./go.sh processes of user 'sapadm'. Re-Install the SDA by executing the Mass Action "Install/Update Agent" in the Agent Management Application (Agent Admin UI).

Error in SDA Configuration

The issue can be seen, if the Agent Action "Configure Agent" ended with "Error". In this case, click on the error message link in the configuration tab. If you see the error details like:

http 500: Internal Server Error; Internal Server Error

Operation [id=00505694209A1ED7A8D674965B8A62D9] terminated with errors : 127 ()

description:Start SDA

Error: could not open `C:\Program Files\SAP\hostctrl\SMDAgent\default\sapjvm\lib\amd64\jvm.cfg'

exitcode:1

Reason: The SDA is not installed or in a corrupt state.
Solution: Re-Install the SDA by using the Agent Action "Install/Upgrade Agent". Re-trigger the "Configure Agent" action afterwards. Ensure that no old SDA process is running (otherwise kill the process) and there is enough disc space left to install and operate the SDA before re-installation will be triggered. Refer to SAP Note 2501820 - Simple Diagnostics Agents needed Disk Space.

Unable to Redeploy an SDA (Install After Manual Deletion)

It is not possible to install/update a SDA after manual deletion of the SDA on the host. The installation procedure skips the installation with the notice "SDA and JRE are already up-to-date, skip updating binaries"

Reason: During the installation procedure it is checked, if the version, that will be installed is newer then the existing one. If they are identical, the installation will be skipped to avoid unnecessary load in the system. The existing version of the SDA was recognized in the LMDB with outside discovery data upload.
Solution: The version in the LMDB must be changed so that the comparison returns a difference in the existing and the update version. Please follow the process

Start the LMDB by selecting the host in the Agent Admin UI and press "Display Host" button.
Change into the "Edit" mode.
Press the "Details" button
Select the tab "Associated Instances"
Click on "Diagnostics Agent default on ...." in the column "Associated Instance"
Select tab "Properties", press "Edit" (confirm the pop up) and scroll to the Version attribute
Change the value to something different than the current value and press "Read Only"
Close the pop up and press "Save"
Restart the update of the agent in the Agent Admin UI

DPCConsumer Could Not Push Metric Data

Reason 1: The Simple Diagnostics Agent uses an outdated HTTP-client implementation.
Solution 1: Update the Simple Diagnostics Agent to version 1.19 or higher.
Reason 2: The Solution Manager or the network is under load and processing or transmitting is delayed.
Solution 2: Set the property servlet-time-out to 120 (default 60) (time in s) in the agent's configuration file (hostctrl/SMDAgent/default/configuration/agent/[SM]/custom.properties).
Component: SV-FRN-INF-SDA

A Sync Point Is Missing in the Result from the ABAP System (Solution Manager XYZ). Check If the DPC Sync Point Functionality Is Available

Reason 1: The ST-PI version might be outdated. This can be checked at SAP Logon → System → Status ... → SAP System Data → Details.
Solution 1: To make the DPC_SYNCPOINT running, the ST-PI version must be at least 4.
Reason 2: Another reason could be a problem with time zone settings of the system. Check the TZCUSTHELP report in the statistic records in STAD. If it reads "System time zone or UTC timer is incorrect"
Solution 2: Correct the time zone settings.
Component: SV-FRN-INF-PRV or SV-FRN-INF-SDA

Additional helpful information for support:

Access right issue: Transaction ST01 → Authorization Trace for user SDAGENT (or the one that is configured) → activate → wait 5 minutes → deactivate → analyze → attach result to the case
Time zone issue: Transaction SA38 in managed system → TZCUSTHELP → Execute → enter current date and time → attach result to the case

Web Service Invocation Error Occurred on Binding Provider

Reason: The SDA does not have appropriate privileges to call WS-methods at sap control.
Solution: Add the following line to the profile DEFAULT.PFL: service/admin_users = sapadm. This is mentioned in the SAP Focused Run Expert Portal.