VSP 360

 View Only
Back to discussions
Expand all | Collapse all

VSP 360 Common Problems Installing

  • 1.  VSP 360 Common Problems Installing

    Posted 14 hours ago
    Edited by Torsten Dutkiewicz 12 hours ago

    Hello,

    I'd like to dedicate this thread to common problems installing VSP 360. I hope the VSP 360 team jumps in to help solve them. I'll update the thread when engineering provides soluitions.

    1. Hanging at initialization for hours and days:

    VSP 360 hanging at: Initializing system services
    Request from engineering: After 1h when the initializing screen doesn't go away:
    • Please provide logs
    • On command line in the pods you can see logs:
      • kubectl get pods
      • kubectl logs <pod>

    2. After update VSP 360 1.2.0 does not start anymore

    Partner tried updating VSP 360:

    • Partner downloaded VSP 360 1.2.1.
    • Tried to update VSP 360 1.2.0
    • Update failed because of resources
    • Shutdown VM and increased CPU and RAM
    • Power ON
    • VSP 360 does not start anymore

    Partner tried to collect logs but connection was refused:

    root@crvvsplc009:/home/hv_partner# kubectl get pods
    E0408 10:19:59.823762    3372 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
    E0408 10:19:59.825345    3372 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
    E0408 10:19:59.826736    3372 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
    E0408 10:19:59.828226    3372 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
    E0408 10:19:59.829523    3372 memcache.go:265] "Unhandled Error" err="couldn't get current server API group list: Get \"http://localhost:8080/api?timeout=32s\": dial tcp 127.0.0.1:8080: connect: connection refused"
    The connection to the server localhost:8080 was refused - did you specify the right host or port?
    root@crvvsplc009:/home/hv_partner#

    After several attempts, our partner gave up and decided to revert to the VMware snapshot he'd taken before starting the update. Partner lost the onboarded storage devices in VSP 360, but Clear Sight Advanced still works and shows storage health.

    Partner gave up on VSP 360 for now, any advise would be welcome.

    3. Clear Sight Advanced can't be accessed due to Error 503 Service Temporarily Unavailable

    Customer clicked on ClearSight Advanced button. It opened a new tab and it shows "https(strikethrough)://172.16.23.91/clearsightadvanced/appui/" in the address bar and Error: "503 Service Temporarily Unavailable - nginx"

    What has been tried to fix the problem (Case Number: 05435332)

    • SSH into the VM and run the diagnostics script located at /opt/vsp360/scripts/vsp360-diag.sh, then shared the generated dump with Hitachi Support
    • Restarted VSP 360 server (no success)
    • If no storage systems have been onboarded to VSP 360 yet, perform a fresh installation of VSP 360 1.2 GA (has been tried, same result)
    • Case has been assigned to GPSD (Global Partner Support Desk). Not sure how they are supposed to be able to help.

    Storage admins are usually no experts in troubleshooting Kubernetes so the request here is to provide a solution and either add some error handling into VSP 360 itself or provide at least some troubleshooting document.

    Thank you!


    #VSP360

    ------------------------------
    Torsten Dutkiewicz
    Solution Consultant Switzerland
    Hitachi Vantara
    ------------------------------