I therefore disabled fetching the library otherwise the PACS would not install.
downside is that the DICOM Wado service does not start. So you need to follow instructions at
https://dcm4che.atlassian.net/wiki/display/ee2/Installation/ section “8. Mac OSX and Windows x64 specific changes for the WADO service:” and restart the dcm4chee service.
to restart dcm4chee
vagrant ssh sudo service dcm4chee restart
to check the log file for any errors
sudo less /opt/dcm4chee/dcm4chee-2.18.1-psql/server/default/log/server.log
to watch it while you send images, or use the dcm4chee ui
are you on the latest master?
seems like you run into a timeout, due to internet bandwidth
we disabled the timeout, so it should work on the latest master. please check
I know this is a trivial thing, but when I ran the current puppet-openmrs-radiologydcm4chee install, the dcm4chee instance is using mysql, so the files are in /opt/dcm4chee/dcm4chee-2.18.1-mysql/server/default/log/server.log not /opt/dcm4chee/dcm4chee-2.18.1-psql/server/default/log/server.log as described above.
Also, when making this change, the description in https://dcm4che.atlassian.net/wiki/display/ee2/Installation/ requires knowing $DCM4CHEE_HOME which is /opt/dcm4chee/dcm4chee-2.18.1-mysql/.
The first time i ran “vagrant up” in the puppet-openmrs-radiologydcm4chee as explained on github, I ran into an error saying that vagrant was a unable to foward ports, 8080, 3306 that they are been used. I am guessing this because i had a running openmrs on port 8080 and mysql on 3306 .
So i modified the ports used by vagrant in the Vagrantfile to 8089 and 3307. I ran “vagrant up” again and i had a new error (==> default: ERROR -> undefined method `[]’ for nil:NilClass). With a little googling, it was suggested that i run “vagrant plugin update”. After running “vagrant plugin update” it said that all plugins are upto date. Running “vagrant up” said vm is alreay running(but i thought it failded due to the error above).
The next steps suggested on the readme on github(that is, open, localhost:8080/openmrs, localhost:8081/dcm4chee-web3/, localhost:8081/jmx-console/). Since i modified the port 8080 to 8089 inside the vagrant file due to the first error i was experiencing, what i actually opened was “localhost:8089/openmrs” but all links gave me a server not found error.
In an effort to start affresh i ran “vagrant destroy -f” and “vagrant up” and ended up with the error here. Reading through the conversations on this thread, i realised that someone had this similiar error at some point and you advice him to run “vagrant up” again. So i ran “vagrant up” again and the out put i received was that vm is already running(which i thought had failed) but trying to open the links again still gives me server not found.
In additions to the problems mentioned above, i have the following questions
I noticed that i had to install vitual box before starting the setup, so do i need to login to this virtualbox before i can open these links (if so, then the readme needs to be updated)
Do I need to have an already running instance of openmrs at localhost:8080/openmrs or this is created during “vagrant up”. I noticed something like this in the Vagrantfile.
From what i understood, actually no OpenMRS initial instance is needed,
Vagrant up is suppose to download everything along side the tomcat, java,
mysql and do the configurations in the virtual box automatically.
yes you need to make sure the ports that are being forwarded from VM to your host are not already in use. If they are just change the port numbers in the Vagrantfile, like you did. The error you get (==> default: ERROR -> undefined method `[]’ for nil:NilClass) might be a syntax error in your Vagrantfile.
Sure if you change the ports from the Vagrantfile you need to adapt the URLs of the readme as well.
If you get a “server not found error” it seems that all the services are not running. I assume they are not properly installed. As I can see from the error message you provided in the link. It says timeout error. These are internet bandwidth issues I cant help you with. You can only try vagrant destroy -f and vagrant up a few times and hope it will finish without errors. If not I am sorry, but not much I can do. You should then do a manual installation of OpenMRS and dcm4chee. Its not that difficult and also good to learn about all the components involved in running those applications (things others using this automated setup miss out on ;)). If you do a manual install I suggest you still use vagrant. Just change the base box in the Vagrantfile to ubuntu/trusty64 and create a vagrant box once your done, before deploying the radiology module.
Regarding:
no need to open virtualbox GUI
OpenMRS is deployed for you all in the process happening after vagrant up. But of course this process needs to be successful.
After multiple unsuccessful attempts to setup environment using vagrant(and am pretty sure its not internet connection, cause lately i have been using a bundle that gives me 300KB/s), i finally decided to go with the manual installation. So i followed the link you gave on the installation guide. But its like wiki has not been updated for a while and almost all the links they provided for me to download dependencies return a 404 on oracle servers. Also some of the instructions are not valid, like for example
Copy files from JBoss to dcm4chee:
Dcm4chee consists of components that run within the JBoss application
server platform. This step will copy the JBoss runtime files to the
dcm4chee directory.
Go to the dcm4chee-2.17.1-xxx/bin directory and execute the
install_jboss.bat or install_jboss.sh script, as appropriate for your
operating system, with the path of your JBoss AS installation directory
as a parameter.
I have copied the puppetlabs-release-trusty.deb to /tmp, did “vagrant destroy -f” and “vagrant up” again (its currently running, keeping my fingers crossed ).
@teleivo now i no longer have a problems with apt.puppetlabs.com not been resolved. But i keep getting command exceeded timeout. While googling it was suggested that i can change the default timeout but i don’t know which file i have to modify to achieve this. Maybe increasing the timeout limit might fix the issue for me. Below is where i started getting problems
==> default: Notice: /Stage[main]/Tomcat/Group[tomcat]/ensure: created==> default: Error: Command exceeded timeout==>
default: Error:
/Stage[main]/Jdk_oracle/Jdk_oracle::Install[jdk_oracle]/Exec[get_jdk_installer_7]/returns:
change from notrun to 0 failed: Command exceeded timeout==>
default: Notice:
/Stage[main]/Jdk_oracle/Jdk_oracle::Install[jdk_oracle]/Exec[extract_jdk_7]:
Dependency Exec[get_jdk_installer_7] has failures: true==>
default: Warning:
/Stage[main]/Jdk_oracle/Jdk_oracle::Install[jdk_oracle]/Exec[extract_jdk_7]:
Skipping because of failed dependencies
If not please do the manual installation. You are wasting time and again it is very valuable to do the installation yourself as well. You will be a pro when troubleshooting later.
I have finished with the installation and configuration of the radiology module as instructed by the guide. I have also successfully created a vagrant box to avoid the configuration from scratch.
Right now i am going through jira issues for radiology to get my self acquainted with the code base. I will also create a thread for the project discussions.
).
