Error: "Invalid user for org Id" and "Invalid user" causes out of space issues on Transfer server storage
search cancel

Error: "Invalid user for org Id" and "Invalid user" causes out of space issues on Transfer server storage

book

Article ID: 434941

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • Out of space in Transfer directory in VMware Cloud Director
  • Transfer Session Cleaner Job is running as scheduled when checking with below:

    /opt/vmware/vcloud-director/bin/cell-management-tool cell -u administrator -p <password> -tt | grep "+--\|UUID\|Transfer"

  • In the /opt/vmware/vcloud-director/logs/vcloud-container-debug.log, the following error stack is logged:

    DEBUG    | Backend-activity-pool-#######| essionCleanerJob$TransferSessionCleanerJobActivity | [Activity Execution] Removing inactive transfer session: ########-####-####-####-############- Handle: urn:uuid:########-####-####-####-############, Current Phase: TransferSessionCleanerJob$TransferSessionCleanerJobActivity$TransferSessionCleanerJobPhase |
    ERROR    | Backend-activity-pool-#######| OrgMemberProvider              | Invalid user for org Id ########-####-####-####-############ - member type User - member Id ########-####-####-####-############ |
    ...
    ERROR    | Backend-activity-pool-#######| essionCleanerJob$TransferSessionCleanerJobActivity | [Activity Execution] Uncaught Exception during Activity execution. Recent phase: com.vmware.vcloud.vdc.TransferSessionCleanerJob$TransferSessionCleanerJobActivity$TransferSessionCleanerJobPhase@########- Handle: urn:uuid:########-####-####-####-############, Current Phase: TransferSessionCleanerJob$TransferSessionCleanerJobActivity$TransferSessionCleanerJobPhase |
    java.util.concurrent.ExecutionException: com.vmware.ssdc.library.exceptions.InvalidUserException: Invalid user.

Environment

  • VMware Cloud Director 10.5.1

Cause

This issue occurs when a stale uploaded item exists in the database which belongs to a user that does not exist anymore.

Resolution

The workaround for this issue requires modification of the Cloud Director database.

For assistance, contact Broadcom Support and note this Article ID (434941) in the problem description. For more information, see Creating and managing Broadcom support cases .

Powered by Wolken Software