Platform User Password Recovery Procedure

The steps below describe how to reset the VOSS Automate platform user password if you forget the password and you are not able to access the CLI via platform user.

  1. Log in to VMWare and choose the VOSS Automate Virtual Machine (VM).

  2. Right-click the VM and choose Edit Settings.

  3. Disconnect the network adapter by un-checking the Connected check box. This ensures that transactions are not lost.

  4. Click the VM Options tab, During the next boot, force entry into the BIOS setup screen check-box is checked.

  5. Click the OK button to apply the settings.

  6. Open the VOSS Automate display (Launch Virtual Machine Console).

  7. Under the Power menu option, click the reboot button (Restart Guest).

  8. In the VM console, press F10 and YES to exit the BIOS (Do not make any changes in the BIOS). The next step needs to be performed quickly before the VOSS Automate system boots.

  9. While the cursor highlights the first GRUB console entry (Ubuntu), press e. For username, enter: platform and password = boot password configured during setup.

  10. Navigate to the second to the last line which starts with linux and ends with fsck.repair=yes.

  11. Navigate to the end of the line after =yes, add a space and add init=/bin/bash.

  12. Press Ctrl-x in order to boot the system.

  13. When the system has booted, on the console at the root@(none):/# prompt, enter commands as follows:

    mount -o remount,rw /

    passwd platform

    Type in and confirm a new password. Check for the success message.

    mount -o rw /var/log

    Allow counters to be reset.

    /sbin/pam_tally2 --reset --user platform

    Reset the failed password attempt counter.

    sync

    Force a file system sync.

    exit

    Exit the console.

  14. Reconnect the VM network adapter under the Edit Settings option.

  15. Power off the VM and power on the VM again.

  16. When the system boots, choose the default highlighted GRUB entry (not recovery mode).

  17. Allow the disk checks to complete if they do run.

  18. You can now log in as platform user with the password set above.

previous

Scenario: Loss of Full Cluster in a Modular Cluster

next

‘No Space Left on Device’ Error