Project

General

Profile

Actions

communication #95668

closed

tsp.o.o is down

Added by cboltz almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Servers hosted in NBG
Target version:
-
Start date:
2021-07-19
Due date:
% Done:

100%

Estimated time:

Description

# systemctl status tsp.service
● tsp.service - Travel Support Program Rails application
     Loaded: loaded (/etc/systemd/system/tsp.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Mon 2021-07-19 19:59:52 UTC; 1s ago
    Process: 22625 ExecStart=/usr/bin/bundler exec puma -C /srv/www/travel-support-program/config/puma.rb ./config.ru (code=exited, status=1/FAILURE)
   Main PID: 22625 (code=exited, status=1/FAILURE)

Jul 19 19:59:51 tsp systemd[1]: tsp.service: Main process exited, code=exited, status=1/FAILURE
Jul 19 19:59:51 tsp systemd[1]: tsp.service: Failed with result 'exit-code'.
Jul 19 19:59:52 tsp systemd[1]: tsp.service: Scheduled restart job, restart counter is at 5.
Jul 19 19:59:52 tsp systemd[1]: Stopped Travel Support Program Rails application.
Jul 19 19:59:52 tsp systemd[1]: tsp.service: Start request repeated too quickly.
Jul 19 19:59:52 tsp systemd[1]: tsp.service: Failed with result 'exit-code'.
Jul 19 19:59:52 tsp systemd[1]: Failed to start Travel Support Program Rails application.

Trying to start tsp manually (with the command found in tsp.service, I get

wwwrun@tsp:~> /usr/bin/bundler exec puma -C /srv/www/travel-support-program/config/puma.rb ./config.ru
Could not locate Gemfile or .bundle/ directory
Actions #1

Updated by cboltz over 2 years ago

Just checked again - my testing was probably wrong. I guess I was in a wrong directory when testing bundler exec manually. Doing it in the right directory results in:

wwwrun@tsp:/srv/www/travel-support-program> /usr/bin/bundler exec puma -C /srv/www/travel-support-program/config/puma.rb ./config.ru
Traceback (most recent call last):
        13: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/bin/puma:23:in `<main>'
        12: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/bin/puma:23:in `load'
        11: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/bin/puma:6:in `<top (required)>'
        10: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/bin/puma:6:in `require'
         9: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/cli.rb:8:in `<top (required)>'
         8: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/cli.rb:8:in `require'
         7: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/launcher.rb:5:in `<top (required)>'
         6: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/launcher.rb:5:in `require'
         5: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/cluster.rb:3:in `<top (required)>'
         4: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/cluster.rb:3:in `require'
         3: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/runner.rb:3:in `<top (required)>'
         2: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/runner.rb:3:in `require'
         1: from /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/server.rb:15:in `<top (required)>'
/srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/server.rb:15:in `require': libssl.so.45: cannot open shared object file: No such file or directory - /srv/www/travel-support-program/vendor/bundle/ruby/2.5.0/gems/puma-4.2.1/lib/puma/puma_http11.so (LoadError)
Actions #2

Updated by cboltz over 2 years ago

  • Private changed from Yes to No
Actions #3

Updated by lrupp over 2 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Hi there - and a Happy and Healthy 2022!

I'm currently closing old tickets which did not see much change.
If the main concern still exists and should be handled, please re-open by just replying to this Email.

Thanks in advance,
Lars

Actions

Also available in: Atom PDF