Unable to login from VM!...

Unable to login from VM! please suggest me.

Hi when i am trying to enter using username: osehratied and Pw: tied, i am getting incorrect login message. I am using VM,ubuntu 12.04. 

like0

Comments

Hi there,

Joseph Snyder's picture

Hi there,

Thanks for the question.  I am assuming you're trying the instructions that are found at the following OSEHRA site: https://www.osehra.org/content/how-setup-osehra-vista-development-virtua...

After doing a little debugging, I think there are a couple of different things that could have put you into this position:

  • During setup, did you change the instance name from the default of 'osehra'?
    • The instance name is set by an environment variable named "instance" when running the 'vagrant up' command/
    • The user account will be "tied" appended to the string used for the instance.  You can check the available accounts by accessing the Vagrant VM through the vagrant command and then check the /home/ directories to see what accounts are available.
    •  A default instance would look like so and would have the user be "osehratied"
      • joe.snyder@PALAVEN ~/Work/OSEHRA/VistA/Scripts/Install/Ubuntu (master)
        $ vagrant ssh
        Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-88-virtual x86_64)
        
         * Documentation:  https://help.ubuntu.com/
        
        <SNIP>
        Last login: Fri Aug  5 14:20:37 2016 from 10.0.2.2
        vagrant@vagrant-ubuntu-precise-64:~$ cd ..
        vagrant@vagrant-ubuntu-precise-64:/home$ ls
        osehra  ubuntu  vagrant
        vagrant@vagrant-ubuntu-precise-64:/home$
    • For another instance where the instance has been modified
      • vagrant@vagrant-ubuntu-precise-64:/home$ ls
        kitwaretest  ubuntu  vagrant
        vagrant@vagrant-ubuntu-precise-64:/home$
      • You would SSH, using the same password, using the following command
        • ssh -p 2222 kitwaretesttied@localhost
  • Are you using the correct port?
    • The Vagrant system forwards the localhost port 2222 to the VM's port 22.  You need to ensure that the 2222 port is specified in the SSH command

If neither of these solve your problem, would you be able to send the following information to us:

  • The result of the "env" command in the Vagrant VM
  • The result of 'ls' in the '/home/' directory
  • the result of 'ls' in the directory within /home for the generated instance,
    • Not the 'ubuntu' or 'vagrant' directory, but one like as "/home/osehra" or "/home/kitwaretest"

 

Thanks in advance!

like0

Hi

Venkata Phani Anne's picture

i am attaching the following screen shot please check. i didn't find the osehra directory in vagrant. I think the port and everthing fine.

cool@mercy:~/Development/VistA/Scripts/Install/Ubuntu$ vagrant up
Bringing machine 'OSEHRA VistA - Ubuntu' up with 'virtualbox' provider...
==> OSEHRA VistA - Ubuntu: Clearing any previously set forwarded ports...
==> OSEHRA VistA - Ubuntu: Clearing any previously set network interfaces...
==> OSEHRA VistA - Ubuntu: Preparing network interfaces based on configuration...
    OSEHRA VistA - Ubuntu: Adapter 1: nat
==> OSEHRA VistA - Ubuntu: Forwarding ports...
    OSEHRA VistA - Ubuntu: 9430 (guest) => 9430 (host) (adapter 1)
    OSEHRA VistA - Ubuntu: 8001 (guest) => 8001 (host) (adapter 1)
    OSEHRA VistA - Ubuntu: 8080 (guest) => 8080 (host) (adapter 1)
    OSEHRA VistA - Ubuntu: 8000 (guest) => 8000 (host) (adapter 1)
    OSEHRA VistA - Ubuntu: 8081 (guest) => 8081 (host) (adapter 1)
    OSEHRA VistA - Ubuntu: 22 (guest) => 2222 (host) (adapter 1)
==> OSEHRA VistA - Ubuntu: Booting VM...
==> OSEHRA VistA - Ubuntu: Waiting for machine to boot. This may take a few minutes...
    OSEHRA VistA - Ubuntu: SSH address: 127.0.0.1:2222
    OSEHRA VistA - Ubuntu: SSH username: vagrant
    OSEHRA VistA - Ubuntu: SSH auth method: private key
==> OSEHRA VistA - Ubuntu: Machine booted and ready!
[OSEHRA VistA - Ubuntu] GuestAdditions 5.1.8 running --- OK.
==> OSEHRA VistA - Ubuntu: Checking for guest additions in VM...
==> OSEHRA VistA - Ubuntu: Mounting shared folders...
    OSEHRA VistA - Ubuntu: /vagrant => /home/cool/Development/VistA/Scripts/Install
==> OSEHRA VistA - Ubuntu: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> OSEHRA VistA - Ubuntu: flag to force provisioning. Provisioners marked to run always will still run.
cool@mercy:~/Development/VistA/Scripts/Install/Ubuntu$ ls
autoInstaller.sh          setupEC2.sh        test.cmake
bootstrapUbuntuServer.sh  setupRackspace.sh  Vagrantfile
cool@mercy:~/Development/VistA/Scripts/Install/Ubuntu$ vagrant ssh
Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 3.2.0-113-virtual x86_64)

 * Documentation:  https://help.ubuntu.com/

  System information as of Tue Nov  1 14:04:00 UTC 2016

  System load:  0.0               Processes:           68
  Usage of /:   3.0% of 39.37GB   Users logged in:     0
  Memory usage: 10%               IP address for eth0: 10.0.2.15
  Swap usage:   0%

  Graph this data and manage this system at:
    https://landscape.canonical.com/

  Get cloud support with Ubuntu Advantage Cloud Guest:
    http://www.ubuntu.com/business/services/cloud

New release '14.04.5 LTS' available.
Run 'do-release-upgrade' to upgrade to it.

 

Last login: Tue Nov  1 13:57:10 2016 from 10.0.2.2
vagrant@vagrant-ubuntu-precise-64:~$ ls
vagrant@vagrant-ubuntu-precise-64:~$ cd ..
vagrant@vagrant-ubuntu-precise-64:/home$ ls
ubuntu  vagrant
vagrant@vagrant-ubuntu-precise-64:/home$ 

 

like0

You are correct.  The port

Joseph Snyder's picture

You are correct.  The port fowarding seems to be fine and a directory where the files and scripts fo the tied user accounts reside is missing!  It seems like the provisioning went wrong somewhere along the set up. The most direct and best way to solve this issue would be to rebuild the VM via "vagrant destroy" and "vagrant up" from the host machine.  Otherwise, we can attempt to run some of the scripts to get you the files in the places you need.

Just to be thorough, as we don't know where the provisioning had a problem, these might not be able to get your system back and you may want to just rebuild.  The first question is how much needs to be redone:

  • Does the VM have a GT.M installation? 
    • This can be found by attempting to execute "mumps -dir" from the command line of the vagrant user
    • If no:
      • Run the "autoinstall.sh" file on the VM in the /vagrant/Ubuntu directory
        • sudo /vagrant/Ubuntu/autoinstall.sh
    • if yes:
      • Execute the scripts to set up the files necessary for the VistA instance and the extra users
      • First set up two environment variables
        • export instance="osehraNew"
        • export basedir = "/home/osehraNew"
      • Then execute the scrips both as sudo:
        • sudo /vagrant/GTM/createVistAInstall.sh -i <instanceName>
        • sudo /vagrant/GTM/importVistA.sh

You should be able to enter as the "osehraNewtied" user after the two scripts have run.  I hope this helps!

like0