Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrated with gitlab, passenger reported can not find gems which were need by deveopment and test environment #2470

Open
coachafei opened this issue Feb 11, 2023 · 0 comments

Comments

@coachafei
Copy link

coachafei commented Feb 11, 2023

Please follow the steps below if you have found an issue with Passenger, or would like to request a feature.

Post to Stack Overflow instead if you are not sure, or if you have a question about your configuration.


Issue report

Fill in as much as possible so that we can understand, find and fix the problem.

Are you sure this is a bug in Passenger?
Please read our troubleshooting and debugging guides first:
https://www.phusionpassenger.com/library/admin/troubleshooting/
https://www.phusionpassenger.com/library/admin/

Please try with the newest version of Passenger to avoid issues that have already been fixed

Question 1: What is the problem?

  • What is the expected behavior?
  • What is the actual behavior? Passenger failed to spawn a ruby process.
  • How can we reproduce it? Please try to provide a sample application (or Virtual Machine) demonstrating the issue. Otherwise, if we can't reproduce it, we might have to ask you a number of followup questions or run certain commands to try and figure out the problem.

Be as detailed as possible in your descriptions, include any logs and stack traces (don't just cut/paste the error, provide some logging before that too).

(if you are requesting a feature instead of reporting an issue, describe here what you have in mind and how it would help you)

Your answer:

behavior

I want Passenger can correctly spawn a ruby process, but it failed. In the integration with GitLab, passenger was a replacement of puma. After nginx was started, when access the domain, nginx's error log reports like below:

Could not spawn process for application /opt/gitlab/embedded/service/gitlab-rails: The application encountered the following error: Could not find grape-swagger-1.5.0, grape-swagger-entity-0.5.1, graphql-docs-2.1.0, lefthook-1.2.6, rubocop-1.38.0, solargraph-0.47.2, letter_opener_web-2.0.0, lookbook-1.2.1, better_errors-2.9.1, sprite-factory-1.7.1, listen-3.7.1, deprecation_toolkit-1.5.1,
...
notiffany-0.1.3, shellany-0.0.1 in any of the sources (Bundler::GemNotFound)

but in gitlab-rails's Gemfile, all these missing gems was in group development and test or has an attribution require: false. Even if I explicit set environment by passenger_app_env production, it's still not work.

Reproduce

  1. Install GitLab
  2. Install passenger and nginx
  3. According to GitLab docs to change GitLab's configuration file /etc/gitlab/gitlab.rb
  4. execute gitlab-ctl reconfigure to make configuration affect.
  5. start nginx and access the website.

Question 2: Passenger version and integration mode:

  • For example: open source 5.0.26 standalone; enterprise 5.0.21/nginx

Your answer:

  • open source 6.0.17 integrated with nginx.

Question 3: OS or Linux distro, platform (including version):

  • For example: Debian 8, x86_64 or OS X 10.10 Yosemite, x86_64

Your answer:

  • CentOS 7.9 x86_64

Question 4: Passenger installation method:

Your answer:
[ ] RubyGems + Gemfile
[ ] RubyGems, no Gemfile
[ ] Phusion APT repo
[x] Phusion YUM repo
[ ] OS X Homebrew
[ ] source tarball
[ ] Other, please specify:

Question 5: Your app's programming language (including any version managers) and framework (including versions):

  • For example: Ruby 2.3.0, RVM, Rails 5.0.0; Node.js 4.0.0 with Express 4.13.4

Your answer:

  • Ruby 2.7.7 Rails 6.x

Question 6: Are you using a PaaS and/or containerization? If so which one?

  • For example: Heroku, Amazon Container Services, Docker 1.9 with an image based on passenger-docker

Your answer:

  • no

Question 7: Anything else about your setup that we should know?

Your answer:

  • no

We strive for quality and appreciate you taking the time to submit a report! Please note that if you want guaranteed response times and priority issue support we encourage you to join our enterprise customer base. They also provide us with the means to continue our high level of open source support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant