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. 503 Service Unavilable after upgrade (9 -> 10)

503 Service Unavilable after upgrade (9 -> 10)

Added by Ricardo Campos Passanezi over 5 years ago

I've upgraded the openproject using the https://www.openproject.org/operations/upgrading/upgrade-guide-packaged-installation and https://www.openproject.org/download-and-installation/

After I issued the sudo openproject configure I have the 503 Service Unavilable page.

In the httpd logs I can see many: Connection refused: AH00957: HTTP: attempt to connect to 127.0.0.1:6000 (127.0.0.1) failed

If I run sudo openproject run web the result is:

I, [2019-09-27T09:49:10.099729 #12714]  INFO -- : Refreshing Gem list
W, [2019-09-27T09:49:31.973673 #12714]  WARN -- : hook registered
W, [2019-09-27T09:49:39.237240 #12714]  WARN -- : Creating scope :order_by_name. Overwriting existing method Sprint.order_by_name.
E, [2019-09-27T09:50:15.910874 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
E, [2019-09-27T09:50:15.910988 #12714] ERROR -- : retrying in 0.5 seconds (4 tries left)
E, [2019-09-27T09:50:16.411912 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
E, [2019-09-27T09:50:16.412049 #12714] ERROR -- : retrying in 0.5 seconds (3 tries left)
E, [2019-09-27T09:50:16.913048 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
E, [2019-09-27T09:50:16.913132 #12714] ERROR -- : retrying in 0.5 seconds (2 tries left)
E, [2019-09-27T09:50:17.414137 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
E, [2019-09-27T09:50:17.414227 #12714] ERROR -- : retrying in 0.5 seconds (1 tries left)
E, [2019-09-27T09:50:17.915154 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
E, [2019-09-27T09:50:17.915241 #12714] ERROR -- : retrying in 0.5 seconds (0 tries left)
E, [2019-09-27T09:50:18.416261 #12714] ERROR -- : adding listener failed addr=127.0.0.1:6000 (in use)
bundler: failed to load command: unicorn (/opt/openproject/vendor/bundle/ruby/2.6.0/bin/unicorn)
Errno::EADDRINUSE: Address already in use - bind(2) for 127.0.0.1:6000
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/socket_helper.rb:164:in `bind'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/socket_helper.rb:164:in `new_tcp_server'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/socket_helper.rb:144:in `bind_listen'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:241:in `listen'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:851:in `block in bind_new_listeners!'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:851:in `each'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:851:in `bind_new_listeners!'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/lib/unicorn/http_server.rb:140:in `start'
 /opt/openproject/vendor/bundle/ruby/2.6.0/gems/unicorn-5.4.1/bin/unicorn:126:in `<top (required)>'
 /opt/openproject/vendor/bundle/ruby/2.6.0/bin/unicorn:23:in `load'
 /opt/openproject/vendor/bundle/ruby/2.6.0/bin/unicorn:23:in `<top (required)>'

If I run openproject restart the result is again:

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

After I restart the machine the behavior is the same.

Any hints?

Its a CentOS install.


Replies (2)

RE: 503 Service Unavilable after upgrade (9 -> 10) - Added by Oliver Günther over 5 years ago

There's already a server running that is blocking the port 6000. This might either be a stuck unicorn server or some other process.

You could check whether it's unicorn by running this as root: netstat -ltnp | grep :6000

And if it says unicorn, please try killing the master server with kill <PID> where PID is the output of netstat like this: <PID>/unicorn master

If not, another service uses this port.

Best,

Oliver

RE: 503 Service Unavilable after upgrade (9 -> 10) - Added by Ricardo Campos Passanezi over 5 years ago

The unicorn was running. The thing is that I've been impatient: after the reboot (ou after systemctl restart openproject) the unicorn took a while to be fully online and I've tried to browse to the portal before everything was running. By the time I issued the "run web" the unicorn was fully working thus the messages.

I've rebooted the machine and waited a bit longer (I'm not used to CentOS and systemd; mostly a FreeBSD user) and then the system worked as expected. I've increased the ammount of RAM the VM uses and it's fine now.

Thanks for the quick answer and sorry for the noise.

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