Help with VistA and CPRS on Centos 7

87 views
Skip to first unread message

Kevin

unread,
Feb 2, 2017, 10:00:04 AM2/2/17
to Hardhats
I installed OSEHRA VistA on Centos 7 from the instructions here https://www.osehra.org/content/how-setup-osehra-vista-development-virtual-machine-vm-0 but I'm having a few issues.

I can login with "ssh -p 2222 osehraprog@localhost" but I get the error below when I use "ssh -p 2222 osehratied@localhost".

%GTM-E-ZROSYNTAX, $ZROUTINES syntax error: /home/osehra/p/V6.2-000_x86_64*(/home/osehra/p) /home/osehra/s/V6.2-                                                                                                                              000_x86_64*(/home/osehra/s) /home/osehra/r/V6.2-000_x86_64*(/home/osehra/r) /home/osehra/lib/gtm/libgtmutil.so                                                                                                                               /home/osehra/lib/gtm /home/osehra/ewdjs/node_modules/nodem/src
%GTM-E-FILEPARSE, Error parsing file specification: /home/osehra/ewdjs/node_modules/nodem/src
%GTM-E-FILENOTFND, File  not found
Connection to localhost closed.



The connection attempt times out when I use CPRS from Windows 10 with the Firewall and SELinux enabled on Centos.  
I get a connection lost message while trying to connect with SELinux and the firewall disabled.
"C:\ ... \CPRSChart.exe" CCOW=disable s=192.168.1.21 p=9430
"C:\ ... \CPRSChart.exe" CCOW=disable s=192.168.1.21 p=22
"C:\ ... \CPRSChart.exe" CCOW=disable s=192.168.1.21 p=2222

I assume I'll need to allow a connection on a specific port after I determine the issue.  I can also SSH on port 22.

Can someone please offer advice on how to correct the issues?

Thanks,
Kevin

Christopher Edwards

unread,
Feb 2, 2017, 10:17:41 AM2/2/17
to hard...@googlegroups.com
Kevin:

For reasons i don't know right now the ewd portion of the installer is broken. edit the vagrantfile as follows:

 remove the "-e" on line 148 and rebuild the vagrant vm.

Christopher Edwards
cje...@gmail.com

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+unsubscribe@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Kevin

unread,
Feb 2, 2017, 10:53:35 AM2/2/17
to Hardhats
Thanks Chris,  I'll try and let you know.

Christopher Edwards
cje...@gmail.com



---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.

Kevin

unread,
Feb 2, 2017, 11:03:04 AM2/2/17
to Hardhats
This is how I installed it.  Where is the Vagrant file?  I assume I would remove an 'e' from the install file but that is a RPM.

1. Install Vagrant
   # rpm -i vagrant_1.9.1_x86_64.rpm
2. Install VirtualBox
        https://wiki.centos.org/HowTos/Virtualization/VirtualBox
        # yum install epel-release
        # cd /etc/yum.repos.d
        # wget http://download.virtualbox.org/virtualbox/rpm/rhel/virtualbox.repo
        # yum groupinstall "Development Tools"
        # yum install kernel-devel
        # yum install VirtualBox-5.1
3. Install Git
        # yum install git
4. Clone the Vista Repository
   # cd /home/kevin
   # mkdir dev
   # cd dev
   # git clone https://github.com/OSEHRA/VistA.git
5. Install Vagrant VirtualBox Guest Additions Plugin
        # cd ..
        # vagrant plugin install vagrant-vbguest
6. Provision the VistA development environment VM.
   # cd dev/VistA/Scripts/Install/Ubuntu
   # vagrant up
   # VBoxManage --5.1
   # sudo /sbin/vboxconfig
   # yum install kernel-devel-3.10.0-514.el7.x86_64
   # /sbin/vboxconfig
   # vagrant up

8. Try to login
   # ssh -p 2222 osehratied@localhost

Christopher Edwards

unread,
Feb 2, 2017, 11:05:23 AM2/2/17
to hard...@googlegroups.com

On Thu, Feb 2, 2017 at 11:03 AM, Kevin <kevint...@gmail.com> wrote:
dev/VistA/Scripts/Install/Ubuntu

The vagrant file is in this directory: dev/VistA/Scripts/Install/Ubuntu

Christopher Edwards
cje...@gmail.com

Kevin

unread,
Feb 2, 2017, 11:15:13 AM2/2/17
to Hardhats
Thanks!

David Wicksell

unread,
Feb 2, 2017, 11:24:36 AM2/2/17
to hard...@googlegroups.com
Kevin,

Could you please send me a copy of log/nodemInstall.log to <d...@linux.com>? The log directory is probably in the home directory of the vagrant install. That should have a stacktrace that I can use to figure out why Nodem didn't install during your build. Thanks.


--
David Wicksell
Fourth Watch Software LC

Kevin

unread,
Feb 2, 2017, 11:33:04 AM2/2/17
to Hardhats
Thanks David,  

I'm looking for it now.  I thought it would be here:

/opt/vagrant/embedded/gems/gems/vagrant-1.9.1

drwxr-xr-x.  2 root root     21 Feb  1 20:58 bin
-rw-r--r--.  1 root root 160614 Dec  7 15:51 CHANGELOG.md
drwxr-xr-x.  7 root root     84 Feb  1 20:58 contrib
-rw-r--r--.  1 root root    235 Dec  7 15:51 Gemfile
drwxr-xr-x.  2 root root     57 Feb  1 20:58 keys
drwxr-xr-x.  3 root root     39 Feb  1 20:58 lib
-rw-r--r--.  1 root root   1084 Dec  7 15:51 LICENSE
drwxr-xr-x. 12 root root    194 Feb  1 20:58 plugins
-rw-r--r--.  1 root root    551 Dec  7 15:51 Rakefile
-rw-r--r--.  1 root root   3334 Dec  7 15:51 README.md
-rw-r--r--.  1 root root   1499 Dec  7 15:51 RELEASE.md
drwxr-xr-x.  2 root roo/opt/vagrant/embedded/gems/gems/vagrant-1.9.1




On Thursday, February 2, 2017 at 11:24:36 AM UTC-5, DL Wicksell wrote:
Kevin,

 Could you please send me a copy of log/nodemInstall.log to <>? The log directory is probably in the home directory of the vagrant install. That should have a stacktrace that I can use to figure out why Nodem didn't install during your build. Thanks.

David Wicksell

unread,
Feb 2, 2017, 11:36:40 AM2/2/17
to hard...@googlegroups.com
I would look in /home/osehra/log/nodemInstall.log.

Kevin

unread,
Feb 2, 2017, 11:38:21 AM2/2/17
to Hardhats
Are you stating to reinstall it from the rpm file when you mention rebuild?


On Thursday, February 2, 2017 at 10:17:41 AM UTC-5, Christopher wrote:
Kevin:

For reasons i don't know right now the ewd portion of the installer is broken. edit the vagrantfile as follows:

 remove the "-e" on line 148 and rebuild the vagrant vm.

Christopher Edwards

Christopher Edwards

unread,
Feb 2, 2017, 11:38:31 AM2/2/17
to hard...@googlegroups.com

On Thu, Feb 2, 2017 at 11:36 AM, David Wicksell <dlwic...@gmail.com> wrote:
I would look in /home/osehra/log/nodemInstall.log.

Which would be on the VM itself.

Christopher Edwards
cje...@gmail.com

Christopher Edwards

unread,
Feb 2, 2017, 11:39:47 AM2/2/17
to hard...@googlegroups.com
in the dev/VistA/Scripts/Install/Ubuntu type the following commands:
vagrant destroy
vagrant up

NOTE: This will delete the created virtual machine, and rebuild it.

Christopher Edwards
cje...@gmail.com

Kevin

unread,
Feb 2, 2017, 11:43:22 AM2/2/17
to Hardhats
I dont have the file but I did find something that I will email.
find / -name "*.log"

/var/log/vbox-install.log
echo >&2;                                                       \
echo >&2 "  ERROR: Kernel configuration is invalid.";           \
echo >&2 "         include/generated/autoconf.h or include/config/auto.conf are missing.";\
echo >&2 "         Run 'make oldconfig && make prepare' on kernel src to fix it.";      \
echo >&2 ; 


/opt/vagrant/embedded/gems/extensions/x86_64-linux/2.2.0/ffi-1.9.14/mkmf.log
/opt/vagrant/embedded/gems/extensions/x86_64-linux/2.2.0/nokogiri-1.6.7.1/mkmf.log
/opt/vagrant/embedded/gems/extensions/x86_64-linux/2.2.0/unf_ext-0.0.7.2/mkmf.log
/opt/vagrant/embedded/gems/gems/erubis-2.7.0/test/data/users-guide/stderr.log
Message has been deleted

Kevin

unread,
Feb 2, 2017, 12:18:18 PM2/2/17
to Hardhats
Thanks.  It's rebuilding now.  These are some of the messages but I don't know if they are pertinent.

[OSEHRA VistA - Ubuntu] GuestAdditions versions on your host (5.1.14) and guest (4.1.44) do not match.
stdin: is not a tty
 * Stopping VirtualBox Additions
   ...done.
ERROR: Module vboxsf does not exist in /proc/modules
stdin: is not a tty

Christopher Edwards
cje...@gmail.com



---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.

Christopher Edwards

unread,
Feb 2, 2017, 12:20:22 PM2/2/17
to hard...@googlegroups.com
those are normal and should not effect the running of VistA on the VM.

Christopher Edwards
cje...@gmail.com

On Thu, Feb 2, 2017 at 12:14 PM, Kevin <kevint...@gmail.com> wrote:
Thanks.  It's rebuilding now.  These are some of the messages but I don't know if they are pertinent.

[OSEHRA VistA - Ubuntu] GuestAdditions versions on your host (5.1.14) and guest (4.1.44) do not match.
stdin: is not a tty
 * Stopping VirtualBox Additions
   ...done.
ERROR: Module vboxsf does not exist in /proc/modules
stdin: is not a tty



On Thursday, February 2, 2017 at 11:39:47 AM UTC-5, Christopher wrote:

Kevin

unread,
Feb 2, 2017, 12:57:26 PM2/2/17
to Hardhats
It worked!  Thanks.  Now I'll see if I can login with CPRS.

Thanks!


On Thursday, February 2, 2017 at 11:39:47 AM UTC-5, Christopher wrote:

Christopher Edwards
cje...@gmail.com



---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.

Kevin

unread,
Feb 2, 2017, 1:03:46 PM2/2/17
to Hardhats
Thanks again for the help!  Now I'll work on logging in with CPRS.  I bet I have an issue with the firewall and SELinux because the ports are not open.
CPRS_Error.png
Reply all
Reply to author
Forward
0 new messages