Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Rails s do not work

  1. #1
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    36

    Default Rails s do not work

    I got a fix:

    Running with
    rails s -b 0.0.0.0 allows it to start.

    But something in the default setting of OpenSuse is wrong.
    Open-suse Leap 15
    Cinnamon

  2. #2
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    16,796

    Default Re: Rails s do not work

    On Tue, 01 Jan 2019 15:56:03 +0000, Asimov wrote:

    > I got a fix:
    >
    > Running with rails s -b 0.0.0.0 allows it to start.
    >
    > But something in the default setting of OpenSuse is wrong.


    It would be helpful if you included details and an error message (if
    any).

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  3. #3
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    36

    Default Re: Rails s do not work

    Quote Originally Posted by hendersj View Post
    On Tue, 01 Jan 2019 15:56:03 +0000, Asimov wrote:

    > I got a fix:
    >
    > Running with rails s -b 0.0.0.0 allows it to start.
    >
    > But something in the default setting of OpenSuse is wrong.


    It would be helpful if you included details and an error message (if
    any).

    Jim
    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
    Oops, I forgot to specified the server: Puma

    Code:
    :~/forum 2/forum> rails s
    WARNING: Nokogiri was built against LibXML version 2.9.8, but has dynamically loaded 2.9.7
    => Booting Puma
    => Rails 5.2.2 application starting in development  
    => Run `rails server -h` for more startup options
    [Simple Form] Simple Form is not configured in the application and will use the default values. Use `rails generate simple_form:inst
    all` to generate the Simple Form configuration.
    Puma starting in single mode...
    * Version 3.12.0 (ruby 2.5.0-p0), codename: Llamas in Pajamas
    * Min threads: 5, max threads: 5
    * Environment: development
    * Listening on tcp://t-bird:3000
    Exiting
    Traceback (most recent call last):
            41: from bin/rails:3:in `<main>'
            40: from bin/rails:3:in `load'
            39: from /home/sinatra/forum 2/forum/bin/spring:15:in `<top (required)>'
            38: from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:70:in `require'
            37: from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:70:in `require'
            36: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `<top (required)>'
            35: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/binstub.rb:31:in `load'
            34: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/bin/spring:49:in `<top (required)>'
            33: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/client.rb:30:in `run'
            32: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/client/command.rb:7:in `call'
            31: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `call'
            30: from /usr/lib64/ruby/gems/2.5.0/gems/spring-2.0.2/lib/spring/client/rails.rb:28:in `load'
            29: from /home/sinatra/forum 2/forum/bin/rails:9:in `<top (required)>'
            28: from /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `require'
            27: from /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:257:in `load_dependency'
            26: from /usr/lib64/ruby/gems/2.5.0/gems/activesupport-5.2.2/lib/active_support/dependencies.rb:291:in `block in require'
            25: from /usr/lib64/ruby/gems/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:29:in `requi
    re'
            24: from /usr/lib64/ruby/gems/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:20:in `requi
    re_with_bootsnap_lfi'
            23: from /usr/lib64/ruby/gems/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/loaded_features_index.rb:65:in `registe
    r'
            22: from /usr/lib64/ruby/gems/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `block
     in require_with_bootsnap_lfi'
            21: from /usr/lib64/ruby/gems/2.5.0/gems/bootsnap-1.3.2/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:21:in `requi
    re'
            20: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/commands.rb:18:in `<main>'
            19: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/command.rb:46:in `invoke'
            18: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/command/base.rb:65:in `perform'
            17: from /usr/lib64/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor.rb:387:in `dispatch'
            16: from /usr/lib64/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor/invocation.rb:126:in `invoke_command'
            15: from /usr/lib64/ruby/gems/2.5.0/gems/thor-0.20.3/lib/thor/command.rb:27:in `run'
            14: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/commands/server/server_command.rb:142:in `perform'
            13: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/commands/server/server_command.rb:142:in `tap'
            12: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/commands/server/server_command.rb:147:in `block in perform
    '
            11: from /usr/lib64/ruby/gems/2.5.0/gems/railties-5.2.2/lib/rails/commands/server/server_command.rb:53:in `start'
            10: from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.6/lib/rack/server.rb:297:in `start'
             9: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/rack/handler/puma.rb:70:in `run'
             8: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/launcher.rb:184:in `run'
             7: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/single.rb:96:in `run'
             6: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/runner.rb:151:in `load_and_bind'
             5: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:88:in `parse'
             4: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:88:in `each'
             3: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:105:in `block in parse'
             2: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:272:in `add_tcp_listener'
             1: from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:272:in `new'
    /usr/lib64/ruby/gems/2.5.0/gems/puma-3.12.0/lib/puma/binder.rb:272:in `initialize': Cannot assign requested address - bind(2) for "t
    -bird" port 3000 (Errno::EADDRNOTAVAIL)
    sinatra@t-bird:~/forum 2/forum> ^C
    sinatra@t-bird:~/forum 2/forum> 
    
    
    Open-suse Leap 15
    Cinnamon

  4. #4
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    16,796

    Default Re: Rails s do not work

    On Wed, 02 Jan 2019 16:46:03 +0000, Asimov wrote:

    > * Listening on tcp://t-bird:3000


    Can the host resolve the DNS name 't-bird'? From the log, it looks like
    it can't.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    9,810
    Blog Entries
    1

    Default Re: Rails s do not work

    Quote Originally Posted by hendersj View Post
    On Wed, 02 Jan 2019 16:46:03 +0000, Asimov wrote:

    > * Listening on tcp://t-bird:3000


    Can the host resolve the DNS name 't-bird'? From the log, it looks like
    it can't.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
    Actually,
    To me it looks like the website hasn't yet been set up receive traffic on the specific port... the website application is listening but nothing is going to arrive.

    Although I set up Ruby to do other things, whenever someone asks me about setting up Rails, I refer them to the following

    http://www.lauradhamilton.com/how-to...sions-of-ruby/

    You'll notice that although Laura sets up on a nodejs server instead, that's trivial.
    Skim down the page until you see the instructions for enabling IP forwarding and begin there.

    It looks like shes updated her guide to include installing a Ruby version manager, which I also endorse but is not required (Installing Rails using openSUSE packages won't set up a Ruby version manager).

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #6
    Join Date
    Jul 2008
    Location
    Seattle, WA
    Posts
    16,796

    Default Re: Rails s do not work

    On Thu, 03 Jan 2019 02:46:03 +0000, tsu2 wrote:

    > Actually,
    > To me it looks like the website hasn't yet been set up receive traffic
    > on the specific port... the website application is listening but nothing
    > is going to arrive.


    Rereading the log posted, I would concur. I somehow missed that t-bird
    was the hostname for the host the command was run on.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

  7. #7
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    36

    Default Re: Rails s do not work

    Quote Originally Posted by tsu2 View Post
    Actually,
    To me it looks like the website hasn't yet been set up receive traffic on the specific port... the website application is listening but nothing is going to arrive.

    Although I set up Ruby to do other things, whenever someone asks me about setting up Rails, I refer them to the following

    http://www.lauradhamilton.com/how-to...sions-of-ruby/

    You'll notice that although Laura sets up on a nodejs server instead, that's trivial.
    Skim down the page until you see the instructions for enabling IP forwarding and begin there.

    It looks like shes updated her guide to include installing a Ruby version manager, which I also endorse but is not required (Installing Rails using openSUSE packages won't set up a Ruby version manager).

    TSU
    Thank you. It's a great article. It's solved my problem with rbenv too.
    Open-suse Leap 15
    Cinnamon

  8. #8
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    9,810
    Blog Entries
    1

    Default Re: Rails s do not work

    Quote Originally Posted by Asimov View Post
    Thank you. It's a great article. It's solved my problem with rbenv too.
    If you have no reason to run rbenv in anything other than the security context of your logged in User account, the standard rbenv install should be fine.

    If you have a need to sometimes run rbenv in another User account context (even as root), then you may be interested in my Wiki article which describes how to install so that any local User account is supported.

    https://en.opensuse.org/User:Tsu2/Install_Ruby

    As always, removing or "uninstalling" rbenv and all its Pythons only involves deleting the directory tree.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  9. #9
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    36

    Default Re: Rails s do not work

    Quote Originally Posted by tsu2 View Post
    If you have no reason to run rbenv in anything other than the security context of your logged in User account, the standard rbenv install should be fine.

    If you have a need to sometimes run rbenv in another User account context (even as root), then you may be interested in my Wiki article which describes how to install so that any local User account is supported.

    https://en.opensuse.org/User:Tsu2/Install_Ruby

    As always, removing or "uninstalling" rbenv and all its Pythons only involves deleting the directory tree.

    TSU
    i am using rbenv because of i am want to make a performance test my Rails and Sinatra apps with JRuby and Truffle-Ruby
    Open-suse Leap 15
    Cinnamon

  10. #10
    Join Date
    Aug 2017
    Location
    Montréal. Canada
    Posts
    36

    Default Re: Rails s do not work

    Quote Originally Posted by hendersj View Post
    On Wed, 02 Jan 2019 16:46:03 +0000, Asimov wrote:

    > * Listening on tcp://t-bird:3000


    Can the host resolve the DNS name 't-bird'? From the log, it looks like
    it can't.

    Jim



    --
    Jim Henderson
    openSUSE Forums Administrator
    Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
    I do not know how verified that.
    Open-suse Leap 15
    Cinnamon

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •