Skip to end of metadata
Go to start of metadata


Purpose

   

This documenation provides some intructions, how to start troubleshooting in case you face some issues with SAP Cloud Connector (SCC).

For what they are useful

  

Logs and Traces are useful to find out specific information based on which you can troubleshoot connection problems. See more in SAP Help: Troubleshooting.

Where to find relevant logs and traces

 

  • SAP Cloud Connector User Interface (SCC UI)

  1. You can open relevant logs directly in SCC UI:

    Open SCC UI (https://localhost:8443) → choose "Log And Trace Files" → open e.g. ljs_trace.log by clicking to the glasses button:
     


      

  2. You can download relevant logs one by one or alltogether from SCC UI:

    You can download them based on your requirements by clicking the arrow buttons:



  • Filesystem

You can find logs and traces in your Operation System's file system where the SCC is installed:

  1. Windows → Default path is "c:\SAP\scc20\log".

  2. Linux → Default path is "/opt/sap/scc/log".

Short description of all log and trace files

 

The following KBA gives a short description of all log and trace files: 2452568 - Log and Trace files for SAP Cloud Connector.

How to point to the relevant log entries


  • Example Scenario for ljs_trace.log

  1. In Europe (Rot) datacenter (UTC timezone) the following error can be experienced on 23.08.2018. at around 04:15 a.m while calling backend system form an SAP Cloud Platform (SCP) destination via SCC:

    Failure reason: "Backend status could not be determined"
        

       

  2. Search for the timestamp in ljs_trace.log. You need to take into account the timezones since SCP and SCC might be in different timezone. To interpret it see the KBA: 2601369 - How to interpret timezone of SCC.

  3. Knowing this the following error can be found in ljs_trace.log based on the timestamp and timezone comparison:
       

    ljs_trace.log
    2018-08-23 09:45:18,850 +0530#ERROR#com.sap.core.connectivity.tunnel.client.notification.NotificationClient#notificationclient-13-1#          #Unable to establish notification service connection to server connectivitynotification.ap1.hana.ondemand.com/157.133.97.47:443
    java.net.ConnectException: Connection timed out: no further information: connectivitynotification.ap1.hana.ondemand.com/157.133.97.47:443
    	at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
    	at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
    	at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:224)
    	at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:289)
    	at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:545)
    	at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:485)
    	at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:399)
    	at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:371)
    	at io.netty.util.concurrent.SingleThreadEventExecutor$2.run(SingleThreadEventExecutor.java:112)
    	at io.netty.util.concurrent.DefaultThreadFactory$DefaultRunnableDecorator.run(DefaultThreadFactory.java:137)
    	at java.lang.Thread.run(Thread.java:745)|

         

  4. However, not the same information is displayed in client (SCP) side and the ljs_trace, these entries can be relevant since "Connection Timeout" means that no response arrived back from the backend to the client. Therefore "Backend status could not be determined" message is valid here.

  • Example Scenario for traffic_trace

  1. Turn on Payload Trace:

       

    In SCC UI go to "Log And trace Files" → Click on the Pencil button → check Payload Trace -> Save:
     

      

  2. Reproduce the issue.

  3.  After that under "Log And Trace Files", find and open the generated Payload Trace. It will be with name format: "traffic_trace_<account id>_on_<landscapehost>.trc".

  4. Based on the virtual hostname, thread ID (in this case 0x9e972b26) and timestamp (converted to the appropriate timezone) the relevant request and response can be found:

    traffic_trace_<account>_on_hana.ondemand.com.trc
    [...]
    <<< Request data
    >>> 2018-05-16 14:11:38,608 +0000 >>> Request data for connection 0x9e972b26 in thread tunnel-client-6-1
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |GET /sap/opu/odata/sap/ZUNITY_MA| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |INTAIN_CUSTOMER_BP_SRV_02/ HTTP/| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |1.1..maxdataserviceversion: 2.0.| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |.x-csrf-token: OmlB8E-vVPPVmLARO| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |fFJdA==, Fetch..accept-language:|
    [...]
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |100..Host: <hostname>:<port>..|
    [...]
    traffic_trace_<account>_on_hana.ondemand.com.trc
    [...]
    <<< Response data
    >>> 2018-05-16 14:11:47,125 +0000 >>> Request data for connection 0x9e972b26 in thread tunnel-client-6-1
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |HTTP/1.1 200 OK..content-type: a| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |pplication/json; charset=utf-8..| 
    0XXXXX | 3XXXXXXX 0XXXXXXX 7XXXXXXX 6XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX |content-length: 239..dataservice|
    [...]
    0XXXXX | 0XXXXXXX 7XXXXXXX 7XXXXXXX 7XXXXXXX 7XXXXXXX 6XXXXXXX 3XXXXXXX 0XXXXXXX |..Host: <hostname>:<port>..|
    [...]


    The whole process took almost 10 seconds in this example case. HTTP response 200 OK shows successful response. This trace is useful to check long running request. In order to find out which component causes the performance problem during the connectivity flow you can refer to the KBA: 2693691 - How to evaluate Cloud Connector Monitor.

Increase the Log Level

 

Sometimes you need to increase the log severity or trigger some special traces in case more information is needed to isolate and analyze the scenario. Use this Debug option only for the time wile you reproduce the issue because high log severity can fill up your system and cause performance problems.

 

  • CPIC Trace

    This trace is ideal to analyse e.g. Secure Network Communications (SNC) related problems. You can activate it in SCC UI choose "Log And trace Files" →  Click on the Pencil button → set the desired trace level (Level 3 trace shows the most detailed inforamtion):



    See an example trace entry:

    CPIC Trace
    [Thr 140086161061632] TIME Wed Jan 24 16:06:53 2018
    [Thr 140086161061632] RELEASE 749
    [Thr 140086161061632] COMPONENT SNC (Secure Network Communication)
    [Thr 140086161061632] VERSION 6
    [Thr 140086161061632] RC -4
    [Thr 140086161061632] MODULE /bas/749_REL/src/krn/snc/sncxxall.c
    [Thr 140086161061632] LINE 3604
    [Thr 140086161061632] DETAIL SncPEstablishContext
    [Thr 140086161061632] SYSTEM CALL gss_init_sec_context
    [Thr 140086161061632] COUNTER 6
    [Thr 140086161061632]
    [Thr 140086161061632] *** ERROR => STISEND:STISncOut failed 20 [r3cpic.c 10473]

        

  • Debug ljs_trace.log

    It can happen that you need more detailed traces to find out the root cause of any connection issues. In this case you need to increase the level of "Cloud Connector Loggers" and "Other Loggers" ("All" is the highest severity):



    See an example trace entry:

    debugged ljs_trace.log
    2018-05-12 14:10:56,155 +0000#DEBUG#com.sap.core.connectivity.protocol.http.HttpProtocolProcessor#tunnel-client-14-2#0xa75a59ce#Opening connection to backend system <virtual host name>:<port>|
    2018-05-12 14:10:56,155 +0000#DEBUG#com.sap.core.connectivity.spi.processing.AbstractProtocolProcessor#tunnel-client-14-2#0xa75a59ce#Mapping for host <virtual host name>:<port> not found|

         

  • SSL Trace

    This trace can be trigger by adding a JVM parameter and useful to investigate e.g. SSL certificate or mismatching cipher suite related problems. For more how to activate SSL Trace, see the following wiki: How to enable SSL trace in SAP Cloud Connector. See an example trace entry:

    SSL trace
    [...]
    2018-05-23 09:51:04,365 -0400#INFO#System.out#notification-client-7-1# #description = certificate_unknown|
    [...]

        

  • Thread Dump

    For more how to trigger thread dump in SCC, see the KBA: 2560025 - How to trigger thread dumps on Cloud Platform Cloud Connector.

Audit log

 

For more information regarding Audit Log, see the SAP Help:

Audit Logging

 

  • No labels