search

WorldVistA / popHealth

popHealth - An open source clinical quality measure reporting and visualization tool. For announcements and information on current state of popHealth, please visit -
http://osehra.org/popHealth
Apache License 2.0
46 stars 45 forks source link

issue with popHealth installation #48

Open crmore0 opened 8 years ago

crmore0 commented 8 years ago

I’m pretty new in Linux development and I have installed popHealth V4.0 on an Amazon Web Sevices, AWS. I getting the message that “Web application could not be started”. Thank you for any help to solve this issue. See the error bellow:

error.zip

[Uploading error.zip…]()

Web application could not be started

An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem.

Raw process output: --> Compiling passenger_native_support.so for the current Ruby interpreter... (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable) --> Downloading precompiled passenger_native_support.so for the current Ruby interpreter... (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable) Could not download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/4.0.50/rubyext-ruby-2.1.5-x86_64-linux.tar.gz: The requested URL returned error: 404 Not Found Trying next mirror... Could not download https://s3.amazonaws.com/phusion-passenger/binaries/passenger/by_release/4.0.50/rubyext-ruby-2.1.5-x86_64-linux.tar.gz: The requested URL returned error: 403 Forbidden --> Continuing without passenger_native_support.so. /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/common.rb:67: [BUG] Segmentation fault at 0x00000000000018 ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]

-- Control frame information ----------------------------------------------- c:0041 p:---- s:0131 e:000130 CFUNC :initialize c:0040 p:---- s:0129 e:000128 CFUNC :new c:0039 p:0075 s:0126 e:000123 METHOD /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/common.rb:67 c:0038 p:0070 s:0115 e:000113 CLASS /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/ext.rb:17 c:0037 p:0011 s:0112 e:000111 CLASS /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/ext.rb:12 c:0036 p:0057 s:0110 e:000109 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/ext.rb:9 [FINISH] c:0035 p:---- s:0108 e:000107 CFUNC :require c:0034 p:0019 s:0104 e:000103 CLASS /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json.rb:58 c:0033 p:0017 s:0102 e:000101 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json.rb:54 [FINISH] c:0032 p:---- s:0100 e:000099 CFUNC :require c:0031 p:0007 s:0096 e:000095 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/activesupport-4.1.14/lib/active_support/core_ext/object/json.rb:2 [FINISH] c:0030 p:---- s:0094 e:000093 CFUNC :require c:0029 p:0071 s:0090 e:000089 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/activesupport-4.1.14/lib/active_support/core_ext/object.rb:11 [FINISH] c:0028 p:---- s:0088 e:000087 CFUNC :require c:0027 p:0015 s:0084 e:000083 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/railties-4.1.14/lib/rails/configuration.rb:2 [FINISH] c:0026 p:---- s:0082 e:000081 CFUNC :require c:0025 p:0015 s:0078 e:000077 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/railties-4.1.14/lib/rails/railtie.rb:2 [FINISH] c:0024 p:---- s:0076 e:000075 CFUNC :require c:0023 p:0007 s:0072 e:000071 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/railties-4.1.14/lib/rails/engine.rb:1 [FINISH] c:0022 p:---- s:0070 e:000069 CFUNC :require c:0021 p:0047 s:0066 e:000065 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/railties-4.1.14/lib/rails/application.rb:6 [FINISH] c:0020 p:---- s:0064 e:000063 CFUNC :require c:0019 p:0063 s:0060 e:000059 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/railties-4.1.14/lib/rails.rb:11 [FINISH] c:0018 p:---- s:0058 e:000057 CFUNC :require c:0017 p:0007 s:0054 e:000053 TOP /usr/local/rvm/gems/ruby-2.1.5/gems/actionpack-4.1.14/lib/action_controller/railtie.rb:1 [FINISH] c:0016 p:---- s:0052 e:000051 CFUNC :require c:0015 p:0026 s:0048 e:000047 TOP /home/pophealth/popHealth/config/application.rb:4 [FINISH]

lrasmus commented 8 years ago

I haven't seen this type of error before, sorry. I'm assuming you went through the install wiki... did you use a different version of the passenger gem or anything like that?

crmore0 commented 8 years ago

Hi Luke,

I’ve installed passenger v 4.0.50. I’m using an instance on Amazon Web Service(AWS). Do you think this is causing the issue?

Thank you, Carlos Moreira.

From: Luke R. [mailto:notifications@github.com] Sent: Tuesday, June 21, 2016 2:57 PM To: OSEHRA/popHealth popHealth@noreply.github.com Cc: Carlos Moreira Carlos.Moreira@thinkhts.com; Author author@noreply.github.com Subject: Re: [OSEHRA/popHealth] issue with popHealth installation (#48)

I haven't seen this type of error before, sorry. I'm assuming you went through the install wiki... did you use a different version of the passenger gem or anything like that?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/OSEHRA/popHealth/issues/48#issuecomment-227537378, or mute the threadhttps://github.com/notifications/unsubscribe/ASk2ptEQhVL7TBEzkAhVsYw8-6OrFgnks5qODPtgaJpZM4I1aJ.

lrasmus commented 8 years ago

Thanks for confirming. I don't think using AWS would cause the issue, unless you've gone through the same steps in another environment and don't see the issue. Looking around for clues, some hints I've seen are to double-check the ruby path that is being used in the apache config file, and to try clearing your gemset to pristine (if you did a lot of installing/uninstalling during the setup).

crmore0 commented 8 years ago

Hi Luke,

I completed popHealth installation on another laptop and it is working. ☺

Unfortunately when I tried to upload patients I go this message:

[cid:image001.png@01D1CE32.58DB51B0]

Please let me know if you have any input on this issue.

Thank you, Carlos Moreira

From: Luke R. [mailto:notifications@github.com] Sent: Tuesday, June 21, 2016 2:57 PM To: OSEHRA/popHealth popHealth@noreply.github.com Cc: Carlos Moreira Carlos.Moreira@thinkhts.com; Author author@noreply.github.com Subject: Re: [OSEHRA/popHealth] issue with popHealth installation (#48)

I haven't seen this type of error before, sorry. I'm assuming you went through the install wiki... did you use a different version of the passenger gem or anything like that?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/OSEHRA/popHealth/issues/48#issuecomment-227537378, or mute the threadhttps://github.com/notifications/unsubscribe/ASk2ptEQhVL7TBEzkAhVsYw8-6OrFgnks5qODPtgaJpZM4I1aJ.

lrasmus commented 8 years ago

Hi Carlos - glad it worked on the laptop! Unfortunately the image didn't come through in the github issue. Would you mind attaching the screenshot?

crmore0 commented 8 years ago

I'm sending you the message. It doesn't say much! Thank you! errormessage

lrasmus commented 8 years ago

Ohhhh, okay :) How about in the logs when the message appears?

crmore0 commented 8 years ago

Hi Luke, thank you for your help.

I'm making progress but I'm still having issues: When I try to upload the patients from "https://github.com/OSEHRA/cqmtest/raw/master/cypress2.6-OSEHRA-popHealth/patient_qrda_pophealth.zip" nothing happen. I don't receive any message on the screen and the patient count is zero. I didn't find any error on /var/log/apache2/error.log. Should I look in another place?

Thank you very much again, Carlos.

cjohnsonal commented 8 years ago

@crmore0, are you sure that the background tasks are running? In a separate process from the server, you should be actively running this: bundle exec rake jobs:work RAILS_ENV=development

crmore0 commented 8 years ago

I tried to run this command and got "Segmentation fault (core dumped)".

Thank you.

lrasmus commented 8 years ago

I haven't seen this before... any other information on the source of the segmentation fault? Which program is causing it, or a stack trace?

lrasmus commented 8 years ago

@crmore0 - any luck?

crmore0 commented 8 years ago

Hi Luke,

I could installed popHealth 4.0 - Development on my AWS server. But when I tried to install popHealth 4.0 production on AWS server it didn't work. The page responded well when I installed apache2. Then it breaks when I tried to install the passenger. Is there something I should do in the AWS server to install apache2/passenger?

This is what I got it:

"Web application could not be started An error occurred while starting up the preloader. It exited before signalling successful startup back to Phusion Passenger. Please read this article for more information about this problem. Raw process output:

--> Compiling passenger_native_support.so for the current Ruby interpreter... (set PASSENGER_COMPILE_NATIVE_SUPPORT_BINARY=0 to disable) --> Downloading precompiled passenger_native_support.so for the current Ruby interpreter... (set PASSENGER_DOWNLOAD_NATIVE_SUPPORT_BINARY=0 to disable) Could not download https://oss-binaries.phusionpassenger.com/binaries/passenger/by_release/4.0.50/rubyext-ruby-2.1.5-x86_64-linux.tar.gz: The requested URL returned error: 404 Not Found Trying next mirror... Could not download https://s3.amazonaws.com/phusion-passenger/binaries/passenger/by_release/4.0.50/rubyext-ruby-2.1.5-x86_64-linux.tar.gz: The requested URL returned error: 403 Forbidden --> Continuing without passenger_native_support.so. /usr/local/rvm/gems/ruby-2.1.5/gems/json-1.8.3/lib/json/common.rb:67: [BUG] Segmentation fault at 0x00000000000018 ruby 2.1.5p273 (2014-11-13 revision 48405) [x86_64-linux]"