Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. Passenger is killing my server

Passenger is killing my server

Added by Don Sefer about 10 years ago

hi,

I have a big problem with Passenger. I am running a vserver with 1gig ram and 1gig burst, some kind of cpu :)
I installed via my following guide here: https://community.openproject.org/topics/4192

I am limited to 128 numprocs (processes/threats) and everytime I access OpenProject or doing some task like trying to synchronize with taskconnector, its overkilling my server.

There will be several “Passenger RubyApp: /openproject”, AppPreloader, PassengerAgent Server and other tasks/threats. Way too much I think.
Is it possible to limit this somehow? It is a single user trying to load the site and thats enough for the server :-(


Replies (3)

RE: Passenger is killing my server - Added by Jonas Heinrich (Finn) about 10 years ago

Hi Don,

what could work is if you limit the pool size, i.e. set PassengerMaxPoolSize to 1 or 2 in apache2.conf. Hopefully, I will find more time tomorrow to test this.

What is the number of your processes (ps aux | wc -l)?

Best,

Jonas

RE: Passenger is killing my server - Added by Jonas Heinrich (Finn) about 10 years ago

Hi Don,

on an ubuntu system I had the following numbers of processes:

  • directly after restart of apache: 91
  • with no pool size set, after one request: 98
  • with pool size = 2, after one request: 94
  • with pool size = 1, after one request: 93 (shortly 94)

So I think limiting this setting is the only thing to decrease the number of processes. But there is only a small change. If that is not enough we would have to look at the concurrency settings of apache itself.

By the way, I think I was wrong before. The setting should not go into apache.conf but much rather in mods-available/passenger.conf like this

<IfModule mod_passenger.c>
  PassengerMaxPoolSize 1
  PassengerRoot /home/vagrant/.rbenv/versions/2.1.5/lib/ruby/gems/2.1.0/gems/passenger-5.0.4
  PassengerDefaultRuby /home/vagrant/.rbenv/versions/2.1.5/bin/ruby
  RailsEnv development
</IfModule>

Best,

Jonas

RE: Passenger is killing my server - Added by Don Sefer about 10 years ago

Hi,
htop says:
tasks: 32
threads: 68
ps aux: 38

One user access:
ps aux: 39
tasks: 35
threads: 81

I am using nginx, not apache. So unfortunately this conf won’t help me :(

When accessing timeline, the first time everything is alright. second time memory overload and nothing works anymore…

Guess I have to change servers ASAP… Only problem is I need a full backup for this.

  • (1 - 3/3)
Loading...