Vagrant script issue with $PATH

I had this issue with each attempt with Vagrant - can't find MUMPS. Pretty likely it's an issue with the $PATH. Even when I manually entered a path so GT.M would start, other files are unavailable, also due to path issues.

I'll look at it again in a few days, but does anyone know where the paths are set during the install?

like0

Comments

Vagrant script issue with $PATH

Nancy Anthracite's picture


Try entering env and see it it is in the environment variables.

 

Nancy Anthracite

 

On Thursday, February 22, 2018 12:25:50 AM EST David Goldstrom wrote:

I had this issue with each attempt with Vagrant - can't find MUMPS. Pretty likely it's an issue with the $PATH. Even when I manually entered a path so GT.M would start, other files are unavailable, also due to path issues.

I'll look at it again in a few days, but does anyone know where the paths are set during the install?

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

like0

Vagrant script issue with $PATH

Sam Habiel's picture

--Sam Habiel, Pharm.D.

Technical Fellow

Open Source Electronic Health Records Alliance (OSEHRA)

Cell: 206-353-1681



On Thu, Feb 22, 2018 at 5:10 AM, Nancy Anthracite <nanthracite@earthlink.net> wrote:

Try entering env and see it it is in the environment variables.

 

Nancy Anthracite

 

On Thursday, February 22, 2018 12:25:50 AM EST David Goldstrom wrote:

I had this issue with each attempt with Vagrant - can't find MUMPS. Pretty likely it's an issue with the $PATH. Even when I manually entered a path so GT.M would start, other files are unavailable, also due to path issues.

I'll look at it again in a few days, but does anyone know where the paths are set during the install?

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932




--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932



like0

Vagrant script issue with $PATH

David Goldstrom's picture


Thanks; I'm going to step through the install scripts on a fresh vagrant box and should see exactly what's going on.

Sent from

Blue

On Feb 22, 2018, at 5:11 AM, Nancy Anthracite <nanthracite@earthlink.net> wrote:

Try entering env and see it it is in the environment variables.

 

Nancy Anthracite

 

On Thursday, February 22, 2018 12:25:50 AM EST David Goldstrom wrote:

I had this issue with each attempt with Vagrant - can't find MUMPS. Pretty likely it's an issue with the $PATH. Even when I manually entered a path so GT.M would start, other files are unavailable, also due to path issues.

I'll look at it again in a few days, but does anyone know where the paths are set during the install?

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932



--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

like0

Vagrant script issue with $PATH

Nancy Anthracite's picture


I assume that you got it installed but you are looking for GT.M on the installed version. If that is not the case, then what I am saying will not apply.

 

Nancy Anthracite

 

On Thursday, February 22, 2018 8:52:03 AM EST David Goldstrom wrote:

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

Thanks; I'm going to step through the install scripts on a fresh vagrant box and should see exactly what's going on.

Sent from Blue

On Feb 22, 2018, at 5:11 AM, Nancy Anthracite <nanthracite@earthlink.net> wrote:

Try entering env and see it it is in the environment variables.

 

Nancy Anthracite

 

On Thursday, February 22, 2018 12:25:50 AM EST David Goldstrom wrote:

I had this issue with each attempt with Vagrant - can't find MUMPS. Pretty likely it's an issue with the $PATH. Even when I manually entered a path so GT.M would start, other files are unavailable, also due to path issues.

I'll look at it again in a few days, but does anyone know where the paths are set during the install?

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

like0

Hello David,

Joseph Snyder's picture

Hello David,

The environment variables are set during the run of the "createVistAInstance.sh" file during the set up process:  https://github.com/OSEHRA/VistA/blob/master/Scripts/Install/GTM/createVi... and below.  The environment files to source for the other Vagrant created users are described in that file as well:

Which user are you trying to access the vagrant VM as?

Thanks!

- Joe

like0

Vagrant script issue with $PATH

David Goldstrom's picture

Thanks, that's exactly what I was looking for. I checked $PATH as root, vagrant and as osehra. I'll dig deeper into this and let you know what I find.


Sent from my phone; please excuse my brevity.

On Feb 22, 2018, at 9:14 AM, Joseph Snyder <joe.snyder@kitware.com> wrote:

Hello David,

The environment variables are set during the run of the "createVistAInstance.sh" file during the set up process:  https://github.com/OSEHRA/VistA/blob/master/Scripts/Install/GTM/createVi... and below.  The environment files to source for the other Vagrant created users are described in that file as well:

Which user are you trying to access the vagrant VM as?

Thanks!

- Joe

--
Full post: https://www.osehra.org/post/vagrant-script-issue-path-0
Manage my subscriptions: https://www.osehra.org/mailinglist
Stop emails for this post: https://www.osehra.org/mailinglist/unsubscribe/6932

like0