How to troubleshoot Spring Cloud Services for VMware Tanzu 3.x management issue
search cancel

How to troubleshoot Spring Cloud Services for VMware Tanzu 3.x management issue

book

Article ID: 297209

calendar_today

Updated On:

Products

Support Only for Spring

Issue/Introduction

Architecture change has been introduced with Spring Cloud Services for VMware Tanzu (SCS) from 2.x to 3.x, this article demonstrates the changes and how to troubleshoot problems when creating, deleting, binding, and/or unbinding service instances.

Environment

Product Version: Other

Resolution

SCS for VMware Tanzu 2.x / 3.x Service Broker Changes

SCS for VMware Tanzu 2.x Broker Architecture

SCS VMware Tanzu 3.x Broker Architecture



In SCS for VMware Tanzu 3.x, the worker and VMware RabbitMQ components are removed. Both the worker and the broker are integrated into the broker, which is deployed on SCS for VMware Tanzu VM instead of on an app on the Diego cell as SCS for VMware Tanzu 1.x / 2.x. 


Troubleshooting Steps

As the broker is not an app on the diego cell anymore, broker logs can't be fetched with `cf logs`. You need to step into SCS for VMware Tanzu VM to view logs or you need to download logs via the Ops Manager web UI. 

1. ssh into SCS for VMware Tanzu VM:

bosh -d p_spring-cloud-services-b513c2ee89e9e2bc806d ssh


2. Change to the root user:

$ sudo -i


3. Confirm all jobs are running correctly:

# monit summary
The Monit daemon 5.2.5 uptime: 4d 19h 25m

Process 'scs-service-broker'        running
Process 'route_registrar'           running
Process 'galera-init'               running
Process 'mirror-service'            running
Process 'bosh-dns'                  running
Process 'bosh-dns-resolvconf'       running
Process 'bosh-dns-healthcheck'      running
System 'system_localhost'           running


4. Change to log directory and check log files - scs-service-broker stdout and stderr log:

$ sudo -i
# cd /var/vcap/sys/log/scs-service-broker
# ls -lrt
-rw------- 1 vcap vcap     0 Apr  4 19:12 scs-service-broker.stderr.log
-rw------- 1 vcap vcap  2511 Apr  4 19:13 bpm.log
-rw-r----- 1 root root     0 Apr  4 19:13 post-start.stderr.log
-rw-r----- 1 root root   142 Apr  4 19:13 post-start.stdout.log
-rw------- 1 vcap vcap 72408 Apr  9 08:27 scs-service-broker.stdout.log


5. If you can't figure out the problem, and if you can't resolve it by reviewing SCS for VMware Tanzu logs, please download those logs via Ops Manager web UI and contact VMware Tanzu Support with the logs.