Previous Topic: Application Editor Fails to OpenNext Topic: Application Stuck Building


Application Migration Fails from Local to Remote Grid

Customer was unable to Migrate the application from their local 3.1 grid to Remote 3.7 Grid.

Description: They try to migrate application to grid 3.7 from grid 3.1, meet some issue. they created trust relational both grid successfully.

Things need to check for the problem.

  1. Check if the application is in stopped state.
  2. If not tell them to stop the application and Migrate.
  3. If still they have a problem check if they have any stuck volume on any of their nodes or controller.
  4. If any stuck volume on the nodes error will show in their log messages as follows "Jun 5 23:19:02 gwt10 applogic: [67336:error s:47]: VDS_SPS01.class.VDS_WIN0864E.boot: failed to mount volume Jun 5 23:19:01 gwt10 ctld:"
  5. If you found any stuck volume on the nodes check for 3tsrv bd list --all status and cat /proc/mdstat to list the devices which are stuck and then to clear the stuck mount follow the document for stuck volume on nodes in our Wiki.
  6. Check the vol list <app name> --all
    (root)gwt10 VDS_TFS> vol list VDS_TFS --all
    Scope Name Size(MB) Server State Filesystem Mirrored Mount State
    ---------------------------------------------------------------------------- --------
    VDS_TFS tfscontent 81921 srv2,srv1 ok ntfs08 Y in_use
    VDS_TFS VDS_WIN0864E.boot 51301 srv2,srv1 ok ntfs08 Y in_use
    

    If the volumes are in use you cannot migrate the application from Local to remote grid.

  7. If any volumes are in error state to verify do vol info VDS_TFS:VDS_WIN0864E.boot 51301 -b.
  8. I have check the logs messages on the controller to verify the problem of this migration failure "Failed to mount volume VDS_TFS.class.VDS_WIN0864E.boot - mount failed - see log for details.Failed to mount volume 'VDS_TFS:VDS_WIN0864E.boot'."
  9. And then I try to do vol manage of these volumes "vol manage VDS_TFS.class.VDS_WIN0864E.boot" but it fails to manage
    Preparing to manage volume... Failed to mount volume VDS_TFS.class.VDS_WIN0864E.boot - mount failed - see log for details.Unable to preserve disk signatures - operation aborted.Failed to manage volume 'VDS_TFS:VDS_WIN0864E.boot'.
    
  10. Also we try to mount the volume on the controller as follows but still fails.
    "3tctl mount sv VDS_TFS.class.VDS_WIN0864E.boot" 
    "Failed to mount volume VDS_TFS.class.VDS_WIN0864E.boot - mount failed - see log for details. command '3tctl "mount" "sv" "VDS_TFS.class.VDS_WIN0864E.boot"', FAILED(16128)"
    
  11. Then we have check if any stuck volume on controller in the controller logs we found as follows
    messages.1:Jun 4 09:25:24 gwt10 ctld: MT_LMC.c(565): m_mnt_create(): Server 127.0.0.1 - status 47 : Mount create request for mount 'VDS_TFS.user.tfscontent' failed messages.1:Jun 4 09:25:24 gwt10 applogic: [67336:error s:47]: VDS_TFS.user.tfscontent: failed to mount volume
    
  12. We have clear the stuck mount on the controller but still unable to migrate the application
  13. Finally we rebooted the controller after customer approval and able to migrate the application successfully.

    Please verify all these steps prior to rebooting the controller. These steps will be helpful for our future issues.