How to troubleshoot Spring Cloud Dataflow for VMware Tanzu
search cancel

How to troubleshoot Spring Cloud Dataflow for VMware Tanzu

book

Article ID: 297119

calendar_today

Updated On:

Products

Support Only for Spring

Issue/Introduction

Spring Cloud Data Flow for VMware Tanzu (SCDF) automates the deployment of SCDF and its dependent services so that developers can use Apps Manager or CF CLI to deploy their own SCDF instances. This article demonstrates how to troubleshoot problems in using service registry (eureka) instance. 


Resolution

SCDF for VMware Tanzu Architecture


Developer creates SCDF instance (dataflow server) with CF CLI or Apps Manager, then access the dataflow server via web UI or shell. There are 3 organizations or spaces getting involved.  

  • SCDF broker app name p-dataflow-<VERSION> is under system organization / p-dataflow space.
  • Service instances (dataflow servers) are under p-dataflow organization / INSTANCE_GUID space
  • After deploying streams or tasks, those apps used by streams and tasks are under your current space. 


Troubleshooting Steps

Troubleshooting Broker Issues 

When hitting problems with service instances operation like creating/deleting instance, the problem is mostly like with the broker app, please check the broker app status and logs. If it crashes, please restart and capture logs with `cf logs` command. 

$ cf t -o system -s p-dataflow
$ cf app p-dataflow-<VERSION>
$ cf logs p-dataflow-<VERSION> --recent


If broker reports any DB access error, please find its backend DB info with `cf env`. 

$ cf env p-dataflow-1.6.8
Getting env variables for app p-dataflow-1.6.8 in org system / space p-dataflow as admin...
OK

System-Provided:
{
 "VCAP_SERVICES": {
  "p.mysql": [
   {
    "binding_name": null,
    "credentials": {
     "hostname": "q-n2s0.q-g20719.bosh",
     "jdbcUrl": "jdbc:mysql://q-n2s0.q-g12345.bosh:3306/service_instance_db?user=7139b08db3824d468f805baef88c6010\u0026password=a89b1llfkxxxxxx\u0026useSSL=true\u0026requireSSL=true\u0026serverSslCert=/etc/ssl/certs/ca-certificates.crt",
     "name": "service_instance_db",
     "password": "a89b1llfkjbxom86",
     "port": 3306,
     "tls": {
      "cert": {
       "ca": ...
      }
   }
  ]
 }
}


"q-n2s0.q-g12345.bosh" in the connection string is BOSH DNS hostname, it can be DNS resolved with `dig` on any BOSH-deployed VMs in the same foundation. 

$ dig q-n2s0.q-g20719.bosh
...
;; ANSWER SECTION:
q-n2s0.q-g12345.bosh.	0	IN	A	10.193.71.152


To check data in SCDF broker DB, please login to the MySQL instance with mysql client.  

$ mysql -h 10.193.71.152 -u 7139b08db3824d468f805baef88c6010 -p
Enter password:
Welcome to the MySQL monitor.  Commands end with ; or \g.
...

mysql> show databases;
+---------------------+
| Database            |
+---------------------+
| information_schema  |
| cf_metadata         |
| mysql               |
| performance_schema  |
| service_instance_db |
| sys                 |
+---------------------+
6 rows in set (0.00 sec)

 

Troubleshooting Instances Issues 

Components of SCDF service instance is under of `p-dataflow` organization or GUID space. 

  • dataflow app
  • skipper app
  • df-messaging service instance - as message bus of dataflow stream
  • df-relational service instance - DB used by dataflow 
  • skipper-relational service instance - DB used by skipper
$ cf apps
Getting apps in org p-dataflow / space 57c3d94b-d2b9-47bd-a90f-4eec8f74dba3 as admin...
cf serOK

name       requested state   instances   memory   disk   urls
dataflow   started           1/1         2G       2G     dataflow-57c3d94b-d2b9-47bd-a90f-4eec8f74dba3.cfapps-06.haas-59.pez.pivotal.io
skipper    started           1/1         2G       2G     skipper-57c3d94b-d2b9-47bd-a90f-4eec8f74dba3.cfapps-06.haas-59.pez.pivotal.io

$ cf services
Getting services in org p-dataflow / space 57c3d94b-d2b9-47bd-a90f-4eec8f74dba3 as admin...

name                 service      plan       bound apps   last operation     broker                   upgrade available
df-messaging         p-rabbitmq   standard                create succeeded   p-rabbitmq
df-relational        p.mysql      db-small   dataflow     create succeeded   dedicated-mysql-broker   no
skipper-relational   p.mysql      db-small   skipper      create succeeded   dedicated-mysql-broker   no

If you encounter any problems with your SCDF instance, please review the dataflow and skipper app logs in above space. If you can't resolve the problem yourself, please collect those two apps logs and open a support ticket and provide the logs.